[issue36109] test_descr fails on AMD64 Windows8 3.x buildbots

2019-02-25 Thread Pablo Galindo Salgado
Change by Pablo Galindo Salgado : -- Removed message: https://bugs.python.org/msg336608 ___ Python tracker <https://bugs.python.org/issue36109> ___ ___ Python-bug

[issue36109] test_descr fails on AMD64 Windows8 3.x buildbots

2019-02-25 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: Although 12044 fixes the problem, something a bit more fundamental may have changed. I have spent time investigating why this is happening and the problem is that in the line: self.assertEqual(c.attr, 1) Evil.__eq__ is invoked twice where before it

[issue36109] test_descr fails on AMD64 Windows8 3.x buildbots

2019-02-25 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: Although PR12004 fixes the problem, something a bit more fundamental may have changed. I have spent time investigating why this is happening and the problem is that in the line: self.assertEqual(c.attr, 1) Evil.__eq__ is invoked twice where before

[issue36109] test_descr fails on AMD64 Windows8 3.x buildbots

2019-02-25 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: Ok, actually this turns to be much easier: Sometimes __eq__ was also called twice but now as we use PyDict_GetItemWithError instead of PyDict_GetItem, if the extra __eq__ happens as a consequence of a dict lookup the error is ignored so that was the

[issue36109] test_descr fails on AMD64 Windows8 3.x buildbots

2019-02-25 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: New changeset ff3d39faa8aa28308cc5eae6843eaac514da8fd8 by Pablo Galindo (Serhiy Storchaka) in branch 'master': bpo-36109: Fix random test_descr failure. (GH-12044) https://github.com/python/cpython/commit/ff3d39faa8aa28308cc5eae6843eaa

[issue36109] test_descr fails on AMD64 Windows8 3.x buildbots

2019-02-25 Thread Pablo Galindo Salgado
Change by Pablo Galindo Salgado : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue36109] test_descr fails on AMD64 Windows8 3.x buildbots

2019-02-25 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: A lot of buildbots were failing for this test so a lot of them will become green after ff3d39faa8aa28308cc5eae6843eaac514da8fd8. -- ___ Python tracker <https://bugs.python.org/issue36

[issue36114] test_multiprocessing_spawn changes the execution environment

2019-02-25 Thread Pablo Galindo Salgado
New submission from Pablo Galindo Salgado : OK (skipped=32) Warning -- files was modified by test_multiprocessing_spawn Before: [] After: ['python.core'] https://buildbot.python.org/all/#/builders/168/builds/632/steps/4/logs/stdio -- components: Tests messages: 3

[issue36114] test_multiprocessing_spawn changes the execution environment

2019-02-25 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: Another failure: https://buildbot.python.org/all/#/builders/168/builds/633 -- ___ Python tracker <https://bugs.python.org/issue36

[issue36114] test_multiprocessing_spawn changes the execution environment

2019-02-25 Thread Pablo Galindo Salgado
Change by Pablo Galindo Salgado : -- nosy: +koobs -pablogsal ___ Python tracker <https://bugs.python.org/issue36114> ___ ___ Python-bugs-list mailing list Unsub

[issue36114] test_multiprocessing_spawn changes the execution environment

2019-02-25 Thread Pablo Galindo Salgado
Change by Pablo Galindo Salgado : -- nosy: +pablogsal ___ Python tracker <https://bugs.python.org/issue36114> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36115] test_ctypes leaks references and memory blocks

2019-02-25 Thread Pablo Galindo Salgado
New submission from Pablo Galindo Salgado : https://buildbot.python.org/all/#/builders/1/builds/515 OK (skipped=89) . test_ctypes leaked [72, 72, 72] references, sum=216 test_ctypes leaked [26, 26, 26] memory blocks, sum=78 2 tests failed again: test_ctypes test_inspect == Tests result

[issue36114] test_multiprocessing_spawn changes the execution environment

2019-02-25 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: PR12045 fixes this -- ___ Python tracker <https://bugs.python.org/issue36114> ___ ___ Python-bugs-list mailin

