Basically, we use a VPS that runs CentOS 4.7, in which Python 2.3 came preinstalled. We've been on a tight schedule and therefore haven't updated Python yet. I probably would've been better off upgrading Python though than working with this bug ...
We're switching hosts within the next weeks as well, so soon enough we'll be on 2.6 (sweet relief). I don't really see the point in supporting 2.3 with Django much longer, it seems as ancient as supporting IE5.5. Alex On Dec 4, 12:55 am, "Karen Tracey" <[EMAIL PROTECTED]> wrote: > Glad to help. Out of curiosity, where are you deploying that your > production server has only Python 2.3? There's been a conversation over on > the developer's list about when to drop support for Python 2.3 in Django, > and the general feeling seems to be that 2.3 ought to be getting pretty > rarely seen nowadays. I'm wondering if you still see needing to run on > Python 2.3 in 3 months time, 6 months time, etc.? > > Karen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
