[issue16543] Use "positional arguments" in PyArg_UnpackTuple

Chris Jerdonek added the comment: > TypeError: f() missing 1 required positional argument: 'a' By the way, changing this message is the subject of issue 16520 (which should probably be retitled). -- ___ Python tracker

[issue16504] IDLE - fatal error when opening a file with certain tokenizing errors

Changes by Terry J. Reedy : -- nosy: +terry.reedy versions: -Python 3.1 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue16508] include the "object" type in the lists of documented types

Terry J. Reedy added the comment: good idea -- nosy: +terry.reedy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue16543] Use "positional arguments" in PyArg_UnpackTuple

Ezio Melotti added the comment: #16520 could be assimilated by this issue, if we decide to widen its scope as I suggested in msg176229. -- ___ Python tracker ___ ___

[issue16543] Use "positional arguments" in PyArg_UnpackTuple

Mark Dickinson added the comment: +1 to msg176229 -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue16510] Using appropriate checks in tests

Changes by Terry J. Reedy : -- nosy: +terry.reedy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue16518] add "buffer protocol" to glossary

Terry J. Reedy added the comment: I would use the term that is currently used in some error messages. -- nosy: +terry.reedy ___ Python tracker ___ ___

[issue16524] File access not always working with Python for Windows 32 bits on Windows 64 bits OS

Changes by Terry J. Reedy : -- resolution: -> invalid status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue16544] Add external link to ast docs

New submission from Andrew Svetlov: http://greentreesnakes.readthedocs.org/en/latest/index.html is excellent and comprehensive documentation for ast tree structures. It would be nice to incorporate that docs into stdlib documentation, but adding *see also* section is good enoigh as first step.

[issue16544] Add external link to ast docs

Ezio Melotti added the comment: I would suggest to contact the author and ask him if he wants to contribute those docs to Python. They could be then be merged to the current docs or included as a separate HOWTO. -- nosy: +ezio.melotti type: -> enhancement ___

[issue16543] Use "positional arguments" in PyArg_UnpackTuple

Chris Jerdonek added the comment: I would keep any "global" discussion (for decision and coordination purposes) as part of a single meta-issue, but retain individual instances that need to be corrected as separate issues. I don't think we should try to fix them all as part of one patch or iss

[issue16518] add "buffer protocol" to glossary

Antoine Pitrou added the comment: "Buffer protocol" is the right term. "Buffer object" doesn't mean anything in Python 3 and, furthermore, it might be mixed up with the Python 2 `buffer` type. As for the error messages, they are generally very bad on this topic, so I would vote to change them

[issue16543] Use "positional arguments" in PyArg_UnpackTuple

Ezio Melotti added the comment: Using this as meta-issue is fine -- there are already enough issues :) The issues can probably be fixed in a single patch too, since it should just be a matter of changing the text of a few error messages. -- ___ Pytho

[issue16518] add "buffer protocol" to glossary

Chris Jerdonek added the comment: Do we have a recommended (and preferably briefer) way of saying, "any object that supports the buffer protocol"? -- ___ Python tracker ___

[issue16518] add "buffer protocol" to glossary

Chris Jerdonek added the comment: s/any// -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue16540] Make itertools count, cycle, and repeat objects subscriptable like range.

Neil Girdhar added the comment: Thanks, that works. One of the things I like about Python is that you can write what you mean. I figured that since I meant "repeat [] as many times as necessary", that I should write it that way. So, from an intuitive standpoint, I still feel that these iter

[issue16518] add "buffer protocol" to glossary

Ezio Melotti added the comment: > "Buffer object" doesn't mean anything in Python 3 and, furthermore, > it might be mixed up with the Python 2 `buffer` type. Agreed. > As for the error messages, they are generally very bad on this topic, > so I would vote to change them :-) I would say that th

[issue16518] add "buffer protocol" to glossary

Antoine Pitrou added the comment: > Do we have a recommended (and preferably briefer) way of saying, "any > object that supports the buffer protocol"? It depends where. There's no recommended way yet, but I would vote for "bytes-like object" in error messages that are targetted at the average de

[issue16518] add "buffer protocol" to glossary

Ezio Melotti added the comment: > I would vote for "bytes-like object" Sounds like a good compromise between brevity and clarity to me. -- ___ Python tracker ___ ___

[issue16544] Add external link to ast docs

Andrew Svetlov added the comment: I've done it just now sending him message via bitbucket. -- ___ Python tracker ___ ___ Python-bugs-l

[issue16518] add "buffer protocol" to glossary

Stefan Krah added the comment: I wouldn't use "bytes-like object". One can certainly argue that *memoryview* should be bytes-like as a matter of preference, but the buffer protocol specifies strongly (or even statically) typed multi-dimensional arrays. PEP-3118 Py_buffer structs are essentially

[issue16518] add "buffer protocol" to glossary