[issue36114] test_multiprocessing_spawn changes the execution environment

2019-02-25 Thread Pablo Galindo Salgado
Change by Pablo Galindo Salgado : -- Removed message: https://bugs.python.org/msg336620 ___ Python tracker <https://bugs.python.org/issue36114> ___ ___ Python-bug

[issue36115] test_ctypes leaks references and memory blocks

2019-02-25 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: PR12045 fixes this -- ___ Python tracker <https://bugs.python.org/issue36115> ___ ___ Python-bugs-list mailin

[issue36116] test_multiprocessing_spawn fails on AMD64 Windows8 3.x

2019-02-25 Thread Pablo Galindo Salgado
New submission from Pablo Galindo Salgado : test test_multiprocessing_spawn failed test_import (test.test_multiprocessing_spawn._TestImportStar) ... ok == FAIL: test_mymanager_context

[issue36116] test_multiprocessing_spawn fails on AMD64 Windows8 3.x

2019-02-25 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: It also fails on Windows 7: https://buildbot.python.org/all/#/builders/58/builds/1983/steps/3/logs/stdio -- ___ Python tracker <https://bugs.python.org/issue36

[issue36116] test_multiprocessing_spawn fails on AMD64 Windows8 3.x

2019-02-25 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: It seems that return code 3221225477 in Windows is: #define STATUS_ACCESS_VIOLATION ((NTSTATUS)0xC005L) so this is a segfault in the manager. -- nosy: +pitrou ___ Python tracker <ht

[issue36131] test.test_urllib2net.TimeoutTest ftp related tests fail due to ftp://www.pythontest.net/ being unavailable

2019-02-26 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: Several buildbots are failing due to this problem. Some examples: https://buildbot.python.org/all/#builders/33/builds/520 https://buildbot.python.org/all/#builders/72/builds/503 https://buildbot.python.org/all/#builders/78/builds/419

[issue36131] test.test_urllib2net.TimeoutTest ftp related tests fail due to ftp://www.pythontest.net/ being unavailable

2019-02-26 Thread Pablo Galindo Salgado
Change by Pablo Galindo Salgado : -- priority: normal -> high versions: +Python 2.7, Python 3.6, Python 3.7 ___ Python tracker <https://bugs.python.org/issu

[issue36131] test.test_urllib2net.TimeoutTest ftp related tests fail due to ftp://www.pythontest.net/ being unavailable

2019-02-27 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: Almost all buildbots have failed due to this issue. It seems that is fixed now: ❯ ./python.exe -m test -v test_urllib2net -u all == CPython 3.8.0a2+ (heads/master:d5a551c269, Feb 27 2019, 09:17:08) [Clang 10.0.0 (clang-1000.10.44.4)] == macOS-10.14.3

[issue36116] test_multiprocessing_spawn fails on AMD64 Windows8 3.x

2019-02-27 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: Adding Łukasz, as I think this is a release blocker (the Windows 8 and 7 multiprocessing module may be causing segfaults). -- nosy: +lukasz.langa priority: normal -> high ___ Python tracker <

[issue36131] test.test_urllib2net.TimeoutTest ftp related tests fail due to ftp://www.pythontest.net/ being unavailable

2019-02-27 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: That was my impression. -- ___ Python tracker <https://bugs.python.org/issue36131> ___ ___ Python-bugs-list mailin

[issue36155] ./python -m test -m test_gc fails

