dev-lang/swig-2.0.0 generates code, which uses PyCObject_*() functions, which are deprecated in Python 3.1 and removed in Python 3.2.
This is upstream, right? Arfrever, can we do something from our side?
This problem should be reported to upstream, so that they fix it before release of Python 3.2.
Two upstream bugs are currently opened about that issue, patches were submitted. http://sourceforge.net/tracker/?func=detail&aid=3047039&group_id=1645&atid=301645 http://sourceforge.net/tracker/?func=detail&aid=3057804&group_id=1645&atid=101645
(In reply to comment #0) > dev-lang/swig-2.0.0 generates code, which uses PyCObject_*() functions, which > are deprecated in Python 3.1 and removed in Python 3.2. > I just bumped swig to 2.0.2 , can you check if it's fixed in the new version?
http://swig.svn.sourceforge.net/viewvc/swig?view=revision&revision=12620
The patch doesn't apply cleanly. Backporting of the following revisions allow to apply this patch (r12620): r12593 r12596 r12597 r12598 r12600 r12602 r12604 r12605 r12606 r12607 r12608 r12609 r12610 r12611 r12612 r12613 r12614 r12615 r12618 r12619 Size of the cumulative patch is about 215 KiB. It might be better to add a dev-lang/swig-2.0.4_pre* snapshot.
01:17 <@pchrist> [Arfrever]: plz, check this snapshot I just took, and tell me if if the python issue is fixed there --> http://dev.gentoo.org/~pchrist/distfiles/swig-2.0.4_pre20110415.tar.bz2 (copy-paste from IRC)
Fixed by upstream in dev-lang/swig-2.0.4_pre12643.
*** Bug 367403 has been marked as a duplicate of this bug. ***