On Tue, Nov 3, 2009 at 05:40, David Cournapeau <courn...@gmail.com> wrote: > On Tue, Nov 3, 2009 at 9:55 PM, Barry Warsaw <ba...@python.org> wrote: > >> >> Then clearly we can't back port features. >> >> I'd like to read some case studies of people who have migrated applications >> from 2.6 to 3.0. > > +1, especially for packages which have a lot of C code: the current > documentation is sparse :) The only helpful reference I have found so > far is an email by MvL concerning psycopg2 port.
There used to be a page on the wiki of case studies, but I couldn't find it. But one C-specific case study is the port of Wing's extension modules to support from Python 2.0 to 3.0: http://pythonology.blogspot.com/2009/02/making-code-run-on-python-20-through-30.html . There is also a wiki pages explicitly about porting C code: http://wiki.python.org/moin/cporting and http://wiki.python.org/moin/Py3kExtensionModules . Those latter pages include links to the official porting docs: http://docs.python.org/3.1/howto/cporting.html . And as Georg pointed out there is always the python-porting mailing list: http://mail.python.org/mailman/listinfo/python-porting . I'm afraid there is some FUD going around here, which is understandable since no one wants to burn a ton of time on something that will be difficult or take a lot of time. But I have not heard anyone in this email thread (or anywhere for that matter) say that they tried a port in earnest and it turned out to be difficult. -Brett _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
