on Wed Apr 01 2009, Haoyu Bai wrote:
> Hi,
>
> I did some preliminary work on BPL py3k support in these days.
>
> With Troy's help we have a py3k SVN tree in sandbox now, which is
> branched from trunk. I also tried to compile BPL with Python 3, and by
> following the error report of the compile
On Fri, Apr 3, 2009 at 9:26 AM, Neal Becker wrote:
> In case you haven't seen it:
>
> http://docs.python.org/3.0/howto/cporting.html#cporting-howto
>
>
>
Hi,
I know that, thanks! But the guide just haven't covered every coiners.
There's also an wiki page which is almost summarized from my SWIG p
In case you haven't seen it:
http://docs.python.org/3.0/howto/cporting.html#cporting-howto
___
Cplusplus-sig mailing list
Cplusplus-sig@python.org
http://mail.python.org/mailman/listinfo/cplusplus-sig
On Thu, Apr 2, 2009 at 4:02 PM, Niall Douglas wrote:
> Surely your project hasn't been approved by Google yet?
>
> Otherwise, good to see such progress. BPL always had hard to find
> resource leaks because of the lack of Py_Finalize support - I used to
> Glowcode my bindings and I was never quite
Surely your project hasn't been approved by Google yet?
Otherwise, good to see such progress. BPL always had hard to find
resource leaks because of the lack of Py_Finalize support - I used to
Glowcode my bindings and I was never quite sure where leaks came
from. None were serious mind e.g. hang
Hi,
I did some preliminary work on BPL py3k support in these days.
With Troy's help we have a py3k SVN tree in sandbox now, which is
branched from trunk. I also tried to compile BPL with Python 3, and by
following the error report of the compiler, I did some patch - now we
have 14 .cpp files out
