A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2007-September/074729.html below:

[Python-Dev] Python 3.0a documentation

[Python-Dev] Python 3.0a documentation [Python-Dev] Python 3.0a documentationscav at blueyonder.co.uk scav at blueyonder.co.uk
Wed Sep 26 10:42:28 CEST 2007
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



More information about the Python-Dev mailing list

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