Message285131
I just experienced the described problem using Python 3.6.0 (Python 3.6.0 (v3.6.0:41df79263a11, Dec 23 2016, 08:06:12) [MSC v.1900 64 bit (AMD64)] on win32), but i do not understand the current status of this issue: On the one hand it is marked as 'open', which seems to imply that is still not resolved. On the other hand the resolution was set to 'fixed' in May 2015. Should i open a new issue for Python 3.6? |
|
Date |
User |
Action |
Args |
2017-01-10 17:01:35 | rocco.matano | set | recipients:
+ rocco.matano, georg.brandl, paul.moore, ncoghlan, rupole, tim.golden, python-dev, takluyver, zach.ware, serhiy.storchaka, eryksun, steve.dower, Billy McCulloch, Paul Doom |
2017-01-10 17:01:35 | rocco.matano | set | messageid: <1484067695.51.0.696976968271.issue22107@psf.upfronthosting.co.za> |
2017-01-10 17:01:35 | rocco.matano | link | issue22107 messages |
2017-01-10 17:01:35 | rocco.matano | create | |
|