[Python] GSoC and Python 3.0 Support
Hi, I'm a student who has finished SWIG's Python 3.0 support in GSoC 2008. If Boost will participate in this year's Summer of Code, I'd like to contribute my knowledge of Python 3 migration to Boost.Python, by implement Python 3.0 support for it. Finally the users of Boost.Python would get 3.0 support smoothly. Is that worth for a GSoC project? Any interesting? Thanks! -- Haoyu Bai
Haoyu Bai wrote:
Hi,
I'm a student who has finished SWIG's Python 3.0 support in GSoC 2008. If Boost will participate in this year's Summer of Code, I'd like to contribute my knowledge of Python 3 migration to Boost.Python, by implement Python 3.0 support for it. Finally the users of Boost.Python would get 3.0 support smoothly. Is that worth for a GSoC project? Any interesting?
That's the most interesting thing I've heard all day!
Neal Becker wrote:
Haoyu Bai wrote:
Hi,
I'm a student who has finished SWIG's Python 3.0 support in GSoC 2008. If Boost will participate in this year's Summer of Code, I'd like to contribute my knowledge of Python 3 migration to Boost.Python, by implement Python 3.0 support for it. Finally the users of Boost.Python would get 3.0 support smoothly. Is that worth for a GSoC project? Any interesting?
That's the most interesting thing I've heard all day!
Very cool. The python c++-sig mailing list would be interested in this... -t
On Monday 09 March 2009 13:21:23 Haoyu Bai wrote:
If Boost will participate in this year's Summer of Code, I'd like to contribute my knowledge of Python 3 migration to Boost.Python, by implement Python 3.0 support for it.
That would be wonderful. It is one of my most wanted features[1] in boost.python. Please post a message to the python c++-sig (cplusplus- sig@python.org). I'd be happy to provide any testing help. Regards, Ravi [1] My most wished for features (in order of decreasing priority): 1. Thread safety 2. PyFinalize support 3. Easier methods to write to_python/from_python converters 4. Python 3.0 support 5. Ability to extend the fundamental PyTypeObject used by boost.python
On Tue, Mar 10, 2009 at 3:54 AM, Ravi <lists_ravi@lavabit.com> wrote:
On Monday 09 March 2009 13:21:23 Haoyu Bai wrote:
If Boost will participate in this year's Summer of Code, I'd like to contribute my knowledge of Python 3 migration to Boost.Python, by implement Python 3.0 support for it.
That would be wonderful. It is one of my most wanted features[1] in boost.python. Please post a message to the python c++-sig (cplusplus- sig@python.org). I'd be happy to provide any testing help.
Regards, Ravi
[1] My most wished for features (in order of decreasing priority):
1. Thread safety 2. PyFinalize support 3. Easier methods to write to_python/from_python converters 4. Python 3.0 support 5. Ability to extend the fundamental PyTypeObject used by boost.python
Hi, Thanks! Seems there's a lot of interesting. So would anyone willing to mentor this? Also thanks Ravi for a list of features that may be candidates for this project. I will dive into Boost.Python source code to see more about these. Thanks! -- Haoyu Bai
On Wednesday 11 March 2009 12:38:55 Haoyu Bai wrote:
1. Thread safety 2. PyFinalize support 3. Easier methods to write to_python/from_python converters 4. Python 3.0 support 5. Ability to extend the fundamental PyTypeObject used by boost.python
Thanks! Seems there's a lot of interesting. So would anyone willing to mentor this?
Sadly, I suspect that finding a mentor will be difficult (perhaps even more difficult than the actual project). Off the top of my head, the following folks come to mind: - Dave Abrahams - Stefan Seefeld - Ralf Grosse-Kunstleve - Roman Yakovenko You might try contacting them off list or on c++-sig (cc'ed on this email).
Also thanks Ravi for a list of features that may be candidates for this project. I will dive into Boost.Python source code to see more about these.
I did not mean to imply that the features I requested should be part of your GSoC. Thread safety & PyFinalize support would each be worth a GSoC project just by themselves, IMHO. If you will be tackling python 3.0 support, it might be possible to combine it with greater support for embedding python since much of the work in both aspects would be about wrapping python C API for C++ programmers. Regards, Ravi
participants (4)
-
Haoyu Bai -
Neal Becker -
Ravi -
troy d. straszheim