[Python-Dev] Need help for SWIG's Python 3.0 backend

[Haoyu Bai]

Hello,

I am a Google Summer of Code student who preparing a SWIG's Python 3.0 
support proposal. Here's detail of my proposal:

http://www.dabeaz.com/cgi-bin/wiki.pl?GSoCPython3Proposal

And abstract shown below for convenient:

This project adds Python 3.0 support for SWIG. We will add a "-3" option 
to SWIG's current backend, which indicates SWIG to generate wrapper for 
Python 3. We also make SWIG generate more efficient code and more clear 
proxy by utilizing Python 3's new features.

The considered features are as follows:

 * Function Annotations

 * Mutable Buffer Support

 * Abstract Base Classes


I have read PEPs and Python 3's document, then did some experiment on 
the API. I have modified a SWIG generated wrapper code by hand so it can 
  running with Python 3.0.

However, there still some API changes I can't handle. SWIG used some 
undocumented C API, for example the _PyInstance_Lookup(). And some API 
disappeared, I can't found the alternative of them, for example 
PyInstance_NewRaw().

I think I will need a lot of help from Python developers if my proposal 
is accepted. So I post this here to make sure if I can get help when 
doing this project. And I really appreciate if you can give any advice 
about how to solve the problems I mentioned before.

Thank you!


Best regards,

Haoyu Bai
4/12/2008
___
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

Re: [Python-Dev] call for help: C-API 2 to 3 porting guide

[Haoyu Bai]

On Sat, Sep 27, 2008 at 9:09 PM, Christian Heimes <[EMAIL PROTECTED]> wrote:
> Benjamin Peterson wrote:
>>
>> Hi guys,
>> I remember a while back we were bemoaning the fact that little
>> documentation exists for the extension module transition between 2.x
>> and 3.x. In the name of this effort, I've created a c porting howto
>> (Doc/howto/cporting.rst). I have started a few sections, but I can't
>> do it all alone. Please consider writing a section.
>
> I'll try to find some time over the weekend to assist you. I'm going to
>  contact the Cython developers, too. They have a great deal of experience
> with Python 2.x and 3.0 compatible C code. Perhaps they can give us some
> hints and tell us about gotchas and tricks.
>

Also, there's a wiki page for some py3k extension moduls migration
tips: http://wiki.python.org/moin/Py3kExtensionModules

Hope it helps.

-- 
Haoyu Bai
___
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

Re: [Python-Dev] RELEASED Python 2.6 final

[Haoyu Bai]

On Thu, Oct 2, 2008 at 11:59 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> Congratulations, Barry!!!
>
> On Wed, Oct 1, 2008 at 8:46 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On behalf of the Python development team and the Python community, I am
>> happy to announce the release of Python 2.6 final.  This is the
>> production-ready version of the latest in the Python 2 series.
>>
>> There are many new features and modules, improvements, bug fixes, and other
>> changes in Python 2.6.  Please see the "What's new" page for details
>>
>>http://docs.python.org/dev/whatsnew/2.6.html
>>
>> as well as PEP 361
>>
>>http://www.python.org/dev/peps/pep-0361/
>>
>> While Python 2.6 is backward compatible with earlier versions of Python, 2.6
>> has many tools and features that will help you migrate to Python 3.
>>  Wherever possible, Python 3.0 features have been added without affecting
>> existing code.  In other cases, the new features can be enabled through the
>> use of __future__ imports and command line switches.
>>
>> Python 3.0 is currently in release candidate and will be available later
>> this year.  Both Python 2 and Python 3 will be supported for the foreseeable
>> future.
>>
>> Source tarballs, Windows installers, and Mac disk images can be downloaded
>> from the Python 2.6 page:
>>
>>http://www.python.org/download/releases/2.6/
>>
>> (Please note that due to quirks in the earth's time zones, the Windows
>> installers will be available shortly.)
>
> Can someone who's still up fix add this note to the website? It looks
> a little dodgy just linking to a 404 error... :-(
>
>> Bugs can be reported in the Python bug tracker:
>>
>>http://bugs.python.org
>>
>> Enjoy,
>> - -Barry
>>
>> Barry Warsaw
>> [EMAIL PROTECTED]
>> Python 2.6/3.0 Release Manager
>> (on behalf of the entire python-dev team)
>>
>> -BEGIN PGP SIGNATURE-
>> Version: GnuPG v1.4.9 (Darwin)
>>
>> iQCVAwUBSOREJ3EjvBPtnXfVAQLAigP/aEnrdvAqk7wbNQLFbmBonIr2YQbd1vEu
>> TyTr5imYXFWGNfv1/JMeMBjMfwpHi1bgPEDTLEZdhDRNj/G1h4NqqnpfJS0lfIaU
>> 4JBKwnsO80se/RGyupcs5f09UdKxOljhbFKEw46CHDkd9lE+cqy2yhetEwyx3c3+
>> AVC11sjcO54=
>> =Oxo3
>> -END PGP SIGNATURE-
>> ___
>> 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/guido%40python.org
>>
>
>
>
> --
> --Guido van Rossum (home page: http://www.python.org/~guido/)

Now almost all the pages on docs.python.org can't be accessed. For
example http://docs.python.org/lib/lib.html returns 403 forbidden.

Is the online docs under updating to 2.6, or there's something wrong?

-- 
Haoyu Bai
___
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