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/2005-September/056143.html below:

[Python-Dev] Replacement for print in Python 3.0

[Python-Dev] Replacement for print in Python 3.0 [Python-Dev] Replacement for print in Python 3.0Tony Meyer t-meyer at ihug.co.nz
Sun Sep 4 08:17:14 CEST 2005
[...]
> maybe a few folks can go off and write up a PEP for a 
> print-replacement. 
[...]
> I'm pulling out of the 
> discussion until I see a draft PEP.

If there are two competing proposals, then the two groups write a PEP and
counter-PEP and the PEPs duke it out.  Is this still the case if proposal B
is very nearly the status quo?

IOW, would writing a "Future of the print statement in Python 3.0" counter
PEP that kept print as a statement be appropriate?  If not, other than
python-dev posting (tiring out the poor summary guys <0.5 wink>), what is
the thing to do?

=Tony.Meyer

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