On Tue, Apr 7, 2015 at 8:18 PM Armin Rigo wrote:
> Hi Yuriy,
>
> On 7 April 2015 at 16:00, Yuriy Taraday wrote:
> >> We can't even be sure that an actual deadlock situation encountered in
> >> a __del__ is really a deadlock; maybe a different thread will come
> >> along and release that lock soo
On Tue, Apr 7, 2015 at 7:18 PM, Armin Rigo wrote:
> Hi Yuriy,
>
> On 7 April 2015 at 16:00, Yuriy Taraday wrote:
>>> We can't even be sure that an actual deadlock situation encountered in
>>> a __del__ is really a deadlock; maybe a different thread will come
>>> along and release that lock soon..
Hi Yuriy,
On 7 April 2015 at 16:00, Yuriy Taraday wrote:
>> We can't even be sure that an actual deadlock situation encountered in
>> a __del__ is really a deadlock; maybe a different thread will come
>> along and release that lock soon... I think this is a problem that is
>> just as hard as the
Sorry for hijacking thread. I hope I won't hider it too much.
On Mon, Apr 6, 2015 at 10:05 PM Armin Rigo wrote:
> (2) cannot be done in Python without major changes in semantics. User
> code that makes no use of threads, for example, certainly doesn't
> expect to be careful about multithreading
Hi Maciej,
On 6 April 2015 at 21:08, Maciej Fijalkowski wrote:
> My question stands - should we add this short explanation (maybe with
> a link to the blog post) to FAQ as to why you should not use locks in
> dels?
My problem with the blog post is that, after it correctly diagnoses
the problem,
