Hello, I'm not actually interested in wrapping Pylons, but I'll sure keep a look on your huge list of samples, when I'm out of deadlines!
On 31 Mar, 06:13, Graham Higgins <[email protected]> wrote: > It's an extensive set of templates, quite a lot of them require > additional modules but because I've not yet figured out how to > dynamically trigger prompts to install optional modules on a per- > template basis, there are a couple of places where running the > generated project will initially fail because a couple of modules need > to be easy_installed I wouldn't trigger automatic installation of packages, and absolutely I wouldn't make Shabti depend on any possible package; what I'd do is adding the custom list of requirements to the newly created project (in its setup.py): then the developer is left free to run "setup.py develop" to install additional stuff. I'm telling this, because it's the way I secretly wish Pylons to deal with its deps -- Mako, for instance, shouldn't be installed if your project uses something else. In the hope it's of some help: your paster templates are not installed with Shabti, then you cannot create projects if you easy_installed it: you could add a MANIFEST.in with "recursive-include shabti/templates *" as Pylons does; ez_setup.py is not present in your tar on Pypi, and setup.py relies on it; sqlalchemy_elixir_validations has no ez_setup.py either, and its setup.py fails: I recommend you to report the issue to its authors, since Shabti depends on it. Cheers. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
