On 7/5/07, anna <[EMAIL PROTECTED]> wrote: > 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.
Then you have no problems here; Django will work on Python 2.4. In a larger sense, it seems like you're confused about the Python language; different versions of Python generally have good compatibility with each other, which means that you don't have to rewrite or recompile (in fact, you never "compile" Python code) when moving between supported versions (e.g., you could "upgrade" or "downgrade" your Python version without needing to change anything). This is why we say Django is not developed "against" any single version of Python -- because Python does a good job of maintaining compatibility between versions, Django can run on any of Python 2.3, 2.4 or 2.5 without modification (and again, the Django test suite verifies this). -- "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 django-developers@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
