News for hackers. Stuff that matters.
Re:Writing Python 2.x forward compatible to Python 3 code by viraptor on Saturday January 22, 2011 @12:03PM (#2130623)
> For new projects, start with Python 2.6 or 2.7

Unless you want your project used on debian stable, that is... In which case your exception handlers will be simply not compatible between versions.

Re:Writing Python 2.x forward compatible to Python 3 code by mariana on Saturday January 22, 2011 @12:28PM (#2130667)
The next release of Debian stable will have Python 2.6 as default and it is expected for the first weekend of February, so it is safe to start with Python 2.6 right now.
Re:Writing Python 2.x forward compatible to Python 3 code by viraptor on Saturday January 22, 2011 @01:34PM (#2130764)
True. However keep in mind who uses debian stable... people who won't jump on squeeze the moment it gets stable. It will still take months before the situation really changes. But yeah - I agree that 2.6 is pretty much safe for new stuff.
Re:Writing Python 2.x forward compatible to Python 3 code by ubernostrum on Saturday January 22, 2011 @04:29PM (#2131120)
People who use Debian stable also aren't going to use your new library anyway. They're not running stable because they want to install a bunch of recent stuff, after all...
Re:Writing Python 2.x forward compatible to Python 3 code by viraptor on Saturday January 22, 2011 @04:53PM (#2131170)
Why wouldn't they? I had to choose which version to target when writing some software lately. The production was debian stable yet I wanted to release the project for others. In the end I have to keep 2 branches - one for 2.X and another for 3.X - it was a trivial piece of code, so it's not a big problem, but I can imagine how silly it must be for bigger projects.
Re:Writing Python 2.x forward compatible to Python 3 code by cdavid on Saturday January 22, 2011 @08:10PM (#2131514)
The rationale for supporting python < 2.6 goes much further than debian stable. Most "enterprise" linux distributions (e. g. RHEL) still require python 2.4.

It is incredibly difficult to install your own python once you need some extra libraries with C dependencies. For example, if you build your own python, say 2.6 on RHEL, but you need to use pyqt, you are in for a fun ride if you don't have admin privileges on your machine.

Re:Writing Python 2.x forward compatible to Python 3 code by zcid on Saturday January 22, 2011 @05:47PM (#2131261)
I believe the major issue right now is Red Hat. I can't find the emails detailing the issue right now, but apparently for applications like Django, they are worried about long term support in RHES for python 2.4 or 2.5 for at least another year or two.

So for python applications that are designed for server deployment, you need to look carefully at what versions your commercial linux users are running. While smaller deployments are important too, the enterprise customers are the ones that will say when 3.x is relevant or not.

Re:Writing Python 2.x forward compatible to Python 3 code by cookiecaper on Saturday January 22, 2011 @11:04PM (#2131754)
This is where I think the server distributions get a little bit ridiculous. It is really silly that everyone on Red Hat is still stuck on 2.4. I understand that keeping a certain set of software at the same version for a while can be useful for system administrators, but really it's time 2.4 bid us adieu.

I'd really like to see a somewhat tighter release cycle from Red Hat, or for people to stop caring about supporting Red Hat after a while. The whole ecosystem shouldn't be trapped because Red Hat's customers, many of whom still have FORTRAN and COBOL programs performing important business functions, don't like to upgrade.