Message323880
| Author | ncoghlan |
|---|---|
| Recipients | koobs, lukasz.langa, matrixise, ncoghlan, pablogsal, vstinner, xtreak |
| Date | 2018-08-22.13:50:31 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1534945831.74.0.56676864532.issue34207@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Nothing has changed recently in the PEP 538 implementation itself, and both those builders were green last month: * https://buildbot.python.org/all/#/builders/60/builds/181 * https://buildbot.python.org/all/#/builders/79/builds/185 The first failing debug build was https://buildbot.python.org/all/#/builders/60/builds/182 which rearranged some parts of the startup sequence: https://github.com/python/cpython/commit/d19d8d5279f156bc8f6736b5f16f069879b9519b Similarly, the 3.7 builds started failing in https://buildbot.python.org/all/#/builders/124/builds/489, which made Py_Initialize work more closely to the way it worked in Python 3.6: https://github.com/python/cpython/commit/0c90d6f75931da4fec84d06c2efe9dd94bb96b77 So given the output reported in the current build failures, my guess would be that something has gotten out of sequence in the code that has to handle re-encoding and decoding command line values and environment variables that have initially been decoded incorrectly (i.e. as surrogate escaped ASCII). |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-08-22 13:50:31 | ncoghlan | set | recipients: + ncoghlan, vstinner, lukasz.langa, koobs, matrixise, pablogsal, xtreak |
| 2018-08-22 13:50:31 | ncoghlan | set | messageid: <1534945831.74.0.56676864532.issue34207@psf.upfronthosting.co.za> |
| 2018-08-22 13:50:31 | ncoghlan | link | issue34207 messages |
| 2018-08-22 13:50:31 | ncoghlan | create | |