>> Shouldn't this procedure be rewritten to use pkg_resources? > > There are a number of other things that have to be changed to make > Pylons apps run as zipped eggs.
Indeed, in the meantime I discovered it :-( I improved find_controllers to face this issue, but then took a look at load_environment and surrendered. > I think the biggest concerns with doing so are the potential lack of > support with third party libraries. Especially templating systems, > which everyone relies on one of. In the good old times when I used perl with Template::Toolkit, I got used to the idea of template provider plugins (plugged in object which provides template code for given paths). Doesn't seem impossible to implement and could be useful (apart from pkg_resources, this is also some way to serve templates from database or from remote site), but of course this is some work... > Also for cases where performance is a concern, you wouldn't want > something like paste's FileApp retrieving file data from a zip for > every request. It could avoid rereading from the zip when responding > with 304 not modified, but even with that, that's still a lot of > unzipping. Depends. Depending on the filesystem, reading from zip need not be worse than reading from fs, especially if there are plenty of small files in one directory... And of course nobody is forced to use compressed zips. Serving app out of egg would make it a bit less tedious to install and maintain it... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