2019-02-28 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: It seems that some collection from some other test is happening between the three calls to get_objects: self.assertIn(l, gc.get_objects(generation=0)) self.assertNotIn(l, gc.get_objects(generation=1)) self.assertNotIn(l, gc.get_objects(generation=2

[issue36155] ./python -m test -m test_gc fails

2019-03-01 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: This may be more complicated that it seems as these two statements are true at the same time: l in gc.get_objects(generation=0) True p l in gc.get_objects(generation=2) True -- ___ Python tracker <ht

[issue36155] ./python -m test -m test_gc fails

2019-03-01 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: But this only happens when running the test suite as ./python.exe -m test -m test_gc -- ___ Python tracker <https://bugs.python.org/issue36

[issue36155] ./python -m test -m test_gc fails

2019-03-01 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: Ok, this is happening because there is a unittest.mock._ANY in the second generation. -- ___ Python tracker <https://bugs.python.org/issue36

[issue36155] ./python -m test -m test_gc fails

2019-03-01 Thread Pablo Galindo Salgado
Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +12122 stage: -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue36155] ./python -m test -m test_gc fails

2019-03-01 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: Yup, I was actually using: ./python.exe -m test test_asyncio test_gc -m test_gc when I found out thst the core cause was mock._ANY :) -- ___ Python tracker <https://bugs.python.org/issue36

[issue36155] ./python -m test -m test_gc fails

2019-03-01 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: New changeset d60a79a1015aa26ff7ee3166820ec43558911b60 by Pablo Galindo in branch 'master': bpo-36155: Check for identity on test_gc.test_get_objects (GH-12116) https://github.com/python/cpython/commit/d60a79a1015aa26ff7ee3166820ec4

[issue36155] ./python -m test -m test_gc fails

2019-03-01 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: Ok, this one has been fun :) Thanks for finding this one @xtreak! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue36155] ./python -m test -m test_gc fails

2019-03-01 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: Well, unless there was a bug on the gc, the only way the list l could be on both lists is if in one of them there was something that was saying that is equal to it. To confirm I checked what was equal to l in the second generation and I saw it was

[issue35808] Let's retire pgen

2019-03-01 Thread Pablo Galindo Salgado
Change by Pablo Galindo Salgado : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue35808] Let's retire pgen

2019-03-01 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: New changeset 1f24a719e7be5e49b876a5dc7daf21d01ee69faa by Pablo Galindo in branch 'master': bpo-35808: Retire pgen and use pgen2 to generate the parser (GH-11814) https://github.com/python/cpython/commit/1f24a719e7be5e49b876a5dc7daf21

[issue36114] test_multiprocessing_spawn dumps core in AMD64 FreeBSD CURRENT Shared custom

2019-03-03 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: After some investigation, this turns out to be more complicated, as this 'python.core' turns to be a core dumped from some of the processes spawned by test_multiprocessing_spawn. So the real problem is that test_multiprocessing_spawn segfau

[issue36116] test_multiprocessing_spawn fails on AMD64 Windows8 3.x

2019-03-03 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: See also https://bugs.python.org/issue36114 -- ___ Python tracker <https://bugs.python.org/issue36116> ___ ___ Pytho

[issue36114] test_multiprocessing_spawn dumps core in AMD64 FreeBSD CURRENT Shared custom

2019-03-03 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: I managed to access the core file and this is the traceback: Thread 3 (LWP 100629): #0 0x0008007d4828 in _accept4 () from /lib/libc.so.7 #1 0x000800672eda in ?? () from /lib/libthr.so.3 #2 0x0008016f7b75 in ?? () #3 0x000800acca10

[issue36114] test_multiprocessing_spawn dumps core in AMD64 FreeBSD CURRENT Shared custom

2019-03-03 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: Apparently is the Thread 1 the one that is causing the core dump -- nosy: +pitrou, vstinner ___ Python tracker <https://bugs.python.org/issue36

[issue36114] test_multiprocessing_spawn dumps core in AMD64 FreeBSD CURRENT Shared custom

2019-03-03 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: This is the state of the thread interpreter: gdb) p tstate $3 = (PyThreadState *) 0x80262ba10 (gdb) p tstate->interp $4 = (PyInterpreterState *) 0xdbdbdbdbdbdbdbdb -- ___ Python tracker <

[issue36114] test_multiprocessing_spawn dumps core in AMD64 FreeBSD CURRENT Shared 3.x

2019-03-04 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: Interesting, I tried several hours to reproduce the crash on the buildbot itself manually and I could not do it. -- ___ Python tracker <https://bugs.python.org/issue36

