obsolete modules are moved to lib-old. deprecated modules remain in the library. This makes the search for a relevant library more difficult. People browsing the code may not realize that they are deprecated. (Example, I found no notice of deprecation within the code for rfc822.) Even when the notice is there, the modules add to the number of alternatives, which hurts One-Obvious-Way-To-Do-It. If these modules were moved to a deprecated directory, these problems would be greatly reduced. (Ensure backwards compatibility by leaving the deprecated directory on the search path.)
Logged In: YES user_id=1188172 I think it's common practise to add a DeprecationWarning to those modules which are deprecated since one or two releases. That should be enough reminder. You should be reading the docs anyway :)
Logged In: YES user_id=1312539 This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker).
Logged In: YES user_id=764593 Reading the docs is not a bad thing, but they aren't always convenient when developing, and the code itself should be correct too. Moving them out of the standard library (and possibly the idlelib module search) will make them less of an attractive nuisance; at the least, it will save people the effort of looking them up and then backing out.
