➜

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.

classification
Title: "new" not marked as deprecated in the docs
Type: Stage:
Components: Documentation Versions:
process
Status: closed Resolution: later
Dependencies: Superseder:
Assigned To: Nosy List: georg.brandl, hoffman, jhermann
Priority: normal Keywords:

Created on 2005-07-29 23:37 by jhermann, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (5)
msg25898 - (view) Author: Jürgen Hermann (jhermann) Date: 2005-07-29 23:37 
While

>>> help('new')

shows the deprecation of this module starting with 2.3,
the docs at

http://www.python.org/doc/current/lib/module-new.html

don't. Shouldn't they?
msg25899 - (view) Author: Michael Hoffman (hoffman) Date: 2005-08-03 08:16 
Logged In: YES 
user_id=987664

The new module should not be deprecated yet; it is
help("new") that should be fixed.
msg25900 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2005-08-03 08:51 
Logged In: YES 
user_id=1188172

Shouldn't it be deprecated? Look at the code in new.py.

The only thing I can say in favour of new is that
new.instancemethod() is prettier and clearer than
types.MethodType().
msg25901 - (view) Author: Michael Hoffman (hoffman) Date: 2005-08-03 09:12 
Logged In: YES 
user_id=987664

When searching Python-dev all I could find was discussion
over the eventual deprecation of types. If you deprecate the
types module you still need a way to access the five types
exposed in new.

new is not listed in PEP 4 (Deprecation of Standard Modules).
msg25902 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2005-08-25 21:46 
Logged In: YES 
user_id=1188172

I think that nothing will happen here before 3.0. Both
modules are used too heavily to be deprecated.
History
Date User Action Args
2022-04-11 14:56:12adminsetgithub: 42228
2005-07-29 23:37:50jhermanncreate