[issue36114] test_multiprocessing_spawn dumps core in AMD64 FreeBSD CURRENT Shared 3.x

2019-03-04 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: Can you paste traceback of the dump that you were able to generate in your FreeBSD? I wonder if you can get the symbols that the one I pasted were missing (likely in libthr.so). -- ___ Python tracker

[issue36183] test_gdb failed on AMD64 FreeBSD CURRENT Shared 3.7 and 3.x

2019-03-04 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: Koobs recently installed gdb on the buildbot to debug some of the recent race conditions. This is very likely to have caused some problems with the test suite. -- ___ Python tracker <ht

[issue36183] test_gdb failed on AMD64 FreeBSD CURRENT Shared 3.7 and 3.x

2019-03-04 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: I think the solution here is uninstalling gdb from the buildbot. I have emailed Kubilay to see if he can revert the gdb installation to check if this is what is causing the problems. -- ___ Python tracker

[issue11614] import __hello__ is broken in Python 3

2019-03-07 Thread Pablo Galindo Salgado
Change by Pablo Galindo Salgado : -- nosy: +pablogsal ___ Python tracker <https://bugs.python.org/issue11614> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36236] Python crash on macOS when CWD is invalid

2019-03-08 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: This is happening because _Py_wgetcwd returns NULL (although the underliying getcwd system call populates the `fullpath` variable correctly) but its caller, _PyPathConfig_ComputeArgv0, does not check the return value: _Py_wgetcwd(fullpath

[issue36236] Python crash on macOS when CWD is invalid

2019-03-08 Thread Pablo Galindo Salgado
Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +12224 stage: -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue36256] parser module fails on legal input

2019-03-11 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: > I would be curious to hear what Pablo has to say with the new parser having > landed and if there's something we should be exposing from that code to > replace what's in 'parser' today? (Either w/o semantic change

[issue36229] Linear-time list, set, and bytearray ops.

2019-03-11 Thread Pablo Galindo Salgado
Change by Pablo Galindo Salgado : -- nosy: +pablogsal ___ Python tracker <https://bugs.python.org/issue36229> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35715] ProcessPool workers hold onto return value of last task in memory

2019-03-16 Thread Pablo Galindo Salgado
Change by Pablo Galindo Salgado : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue35715] ProcessPool workers hold onto return value of last task in memory

2019-03-16 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: New changeset 962bdeab191ee64459caa199209331005797ea7a by Pablo Galindo (Dave Chevell) in branch 'master': bpo-35715: Liberate return value of _process_worker (GH-11514) https://github.com/python/cpython/commit/962bdeab191ee64459caa199209331

[issue35493] multiprocessing.Pool._worker_handler(): use SIGCHLD to be notified on worker exit

2019-03-16 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: New changeset 7c994549dcffd0d9d3bb37475e6374f356e7240e by Pablo Galindo in branch 'master': bpo-35493: Use Process.sentinel instead of sleeping for polling worker status in multiprocessing.Pool (#11488) https://github.com/python/cpyt

[issue35493] multiprocessing.Pool._worker_handler(): use SIGCHLD to be notified on worker exit

2019-03-16 Thread Pablo Galindo Salgado
Change by Pablo Galindo Salgado : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue36332] compile() error on AST object with assignment expression

2019-03-18 Thread Pablo Galindo Salgado
Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +12353 stage: -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue36332] compile() error on AST object with assignment expression

2019-03-18 Thread Pablo Galindo Salgado
Change by Pablo Galindo Salgado : -- nosy: +pablogsal ___ Python tracker <https://bugs.python.org/issue36332> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36332] compile() error on AST object with assignment expression

2019-03-18 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: New changeset 0c9258a6d299e0484538ef8d4b23f30515283db2 by Pablo Galindo in branch 'master': bpo-36332: Allow compile() to handle AST objects with assignment expressions (GH-12398) https://github.com/python/cpyt

[issue36332] compile() error on AST object with assignment expression

2019-03-18 Thread Pablo Galindo Salgado
Change by Pablo Galindo Salgado : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue36236] Python crash on macOS when CWD is invalid

