Message253874
@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. |
|
Date |
User |
Action |
Args |
2015-11-01 20:27:41 | John Hagen | set | recipients:
+ John Hagen, r.david.murray, SilentGhost, martin.panter, serhiy.storchaka, matrixise |
2015-11-01 20:27:41 | John Hagen | set | messageid: <1446409661.56.0.632797990915.issue25521@psf.upfronthosting.co.za> |
2015-11-01 20:27:41 | John Hagen | link | issue25521 messages |
2015-11-01 20:27:41 | John Hagen | create | |
|