Message283178
| Author | vstinner |
|---|---|
| Recipients | Ringding, Trundle, aronacher, benjamin.peterson, doko, jdemeyer, larry, ned.deily, prologic, python-dev, sebastinas, serhiy.storchaka, thansen, vstinner |
| Date | 2016-12-14.09:17:29 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1481707049.62.0.726959397933.issue5322@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Since this change seems to break the backward compatibility, is it safe to apply it to Python 3.5.x and Python 3.6.x? The bug was reported in 2009, 7 years ago. Can the fix wait for Python 3.7? test_file contains code which worked well before the change and started to crash after the change. If it occurs for an application, I expect users to be unhappy of getting such "behaviour change" in a minor release, no? -- Is it possible to prevent the crash of test_file without modifying its code (without the change 4a610bc8577b "Change order of io.UnsupportedOperation base classes")? Sorry, I didnd't follow this issue. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2016-12-14 09:17:29 | vstinner | set | recipients: + vstinner, doko, larry, sebastinas, benjamin.peterson, ned.deily, aronacher, prologic, Trundle, Ringding, python-dev, serhiy.storchaka, jdemeyer, thansen |
| 2016-12-14 09:17:29 | vstinner | set | messageid: <1481707049.62.0.726959397933.issue5322@psf.upfronthosting.co.za> |
| 2016-12-14 09:17:29 | vstinner | link | issue5322 messages |
| 2016-12-14 09:17:29 | vstinner | create | |