It's complicated to explain, but basically, anything that goes onto our systems must be approved and only certain versions of Python are approved for use/development (2.4 and possibly earlier ones, but I'm not sure). We haven't yet chosen a framework to use for development and it would be easier to get something approved if it was developed against version(s) of Python already approved for our systems.
On Jul 5, 11:19 am, "James Bennett" <[EMAIL PROTECTED]> wrote: > On 7/5/07, anna <[EMAIL PROTECTED]> wrote: > > > Just in case anyone knows, is it the same with the other frameworks > > for Python, like Pylons, Turbogears, etc? I'm thinking yes, based on > > your answers here, but just wondering. > > In the Python world, developing "against" a single specific version of > the language tends to be frowned upon; there's quite a lot of code out > there which runs compatibly on versions of Python from 1.5 through > 2.5, and comparatively very little which is tied to a single specific > version of Python. Web framworks that I've seen tend to be upwards > compatible from 2.3 or 2.4, while in general a lot of Python software > aims for compatibility from 2.2 or 2.4, depending on what features > they need. > > Is there a reason why you were hoping Django would somehow "favor" a > single specific version? > > -- > "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