2019-03-18 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: If we set argv0 to ".": if (_Py_wgetcwd(fullpath, Py_ARRAY_LENGTH(fullpath))) { argv0 = fullpath; n = wcslen(argv0); } else { argv0 = L".";

[issue36236] Python crash on macOS when CWD is invalid

2019-03-18 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: Yup. But what is the best way to signal the caller that _PyPathConfig_ComputeArgv0 has failed because _Py_wgetcwd has failed without changing the API massively? Right now if _PyPathConfig_ComputeArgv0 returns null is assumed that is due to a memory

[issue36309] Remove tempfile.mktemp()

2019-03-18 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: There was a warning, but it was suppressed by this commit: commit 44f602dd3b452bbacd3c85b1e5f9873c892b46e3 Author: Guido van Rossum Date: Fri Nov 22 15:56:29 2002 + Comment out the warnings about mktemp(). These are too annoying, and

[issue36131] test.test_urllib2net.TimeoutTest ftp related tests fail due to ftp://www.pythontest.net/ being unavailable

2019-03-18 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: A similar issue happened again on s390x SLES 2.7: https://buildbot.python.org/all/#/builders/66/builds/373 -- ___ Python tracker <https://bugs.python.org/issue36

[issue36236] Python crash on macOS when CWD is invalid

2019-03-19 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: It seems to work: ❯ uname -a Darwin C02VL073HTDG 18.2.0 Darwin Kernel Version 18.2.0: Thu Dec 20 20:46:53 PST 2018; root:xnu-4903.241.1~1/RELEASE_X86_64 x86_64 ❯ pwd /tmp/check /tmp/check ❯ rm -rf ../check /tmp/check ❯ ~/github/cpython/python.exe -m

[issue36308] Fix warning in _PyPathConfig_ComputeArgv0

2019-03-19 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: This issue is already been handled in https://github.com/python/cpython/pull/12441 -- nosy: +pablogsal ___ Python tracker <https://bugs.python.org/issue36

[issue36308] Fix warning in _PyPathConfig_ComputeArgv0

2019-03-19 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: Thanks for the time detecting this, opening this issue and the PR (and all the others), Stéphane! :) -- ___ Python tracker <https://bugs.python.org/issue36

[issue35866] concurrent.futures deadlock

2019-03-19 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: This seem related to https://bugs.python.org/issue35809 -- nosy: +pablogsal ___ Python tracker <https://bugs.python.org/issue35

[issue35866] concurrent.futures deadlock

2019-03-19 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: Could you use gdb/lldb to attach to the process hanging and give us a stack trace? -- ___ Python tracker <https://bugs.python.org/issue35

[issue36367] tokenizer.c memory leak in case of realloc failure

2019-03-19 Thread Pablo Galindo Salgado
Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +12397 stage: -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue36367] tokenizer.c memory leak in case of realloc failure

2019-03-19 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: New changeset cb90c89de14aab636739b3e810cf949e47b54a0c by Pablo Galindo in branch 'master': bpo-36367: Free buffer if realloc fails in tokenize.c (GH-12442) https://github.com/python/cpython/commit/cb90c89de14aab636739b3e810cf94

[issue36367] tokenizer.c memory leak in case of realloc failure

2019-03-19 Thread Pablo Galindo Salgado
Change by Pablo Galindo Salgado : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue36236] Python crash on macOS when CWD is invalid

2019-03-19 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: Yup: ~ ❯ cd /tmp /tmp ❯ mkdir check /tmp ❯ cd check /tmp/check ❯ rm -rf ../check /tmp/check ❯ python3.7 -m pdb Fatal Python error: pymain_compute_path0: memory allocation failed ValueError: character U+e0895f00 is not in range [U+; U+10

[issue36143] Auto-generate Lib/keyword.py

2019-03-19 Thread Pablo Galindo Salgado
Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +12409 stage: -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue36256] parser module fails on legal input

2019-03-20 Thread Pablo Galindo Salgado
Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +12429 stage: -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue36256] parser module fails on legal input

