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 John Hagen
Recipients John Hagen, SilentGhost, martin.panter, matrixise, r.david.murray, serhiy.storchaka
Date 2015-11-01.20:27:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1446409661.56.0.632797990915.issue25521@psf.upfronthosting.co.za>
In-reply-to
Content
@martin.panter My new patch fixes Lib/test_optparse.py by suppressing the warning like test_imp does as you suggested.

@serhiy.storchaka I don't have a strong preference that it be a DeprecationWarning vs. PendingDeprecationWarning since to me, both get the point across to the end-user to avoid it.  I do, however, feel that it is important raise some kind of warning since it seems clear from the docs that is deprecated.

In my new patch I changed the type of warning to a PendingDeprecationWarning, as there seems to be at least some notion that optparse is a special case.  I don't have a strong opinion about which type of deprecation warning is used.

My new patch works when test_optparse.py is run with -Werror on 3.6.0a0.
History
Date User Action Args
2015-11-01 20:27:41John Hagensetrecipients: + John Hagen, r.david.murray, SilentGhost, martin.panter, serhiy.storchaka, matrixise
2015-11-01 20:27:41John Hagensetmessageid: <1446409661.56.0.632797990915.issue25521@psf.upfronthosting.co.za>
2015-11-01 20:27:41John Hagenlinkissue25521 messages
2015-11-01 20:27:41John Hagencreate