Daryl Tester wrote: > I'm just about to start writing myself a C extension module, and as I > was pondering how far to make it backward compatible the following > thought sprung to mind. What's the oldest and newest version of > Python you currently write code for [1]? > > I still have a fairly sizeable system that's running on Python 1.5.2 > (it's slooowly being migrated across on a break/fix basis, which is the > only time the customer pays, but alas it rarely breaks), but most of the > stuff I do these days is based around 2.5.x (various flavours of .2 to > .4) as py2exe doesn't cope well with 2.6. I've done little under 2.6 > (certainly nothing that would specifically use any of its features), and > apart from library changes (e.g. MIMEWriter's severe makeover) I tend to > code in a subset of Python that will allow me to run on a fairly wide > range of versions (although not as far back as 1.5.2, I have to remember > how to convert between "idioms" like list comprehensions). > > So what's your version range? > > 1 - this won't effect my decision, it's just something I'm idly > curious about. However, I probably won't code the extension as > a type for that reason as I know the extension types have changed > between major versions.
Python 2.5.1 (r251:54863, Jul 31 2008, 23:17:40) [GCC 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)] on linux2 Python 2.4.3 (#1, Jan 14 2008, 18:31:21) [GCC 4.1.2 20070626 (Red Hat 4.1.2-14)] on linux2 Python 2.3.5 (#2, Oct 16 2006, 19:19:48) [GCC 3.3.5 (Debian 1:3.3.5-13)] on linux2 cheers, Kim -- Operating Systems, Services and Operations Information Technology Services, The University of Adelaide [email protected] _______________________________________________ sapug mailing list [email protected] http://mail.python.org/mailman/listinfo/sapug
