Message334057
| Author | serhiy.storchaka |
|---|---|
| Recipients | rhettinger, serhiy.storchaka |
| Date | 2019-01-19.11:28:16 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1547897296.22.0.210770432288.issue35780@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
> If so, then why is the link being moved to the front of the lru_cache -- it should have remained at the oldest position. It may be unintentionally. In any case, this is a case that should be very rare. > The solution to this is only extract the link after a successful pop rather than before. Then there is a possibility to pop the same key (from the last link) twice. The GIL can be released in _PyDict_Pop_KnownHash() and other thread can went the same way. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019-01-19 11:28:18 | serhiy.storchaka | set | recipients: + serhiy.storchaka, rhettinger |
| 2019-01-19 11:28:16 | serhiy.storchaka | set | messageid: <1547897296.22.0.210770432288.issue35780@roundup.psfhosted.org> |
| 2019-01-19 11:28:16 | serhiy.storchaka | link | issue35780 messages |
| 2019-01-19 11:28:16 | serhiy.storchaka | create | |