GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • [ date ]
  • [ thread ]
  • [ subject ]
  • [ author ]

This view

  • Original page
  • New address

GeezerVison is showing mail.python.org — [Python-Dev] Any PEP about 2.6 -> 3000 code transition?

[Python-Dev] Any PEP about 2.6 -> 3000 code transition?

Brett Cannon brett at python.org
Sun May 25 07:43:00 CEST 2008

  • Previous message: [Python-Dev] Any PEP about 2.6 -> 3000 code transition?
  • Next message: [Python-Dev] Any PEP about 2.6 -> 3000 code transition?
  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Sat, May 24, 2008 at 9:25 PM, Jesus Cea <jcea at jcea.es> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I can't find any PEP about detailed 2.6 -> 3000 migration guidelines,
> specially in the module (C code) extension area. Yes, I know about the
> 2to3 tool, but I'm interested in updating my 2.x code in order to keep
> (automatic via "2to3") difference between 2.x and 3.x codebase so small
> as possible. Also, 2to3 doesn't manage migration for C modules.
>
> Since I need to port bsddb3 to py3k, what I need to know?. Is any
> *updated* document out there?.
>

No definitive porting guide has been written, although it has been
discussed as being needed before. One should probably be written ASAP
if we are going to get any decent testing done by people with the beta
(and I am definitely NOT volunteering to write the doc).

-Brett

  • Previous message: [Python-Dev] Any PEP about 2.6 -> 3000 code transition?
  • Next message: [Python-Dev] Any PEP about 2.6 -> 3000 code transition?
  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the Python-Dev mailing list
You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.