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 gregory.p.smith
Recipients Anthony Sottile, bethard, bskinn, eric.araujo, gregory.p.smith, memeplex, ned.deily, paul.j3, wolma
Date 2018-05-15.20:41:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1526416881.48.0.682650639539.issue33109@psf.upfronthosting.co.za>
In-reply-to
Content
If the behavior was consistent from 3.3 through 3.6, that is the behavior we should keep going forward in 3.7+ without a deprecation period.  (and this does not seem worth deprecating, lets just keep the behavior the same as it was in 3.3-3.6)

That 2.7 is different than >=3.3 here isn't important.  There are a lot of things that have conditional behavior differences when using 2 and over time that is becoming increasingly irrelevant.

Libraries often keep compatibility with both 2.7 and 3.4+ today, but it is less common for a command line tool entry point to need to be compatible with both.
History
Date User Action Args
2018-05-15 20:41:21gregory.p.smithsetrecipients: + gregory.p.smith, bethard, ned.deily, eric.araujo, memeplex, paul.j3, wolma, Anthony Sottile, bskinn
2018-05-15 20:41:21gregory.p.smithsetmessageid: <1526416881.48.0.682650639539.issue33109@psf.upfronthosting.co.za>
2018-05-15 20:41:21gregory.p.smithlinkissue33109 messages
2018-05-15 20:41:21gregory.p.smithcreate