On 7/5/07, anna <[EMAIL PROTECTED]> wrote: > > On Jul 5, 11:19 am, "James Bennett" <[EMAIL PROTECTED]> wrote: > > > > 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? > > 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.
Django is made to work with Python 2.3 *and later*, as stated earlier in this thread. If your organization uses Python 2.4, you won't have a problem. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