2019-03-21 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: New changeset 9ad15d27361eaa47b77600c7c00a9787a894 by Pablo Galindo in branch 'master': bpo-36256: Fix bug in parsermodule when parsing if statements (GH-12477) https://github.com/python/cpython/commit/9ad15d27361eaa47b77600c7c0

[issue36256] parser module fails on legal input

2019-03-21 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: New changeset 00eb97b4a7d9a73b88ed7c76faee4e49204d5a00 by Pablo Galindo (Miss Islington (bot)) in branch '3.7': bpo-36256: Fix bug in parsermodule when parsing if statements (GH-12488) https://github.com/python/cpyt

[issue36256] parser module fails on legal input

2019-03-21 Thread Pablo Galindo Salgado
Change by Pablo Galindo Salgado : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue36394] test_multiprocessing_spawn fails on Windows7 3.x buildbot

2019-03-21 Thread Pablo Galindo Salgado
New submission from Pablo Galindo Salgado : https://buildbot.python.org/all/#/builders/58/builds/2098/steps/3/logs/stdio Process Process-2: Traceback (most recent call last): File "D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\multiprocessing\process.py", li

[issue36394] test_multiprocessing_spawn fails on Windows7 3.x buildbot

2019-03-21 Thread Pablo Galindo Salgado
Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +12441 stage: -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue36143] Auto-generate Lib/keyword.py

2019-03-25 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: New changeset 91759d98015e1d6d5e1367cff60592ab548e7806 by Pablo Galindo in branch 'master': bpo-36143: Regenerate Lib/keyword.py from the Grammar and Tokens file using pgen (GH-12456) https://github.com/python/cpyt

[issue36143] Auto-generate Lib/keyword.py

2019-03-25 Thread Pablo Galindo Salgado
Change by Pablo Galindo Salgado : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue36427] Document that PyEval_RestoreThread and PyGILState_Ensure can terminate the calling thread

2019-03-25 Thread Pablo Galindo Salgado
New submission from Pablo Galindo Salgado : Currently PyEval_RestoreThread and its callers (mainly PyGILState_Ensure) can terminate the thread if the interpreter is finalizing: PyEval_RestoreThread(PyThreadState *tstate) { if (tstate == NULL) Py_FatalError("PyEval_RestoreT

[issue36427] Document that PyEval_RestoreThread and PyGILState_Ensure can terminate the calling thread

2019-03-25 Thread Pablo Galindo Salgado
Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +12490 stage: -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue36427] Document that PyEval_RestoreThread and PyGILState_Ensure can terminate the calling thread

2019-03-25 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: > I really dislike the design of daemon threads. If it would be only me, I > would prefer this nasty feature causing so much issues at Python shutdown. Well, given that this happens as well in Python3.7 and before, at least we should document

[issue36427] Document that PyEval_RestoreThread and PyGILState_Ensure can terminate the calling thread

2019-03-25 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: > Right. It was just a general comment :-) Yep, daemon threads are evil :) -- ___ Python tracker <https://bugs.python.org/issu

[issue36440] more helpful diagnostics for parser module

2019-03-26 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: Thank you very much for creating the issue :) > Seeing that the implicit resolution at #36256 was to keep the parser module > in place Nothing was really "decided", just that meanwhile is better not to ship a broken parser module.

[issue36440] more helpful diagnostics for parser module

2019-03-26 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: Haha, you were faster creating the PR than me posting the message! -- ___ Python tracker <https://bugs.python.org/issue36

[issue36440] more helpful diagnostics for parser module

2019-03-26 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: > Meaning that no one will ever look at it again. I am very interested in a better alternative to the parser module, so I will open soon another issue for that matter. But as the original issue was about a specific bug, I prefer to mark it

[issue36447] test__xxsubinterpreters leaked regards and memory blocks

2019-03-27 Thread Pablo Galindo Salgado
New submission from Pablo Galindo Salgado : The buildbot x86 Gentoo Refleaks 3.x/546 had detected that test__xxxsubinterpreters is leaking references and blocks: test__xxsubinterpreters leaked [138, 138, 138] references, sum=414 test__xxsubinterpreters leaked [69, 69, 69] memory blocks, sum

