You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=<Date2013-10-12.16:11:23.674>created_at=<Date2010-03-08.21:51:34.457>labels= ['type-bug', 'docs']
title='PEP 4 should say something about the standard library'updated_at=<Date2013-10-12.16:11:23.672>user='https://github.com/sjoerdmullender'
When a module or feature is deprecated, all uses of the deprecated module/feature should be removed from the non-deprecated part of the distribution (and, I would argue, also from the other deprecated modules).
I think PEP-4 should say something to this effect.
I suggest adding a sentence to the section "Procedure for declaring a module deprecated", something like: "The proposal MUST include patches to remove any use of the deprecated module from the standard library."
I don't really think this is a documentation bug, more of an issue you have with the policy, in which case this is better being discussed on python-dev.
New changeset f7e3f6a53823 by Georg Brandl in branch 'default': PEP-4: convert to reST, update SourceForge -> bugs.python.org, update DeprecationWarning policy http://hg.python.org/peps/rev/f7e3f6a53823
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: