On Thu, 4 Oct 2012 22:08:40 +0530
Nick Coghlan wrote:
> On Thu, Oct 4, 2012 at 7:54 PM, Brett Cannon wrote:
> > This used to be a no-no, though, because if someone called that function in
> > a thread during an import it would deadlock. Now Antoine reworked the locks
> > so I don't know if this i
On Thu, Oct 4, 2012 at 5:37 PM, Jesus Cea wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 04/10/12 18:38, Nick Coghlan wrote:
> > You can still technically deadlock, but you need a circular import
> > *and* two different threads that start at different parts of the
> > cycle.
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/10/12 18:38, Nick Coghlan wrote:
> You can still technically deadlock, but you need a circular import
> *and* two different threads that start at different parts of the
> cycle.
Is this true for 2.7 too, or only for recent 3.x?
- --
Jesús Ce
On Thu, Oct 4, 2012 at 7:54 PM, Brett Cannon wrote:
> This used to be a no-no, though, because if someone called that function in
> a thread during an import it would deadlock. Now Antoine reworked the locks
> so I don't know if this is still true or not.
You can still technically deadlock, but y
On Thu, Oct 4, 2012 at 9:17 AM, Jesus Cea wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 04/10/12 14:34, Benjamin Peterson wrote:
> > 2012/10/4 Jesus Cea :
> >> Any suggestion about how to solve this?
> >
> > Easy solutions include somehow removing the dependence on
> > subproces
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/10/12 14:34, Benjamin Peterson wrote:
> 2012/10/4 Jesus Cea :
>> Any suggestion about how to solve this?
>
> Easy solutions include somehow removing the dependence on
> subprocess or moving the import of subprocess into the function
> that uses
2012/10/4 Jesus Cea :
> Any suggestion about how to solve this?
Easy solutions include somehow removing the dependence on subprocess
or moving the import of subprocess into the function that uses it.
--
Regards,
Benjamin
___
Python-Dev mailing list
P
