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 gvanrossum
Recipients Anthony Sottile, ethan smith, gregory.p.smith, gvanrossum, levkivskyi, lukasz.langa, vstinner
Date 2019-06-11.20:15:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1560284128.95.0.623260243624.issue35766@roundup.psfhosted.org>
In-reply-to
Content
> What will happen with Python 4? Why not using "full" Python version like (3, 4) or 0x304?

I don't think Python 4 is just around the corner, so I prefer to kick that problem down the road. I'm sure we can come up with a sufficiently backwards-compatible API.  (I'd prefer not to go the hex route, because printing the value would show as 52, which is pretty meaningless.)
History
Date User Action Args
2019-06-11 20:15:28gvanrossumsetrecipients: + gvanrossum, gregory.p.smith, vstinner, lukasz.langa, levkivskyi, Anthony Sottile, ethan smith
2019-06-11 20:15:28gvanrossumsetmessageid: <1560284128.95.0.623260243624.issue35766@roundup.psfhosted.org>
2019-06-11 20:15:28gvanrossumlinkissue35766 messages
2019-06-11 20:15:28gvanrossumcreate