[Python-porting] Port of psycopg2

[M.-A. Lemburg]

On 2008-12-07 22:45, Mark Hammond wrote:
> Brett Cannon wrote:
>> Well, there are two things that require porting: Python and extension
>> modules. So that is a high-level point of separation. From there we
>> can list the various steps that are needed (i.e. port to 2.6 with no
>> warnings, run with -3, add any __future__ statements you want, run
>> 2to3, test). The trick is where to put little tips like making sure
>> you clearly separate your string code from your bytes code.
> 
> Although the official line is to port to 2.6 first, it will be
> interesting to know how many people who are hanging out here care about
> earlier versions too?  ie, while many *application* authors can easily
> choose to target a specific version, *library* authors may not be so lucky.
> 
> Is there anyone else here for whom the step of "port to python 2.6" is a
> deal-breaker?

I'm not sure where the problems would lie in porting to Python 2.6
first.

The latest big porting effort was moving from Python 2.4 to 2.5
due to the Py_ssize_t changes, but those only affected C extensions.

-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Source  (#1, Dec 08 2008)
>>> Python/Zope Consulting and Support ...        http://www.egenix.com/
>>> mxODBC.Zope.Database.Adapter ...             http://zope.egenix.com/
>>> mxODBC, mxDateTime, mxTextTools ...        http://python.egenix.com/
________________________________________________________________________
2008-12-02: Released mxODBC.Connect 1.0.0      http://python.egenix.com/

::: Try our new mxODBC.Connect Python Database Interface for free ! ::::


   eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
    D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
           Registered at Amtsgericht Duesseldorf: HRB 46611
               http://www.egenix.com/company/contact/