> Sorry to be contrary, but I think this statement is somewhat > incorrect. A typical Pylons-based projects--created via `paster > create`--makes use of certain packages/libraries (by default), but > Pylons itself doesn't necessarily depend on those packages--*your My scenario looks as follow: I've tried to move some service based on Pylons 0.9.7 (created using paster in 2009) to the new server a few months ago. I've installed fresh copy of Python and new Pylons instance from the scratch (using easy_install -U "Pylons==0.9.7"). After copy of application on destination environment a lot of errors were thrown related to Routes (used by WebHelpers). AFAIK comparing both instances I've noticed that two components were changed: WebHelpers and Routes. I didn't remember revision number, maybe it was beta? After back to the previous version of these components (0.6.4 and 1.10.3 respectively) everything is ok.
> that the dependency should be *removed* from Pylons itself (i.e., from I agree with you. But according to information from requires.txt file these components are required: Routes>=1.10.3 WebHelpers>=0.6.4 Maybe Pylons should be provided as a standalone package with all required libraries included (bateries included LOL :) ) with proper versions? Every change in external library will cause update Pylons version postfix or something like that? -- Thanks, Artur -- 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.