[issue36447] test__xxsubinterpreters leaked regards and memory blocks

2019-03-27 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: I cannot reproduce with the current master: ❯ ./python -m test test__xxsubinterpreters -R : Run tests sequentially 0:00:00 load avg: 1.50 [1/1] test__xxsubinterpreters beginning 9 repetitions 123456789 . == Tests result: SUCCESS == 1 test OK

[issue36447] test__xxsubinterpreters leaked regards and memory blocks

2019-03-27 Thread Pablo Galindo Salgado
Change by Pablo Galindo Salgado : -- Removed message: https://bugs.python.org/msg338950 ___ Python tracker <https://bugs.python.org/issue36447> ___ ___ Python-bug

[issue36447] test__xxsubinterpreters leaked regards and memory blocks

2019-03-27 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: Bisecting shows that: 8b9dbc017a190d13f717e714630d620adb7c7ac2 is the first bad commit commit 8b9dbc017a190d13f717e714630d620adb7c7ac2 Author: Victor Stinner Date: Wed Mar 27 01:36:16 2019 +0100 bpo-36444: Remove _PyMainInterpreterConfig (GH

[issue36447] test__xxsubinterpreters leaked regards and memory blocks

2019-03-27 Thread Pablo Galindo Salgado
Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +12528 stage: -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue32312] Create Py_AtExitRegister C API

2019-03-27 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: This may be especially useful to make sure that extension modules that have threads that were not created by Python calling into Python (registering with the interpreter and picking up the GIL) are stopped before the interpreter starts shutting down

[issue36440] more helpful diagnostics for parser module

2019-04-02 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: New changeset cb0748d3939c31168ab5d3b80e3677494497d5e3 by Pablo Galindo (tyomitch) in branch 'master': bpo-36440: include node names in ParserError messages, instead of numeric IDs (GH-12565) https://github.com/python/cpyt

[issue36440] more helpful diagnostics for parser module

2019-04-02 Thread Pablo Galindo Salgado
Change by Pablo Galindo Salgado : -- pull_requests: +12599 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue36440> ___ ___ Python-

[issue36440] more helpful diagnostics for parser module

2019-04-03 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: New changeset 513d142993bb8c13e6803727fa086e44eafc360f by Pablo Galindo in branch '3.7': [3.7] bpo-36440: include node names in ParserError messages, instead of numeric IDs (GH-12565) (GH-12671) https://github.com/python/cpyt

[issue36440] more helpful diagnostics for parser module

2019-04-03 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: Thanks A. Skrobov for your contribution! :) -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue36440] more helpful diagnostics for parser module

2019-04-03 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: Issue #36256 (a real bug) was backported to 3.7 but also includes a similar improvement regarding node names in error messages. I can revert it from 3.7 if you consider it should not be there

[issue36256] parser module fails on legal input

2019-04-05 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: 3.6 only accepts security fixes at this point. -- ___ Python tracker <https://bugs.python.org/issue36256> ___ ___ Pytho

[issue36540] PEP 570: Python Positional-Only Parameters

2019-04-05 Thread Pablo Galindo Salgado
New submission from Pablo Galindo Salgado : This issue will serve to track development and PRs for the implementation of PEP 570: Python Positional-Only Parameters. -- assignee: pablogsal components: Interpreter Core messages: 339521 nosy: pablogsal priority: normal severity: normal

[issue36540] PEP 570: Python Positional-Only Parameters

2019-04-05 Thread Pablo Galindo Salgado
Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +12625 stage: -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue36541] Make lib2to3 grammar more closely match Python

2019-04-06 Thread Pablo Galindo Salgado
Change by Pablo Galindo Salgado : -- nosy: +pablogsal ___ Python tracker <https://bugs.python.org/issue36541> ___ ___ Python-bugs-list mailing list Unsubscribe:

<    35   36   37   38   39   40   41   42   43   44   >