[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

[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

[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

[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

[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.

[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

[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.

[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

[issue16501] deprecate RISCOS "support"

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

[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

[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

[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

[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

[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

[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

[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

[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

[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

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

[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". 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

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

[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

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 ___ ___

[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: > "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

[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

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

[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 ___

[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

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

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

[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 ___

[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.

[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

[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 ___ ___

[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

[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

[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 ___ ___

[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

[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

[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

[issue10712] 2to3 fixer for deprecated unittest method names

Changes by Ezio Melotti : -- nosy: +gregory.p.smith versions: +Python 3.3, Python 3.4 ___ Python tracker ___ ___ Python-bugs-list mail

[issue2454] sha and md5 fixer

Gregory P. Smith added the comment: Any code conversion is useful. This will help with old libraries and is even good for just updating old 2.4 code to 2.7 best practices. -- ___ Python tracker _

[issue16543] Use "positional arguments" in PyArg_UnpackTuple

Ezio Melotti added the comment: I would be fine with just dropping "positional" there, and say "required argument". With no further specification it means the "default" type of argument, i.e. positional or keyword. See also the end of msg170876. -- __

[issue16491] IDLE and except: raise from

Serhiy Storchaka added the comment: On Linux the result is the same. -- nosy: +serhiy.storchaka ___ Python tracker ___ ___ Python-bugs

[issue16543] Use "positional arguments" in PyArg_UnpackTuple

Chris Jerdonek added the comment: > TypeError: f() missing 1 required positional argument: 'a' Yes, I think this should also be changed because passing "a" as a keyword argument is okay: >>> f(a=1) I would suggest something like-- TypeError: f() missing argument for parameter 'a' --

[issue8109] Server-side support for TLS Server Name Indication extension

Changes by Piotr Dobrogost : -- nosy: +piotr.dobrogost ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue16543] Use "positional arguments" in PyArg_UnpackTuple

Ezio Melotti added the comment: Maybe we should follow a more systematic approach and collect the different errors raised in the different situations, and then come up with error messages that are accurate and follow the terminology that we are adopting in #15990. -- _

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

Serhiy Storchaka added the comment: Why not use `dummy = [[]] * 3` as dummy? -- ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue16491] IDLE and except: raise from

Terry J. Reedy added the comment: I marked this as 3.3+ bug because double reporting is new in 3.x and 'from None' is new in 3.3 (it causes a TypeError in the raise statement ;-). Command prompt output appears 'correct' (as intended). [I added blank lines before each try: for reading ease] Pyt

[issue16543] Use "positional arguments" in PyArg_UnpackTuple

Mark Dickinson added the comment: > Here the error message is about "positional arguments," which are > different from parameters. Okay. So is it also planned to change the existing error messages for user-defined functions? E.g.: >>> def f(a, b=1): ... pass ... >>> f() Traceback (most

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

Neil Girdhar added the comment: My code looks like this: presignal_abd = [[], [0.1, 0.6], []] tarsignal_abd = [[], [0.4, 0.9], []] diagsignal_abd = [[], [0.1, 0.6, 0.7, 0.8], []] # etc. for (filename, observations, presignals, tarsignals, diagsignals, diagram_type) in z

[issue16480] pyvenv 3.3 fails to create symlinks for /local/{bin, lib} to /{bin, lib}

Vinay Sajip added the comment: IIUC, Debian Experimental is not a complete distribution. Are there other, non-experimental OS variants where posix_local is used with Python 3.x? On my Ubuntu Oneiric and Precise 64-bit machines, the default install scheme on the official Python 3.2 - as determi

[issue16543] Use "positional arguments" in PyArg_UnpackTuple

Chris Jerdonek added the comment: > This can be fixed by adding "positional" before "arguments" in the error > message. Do we know for sure that the values in the args argument in a call to PyArg_UnpackTuple always correspond to the positional arguments of a call to a Python function? Can Py

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

Serhiy Storchaka added the comment: What kind of problem you want to solve? I'm sure there is a simple enough solution without changing itertools objects. -- ___ Python tracker

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

Neil Girdhar added the comment: My suggestion is then to update collection.abc to have an InfiniteSequence, which inherits from Iterable, and adds abstract methods __getitem__ and mixin methods __iter__. Then, itertools count, cycle, and repeat could implement collection.abc.InfiniteSequence,

[issue16532] AMD64 Windows 7 build failures

Antoine Pitrou added the comment: Ah, thank you! There is a test failure on 3.2, but it's probably unrelated. -- resolution: -> fixed status: open -> closed ___ Python tracker _

[issue16519] site.venv() should use abspath(executable)

Roundup Robot added the comment: New changeset fe2200c1c2d3 by Vinay Sajip in branch '3.3': Issue #16519: Used os.path.abspath, removed unnecessary code for executable_name. http://hg.python.org/cpython/rev/fe2200c1c2d3 New changeset a874c4a6ad5f by Vinay Sajip in branch 'default': Closes #1651

[issue16543] Use "positional arguments" in PyArg_UnpackTuple

Chris Jerdonek added the comment: > Here we're using 'positional' to refer to parameters that PEP 362 calls > "POSITIONAL_ONLY", whereas the regular TypeErrors (e.g. produced for > user-defined functions) use 'positional' to mean what PEP 362 calls > "POSITIONAL_OR_KEYWORD". Here the error me

[issue4473] POP3 missing support for starttls

Antoine Pitrou added the comment: Patches committed. Thank you very much! -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker

[issue4473] POP3 missing support for starttls

Roundup Robot added the comment: New changeset 79e33578dc05 by Antoine Pitrou in branch 'default': Issue #4473: Ensure the socket is shutdown cleanly in POP3.close(). http://hg.python.org/cpython/rev/79e33578dc05 New changeset d30fd9834cec by Antoine Pitrou in branch 'default': Issue #4473: Add

[issue16306] Multiple error line for unknown command line parameter

Ezio Melotti added the comment: Buildbots are happy, closing. Thanks Serhiy for the patches! -- status: open -> closed ___ Python tracker ___

[issue4473] POP3 missing support for starttls

Antoine Pitrou added the comment: Thank you Lorenzo. Your patch lacks a couple of details, such as "versionadded" and "versionchanged" tags, but I can handle this myself. -- ___ Python tracker _

[issue16543] Use "positional arguments" in PyArg_UnpackTuple

Changes by Chris Jerdonek : -- nosy: +chris.jerdonek ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue16543] Use "positional arguments" in PyArg_UnpackTuple

Ezio Melotti added the comment: > Okay, but what exactly is this fixing? If the function parses positional args, it should say so in the error message. If the function is never used (except for min/max) or if the error is never reported, then we have a different problem. Even if this code i

[issue16543] Use "positional arguments" in PyArg_UnpackTuple

Mark Dickinson added the comment: > If there are no such cases I think we should fix it. Okay, but what exactly is this fixing? I can't find any examples apart from max and min where the new error messages seem any better than the old. Your first message talks about "a function that receives

[issue16528] 3.2 docs not updating on docs.python.org

Changes by Chris Jerdonek : -- keywords: +easy resolution: invalid -> fixed type: behavior -> enhancement ___ Python tracker ___ ___ P

[issue16528] 3.2 docs not updating on docs.python.org

Roundup Robot added the comment: New changeset 31bb42754962 by Chris Jerdonek in branch 'default': Clarify that only the latest maintenance branches are rebuilt (issue #16528). http://hg.python.org/devguide/rev/31bb42754962 -- nosy: +python-dev ___ Py

[issue16543] Use "positional arguments" in PyArg_UnpackTuple

Mark Dickinson added the comment: One more thing: I'm not sure this is the right terminology. Here we're using 'positional' to refer to parameters that PEP 362 calls "POSITIONAL_ONLY", whereas the regular TypeErrors (e.g. produced for user-defined functions) use 'positional' to mean what PEP

[issue16543] Use "positional arguments" in PyArg_UnpackTuple

Ezio Melotti added the comment: > do you know of any other cases where this gives a misleading error message? Actually my concern was about cases where the new error might be wrong/misleading, but I haven't checked yet. If there are no such cases I think we should fix it; the error message wi

[issue16543] Use "positional arguments" in PyArg_UnpackTuple

Mark Dickinson added the comment: Of course, the 'arguments' -> 'argument' fix would still be nice to have. -- ___ Python tracker ___

[issue16543] Use "positional arguments" in PyArg_UnpackTuple

Mark Dickinson added the comment: Now that I look at uses of PyArg_UnpackTuple, I'm wondering whether this needs to be fixed at all. Apart from `max` and `min`, do you know of any other cases where this gives a misleading error message? Almost all the uses I can find are for simple functions/

[issue16523] attrgetter and itemgetter signatures in docs need cleanup

Chris Jerdonek added the comment: You can also make that distinction using *. For example: .. function:: attrgetter(attr, *attrs) or .. function:: attrgetter(attr) attrgetter(attr1, attr2, *attrs) (cf. http://docs.python.org/dev/library/functions.html#max ) Elsewhere we starte

[issue16543] Use "positional arguments" in PyArg_UnpackTuple

Serhiy Storchaka added the comment: > +(min == 1 ? "" : "s"), l); In second part of patch should be "max". Reformat the code so that `min` and `(min == 1 ? "" : "s")` will be in one line and it will be more clear. -- nosy: +serhiy.storchaka

[issue16543] Use "positional arguments" in PyArg_UnpackTuple

Changes by Mark Dickinson : -- nosy: +mark.dickinson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue16515] TypeError message incorrect for max() with one keyword arg

Ezio Melotti added the comment: I created #16543 for PyArg_UnpackTuple. Once that is fixed we can continue with this. -- dependencies: +Use "positional arguments" in PyArg_UnpackTuple ___ Python tracker ___

[issue16523] attrgetter and itemgetter signatures in docs need cleanup

Ezio Melotti added the comment: I thought about that, but wanted to make a distinction between the form that accepts only 1 arg and returns an item and the form that receives 2+ args and returns a tuple. -- nosy: +ezio.melotti ___ Python tracker

[issue16543] Use "positional arguments" in PyArg_UnpackTuple

New submission from Ezio Melotti: This came up in #16515. While using PyArg_UnpackTuple to parse the positional arguments in a function that receives both positional and keyword arguments, the error message returned when the number of arguments is incorrect is misleading, e.g.: >>> max(foo=1) T

[issue16523] attrgetter and itemgetter signatures in docs need cleanup

Chris Jerdonek added the comment: +.. function:: attrgetter(attr[, attr2, attr3, ...]) Why not reword to use the *attr notation? It is even already being used below: + The function is equivalent to:: def attrgetter(*items): if any(not isinstance(item, str) for item in ite

[issue16539] Turn off 'No handlers could be found for logger' message

Amaury Forgeot d'Arc added the comment: Python 3 has exactly the same documentation: http://docs.python.org/3.3/howto/logging.html#configuring-logging-for-a-library -- nosy: +amaury.forgeotdarc resolution: wont fix -> works for me status: languishing -> closed __

[issue16541] tk_setPalette doesn't accept keyword parameters

Guilherme Polo added the comment: If doing list(kw.items()) works, I'm fine with that. If it does not, then ttk._format_optdict(kw) should. -- ___ Python tracker ___ ___

[issue16531] Allow IPNetwork to take a tuple

Changes by Ezio Melotti : -- keywords: +easy nosy: +ezio.melotti stage: -> needs patch ___ Python tracker ___ ___ Python-bugs-list ma

[issue16530] documentation of os.wait3

Ezio Melotti added the comment: Fixed, thanks for the report! -- assignee: docs@python -> ezio.melotti nosy: +ezio.melotti resolution: -> fixed stage: -> committed/rejected status: open -> closed versions: -Python 2.6, Python 3.1 ___ Python tracker

[issue16530] documentation of os.wait3

Roundup Robot added the comment: New changeset a2038edb51cd by Ezio Melotti in branch '2.7': #16530: the "options" arg of os.wait3 is required. http://hg.python.org/cpython/rev/a2038edb51cd New changeset 1cf1194a443e by Ezio Melotti in branch '3.2': #16530: the "options" arg of os.wait3 is requi

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

Serhiy Storchaka added the comment: > Apologies if this is a bad question, but why do count, cycle, and repeat > return iterators rather than iterables? Actually they are iterables too. -- ___ Python tracker

[issue16542] http//bugs.python/joko.suwito

Changes by Ezio Melotti : -- resolution: -> invalid stage: -> committed/rejected status: open -> closed ___ Python tracker ___ ___ P

[issue16523] attrgetter and itemgetter signatures in docs need cleanup

Changes by Ezio Melotti : -- keywords: +patch nosy: +chris.jerdonek stage: needs patch -> patch review versions: +Python 3.2 Added file: http://bugs.python.org/file28089/issue16523.diff ___ Python tracker _

[issue16541] tk_setPalette doesn't accept keyword parameters

Serhiy Storchaka added the comment: There are two ways to fix this issue: 1. Fix tk_setPalette() (just wrap kw.items() with list() or tuple()). 2. Fix C implementation of _flatten() for work with any iterators. -- nosy: +gpolo, serhiy.storchaka stage: -> needs patch type: compile error

[issue16542] http//bugs.python/joko.suwito

New submission from joko suwito: thank you -- messages: 176194 nosy: joko.suwito priority: normal severity: normal status: open title: http//bugs.python/joko.suwito ___ Python tracker __

[issue16541] tk_setPalette doesn't accept keyword parameters

New submission from Helmut Jarausch: import tkinter as Tk root= Tk.Tk() root.tk_setPalette(background = 'AntiqueWhite1', foreground = 'blue') but python-3.3:0+ (3.3:27cb1a3d57c8+) gives Traceback (most recent call last): File "Matr_Select.py", line 174, in root.tk_setPalette(background =

[issue16488] Add context manager support to epoll object

Andrew Svetlov added the comment: +0 for patch -- nosy: +asvetlov ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue16539] Turn off 'No handlers could be found for logger' message

anatoly techtonik added the comment: I'd say this is a pretty valid issue with "won't fix" or "workaround available" resolution. The question - is the same behavior preserved for Python 3? -- resolution: invalid -> wont fix status: closed -> languishing ___

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

Éric Araujo added the comment: The point of itertools is to implement building blocks for iterators, which are memory-efficient and can sometimes be infinite, contrary to sequences. -- nosy: +eric.araujo ___ Python tracker

[issue16518] add "buffer protocol" to glossary

Changes by Ezio Melotti : -- stage: -> needs patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue16509] sqlite3 docs do not explain check_same_thread

Changes by Ezio Melotti : -- nosy: +ghaering stage: -> needs patch versions: +Python 3.2, Python 3.4 ___ Python tracker ___ ___ Pytho

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

Changes by Ezio Melotti : -- stage: -> needs patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue16477] tarfile fails to close file handles in case of exception

Andrew Svetlov added the comment: LGTM -- nosy: +asvetlov ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue16519] site.venv() should use abspath(executable)

Changes by Éric Araujo : -- nosy: +eric.araujo, vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: htt

[issue16526] Python does not cross compile properly

Éric Araujo added the comment: See also: http://bugs.python.org/issue3754 cross-compilation support for python build http://bugs.python.org/issue1006238 cross compile patch http://bugs.python.org/issue1597850 Cross compiling patches for MINGW (superseder of http://bugs.python.org/issue1

  1   2   >