On 24/12/13 07:41, Prasad Joshi wrote:
> Hello All,
>
> I am interested in participating GSoC 2014. I have went through last
> year's eligibility criterion, I think I am qualified to participate. I
> know GSoC 2014 still has more than 2-3 months, however I would like to
> start early. Please let me
On 19/12/13 12:22, Nick Coghlan wrote:
> On 19 December 2013 07:58, Daniel Pocock wrote:
>>
>> On 18/12/13 16:29, Victor Stinner wrote:
>>> 2013/12/18 Antoine Pitrou :
>>>> You only need to call PyEval_InitThreads() once in the main Python
>>>> t
On 18/12/13 16:29, Victor Stinner wrote:
> 2013/12/18 Antoine Pitrou :
>> You only need to call PyEval_InitThreads() once in the main Python
>> thread.
>
> This is not well documented. For your information, PyGILState_Ensure()
> now calls PyEval_InitThreads() in Python 3.4, see:
> http://bugs.py
On 18/12/13 16:02, Chris Angelico wrote:
> On Wed, Dec 18, 2013 at 9:26 PM, Daniel Pocock wrote:
>> b) when each worker thread starts, call
>> PyThreadState_New(mInterpreterState) and save the result in a thread
>> local mPyThreadState
>>
>> c) use the mPyThre
to make it work. Specifically, the PyWorkerThread constructor
was taking an object argument when it should have taken a reference
argument and this was creating an invalid Py::Callable member in my worker.
On 18/12/13 00:19, Daniel Pocock wrote:
>
> I've successfully embedded Python f
I've successfully embedded Python for a single thread
I tried to extend the implementation for multiple threads (a worker
thread scenario) and I'm encountering either deadlocks or seg faults
depending upon how I got about it.
There seems to be some inconsistency between what is covered in the d
I've successfully embedded Python for a single thread
I tried to extend the implementation for multiple threads (a worker
thread scenario) and I'm encountering either deadlocks or seg faults
depending upon how I got about it.
There seems to be some inconsistency between what is covered in the d
