I fully support removing all historic references from the 3.0 language manual. Please do help out! You can just start putting patches ("svn diff") into bugs.python.org; typically Georg gets to these very quickly. Do use subversion, not the distributed tarbal (which was out of date by the time it was uploaded to python.org. :-). --Guido On 9/26/07, scav at blueyonder.co.uk <scav at blueyonder.co.uk> wrote: > I'd like to help out cleaning up the Python3.0 documentation. There are a > lot of little leftovers from 2.x that are no longer true. (mentions of > long, callable() etc.) > > Ideally (especially in the tutorial), we should only refer to 3.0 features > and syntax, and keep the special cases and "other ways to do it" to a > minimum. > > Before I dive in and start submitting patches, what does everyone else > think? How much reference to previous python versions should be left in? > Does it make sense to keep notes of the nature of "since version 2.3 ..." > when there is an intentional discontinuity at 3.0? > > Peter Harris > > > > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: http://mail.python.org/mailman/options/python-dev/guido%40python.org > -- --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4