Message285384
| Author | arigo |
|---|---|
| Recipients | Gian-Carlo Pascutto, arigo, benjamin.peterson, berker.peksag, ghaering, larry, lemburg, palaviv, python-dev |
| Date | 2017-01-13.11:17:07 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1484306227.63.0.000171717140162.issue29006@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Managed to write a patch in PyPy that seems to pass all tests including the new one, including on Windows. I know think that dd13098a5dc2 should be backed out (i.e. 030e100f048a should be kept). Reference to the PyPy changes: https://bitbucket.org/pypy/pypy/commits/235e8a3889790042b3f148bcf04891b27f97a1fc Maybe something similar should be added to CPython, to avoid the unexpected "database table is locked" case; but such a change should probably be done only in trunk, because the <= 2.6 experience seems to suggest it is rare enough in practice. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2017-01-13 11:17:07 | arigo | set | recipients: + arigo, lemburg, ghaering, larry, benjamin.peterson, python-dev, berker.peksag, Gian-Carlo Pascutto, palaviv |
| 2017-01-13 11:17:07 | arigo | set | messageid: <1484306227.63.0.000171717140162.issue29006@psf.upfronthosting.co.za> |
| 2017-01-13 11:17:07 | arigo | link | issue29006 messages |
| 2017-01-13 11:17:07 | arigo | create | |