Home Original page

[Python-porting] Port of psycopg2

Brett Cannon brett at python.org
Sun Dec 7 01:09:18 CET 2008 
On Sat, Dec 6, 2008 at 14:34, Georg Brandl <georg at python.org> wrote:
> Brett Cannon schrieb:
>> On Sat, Dec 6, 2008 at 02:31, "Martin v. Löwis" <martin at v.loewis.de> wrote:
>>> I created to run psycopg2 on Python 3.0, at
>>>
>>> http://www.dcl.hpi.uni-potsdam.de/home/loewis/psycopg_3k.diff
>>>
>>> I also submitted the patch to Frederico di Gregorio, who will
>>> integrate it when he finds time.
>>>
>>> The patch passes nearly all tests (the failures seem unrelated,
>>> since the unmodified code also fails in nearly the same way).
>>>
>>
>> Martin, the porting machine!
>>
>> I know this keeps coming up, but I have not heard of a porting doc
>> being written yet. Is there one somewhere like the wiki?
>
> I searched for "Porting", and found only Martin's PortingDjango page.
>

Thought so.

> We should start drafting a porting document,

Definitely.

> which I also would like
> to include in the official docs

Yep.

> as soon as it's in a good shape, in
> the Wiki.
>
> Any suggestions for the general lay-out of such a document?

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.

-Brett
More information about the Python-porting mailing list