Multi-line comments - a case for PEP 3099?
Hi, we got another feature request for multi-line comments. While it is nice to comment out multiple lines at once, every editor that deserves that name can add a '#' to multiple lines. And there's always "if 0" and triple-quoted strings... Georg
On 6/19/07, Georg Brandl <g.brandl@gmx.net> wrote:
we got another feature request for multi-line comments.
While it is nice to comment out multiple lines at once, every editor that deserves that name can add a '#' to multiple lines.
And there's always "if 0" and triple-quoted strings... I'd als say that the case for TOOWTDI is pretty clear on that.
But perhaps we can keep the Py3k discussions on the python-3000@python.org list? -- --Guido van Rossum (home page: http://www.python.org/~guido/)
Guido van Rossum schrieb:
On 6/19/07, Georg Brandl <g.brandl@gmx.net> wrote:
we got another feature request for multi-line comments.
While it is nice to comment out multiple lines at once, every editor that deserves that name can add a '#' to multiple lines.
And there's always "if 0" and triple-quoted strings... I'd als say that the case for TOOWTDI is pretty clear on that.
But perhaps we can keep the Py3k discussions on the python-3000@python.org list?
I haven't really seen this as a python-3000 specific issue. Or are you referring to the other cross-posting thread? Georg
On 6/19/07, Georg Brandl <g.brandl@gmx.net> wrote:
Guido van Rossum schrieb:
On 6/19/07, Georg Brandl <g.brandl@gmx.net> wrote:
we got another feature request for multi-line comments.
While it is nice to comment out multiple lines at once, every editor that deserves that name can add a '#' to multiple lines.
And there's always "if 0" and triple-quoted strings... I'd als say that the case for TOOWTDI is pretty clear on that.
But perhaps we can keep the Py3k discussions on the python-3000@python.org list?
I haven't really seen this as a python-3000 specific issue. Or are you referring to the other cross-posting thread?
That too, but at this point *any* feature request is a Py3k request. If it's not good for Py3k there's no point in having it in 2.6. And I'd like new functionality in 2.6 to be restricted to backported Py3k features. -- --Guido van Rossum (home page: http://www.python.org/~guido/)
participants (2)
-
Georg Brandl -
Guido van Rossum