Re: migrating to Pylons 0.9.6rc1
Just wanted to report my experience with 0.9.6rc1 while migrating my
app to it.
Another problem is that I can't use nose-0.10 alpha releases with
Pylons, since I got:
VersionConflict: (nose 0.10.0a2 (/usr/lib/python2.5/site-packages/
nose-0.10.0a2-py2.5.egg), Requirement.parse('nose=0.9.2,=0.9.9'))
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
pylons-discuss group.
To post to this group, send email to pylons-discuss@googlegroups.com
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
-~--~~~~--~~--~--~---
Re: migrating to Pylons 0.9.6rc1
On Jul 21, 2007, at 11:03 PM, Max Ischenko wrote:
Another problem is that I can't use nose-0.10 alpha releases with
Pylons, since I got:
VersionConflict: (nose 0.10.0a2 (/usr/lib/python2.5/site-packages/
nose-0.10.0a2-py2.5.egg), Requirement.parse('nose=0.9.2,=0.9.9'))
For reasons I'm not entirely sure about, the Pylons tests themselves
do not work under nose 0.10.0a2. And I'm weary of trying to hack
something together to work with an alpha version. Ideally Pylons
could just have a requirement to use the latest *release* of a
package, that wouldn't pick up beta/alpha stuff. Until we work out
the nose issues though, I've had to peg nose down to the last 0.9.x
release.
Cheers,
Ben
smime.p7s
Description: S/MIME cryptographic signature
migrating to Pylons 0.9.6rc1
Hello, Just wanted to report my experience with 0.9.6rc1 while migrating my app to it. Most time consuming part was manual diff/merge procedure, since I made _a lot_ of changes to framework-generated files and they do change a lot as well. Migrating to SAContext was a breeze, I was able to through out my custom code that did roughly the same. One note. While starting the app I see /usr/lib/python2.5/site-packages/PasteDeploy-1.3-py2.5.egg/paste/ deploy/util/fixtypeerror.py:57: DeprecationWarning: The attribute 'config.paths' has moved to the pylons.config dictionary: Please access it via pylons.config['pylons.paths'] Is it my fault or PasteDeploy not being updated? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com 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 -~--~~~~--~~--~--~---
