On 9/21/2010 5:29 AM Ant said...
Is there a solution to this that anyone knows of? Has Zed jumped to conclusions? Have I?
I'd say the error was in selecting something other that the lowest common subset of python functions when designing and writing a python version dependent Mongrel2. There are certainly ways (and perhaps compatibility libraries as well) to write python at a 2.4 (or 2.2) level to sidestep installation issues related to python versions. Targeting a wide range of installation platforms without taking that into account is the problem. When you issue a 2.5 dependent version and find it easier to convert it all to C rather than write the (relatively minor) python fixes, it speaks to the level of python competency as well.
What if I wrote a 64bit app and complained that in 32bit environments it didn't do the right thing?
Emile -- http://mail.python.org/mailman/listinfo/python-list