Antoine Pitrou added the comment: > I wouldn't use "bytes-like object". One can certainly argue that *memoryview* > should be bytes-like as a matter of preference, but the buffer protocol > specifies strongly (or even statically) typed multi-dimensional arrays. Ach :-( > PEP-3118 Py_buffer stru

[issue16518] add "buffer protocol" to glossary

Chris Jerdonek added the comment: > I wouldn't use "bytes-like object". What about "buffer-like object"? -- ___ Python tracker ___ __

[issue16518] add "buffer protocol" to glossary

Antoine Pitrou added the comment: > > I wouldn't use "bytes-like object". > > What about "buffer-like object"? "buffer-like" means "like a buffer" which is wrong on two points: - "buffer" is not defined at this point, so the user doesn't understand what it means - we are not talking about an ob

[issue16504] IDLE - fatal error when opening a file with certain tokenizing errors

Serhiy Storchaka added the comment: The bug is somewhere in print_exception() function in Lib/idlelib/run.py. -- ___ Python tracker ___ __

[issue16518] add "buffer protocol" to glossary

Stefan Krah added the comment: Antoine Pitrou wrote: > > PEP-3118 Py_buffer structs are essentially how NumPy works internally. > > Well, we should still write a Python documentation, not a NumPy > documentation (on this tracker anyway). Outside of NumPy, there's little > use for multi-dimensio

[issue16518] add "buffer protocol" to glossary

Antoine Pitrou added the comment: > > Well, we should still write a Python documentation, not a NumPy > > documentation (on this tracker anyway). Outside of NumPy, there's little > > use for multi-dimensional objects. > > Ok, but people should not be surprised if their (Python) array.array() of

[issue12806] argparse: Hybrid help text formatter

rurpy the second added the comment: I happened upon this issue while Googling for a formatter with the behavior described here. I put together a formatter derived from the code submitted by GraylinKim (2011-08-22) and offer it for consideration (though it is missing some things like docstring

[issue12806] argparse: Hybrid help text formatter

rurpy the second added the comment: Additional comment loosely related to the ParagraphFormatter offered in previous comment... [If this is not the right venue -- perhaps a new issue or one of the python mail lists would be better -- please tell me.] I notice that argparse.ArgumentParser requ

[issue16546] ast.YieldFrom needlessly has its expr value as optional

New submission from Brett Cannon: The grammar guarantees that 'yield from' statements have an expression to evaluate, plus a 'yield from' without an expression makes no sense. -- components: Library (Lib) messages: 176261 nosy: brett.cannon priority: normal severity: normal stage: test

[issue16545] ast.FunctionDef sets a bad value for kw_defaults when keyword-only arguments present

New submission from Brett Cannon: When there are no keyword-only arguments, the value of kw_defaults for FunctionDef is []. But when keyword-only arguments are present with no default values, it becomes [None]. That's bad as every other value in FunctionDef has a default of [] when there is no

[issue16518] add "buffer protocol" to glossary

Stefan Krah added the comment: Antoine Pitrou wrote: > > How about "object does not provide a byte buffer" for error messages > > and "(byte) buffer provider" as a shorthand for "any buffer provider > > that exposes its memory as a sequence of unsigned bytes in response > > to a PyBUF_SIMPLE req

[issue16540] Make itertools count, cycle, and repeat objects subscriptable like range.

Changes by Raymond Hettinger : -- resolution: -> rejected status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing

[issue16501] deprecate RISCOS "support"

Changes by Jesús Cea Avión : -- nosy: +jcea ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue16501] deprecate RISCOS "support"

Jesús Cea Avión added the comment: Please, update PEP 11. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue16500] Add an 'afterfork' module

Changes by Jesús Cea Avión : -- nosy: +jcea ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue6923] Need pthread_atfork-like functionality in CPython

Changes by Jesús Cea Avión : -- nosy: +jcea ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue16512] imghdr doesn't support jpegs with an ICC profile

Changes by Jesús Cea Avión : -- nosy: +jcea ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue16518] add "buffer protocol" to glossary

Chris Jerdonek added the comment: > > That's why I'm proposing "bytes-like object". > > If it is somehow possible to establish the term as a shorthand for the real meaning, This can be established via the glossary. We can still use "buffer provider" for the general case, if we find that it is

[issue16534] test_float failure on IA64 (HPUX)

Stefan Krah added the comment: For some reason ./configure detects x87-style-double-rounding=yes, but when I compile the test manually with the same command line "cc -Ae -g", no double rounding is detected. -- ___ Python tracker

[issue16504] IDLE - fatal error when opening a file with certain tokenizing errors

Roger Serwy added the comment: Serhiy, was msg176255 meant for issue16491? -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue3871] cross and native build of python for mingw* hosts

Changes by Tshepang Lekhonkhobe : -- nosy: +tshepang ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

<    1   2