Message216339
ok, so in this case, I can only change the documentation with a ".. deprecated:". But for the future, how can we know we have to deprecate this function for >= 3.6 ? Will you parse the documentation and check there is an deprecation to add in the code?
Or is there a file with the "future" deprecations?
Are you agree with the deprecation in the documentation? |
|
Date |
User |
Action |
Args |
2014-04-15 17:02:52 | matrixise | set | recipients:
+ matrixise, brett.cannon, ncoghlan, larry, yselivanov |
2014-04-15 17:02:52 | matrixise | set | messageid: <1397581372.32.0.425782882575.issue20438@psf.upfronthosting.co.za> |
2014-04-15 17:02:52 | matrixise | link | issue20438 messages |
2014-04-15 17:02:52 | matrixise | create | |
|