➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gvanrossum
Recipients gvanrossum, r.david.murray, sss, vstinner, yselivanov
Date 2016-08-04.15:06:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAP7+vJJkHdUwN8wsXkZU32HCRtYtW39TmiOWMrPthFvQduBbew@mail.gmail.com>
In-reply-to <CAP7+vJJr=uYRy9hwi0EEz6qsXD+0uB2QwoATV4LKb+mL6CD8_Q@mail.gmail.com>
Content 
Does this repro with the latest Python 3.5.2? IIRC the lock code was
overhauled after 3.5.0 or 3.5.1.

(PS. These are tasks, not threads.)

--Guido (mobile)

On Aug 4, 2016 2:33 AM, "sss" <report@bugs.python.org> wrote:

sss added the comment:

Yes, await asyncio.sleep(0) does fix it, but it would be weird if I'm
supposed to put those all over my code. I made a new reproducer now that
uses 2 threads in case it's not allowed to take the same lock twice from
the same thread.

----------
Added file: http://bugs.python.org/file44007/lock2.py

_______________________________________
Python tracker <report@bugs.python.org>
<http://bugs.python.org/issue27585>
_______________________________________
History
Date User Action Args
2016-08-04 15:06:30gvanrossumsetrecipients: + gvanrossum, vstinner, r.david.murray, yselivanov, sss
2016-08-04 15:06:30gvanrossumlinkissue27585 messages
2016-08-04 15:06:29gvanrossumcreate