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 martin.panter
Recipients martin.panter, piotr.dobrogost
Date 2017-01-27.00:21:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1485476498.98.0.648777621046.issue29379@psf.upfronthosting.co.za>
In-reply-to
Content
I presume this is the same as in Issue 18543 (and a few other duplicates). Let me know if I got it wrong.

IMO there is no easy fix. The best solution may be to just document the behaviour as a limitation of the API, and design a new/improved API for the future (Py 3.7+) that handles these cases.
History
Date User Action Args
2017-01-27 00:21:39martin.pantersetrecipients: + martin.panter, piotr.dobrogost
2017-01-27 00:21:38martin.pantersetmessageid: <1485476498.98.0.648777621046.issue29379@psf.upfronthosting.co.za>
2017-01-27 00:21:38martin.panterlinkissue29379 messages
2017-01-27 00:21:38martin.pantercreate