[issue26523] multiprocessing ThreadPool is untested

Serhiy Storchaka added the comment: LGTM. Is it worth to change multiprocessing.Pool in _TestPoolWorkerErrors and _TestPoolWorkerLifetime? Currently they work only for processes, but may be they can be generalized. -- nosy: +serhiy.storchaka ___

[issue26509] spurious ConnectionAbortedError logged on Windows

Sebastien Bourdeauducq added the comment: Your patch seems to miss the ``_fatal_error`` method in ``proactor_events.py`` (which is actually where the bug happens in my application - it's using ``ProactorEventLoop``). -- ___ Python tracker

[issue26523] multiprocessing ThreadPool is untested

Changes by Ned Deily : -- nosy: +davin ___ Python tracker ___ ___ Python-bugs-list mailing

[issue26322] Missing docs for typing.Set

Joseph Moran added the comment: Deleted second ABSTRACTSET and added SET in typing docs -- nosy: +joegotflow83 Added file: http://bugs.python.org/file42109/26322 ___ Python tracker

[issue26396] Create json.JSONType

Changes by Jakub Stasiak : -- nosy: +jstasiak ___ Python tracker ___ ___

[issue26506] hex() documentation: mention "%x" % int

STINNER Victor added the comment: > Ah, but it's not that format() is slower in 3.5, but that %-formatting got > faster. Hum, python3 looks faster on this dummy microbenchmark yeah. Who said that Python 3 is slower? :-) $ python2 -m timeit -s 'import random; nums = [random.randint(0, 255)

[issue20211] setup.py: do not add invalid header locations

Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___

[issue26506] hex() documentation: mention "%x" % int

Wolfgang Maier added the comment: Ah, but it's not that format() is slower in 3.5, but that %-formatting got faster. It looks as if it got optimized and I was wondering whether the same optimization could be applied to format(). -- ___ Python

[issue26506] hex() documentation: mention "%x" % int

Eric V. Smith added the comment: Without lots of analysis (and disassembly), I can't speak to how valid your tests are, but they don't seem unreasonable. format() will always be slower, because it's more general (primarily in that it can be extended to new types). Plus, it involves at least a

[issue26522] pickle.whichmodule(object.__new__, None) = 'email.MIMEAudio'

Changes by Serhiy Storchaka : -- stage: -> resolved status: open -> closed ___ Python tracker ___

[issue26506] hex() documentation: mention "%x" % int

Wolfgang Maier added the comment: Your two suggestions prompted me to do a speed comparison between them and the result surprised me. I tried: import random nums = [random.randint(0, 255) for n in range(1000)] then timed the simple: for n in nums: hx = '%X' % n # or hx = format(n,

[issue26524] document what config directory is used for

New submission from John Beck: Solaris ships Python versions 2.7, 3.4 and 3.5 at present. For 2.7, we ship both 32-bit and 64-bit versions; for 3.4 and 3.5 we only ship 64-bit versions. For 2.7, we ship /usr/lib/python2.7/config/ with the usual suspects (Makefile, Setup.config, config.c,

[issue26523] multiprocessing ThreadPool is untested

Antoine Pitrou added the comment: Turns out a couple of tests were calling multiprocessing.Pool directly, updating patch. -- Added file: http://bugs.python.org/file42108/test_threadpool2.patch ___ Python tracker

[issue26520] asyncio.new_event_loop() hangs

Guido van Rossum added the comment: Closing the loop is not taken care of by GC, so I would start there. AFAIK that's covered by the docs, but if you think the docs could be clearer please do submit a separate issue with a documentation update (you can easily submit a patch for that!). It would

[issue26523] multiprocessing ThreadPool is untested

New submission from Antoine Pitrou: There is a mistake in _test_multiprocessing.py which means that ThreadPool is untested, the regular Pool is tested instead by the ThreadsMixin. Patch attached. -- components: Library (Lib), Tests files: test_threadpool.patch keywords: patch

[issue26520] asyncio.new_event_loop() hangs

Erwin Mayer added the comment: I understand that asyncio is not .NET and did my best to implement "by the book" according to the asyncio documentation I read extensively. My await_async function has in fact nothing in common with what I would do in .NET but is hopefully as close as possible to

[issue26521] add `extend_enum` to Enum

Serhiy Storchaka added the comment: To me, the essential property of enums in other languages is that there is known limited set of possible values. If this set is dynamically extended, this is not enum. -- nosy: +serhiy.storchaka ___ Python

[issue26522] pickle.whichmodule(object.__new__, None) = 'email.MIMEAudio'

Richard Futrell added the comment: Ah, I get the same result as you in a clean interpreter session. Looks like it's not Python's fault. The bug seems to arise from an interaction with cloudpickle 0.2.1 (and only in IPython), which puts the bad value into a cache somewhere in the pickle

[issue26499] http.client.IncompleteRead from HTTPResponse read after part reading file

SilentGhost added the comment: All the highlighted issue are now fixed. The limit on n in read1 wasn't tested. Your suggestion regarding testing went a bit over my head, Martin. So, just trying to make sure we're on the same page. ExtendedReadTest, where I thought placing these new tests, is

[issue26522] pickle.whichmodule(object.__new__, None) = 'email.MIMEAudio'

Serhiy Storchaka added the comment: I get other result: >>> import pickle >>> pickle.whichmodule(object.__new__, None) Traceback (most recent call last): File "", line 1, in File "/home/serhiy/py/cpython2.7/Lib/pickle.py", line 823, in whichmodule if name != '__main__' and

[issue26520] asyncio.new_event_loop() hangs

Guido van Rossum added the comment: Asyncio is not .NET. Don't assume that what's "by the book" according to .NET applies to asyncio. -- ___ Python tracker

[issue26520] asyncio.new_event_loop() hangs

Erwin Mayer added the comment: I simply need to run a coroutine synchronously (which may or may not have a loop parameter), so I tried to do it by the book. With .NET it is easy to call .Wait() on a Task (but .NET by default uses a threadpool, not a single-threaded event loop). I am

[issue26521] add `extend_enum` to Enum

Barry A. Warsaw added the comment: I was thrown off a bit by the description below. it's not that the OP wants to generate an Enum lazily (the functional API lets them do that), it's that the OP wants to *extend* an Enum lazily. Seems like a pretty obscure use case to me. I'd vote for

[issue26522] pickle.whichmodule(object.__new__, None) = 'email.MIMEAudio'

New submission from Richard Futrell: On Python 2.7.11, pickle.whichmodule(object.__new__, None) = 'email.MIMEAudio' This is unlikely to be the correct module. -- components: XML messages: 261465 nosy: canjobear priority: normal severity: normal status: open title:

[issue26521] add `extend_enum` to Enum

New submission from Ethan Furman: In this SO question [1] the OP has a need to generate an Enum lazily. I created an `extend_enum` function to do so. By the time I was done I realized I would not want anyone to have to create that function by hand, nor keep it up to date (should we ever

[issue26512] Vocabulary: Using "integral" in library/stdtypes.html

Alexander Belopolsky added the comment: > Can you provide a source ? How about a dictionary? For example, Oxford English Dictionary has """ integral, adj. and n. 4. Math. a. That is, or is denoted by, an integer, or involves only integers; consisting of a whole number or undivided

[issue26520] asyncio.new_event_loop() hangs

Guido van Rossum added the comment: Why are you creating a new event loop for this purpose? There are all sorts of things that can go wrong with that. This is not appropriate for a bug report, you should continue to seek help on StackOverflow. -- resolution: -> rejected status: open

[issue26520] asyncio.new_event_loop() hangs

Erwin Mayer added the comment: This cannot be a firewall issue as a loop can be successfully created thousands of time, for hours, before a creation attempt will hang (with no change from the firewall). The rest of the program (other threads) continues to run and there is memory issue. If I

[issue26519] Cython doesn't work anymore on Python 3.6

Serhiy Storchaka added the comment: Cython 0.23.4 was released at 2015-10-10. The fix was applied 2016-01-16. Try to use Cython from trunk. May be this is not exactly the same bug and Cython needs other fix. The change is deliberate. It helps to find existing bugs. Except trivial case when

[issue26249] Change PyMem_Malloc to use pymalloc allocator

Changes by Yury Selivanov : -- nosy: -Yury.Selivanov, yselivanov ___ Python tracker ___

[issue26249] Change PyMem_Malloc to use pymalloc allocator

STINNER Victor added the comment: 2016-03-09 18:28 GMT+01:00 Antoine Pitrou : > Does the API doc say anything about the GIL, for example? Or Valgrind? For the GIL, yes, Python 3 doc is explicit: https://docs.python.org/dev/c-api/memory.html#memory-interface Red and bold

[issue26249] Change PyMem_Malloc to use pymalloc allocator

STINNER Victor added the comment: cryptography: good * Git commit 0681de7241dcbaec7b3dc85d3cf3944e4bec8309 (Mar 9 2016) "4 failed, 77064 passed, 3096 skipped in 405.09 seconds" 1 error is related to the version number (probably an issue on how I run the tests), 3 errors are

[issue26249] Change PyMem_Malloc to use pymalloc allocator

Antoine Pitrou added the comment: Le 09/03/2016 18:27, STINNER Victor a écrit : > > I disagree on the fact that my change breaks any API. The API doc is clear. Does the API doc say anything about the GIL, for example? Or Valgrind? > I suggest you to continue the discussion on python-dev for a

[issue26249] Change PyMem_Malloc to use pymalloc allocator

STINNER Victor added the comment: > I'm talking about the performance improvement in third-party libraries, not > the performance improvement in CPython itself which can be addressed by > replacing the internal API calls. Oh ok. I don't know how to measure the performance of third-party

[issue26249] Change PyMem_Malloc to use pymalloc allocator

Antoine Pitrou added the comment: > Yes. It was discussed in the python-dev thread. I'm talking about the performance improvement in third-party libraries, not the performance improvement in CPython itself which can be addressed by replacing the internal API calls. --

[issue26249] Change PyMem_Malloc to use pymalloc allocator

STINNER Victor added the comment: > Define "slow". malloc() on Linux should be reasonably fast. See first messages of this issue for benchmark results. Some specific benchmarks are faster, none is slower. > Do you think it's reasonable to risk breaking external libraries just for a

[issue26249] Change PyMem_Malloc to use pymalloc allocator

Antoine Pitrou added the comment: Le 09/03/2016 18:01, STINNER Victor a écrit : > I don't understand why we should keep a slow allocator if Python has a faster > allocator? Define "slow". malloc() on Linux should be reasonably fast. Do you think it's reasonable to risk breaking external

[issue26249] Change PyMem_Malloc to use pymalloc allocator

STINNER Victor added the comment: Pillow: good Note: I had to install JPEG headers (sudo dnf install -y libjpeg-turbo-devel). Tested version: git commit 44c5cfc3874deaac9cfa87780822ee714c0d (Mar 8 2016). --- Pillow$ python setup.py install Pillow$ python selftest.py Pillow$ python

[issue26513] platform.win32_ver() broken in 2.7.11

Steve Dower added the comment: That's what I initially assumed, but when I looked in my 2.7 repo those changes weren't there. But according to the bug I checked them in, so I guess it is my fault. Looking at the diff (e.g. 2f57270374f7), it seems I got sucked in by following the old code

[issue26249] Change PyMem_Malloc to use pymalloc allocator

STINNER Victor added the comment: Antoine Pitrou added the comment: > Victor, why do you insist on this instead of changing internal API calls in > CPython? https://mail.python.org/pipermail/python-dev/2016-February/143097.html "There are 536 calls to the functions PyMem_Malloc(),

[issue26249] Change PyMem_Malloc to use pymalloc allocator

STINNER Victor added the comment: lxml: good! * I patched Python 3.6 with pymem.patch of this issue + pymem-3.patch of issue #26516 * Tested lxml version: git commit 93ec66f6533995a7742278f9ba14b925149ac140 (Mar 8 2016) lxml$ make test (...) Ran 1735 tests in 27.663s OK --

[issue26249] Change PyMem_Malloc to use pymalloc allocator

Antoine Pitrou added the comment: > "There are 536 calls to the functions PyMem_Malloc(), PyMem_Realloc() and PyMem_Free()." I'm sure you can use powerful tools such as "sed" ;-) -- ___ Python tracker

[issue26249] Change PyMem_Malloc to use pymalloc allocator

STINNER Victor added the comment: > I'm sure you can use powerful tools such as "sed" ;-) I guess that PyMem functions are used in third party C extensions modules. I expect (minor) speedup in these modules too. I don't understand why we should keep a slow allocator if Python has a faster

[issue26249] Change PyMem_Malloc to use pymalloc allocator

STINNER Victor added the comment: numpy: good! * I patched Pyhon 3.6 with pymem.patch of this issue + pymem-3.patch of issue #26516 * I had issues to run tests with Python 3.6 compiled in debug mode: http://bugs.python.org/issue26519 & https://github.com/numpy/numpy/issues/7399 * I ran the

[issue26249] Change PyMem_Malloc to use pymalloc allocator

Antoine Pitrou added the comment: Victor, why do you insist on this instead of changing internal API calls in CPython? -- ___ Python tracker ___

[issue26519] Cython doesn't work anymore on Python 3.6

STINNER Victor added the comment: > This was a bug in Cython and it is fixed now. If the change is deliberate, can you please mention it in "What's New in Python 3.6" doc? Especially in the "Porting to Python 3.6" section: https://docs.python.org/dev/whatsnew/3.6.html#porting-to-python-3-6

[issue26520] asyncio.new_event_loop() hangs

STINNER Victor added the comment: Do you have a firewall? Maybe the firewall blocks programs listening on sockets? It would be silly, the socket is only listening on 127.0.0.1 (local link) (or ::1 in IPv6, also local link). Extract of the socketpair() function: try:

[issue26519] Cython doesn't work anymore on Python 3.6

STINNER Victor added the comment: "May be this is the same issue as reported in msg257646. This was a bug in Cython and it is fixed now." Oh, I wasn't aware of the issue #22995. I will read it. The bug isn't fixed yet in the latest release of Cython (0.23.4, released at 2015-10-10). I guess

[issue26519] Cython doesn't work anymore on Python 3.6

Serhiy Storchaka added the comment: May be this is the same issue as reported in msg257646. This was a bug in Cython and it is fixed now. -- nosy: +scoder ___ Python tracker

[issue26520] asyncio.new_event_loop() hangs

New submission from Erwin Mayer: I am using the following function to force a coroutine to run synchronously: def await_sync(coro: types.CoroutineType, timeout_s: int=None): """ :param coro: a coroutine or lambda loop: coroutine(loop) :param timeout_s: :return: """ loop

[issue26512] Vocabulary: Using "integral" in library/stdtypes.html

Julien added the comment: > It could be made into a link like the other use of Integral. I'll propose a patch. > The other uses are "integral float", which is *not* the same as an integer. > It is a float whose value is a whole number, and AFAIK "integral" is the > correct adjective for

[issue26519] Cython doesn't work anymore on Python 3.6

STINNER Victor added the comment: Oops, my commands to reproduce the bug were wrong. Commands to reproduce the bug: --- tar -xf mtrand.tar.gz # download mtrand.tar.gz attached to this issue ./python -m venv ENV ENV/bin/python -m pip install cython ENV/bin/python ENV/bin/cython --fast-fail

[issue26519] Cython doesn't work anymore on Python 3.6

New submission from STINNER Victor: I tried to run numpy test suite on Python 3.6 compiled in debug mode. I got an assertion error. Then I wanted to try the Git version of numpy, but the "Cythonizing sources" step of the numpy installer fails with: --- Traceback (most recent call last): File

[issue26512] Vocabulary: Using "integral" in library/stdtypes.html

Georg Brandl added the comment: There's two different uses here: The one use in "truncated to Integral" means that you get an integer type out. It is not specified to be `int` because `__trunc__` may return other types. It could be made into a link like the other use of Integral. The other

[issue20211] setup.py: do not add invalid header locations

Martin Hundebøll added the comment: The patch looks good to me, and works in my setup. -- nosy: +hundeboll ___ Python tracker ___

[issue26443] cross building extensions picks up host headers

Changes by Berker Peksag : -- stage: -> resolved superseder: -> setup.py: do not add invalid header locations ___ Python tracker

[issue26443] cross building extensions picks up host headers

Martin Hundebøll added the comment: Yes, it is a duplicate of #20211, and I agree with the fix proposed in there. Thanks for pointing it out. -- resolution: -> duplicate status: open -> closed ___ Python tracker

[issue26249] Change PyMem_Malloc to use pymalloc allocator

STINNER Victor added the comment: In february 2016, I started a thread on the python-dev mailing list: [Python-Dev] Modify PyMem_Malloc to use pymalloc for performance https://mail.python.org/pipermail/python-dev/2016-February/143084.html M.-A. Lemburg wrote: """ > Do you see any drawback of

[issue26249] Change PyMem_Malloc to use pymalloc allocator

Changes by STINNER Victor : Removed file: http://bugs.python.org/file42103/pymem-3.patch ___ Python tracker ___

[issue26516] Add PYTHONMALLOC env var and add support for malloc debug hooks in release mode

STINNER Victor added the comment: Patch 3: - Ooops, I updated pymem_api_misuse(), but I forgot to update the related unit test. It's now fixed. -- Added file: http://bugs.python.org/file42104/pymem-3.patch ___ Python tracker

[issue26249] Change PyMem_Malloc to use pymalloc allocator

STINNER Victor added the comment: Patch 3: - Ooops, I updated pymem_api_misuse(), but I forgot to update the related unit test. It's now fixed. -- Added file: http://bugs.python.org/file42103/pymem-3.patch ___ Python tracker

[issue26249] Change PyMem_Malloc to use pymalloc allocator

STINNER Victor added the comment: I created the issue #26516 "Add PYTHONMALLOC env var and add support for malloc debug hooks in release mode" to help developers to detect bugs in their code, especially misuse of the PyMem_Malloc() API. -- ___

[issue26516] Add PYTHONMALLOC env var and add support for malloc debug hooks in release mode

STINNER Victor added the comment: When I wrote the PEP 445, I already proposed to add a new environment variable to install debug hooks on a Python compiled in release mode: https://www.python.org/dev/peps/pep-0445/#add-a-new-pydebugmalloc-environment-variable But the proposition was rejected

[issue26249] Change PyMem_Malloc to use pymalloc allocator

Changes by STINNER Victor : -- title: Change PyMem_Malloc to use PyObject_Malloc allocator? -> Change PyMem_Malloc to use pymalloc allocator ___ Python tracker

[issue26516] Add PYTHONMALLOC env var and add support for malloc debug hooks in release mode

STINNER Victor added the comment: More complete patch (version 2): * Document PYTHONMALLOC environment variable * Add PYTHONMALLOC=debug to install debug hooks without forcing a specific memory allocator (keep the default memory allocator) * Fix sys._debugmallocstats() for PYTHONMALLOC=malloc:

[issue26516] Add PYTHONMALLOC env var and add support for malloc debug hooks in release mode

Changes by Serhiy Storchaka : -- stage: -> patch review ___ Python tracker ___ ___

[issue26415] Fragmentation of the heap memory in the Python parser

Changes by Serhiy Storchaka : -- stage: -> patch review ___ Python tracker ___ ___

[issue26415] Fragmentation of the heap memory in the Python parser

A. Skrobov added the comment: The attached patch for the parser reduces "Maximum resident set size (kbytes)" threefold, for the degenerate example of 'import ast; ast.parse("0,"*100, mode="eval")', by eliminating many CST nodes that have a single child. According to the comment in node.c

[issue26494] Double deallocation on iterator exhausting

Serhiy Storchaka added the comment: It crashes in debug build. -- ___ Python tracker ___ ___ Python-bugs-list

[issue26516] Add PYTHONMALLOC env var and add support for malloc debug hooks in release mode

Roundup Robot added the comment: New changeset af2fc10f703b by Victor Stinner in branch '3.5': Issue #26516: Enhance Python mem allocators doc https://hg.python.org/cpython/rev/af2fc10f703b -- nosy: +python-dev ___ Python tracker

[issue26517] Crash in installer

Steve Dower added the comment: Do you have any more details about this? A log file perhaps? With the current information there's nothing we can do to help you. -- ___ Python tracker

[issue26518] AttributeError: 'module' object has no attribute '_handlerList'

Berker Peksag added the comment: This doesn't look like an issue with the Python standard library. I think you should report this to pip. Also, why are you installing logging module on Python 2.7? The PyPI version of logging module is very old (last updated 2005). -- nosy:

[issue26518] AttributeError: 'module' object has no attribute '_handlerList'

New submission from Jools: AttributeError: 'module' object has no attribute '_handlerList' when trying to install any packages with pip. This one is with trying to install the logging package: http://pastebin.com/TCUpUMYn -- components: Library (Lib) messages: 261422 nosy: jools

[issue26517] Crash in installer

New submission from Jools: Crash when installing python 2.7.11 x64 edition out of the box. x86 version works. I chose to install for all users, and the system has write permissions to the folder (C:\bin\python27). -- components: Windows messages: 261421 nosy: jools, paul.moore,

[issue26494] Double deallocation on iterator exhausting

Filipp Andjelo added the comment: Hi Serhiy, I tried the short example you gave, but it doesn't crash. I'm getting: Exception ignored in: Traceback (most recent call last): File "./test.py", line 5, in __del__ next(it) StopIteration Exception ignored in: Traceback (most recent call

[issue26504] tclErr: invalid command name "PyAggImagePhoto"

Roger Mosher added the comment: It appears to be a problem with the Anaconda 3 distribution. See: https://groups.google.com/a/continuum.io/forum/#!topic/anaconda/xssOnleIPFw for a discussion. -- status: open -> closed ___ Python tracker

[issue25458] ftplib: command response shift - mismatch

Peter Pan added the comment: Here is a small test for the new version. (To see the original ftplib.py version failing copy+paste the code from my initial post into a python file and run) -- Added file: http://bugs.python.org/file42100/test_ftp.py

[issue25458] ftplib: command response shift - mismatch

Peter Pan added the comment: I've updated "ftplib.py" from the 3.5.1 source code release. This should fix issues: http://bugs.python.org/issue25458 http://bugs.python.org/issue25491 -- Added file: http://bugs.python.org/file42099/ftplib.py ___

[issue26516] Add PYTHONMALLOC env var and add support for malloc debug hooks in release mode

STINNER Victor added the comment: The motivation to support PYTHONMALLOC=malloc (always use malloc) and not just PYTHONMALLOC=debug (enable debug hooks) is to allow to use external memory debugger like Valgrind. Valgrind doesn't like pymalloc (pymalloc raises false alarms), we had to a

[issue26516] Add PYTHONMALLOC env var and add support for malloc debug hooks in release mode

STINNER Victor added the comment: Example with Python compiled in release mode. By default, a buffer overflow is not detected. It may crash later, in a random place... $ ./python -c 'import _testcapi; _testcapi.pymem_buffer_overflow()' Enabling debug hooks detects the buffer overflow

[issue26516] Add PYTHONMALLOC env var and add support for malloc debug hooks in release mode

STINNER Victor added the comment: The output of sys._debugmallocstats() contains different info: * Stats of type free lists * pymalloc stats * number of calls to memory allocators The available info depends on: * pymalloc disabled at compilation with ./configure --without-pymalloc * pymalloc

[issue26516] Add PYTHONMALLOC env var and add support for malloc debug hooks in release mode

New submission from STINNER Victor: Attached patch: - Add PYTHONMALLOC env var which accepts 4 values: * pymalloc: use pymalloc for PyObject_Malloc(), malloc for PyMem_Malloc() and PyMem_RawMalloc() * pymalloc_debug: pymalloc + debug hooks * malloc: use malloc for PyObject_Malloc(),

[issue9998] ctypes find_library should search LD_LIBRARY_PATH on linux

Pau Tallada added the comment: Any progress on this? It also affects installation of rtree (https://github.com/Toblerity/rtree/issues/56) -- nosy: +Pau Tallada ___ Python tracker

[issue26387] Crash calling sqlite3_close with invalid pointer

Filipp Andjelo added the comment: The issue26494 seems really suspicious, could be our case. And regarding my patch, nice to know, you are the same opinion. However, the code there is looking very strange. I really don't understand, why there are mutex guards anyway, since close() can only be

[issue26513] platform.win32_ver() broken in 2.7.11

Serhiy Storchaka added the comment: May be this is related to issue19143. -- nosy: +serhiy.storchaka ___ Python tracker ___

[issue26499] http.client.IncompleteRead from HTTPResponse read after part reading file

Martin Panter added the comment: Yes I agree it would be best to fix the bug(s) without major refactoring if practical. To fix the other bug, I think the parameters in read1(n) and readline(limit) need to be capped at self.length. The inherited BufferedIOBase.readlines() implementation

[issue26508] Infinite crash leading to DoS

STINNER Victor added the comment: "Then it is no bug that it crashes python?" The bug is your program creating inconsistent data. Without ctypes, you cannot create such inconsistent data. "Is a crash not a bug?" There are various ways to "crash" Python, but most of them are deliberate bugs.

[issue26177] tkinter: Canvas().keys returns empty strings.

Changes by Serhiy Storchaka : -- resolution: -> fixed stage: commit review -> resolved status: open -> closed ___ Python tracker

[issue26177] tkinter: Canvas().keys returns empty strings.

Roundup Robot added the comment: New changeset d86891dee68a by Serhiy Storchaka in branch '3.5': Issue #26177: Fixed the keys() method for Canvas and Scrollbar widgets. https://hg.python.org/cpython/rev/d86891dee68a New changeset f0c895fb0374 by Serhiy Storchaka in branch '2.7': Issue #26177:

[issue26512] Vocabulary: Using "integral" in library/stdtypes.html

Julien added the comment: > In the contexts that you mentioned, "integral" is a synonym of "integer." Can you provide a source ? There's no mention of "integral" in the Wikipedia page of "integer" (but there's mentions of "integral element" and "integral domain" which are not synonyms for

[issue26499] http.client.IncompleteRead from HTTPResponse read after part reading file

SilentGhost added the comment: Here is the updated patch. I only included the additional fix for read1 since readlines is not overwritten in the HTTPConnection. Not sure how to write test for it, does it need a much longer body (compared to the one in tests) to produce this behaviour? The

[issue26513] platform.win32_ver() broken in 2.7.11

Florian Roth added the comment: Confirmed. Version 2.7.11 64bit is erroneous too. Version 2.7.10 64bit works fine. I added the 64bit version screenshots to the shared dropbox folder. I'll downgrade all my projects to version 2.7.10 as the OS version detection is essential for proper

[issue26513] platform.win32_ver() broken in 2.7.11

Florian Roth added the comment: I tested it on two different Windows 2008 R2 server systems. Same results. And I checked the issue by uninstalling 2.7.11 and installed 2.7.9 and 2.9.10 to verify. This means that not the system itself can be the problem. Please see screenshots:

[issue26513] platform.win32_ver() broken in 2.7.11

Florian Roth added the comment: Screenshot 2.7.9 and platform.win32_ver() -- Added file: http://bugs.python.org/file42095/Screen Shot 2016-03-08 at 19.05.38.png ___ Python tracker