On Thu, Oct 8, 2009 at 12:08 PM, Ian Bicking <[email protected]> wrote: > Correct; I have in the past basically flattened things for appengine. > Unfortunately that doesn't work well with paster create -t pylons. It might > however be more productive to have an appengine template, since you already > know what the models will have to look like, you can skip setup.py etc., and > generally make a tighter setup.
That's worth considering. However, most of the differences are in the relationship of the Pylons application to the virtualenv, not in the application itself. That would be too much for "paster create". However, we could experiment with creating an application directory with app.yaml and without setup.py, and see if it's feasable. When the template is finished it can be distributed as a PyPI package. -- Mike Orr <[email protected]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
