[issue25810] Python 3 documentation for eval is incorrect

Irit Katriel added the comment: Help is now showing eval(source, globals=None, locals=None, /) with the / that indicates the args are positional only. The docs were updated here to state that the args are positional. -- nosy: +iritkatriel resolution: -> fixed stage: patch review ->

[issue25810] Python 3 documentation for eval is incorrect

miss-islington added the comment: New changeset d378fdb10a5476b86b5a01d74c1bcc4e2f52e003 by Miss Islington (bot) in branch '3.7': bpo-25810: Clarify eval() docs, it does not keywords (GH-15173) https://github.com/python/cpython/commit/d378fdb10a5476b86b5a01d74c1bcc4e2f52e003 -- ___

[issue25810] Python 3 documentation for eval is incorrect

miss-islington added the comment: New changeset 4e914ab29f6d48a9fd045ea6a25dbf9e2fb603f9 by Miss Islington (bot) in branch '3.8': bpo-25810: Clarify eval() docs, it does not keywords (GH-15173) https://github.com/python/cpython/commit/4e914ab29f6d48a9fd045ea6a25dbf9e2fb603f9 -- nosy

[issue25810] Python 3 documentation for eval is incorrect

Change by miss-islington : -- pull_requests: +15552 pull_request: https://github.com/python/cpython/pull/15911 ___ Python tracker ___ __

[issue25810] Python 3 documentation for eval is incorrect

Change by miss-islington : -- pull_requests: +15551 pull_request: https://github.com/python/cpython/pull/15910 ___ Python tracker ___ __

[issue25810] Python 3 documentation for eval is incorrect

Gregory P. Smith added the comment: New changeset 7a0023e8d17566eb32c836b65c33663303a2224f by Gregory P. Smith (smokephil) in branch 'master': bpo-25810: Clarify eval() docs, it does not keywords (GH-15173) https://github.com/python/cpython/commit/7a0023e8d17566eb32c836b65c33663303a2224f --

[issue25810] Python 3 documentation for eval is incorrect

Change by Roundup Robot : -- keywords: +patch pull_requests: +14905 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/15173 ___ Python tracker ___

[issue25810] Python 3 documentation for eval is incorrect

Change by Philipp Rauch : -- versions: +Python 3.8, Python 3.9 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue25810] Python 3 documentation for eval is incorrect

Change by Philipp Rauch : -- versions: +Python 3.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue25810] Python 3 documentation for eval is incorrect

Cheryl Sabella added the comment: See also PEP570 and issue 36540. -- nosy: +cheryl.sabella ___ Python tracker ___ ___ Python-bugs-

[issue25810] Python 3 documentation for eval is incorrect

Change by Berker Peksag : -- nosy: +berker.peksag ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue25810] Python 3 documentation for eval is incorrect

Changes by Ezio Melotti : -- nosy: +ezio.melotti type: -> enhancement versions: -Python 3.4 ___ Python tracker ___ ___ Python-bugs-l

[issue25810] Python 3 documentation for eval is incorrect

R. David Murray added the comment: As I recall it, in the python2 docs we used the [... notation, sometimes even when the actual arguments were or accepted keywords. In the python3 docs we converted to always using keyword notation...and then realized that that also caused confusion, in the o

[issue25810] Python 3 documentation for eval is incorrect

Martin Panter added the comment: See Issue 8706 about changing functions and methods to accept keyword arguments. But this cannot be done in general. What would you call the first argument to dict() such that all possible keyword arguments still work? What is the first range() argument called:

[issue25810] Python 3 documentation for eval is incorrect

random832 added the comment: What about fixing all methods so that they can take keywords? Are the functions with their current C signatures part of the stable ABI? Is there somewhere we could centrally add some magic "convert tuple+keywords to tuple, given list of names" code? -- __

[issue25810] Python 3 documentation for eval is incorrect

Martin Panter added the comment: See Issue 23738 where my current patch proposes using the PEP 457 slash (/) notation in the RST documentation, including for eval(). I’m not sure if there is a clear concensus for applying my patch however. An alternative would be to use the square-bracket nota

[issue25810] Python 3 documentation for eval is incorrect

Changes by SilentGhost : -- nosy: +larry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.or

[issue25810] Python 3 documentation for eval is incorrect

SilentGhost added the comment: I'm not sure how the people are supposed to discover this convention according to pep 436. Or is this now intended as two separate incompatible conventions for online docs and built-in help? -- ___ Python tracker

[issue25810] Python 3 documentation for eval is incorrect

random832 added the comment: I guess the next question is what the intent is. Was there an intent, which was not followed through on, to upgrade these methods to support keyword arguments? Or is there an intent (here and everywhere) that documentation using keyword argument syntax is appropria

[issue25810] Python 3 documentation for eval is incorrect

SilentGhost added the comment: Yes, whatever Andre's posted is not an output from 3.5. It's 3.4 or earlier. Also it's a wider problem because the same issue exists for exec: built-in help shows keyword arguments, while docs and implementation require only positional. -- versions: +Pyth

[issue25810] Python 3 documentation for eval is incorrect

random832 added the comment: Oh, I just noticed, the help string is also wrong in 3.5 (which explains why you removed 3.5 from the versions list, which I hadn't noticed until after posting my previous comment). -- ___ Python tracker

[issue25810] Python 3 documentation for eval is incorrect

random832 added the comment: Whatever the case may be, it *doesn't* support keyword arguments. e.g.: >>> eval("a+b", globals={'a':1}, locals={'b':2}) TypeError: eval() takes no keyword arguments So as the current situation stands, the documentation is wrong, and the help string is consistent w

[issue25810] Python 3 documentation for eval is incorrect

Changes by SilentGhost : -- stage: -> needs patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue25810] Python 3 documentation for eval is incorrect

SilentGhost added the comment: I think this is the case where hard-coded strings where not updated in the C files. -- nosy: +SilentGhost versions: -Python 3.5, Python 3.6 ___ Python tracker __

[issue25810] Python 3 documentation for eval is incorrect

New submission from Andre Roberge: The documentation for eval() indicates that it takes keyword arguments: eval(expression, globals=None, locals=None) However, that is incorrect, as indicated by the builtin help: >>> help(eval) Help on built-in function eval in module builtins: eval(...)