➜

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 Edward.K..Ream
Recipients Edward.K..Ream, SilentGhost, anshul6, eryksun, paul.moore, r.david.murray, random832, steve.dower, stutzbach, tim.golden, zach.ware
Date 2016-12-03.10:57:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1480762642.69.0.0173285654325.issue25778@psf.upfronthosting.co.za>
In-reply-to
Content 
The last message on this thread was in January, and this item is Open. According to Pep 478, 3.5.2 final was released Sunday, June 26, 2016.

How is this issue not a release blocker?

Why does there appear to be no urgency in fixing this bug?

This bug bites for 64-bit versions of Python 3. When it bit, it caused Leo to crash during startup. When it bit, it was reason to recommend Python 2 over Python 3.

I have just released an ugly workaround in Leo. So now Leo itself can start up, but there is no guarantee that user plugins and scripts will work.

Imo, no future version of Python 3 should go out the door until this bug is fixed, for sure, and for all time. If you want people to use Python 3, it can NOT have this kind of bug in it.
History
Date User Action Args
2016-12-03 10:57:22Edward.K..Reamsetrecipients: + Edward.K..Ream, paul.moore, tim.golden, stutzbach, r.david.murray, SilentGhost, zach.ware, eryksun, steve.dower, random832, anshul6
2016-12-03 10:57:22Edward.K..Reamsetmessageid: <1480762642.69.0.0173285654325.issue25778@psf.upfronthosting.co.za>
2016-12-03 10:57:22Edward.K..Reamlinkissue25778 messages
2016-12-03 10:57:22Edward.K..Reamcreate