[issue6574] List the __future__ features in a table

Changes by Robert Lehmann : Added file: http://bugs.python.org/file14886/future.patch ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue6574] List the __future__ features in a table

Georg Brandl added the comment: I added a reference in line 13, changed the table header not to use colspans (the latex writer doesn't support that), and committed as r74791. -- assignee: ezio.melotti -> georg.brandl status: open -> closed ___ Python

[issue6574] List the __future__ features in a table

Robert Lehmann added the comment: Implemented proposed changes. Additionally, I'd change line 13 to state either "future statements" or "`future`:ref:" instead of "future_statements", which does not make sense in normal, unmarked text. -- Added file: http://bugs.python.org/file14885/fu

[issue6574] List the __future__ features in a table

Georg Brandl added the comment: Accepted, except for two things: * I'd drop the "a0" suffix for the mandatory version. "2.2" instead of "2.2.0a0" is much better to comprehend. * Why the ugly markup with the PEP refs? ``:pep:`number`: blah`` should work well. For 3k, all previous future featur

[issue6574] List the __future__ features in a table

Changes by Ezio Melotti : -- nosy: +georg.brandl stage: needs patch -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing

[issue6574] List the __future__ features in a table

Terry J. Reedy added the comment: For Python3, the table should start empty as of 3.0/3.1 -- nosy: +tjreedy ___ Python tracker ___ ___

[issue6574] List the __future__ features in a table

Robert Lehmann added the comment: I composed a list of __future__ features and linked the respective PEPs. Even though the language reference would be a better place to store such general information (being PEP'd and all) I found the library reference's __future__.py documentation to be a clean

[issue6574] List the __future__ features in a table

New submission from Ezio Melotti : The documentation about the __future__ features [1] only lists the features available for that particular version, without specifying when they were added and their effects. It would be nice to have a table with |feature|version added|effect|. A better place for