Terry J. Reedy added the comment:
I have started indexing symbol uses on other issue and will continue after
GSOC. I am closing this as there is nothing specific to do.
--
resolution: - wont fix
stage: needs patch - resolved
status: open - closed
Ezio Melotti added the comment:
223 people + me out of 1422 disagree with you both.
Note that those votes doesn't necessarily mean I didn't know about the
feature -- they might mean I find this feature useful/I like this feature.
Features like decorators have even more votes and I don't
Changes by Xavier Combelle xavier.combe...@gmail.com:
--
nosy: +xcombelle
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19024
___
___
anatoly techtonik added the comment:
223 people + me out of 1422 disagree with you both.
http://stackoverflow.com/questions/101268/hidden-features-of-python
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19024
anatoly techtonik added the comment:
To narrow the point of conflict, I say that argument unpacking *operators*
should have a prominent place in Python documentation that people can link
to. Current page
http://docs.python.org/3/tutorial/controlflow.html#unpacking-argument-lists is
about
Nick Coghlan added the comment:
Unfortunately, there's currently no good place for this kind of detailed syntax
reference documentation to go. The library reference doesn't cover syntax, the
tutorial doesn't go into detailed semantics, and the language reference is
written more for language
Terry J. Reedy added the comment:
The StackOverflow question and answer about function calls is 5 years old and
therefore out of date with respect to #12531, which specifically added index
entries for function calls.
Perhaps my Python 3 symbol glossary Python3 Syntax Symbol Uses
Terry J. Reedy added the comment:
Index entries for * and ** were added in #12531 so that both are indexed as
operators, in function definitions, in function calls, and in the tutorial. If
any of these places need improvement, there should be specific suggestions.
I do not think there should
Raymond Hettinger added the comment:
I concur with Terry.
--
nosy: +rhettinger
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19024
___
___
Changes by Mike Hoy mho...@gmail.com:
--
nosy: +mikehoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19024
___
___
Python-bugs-list mailing list
New submission from anatoly techtonik:
I'd say this is a critical documentation bug that leads to head bang when you
try to figure out what does '*' in code means.
This bug is two fold:
1. Define a dedicated place in documentation for '*' operator with examples. I
propose
anatoly techtonik added the comment:
tag:easy
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19024
___
___
Python-bugs-list mailing list
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
keywords: +easy
nosy: +ezio.melotti
stage: - needs patch
type: crash - enhancement
versions: -Python 2.6, Python 3.1, Python 3.2, Python 3.5
___
Python tracker rep...@bugs.python.org
Changes by Georg Brandl ge...@python.org:
--
Removed message: http://bugs.python.org/msg197774
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19024
___
Madison May added the comment:
http://docs.python.org/3/tutorial/controlflow.html#arbitrary-argument-lists
http://docs.python.org/3/tutorial/controlflow.html#unpacking-argument-lists
The above links do a so-so of explaining the splat operator, although I agree
that the docs for '*' could be
15 matches
Mail list logo
