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
I'm recruiting C/C++/Linux Developers for a NYC client. Successful
candidates:
* will be around 5 years out of school
* have a Bachelors at least in CS/Eng from a top university
* do NOT have financial industry experience
* have fluency in C/C++, stl, pthreads, shared memory, networking and
e
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
