Re: [Python.NET] Python.Net for Python3: bug when using an embedded interpreter

2014-10-02 Thread Serge WEINSTOCK
=uk.bnpparibas@python.org] Sent: 30 September 2014 19:16 To: pythondotnet@python.org Subject: Re: [Python.NET] Python.Net for Python3: bug when using an embedded interpreter Should be fixed now. Please re-open if it's still a problem (https://github.com/renshawbay/pythonnet/issues/13). cheers,

Re: [Python.NET] Python.Net for Python3: bug when using an embedded interpreter

2014-09-30 Thread Tony Roberts
Should be fixed now. Please re-open if it's still a problem ( https://github.com/renshawbay/pythonnet/issues/13). cheers, Tony On Tue, Sep 30, 2014 at 4:57 PM, Tony Roberts wrote: > Hi Serge, > > I see what you're saying. It would think that bit just needs to be moved > until after we're sure p

Re: [Python.NET] Python.Net for Python3: bug when using an embedded interpreter

2014-09-30 Thread Tony Roberts
Hi Serge, I see what you're saying. It would think that bit just needs to be moved until after we're sure python has been initialized so it works in both cases. I don't see any need to move it into a separate python module; having it compiled into one is cleaner IMHO. If you're not subclassing .NE

[Python.NET] Python.Net for Python3: bug when using an embedded interpreter

2014-09-30 Thread Serge WEINSTOCK
Hi Tony, You recently made a change which prevents me using the library in an embedded Python interpreter. In pythonengine.cs, you "inject" decorators with the following code: //= public static void Initialize() { . IntPtr glob