In article ,
Martin P. Hellwig wrote:
>
>Currently my solution is to wrap the module around a module that when
>used creates a directory and pipes to the process
>(multiprocessing.Connection) thus enforcing single access and within
>that I have wrapped the db function around again so that selec
On 01/14/11 10:05, Kushal Kumaran wrote:
This might help though:
https://code.google.com/p/modwsgi/wiki/ProcessesAndThreading
It seems if you're not using 'daemon' mode, global data might be shared.
Yes I read that thoroughly before I started out implementing a solution.
But in my case I want
On Fri, Jan 14, 2011 at 1:51 PM, Martin P. Hellwig
wrote:
> On 01/14/11 03:04, Kushal Kumaran wrote:
>>
>> - Original message -
>>>
>>> Hi all,
>>>
>>> I have the following problem (which I already have a hacked around
>>> solution that works but I'd would like some more input on it):
>>>
On 01/14/11 03:04, Kushal Kumaran wrote:
- Original message -
Hi all,
I have the following problem (which I already have a hacked around
solution that works but I'd would like some more input on it):
I have a situation where multiple python processes are started
independently from each
- Original message -
> Hi all,
>
> I have the following problem (which I already have a hacked around
> solution that works but I'd would like some more input on it):
>
> I have a situation where multiple python processes are started
> independently from each other but by the same user
Hi all,
I have the following problem (which I already have a hacked around
solution that works but I'd would like some more input on it):
I have a situation where multiple python processes are started
independently from each other but by the same user with the same
environment (as happens wi
