[issue23762] python.org page on new-style classes should be updated
![](https://secure.gravatar.com/avatar/fa0f7819f1825f596b384c19aa7dcf33.jpg?s=120&d=mm&r=g)
New submission from Joël Schaerer: This page (found it via a search engine): https://www.python.org/doc/newstyle/ is supposed to give the status of "New-style classes". However this information is no longer relevant for Python 3, and my needlessly scare newcomers. I believe it should be either deleted or updated to mention that python3 users don't need to care about this anymore. ---------- assignee: docs@python components: Documentation messages: 239127 nosy: docs@python, joelthelion priority: normal severity: normal status: open title: python.org page on new-style classes should be updated type: enhancement _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue23762> _______________________________________
![](https://secure.gravatar.com/avatar/fa0f7819f1825f596b384c19aa7dcf33.jpg?s=120&d=mm&r=g)
Terry J. Reedy added the comment: "Unfortunately, new-style classes have not yet been integrated into Python's standard documention" is not even true for 2.7. I think the page should be deleted. Any of the reverences that are both useful and not in the docs could be added to the docs. ---------- nosy: +terry.reedy _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue23762> _______________________________________
![](https://secure.gravatar.com/avatar/fa0f7819f1825f596b384c19aa7dcf33.jpg?s=120&d=mm&r=g)
Terry J. Reedy added the comment: This tracker can only handle changes to the docs. Deleting a web page would be an issue for the python.org tracker on github. But we should not make a request there until the docs have been checked and we are sure it should go. ---------- stage: -> needs patch _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue23762> _______________________________________
![](https://secure.gravatar.com/avatar/fa0f7819f1825f596b384c19aa7dcf33.jpg?s=120&d=mm&r=g)
Berker Peksag added the comment: IMHO, it can stay as a historical document. We just need to add a note to point out the correct documentation. So I think this can be handled on GitHub. I can't update the content since I don't have edit rights, so please open a new issue at https://github.com/python/pythondotorg/issues ---------- nosy: +berker.peksag _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue23762> _______________________________________
![](https://secure.gravatar.com/avatar/fa0f7819f1825f596b384c19aa7dcf33.jpg?s=120&d=mm&r=g)
Changes by Ezio Melotti <ezio.melotti@gmail.com>: ---------- resolution: -> third party status: open -> pending _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue23762> _______________________________________
![](https://secure.gravatar.com/avatar/fa0f7819f1825f596b384c19aa7dcf33.jpg?s=120&d=mm&r=g)
Berker Peksag added the comment: I've now added a warning to the document. ---------- stage: needs patch -> resolved status: pending -> closed _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue23762> _______________________________________
participants (4)
-
Berker Peksag
-
Ezio Melotti
-
Joël Schaerer
-
Terry J. Reedy