A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2008-April/078561.html below:

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

[Python-Dev] Need help for SWIG's Python 3.0 backend [Python-Dev] Need help for SWIG's Python 3.0 backendHaoyu Bai divinekid at gmail.com
Fri Apr 11 18:35:47 CEST 2008
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
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4