No worries, Python 2.6 will be actively supported for many, many years to come and the differences between 2.6 and 3 are not that huge. You can program for 2.6 while keeping in mind the code will be ported to 3 one day. It'll make a shift a breeze.
2B On Aug 5, 10:47 pm, snfctech <tschm...@sacfoodcoop.com> wrote: > Hello. > > We are researching technologies to begin what may become a pretty > large intranet Dashboard project. > > I'm a PHP developer, so the fact that Django uses Python doesn't give > me a head-start - but I've been wanting to consider it, because I am > interested in learning Python. > > However, I'm nervous about the Python 3 situation. What if I start > building a large project based on Django/Python 2.6, and then a year > or two down the road the project starts limping because of all of the > cool new Python 3 modules coming out? And I've got a bunch of Django/ > Python 2.6 code that needs to be ported? > > Any tips would be greatly appreciated. Thanks. > > Tony --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
