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 nadeem.vawda
Recipients Arfrever, docs@python, georg.brandl, gvanrossum, jackjansen, nadeem.vawda, pitrou, r.david.murray, serhiy.storchaka, stutzbach
Date 2012-06-28.21:28:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1340918916.39.0.958081555109.issue15204@psf.upfronthosting.co.za>
In-reply-to
Content
+1 for the general idea of deprecating and eventually removing the "U"
modes.

But I agree with David, that it doesn't make sense to have separate steps
for 3.5 and 3.6/4.0. If you make the code raise an exception when "U" is
used, how is that different from what will happen when you remove the
code for processing it? Surely we want it to eventually be treated just
like any other invalid mode string?
History
Date User Action Args
2012-06-28 21:28:36nadeem.vawdasetrecipients: + nadeem.vawda, gvanrossum, jackjansen, georg.brandl, pitrou, stutzbach, Arfrever, r.david.murray, docs@python, serhiy.storchaka
2012-06-28 21:28:36nadeem.vawdasetmessageid: <1340918916.39.0.958081555109.issue15204@psf.upfronthosting.co.za>
2012-06-28 21:28:35nadeem.vawdalinkissue15204 messages
2012-06-28 21:28:35nadeem.vawdacreate