This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author rocco.matano
Recipients Billy McCulloch, Paul Doom, eryksun, georg.brandl, ncoghlan, paul.moore, python-dev, rocco.matano, rupole, serhiy.storchaka, steve.dower, takluyver, tim.golden, zach.ware
Date 2017-01-10.17:01:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1484067695.51.0.696976968271.issue22107@psf.upfronthosting.co.za>
In-reply-to
Content
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?
History
Date User Action Args
2017-01-10 17:01:35rocco.matanosetrecipients: + 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:35rocco.matanosetmessageid: <1484067695.51.0.696976968271.issue22107@psf.upfronthosting.co.za>
2017-01-10 17:01:35rocco.matanolinkissue22107 messages
2017-01-10 17:01:35rocco.matanocreate