[issue40455] GCC 10 compiler warnings

Change by Pablo Galindo Salgado : -- nosy: +pablogsal nosy_count: 5.0 -> 6.0 pull_requests: +23200 pull_request: https://github.com/python/cpython/pull/24384 ___ Python tracker <https://bugs.python.org/issu

[issue42986] pegen parser: Crash on SyntaxError with f-string on Windows

Pablo Galindo Salgado added the comment: New changeset 40901518167c66abc1ebc5b71c5b86d733cfa154 by Pablo Galindo in branch 'master': bpo-42986: Fix parser crash when reporting syntax errors in f-string with newlines (GH-24279) https://github.com/python/cpyt

[issue43017] Improve error message in the parser when using un-parenthesised tuples in comprehensions

Pablo Galindo Salgado added the comment: New changeset 835f14ff8eec10b3d96f821a1eb46a986e00c690 by Pablo Galindo in branch 'master': bpo-43017: Improve error message for unparenthesised tuples in comprehensions (GH24314) https://github.com/python/cpyt

[issue43017] Improve error message in the parser when using un-parenthesised tuples in comprehensions

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

[issue42927] Inline cache for slots

Pablo Galindo Salgado added the comment: New changeset a776da90b8f2a1342f4f9bfd23a62cea9a0497c6 by Pablo Galindo in branch 'master': bpo-42927: Update the What's new entry for LOAD_ATTR optimizations (GH-24383) https://github.com/python/cpython/commit/a776da90b8f2a1342f4f9bfd2

[issue42986] pegen parser: Crash on SyntaxError with f-string on Windows

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

[issue42899] Is it legal to eliminate tests of a value, when that test has no effect on control flow?

Pablo Galindo Salgado added the comment: Mark, what is the status of this issue? This is marked as a release blocker so I would prefer not to release the next alpha with this being unfixed. -- ___ Python tracker <https://bugs.python.

[issue41490] Update bundled pip to 20.2.1 and setuptools to 49.2.1

Pablo Galindo Salgado added the comment: Friendly reminder that this issue is currently blocking the 3.10a5 release. If you are ok with waiting for the next release to include the fix, please say so here or drop me an email/ -- ___ Python tracker

[issue42634] Incorrect line number in bytecode for try-except-finally

Pablo Galindo Salgado added the comment: Friendly reminder that this issue is currently blocking the 3.10a5 release. If you are ok with waiting for the next release to include the fix, please say so here or drop me an email/ -- nosy: +pablogsal

[issue38302] [3.10] __pow__ and __rpow__ are not reached when __ipow__ returns NotImplemented for **=

Pablo Galindo Salgado added the comment: Friendly reminder that this issue is currently blocking the 3.10a5 release. If you are ok with waiting for the next release to include the fix, please say so here or drop me an email/ -- nosy: +pablogsal

[issue41490] Update bundled pip to 20.2.1 and setuptools to 49.2.1

Pablo Galindo Salgado added the comment: Do we need to wait for PR 22779 or can it be closed? -- ___ Python tracker <https://bugs.python.org/issue41490> ___ ___

[issue42997] Improve error message for missing : before suites

Pablo Galindo Salgado added the comment: New changeset 58fb156edda1a0e924a38bfed494bd06cb09c9a3 by Pablo Galindo in branch 'master': bpo-42997: Improve error message for missing : before suites (GH-24292) https://github.com/python/cpython/commit/58fb156edda1a0e924a38bfed494bd

[issue42997] Improve error message for missing : before suites

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

[issue43108] test_curses is leaking references

New submission from Pablo Galindo Salgado : ❯ ./python -m test test_curses -uall -R : 0:00:00 load avg: 3.77 Run tests sequentially 0:00:00 load avg: 3.77 [1/1] test_curses beginning 9 repetitions 123456789 . test_curses leaked [4, 4, 4, 4] references, sum=16 test_curses failed == Tests result

[issue43108] test_curses is leaking references

Pablo Galindo Salgado added the comment: d64fd4bb5bb4fd2e3277f39d3ad99b5a8d193e1b is the first bad commit commit d64fd4bb5bb4fd2e3277f39d3ad99b5a8d193e1b Author: Serhiy Storchaka Date: Sun Jan 31 17:22:27 2021 +0200 bpo-43016: Rewrite tests for curses (GH-24312) Lib/test

[issue43108] test_curses is leaking references

Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +23235 stage: -> patch review pull_request: https://github.com/python/cpython/pull/24420 ___ Python tracker <https://bugs.python.org/issu

[issue41149] Threads can fail to start

Pablo Galindo Salgado added the comment: New changeset 01c4fddc4b2ac707f226e0bd92679588d2252cc4 by BarneyStratford in branch 'master': bpo-41149: Fix a bug in threading that causes fals-y threads callables to fail to start. (GH-21201) https://github.com/python/cpyt

[issue41149] Threads can fail to start

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

[issue43108] test_curses is leaking references

Pablo Galindo Salgado added the comment: New changeset bb739ec922c6992a2be38f9fd3c544c2cc322dde by Pablo Galindo in branch 'master': bpo-43108: Fix a reference leak in the curses module (GH-24420) https://github.com/python/cpython/commit/bb739ec922c6992a2be38f9fd3c544

[issue43108] test_curses is leaking references

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

[issue43103] Add configure option to disable build libpython.a and don't install python.o

Pablo Galindo Salgado added the comment: There are some build systems and downstream distributors that expect the .a to be there, so I propose to at least not changing the default. -- nosy: +pablogsal ___ Python tracker <https://bugs.python.

[issue43121] Incorrect SyntaxError message for missing comma (3.10.a5)

Pablo Galindo Salgado added the comment: Thanks Andre for the report. Will fix it soon -- ___ Python tracker <https://bugs.python.org/issue43121> ___ ___ Pytho

[issue43121] Incorrect SyntaxError message for missing comma (3.10.a5)

Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +23244 stage: -> patch review pull_request: https://github.com/python/cpython/pull/24436 ___ Python tracker <https://bugs.python.org/issu

[issue43121] Incorrect SyntaxError message for missing comma (3.10.a5)

Pablo Galindo Salgado added the comment: Andre, could you check if this works in your test suite correctly? -- ___ Python tracker <https://bugs.python.org/issue43

[issue43121] Incorrect SyntaxError message for missing comma (3.10.a5)

Pablo Galindo Salgado added the comment: > Pablo: I have almost exactly the same 4 test cases that you added in the test > suite, so it would pass my tests too. I would consider it to be resolved. Fantastic. Also, for the future, could you indicate how could I run the test suite of fr

[issue43121] Incorrect SyntaxError message for missing comma (3.10.a5)

Pablo Galindo Salgado added the comment: New changeset d4e6ed7e5fb43320ea714d7436bc11667c624d43 by Pablo Galindo in branch 'master': bpo-43121: Fix incorrect SyntaxError message for missing comma (GH-24436) https://github.com/python/cpython/commit/d4e6ed7e5fb43320ea714d7436bc11

[issue43121] Incorrect SyntaxError message for missing comma (3.10.a5)

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

[issue43121] Incorrect SyntaxError message for missing comma (3.10.a5)

Pablo Galindo Salgado added the comment: Thanks Andre for the thorough explanation! The reason I was interested in running it myself is that as you are running on syntax errors, is a good corpus of things that fail with error messages, which is something that we have not been able to find

[issue42919] Blank in multiline “if expressions” will lead to EOF errors

Pablo Galindo Salgado added the comment: Yeah, I also believe this doesn't look like a bug and the fact that is consistent with 3.8 makes me more confident to say that is not. -- ___ Python tracker <https://bugs.python.org/is

[issue43149] Misleading error message for except with missing parens (3.10.a5)

Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +23262 stage: -> patch review pull_request: https://github.com/python/cpython/pull/24467 ___ Python tracker <https://bugs.python.org/issu

[issue43149] Misleading error message for except with missing parens (3.10.a5)

Pablo Galindo Salgado added the comment: New changeset 206cbdab16cb054e859597a562e2f6ab35e99766 by Pablo Galindo in branch 'master': bpo-43149: Improve error message for exception group without parentheses (GH-24467) https://github.com/python/cpyt

[issue43149] Misleading error message for except with missing parens (3.10.a5)

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

[issue40692] Adjust test_concurrent_futures to run more of its tests if multiprocessing.synchronize is missing

Pablo Galindo Salgado added the comment: New changeset bf2e7e55d7306b1e2fce7dce767e8df5ff42cf1c by Asheesh Laroia in branch 'master': bpo-40692: Run more test_concurrent_futures tests (GH-20239) https://github.com/python/cpython/commit/bf2e7e55d7306b1e2fce7dce767e8d

[issue40692] Adjust test_concurrent_futures to run more of its tests if multiprocessing.synchronize is missing

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

[issue43163] codeop prematurely raises on 2nd line when closer is needed

Pablo Galindo Salgado added the comment: > (I think it would be good if a C expert compared it to the *current* C code.) That would be very beneficial but is quite a big task, specially given that codeop design is quite surprising. I personally find quite confusing the way codeop

[issue43163] codeop prematurely raises on 2nd line when closer is needed

Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +23275 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/24483 ___ Python tracker <https://bugs.python.org/issu

[issue43163] codeop prematurely raises on 2nd line when closer is needed

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

[issue43163] codeop prematurely raises on 2nd line when closer is needed

Pablo Galindo Salgado added the comment: New changeset dbb228189b4eb7ab41f326eb79dae669b2c81177 by Pablo Galindo in branch 'master': bpo-43163: Handle unclosed parentheses in codeop (GH-24483) https://github.com/python/cpython/commit/dbb228189b4eb7ab41f326eb79dae6

[issue42919] Blank in multiline “if expressions” will lead to EOF errors

Pablo Galindo Salgado added the comment: Closing as "not a bug" as per the previous discussion. If someone sees new information here, please, feel free to re-open. -- resolution: -> not a bug stage: -> resolved status: open -> closed ___

[issue43163] codeop prematurely raises on 2nd line when closer is needed

Pablo Galindo Salgado added the comment: >Pablo, Is there any sane possibility that the compiler could, at least >sometimes, raise an IncompleteSyntax subclass of SyntaxError when code is >merely incomplete, as opposed to wrong? I'm assuming you mean the parser (when the com

[issue15108] ERROR: SystemError: ./../Objects/tupleobject.c:118: bad argument to internal function

Change by Pablo Galindo Salgado : -- keywords: +patch nosy: +pablogsal nosy_count: 8.0 -> 9.0 pull_requests: +23297 stage: -> patch review pull_request: https://github.com/python/cpython/pull/24510 ___ Python tracker <https://bugs.p

[issue15108] Incomplete tuple created by PyTuple_New() and accessed via the GC can trigged a crash

Pablo Galindo Salgado added the comment: > IMO the unsafe PyTuple_New() API should be avoided. Is not that simple, there are other APIs that track the tuple as _PyTuple_Resize. This problem also is not unique to tuples, although is mainly prominent in them. We have this warning in the d

[issue15108] Incomplete tuple created by PyTuple_New() and accessed via the GC can trigged a crash

Pablo Galindo Salgado added the comment: > There are other safe alternatives like Py_BuildValue("(OOO)", item1, item2, > item3). That's a lot slower unfortunately -- ___ Python tracker <https://bu

[issue15108] Incomplete tuple created by PyTuple_New() and accessed via the GC can trigged a crash

Pablo Galindo Salgado added the comment: > If the GIL is released before the tuple is fully populated and something > access to this tuple via the GC (ex: gc.get_objects()), accessing the tuple > can crash, especially in the Python land (for example, repr(the_tuple) is > lik

[issue43108] test_curses is leaking references

Pablo Galindo Salgado added the comment: New changeset ede1ff226c9ef4efd053109c69b4e33f75b2b17b by Miss Islington (bot) in branch '3.8': bpo-43108: Fix a reference leak in the curses module (GH-24420) (GH-24429) https://github.com/python/cpyt

[issue43231] test.test_curses.TestCurses.test_init_pair fails in s390x Fedora

New submission from Pablo Galindo Salgado : https://buildbot.python.org/all/#/builders/433/builds/181/steps/5/logs/stdio == ERROR: test_init_pair (test.test_curses.TestCurses

[issue43231] test.test_curses.TestCurses.test_init_pair fails in s390x Fedora

Change by Pablo Galindo Salgado : -- versions: +Python 3.10, Python 3.9 ___ Python tracker <https://bugs.python.org/issue43231> ___ ___ Python-bugs-list mailin

[issue43231] test.test_curses.TestCurses.test_init_pair fails in s390x Fedora

Pablo Galindo Salgado added the comment: This seems to happen only when running with -R -- ___ Python tracker <https://bugs.python.org/issue43231> ___ ___ Pytho

[issue43231] test.test_curses.TestCurses.test_init_pair fails in s390x Fedora

Change by Pablo Galindo Salgado : -- nosy: +lukasz.langa ___ Python tracker <https://bugs.python.org/issue43231> ___ ___ Python-bugs-list mailing list Unsub

[issue43233] test_copy_file_range_offset fails on AMD64 FreeBSD Shared 3.9

New submission from Pablo Galindo Salgado : == FAIL: test_copy_file_range_offset (test.test_os.FileTests) -- Traceback (most recent call last): File "

[issue43233] test_copy_file_range_offset fails on AMD64 FreeBSD Shared 3.9

Pablo Galindo Salgado added the comment: koobs, can you give us access to the buildbot? The latest IP you provided do not work anymore -- ___ Python tracker <https://bugs.python.org/issue43

[issue43231] test.test_curses.TestCurses.test_init_pair fails in s390x Fedora

Pablo Galindo Salgado added the comment: The logic in _curses_init_pair_impl is quite odd. Seems that _CURSES_INIT_PAIR_FUNC succeeds the first run of (-R) even if pair_number >= COLOR_PAIRS but fails the second. Serhiy, do you know what's going

[issue43231] test.test_curses.TestCurses.test_init_pair fails in s390x Fedora

Pablo Galindo Salgado added the comment: Hu, commenting out test_use_default_colors fixes the issue, so something is going on there -- ___ Python tracker <https://bugs.python.org/issue43

[issue43231] test.test_curses.TestCurses.test_init_pair fails in s390x Fedora

Pablo Galindo Salgado added the comment: >From the curses docs: init_pair The init_pair routine changes the definition of a color-pair. It takes three arguments: the number of the color-pair to be changed, the foreground color number, and the background co

[issue43231] test.test_curses.TestCurses.test_init_pair fails in s390x Fedora

Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +23325 stage: -> patch review pull_request: https://github.com/python/cpython/pull/24539 ___ Python tracker <https://bugs.python.org/issu

[issue43231] test.test_curses.TestCurses.test_init_pair fails in s390x Fedora

Change by Pablo Galindo Salgado : -- pull_requests: +23327 pull_request: https://github.com/python/cpython/pull/24541 ___ Python tracker <https://bugs.python.org/issue43

[issue43231] test.test_curses.TestCurses.test_init_pair fails in s390x Fedora

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

[issue43231] test.test_curses.TestCurses.test_init_pair fails in s390x Fedora

Pablo Galindo Salgado added the comment: New changeset d0204963ec87beb9732e924e464b8a6a1ef4d341 by Pablo Galindo in branch 'master': bpo-43231: Correctly calculate the curses color pair limit when checking for it (GH-24541) https://github.com/python/cpyt

[issue43233] test_copy_file_range_offset fails on AMD64 FreeBSD Shared 3.9

Pablo Galindo Salgado added the comment: Hu. The last time it succeeded was with platform.platform: FreeBSD-13.0-CURRENT-amd64-64bit-ELF: https://buildbot.python.org/all/#/builders/151/builds/280 -- ___ Python tracker <ht

[issue43233] test_copy_file_range_offset fails on AMD64 FreeBSD Shared 3.9

Pablo Galindo Salgado added the comment: This seems a problem in FreeBSD 14.0 CURRENT. Koobs, could you report this upstream? -- ___ Python tracker <https://bugs.python.org/issue43

[issue15108] Incomplete tuple created by PyTuple_New() and accessed via the GC can trigged a crash

Pablo Galindo Salgado added the comment: > PyList_New() is also affected. Do you think about other types? Any C extension class that implements a new_whatever() method that leaves the class tracked and not ready. -- ___ Python tracker <

[issue34013] Inconsistent SyntaxError for print

Pablo Galindo Salgado added the comment: > Would it be too much if add a Python 2 rule for print statement in grammar to > produce better error message? Please, go ahead. I think it makes sense and with our latest change in the parser, such new error message will have no imp

[issue15108] Incomplete tuple created by PyTuple_New() and accessed via the GC can trigged a crash

Pablo Galindo Salgado added the comment: > Should we still fix sqlite3, or wait for an agreement on GH-24510? I suggest to let's all agree on how to fix this on the bigger scale first. -- ___ Python tracker <https://bugs.python.org

[issue34013] Inconsistent SyntaxError for print

Pablo Galindo Salgado added the comment: Let's step back a bit and focus on the issue at hand. The problem is the following: * We **already** have a warning for the print statement without parens: Python 3.9.1 (default, Dec 14 2020, 11:49:16) [Clang 12.0.0 (clang-1200.0.32.27)] on d

[issue37146] opcode cache for LOAD_GLOBAL emits false alarm in memory leak hunting

Pablo Galindo Salgado added the comment: > Or maybe need a generic -X flag to tell Python that libregrtest is tracking > leaks, since we might need to change other parameters than only the opcode > cache size. I think we should go this way, maybe even less "public". If we

[issue43271] AMD64 Windows10 3.x crash with Windows fatal exception: stack overflow

Change by Pablo Galindo Salgado : -- priority: normal -> release blocker ___ Python tracker <https://bugs.python.org/issue43271> ___ ___ Python-bugs-list mai

[issue43272] AMD64 Arch Linux VintageParser 3.9: test_fstring test_named_expressions test_unpack_ex failed

Change by Pablo Galindo Salgado : -- keywords: +patch nosy: +pablogsal nosy_count: 1.0 -> 2.0 pull_requests: +23371 stage: -> patch review pull_request: https://github.com/python/cpython/pull/24591 ___ Python tracker <https://bugs.p

[issue43272] AMD64 Arch Linux VintageParser 3.9: test_fstring test_named_expressions test_unpack_ex failed

Pablo Galindo Salgado added the comment: New changeset f9d1bf2de07131a8d80bc1e4914ee534bc5effa4 by Pablo Galindo in branch '3.9': [3.9] bpo-43272: Fix old parser test failures for backported grammar constructs (GH-24591) https://github.com/python/cpyt

[issue43272] AMD64 Arch Linux VintageParser 3.9: test_fstring test_named_expressions test_unpack_ex failed

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

[issue43272] AMD64 Arch Linux VintageParser 3.9: test_fstring test_named_expressions test_unpack_ex failed

Pablo Galindo Salgado added the comment: ;) -- ___ Python tracker <https://bugs.python.org/issue43272> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43277] Add PySet_CheckExact

New submission from Pablo Galindo Salgado : For some mysterious reason we have PySet_Check, PyFrozenSet_Check, PyAnySet_Check, PyAnySet_CheckExact and PyFrozenSet_CheckExact but no PySet_CheckExact -- components: C API messages: 387413 nosy: pablogsal priority: normal severity

[issue43277] Add PySet_CheckExact

Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +23376 stage: -> patch review pull_request: https://github.com/python/cpython/pull/24598 ___ Python tracker <https://bugs.python.org/issu

[issue43277] Add PySet_CheckExact

Pablo Galindo Salgado added the comment: New changeset d439fb304ca3098aab1ed0a314996f9d29347b21 by Pablo Galindo in branch 'master': bpo-43277: Add PySet_CheckExact to the C-API (GH-24598) https://github.com/python/cpython/commit/d439fb304ca3098aab1ed0a314996f

[issue43277] Add PySet_CheckExact

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

[issue15108] Incomplete tuple created by PyTuple_New() and accessed via the GC can trigged a crash

Pablo Galindo Salgado added the comment: I mainly agree on closing this issue as we already have a warning about this behaviour in gc.get_referrers and other friends. On the other hand I am still a bit afraid of a crash that could happen if the GC does a pass and one of these tuples is in

[issue43303] ASAN : Memory leak in compilation

Pablo Galindo Salgado added the comment: To run the address sanitizer you need to deactivate pymalloc and pass some of the asan flags to avoid false positives. Check our our buildbot configuration for it: https://github.com/python/buildmaster-config/blob/master/master/custom/factories.py

[issue43293] Move note about GIL to top of threading module

Pablo Galindo Salgado added the comment: New changeset 32181be6081f6c70a1e0bd0540050805c8e88e83 by Guanzhong Chen in branch 'master': bpo-43293: Doc: move note about GIL to top of threading module (GH-24622) https://github.com/python/cpython/commit/32181be6081f6c70a1e0bd05400508

[issue37146] opcode cache for LOAD_GLOBAL emits false alarm in memory leak hunting

Change by Pablo Galindo Salgado : -- pull_requests: +23428 stage: resolved -> patch review pull_request: https://github.com/python/cpython/pull/24643 ___ Python tracker <https://bugs.python.org/issu

[issue43293] Move note about GIL to top of threading module

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

[issue43293] Move note about GIL to top of threading module

Pablo Galindo Salgado added the comment: New changeset 30927fa4658a36f647155e9582b598434582a5ce by Guanzhong Chen in branch '3.7': [3.7] bpo-43293: Doc: move note about GIL to top of threading module (GH-24622) (#24642) https://github.com/python/cpyt

[issue42128] Structural Pattern Matching (PEP 634)

Pablo Galindo Salgado added the comment: I can pick up the AST docs PR -- ___ Python tracker <https://bugs.python.org/issue42128> ___ ___ Python-bugs-list mailin

[issue42128] Structural Pattern Matching (PEP 634)

Change by Pablo Galindo Salgado : -- pull_requests: +23458 pull_request: https://github.com/python/cpython/pull/24673 ___ Python tracker <https://bugs.python.org/issue42

[issue37146] opcode cache for LOAD_GLOBAL emits false alarm in memory leak hunting

Pablo Galindo Salgado added the comment: New changeset af5fa13ef6f648fc7a7a33a7556db13887e7d643 by Pablo Galindo in branch 'master': bpo-37146: Deactivate opcode cache only when using huntrleaks in the test suite (GH-24643) https://github.com/python/cpyt

[issue37146] opcode cache for LOAD_GLOBAL emits false alarm in memory leak hunting

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

[issue11717] conflicting definition of ssize_t in pyconfig.h

Pablo Galindo Salgado added the comment: New changeset c994ffe69553cbb34f1cea6a4494d6e7657f41b0 by Jozef Grajciar in branch 'master': bpo-11717: fix ssize_t redefinition error when targeting 32bit Windows app (GH-24479) https://github.com/python/cpyt

[issue11717] conflicting definition of ssize_t in pyconfig.h

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

[issue43233] test_os: test_copy_file_range_offset fails on FreeBSD CURRENT

Pablo Galindo Salgado added the comment: Buildbot is green! https://buildbot.python.org/all/#/builders/483/builds/841 -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue39199] Improve the AST documentation

Change by Pablo Galindo Salgado : -- pull_requests: +23499 pull_request: https://github.com/python/cpython/pull/24727 ___ Python tracker <https://bugs.python.org/issue39

[issue42128] Structural Pattern Matching (PEP 634)

Change by Pablo Galindo Salgado : -- pull_requests: +23503 pull_request: https://github.com/python/cpython/pull/24732 ___ Python tracker <https://bugs.python.org/issue42

[issue42128] Structural Pattern Matching (PEP 634)

Pablo Galindo Salgado added the comment: Opened https://github.com/python/cpython/pull/24732 > I'm also not entirely sure how "unnamed fields" work, or what they're used > for. Presumably, we'd want to end the __match_args__ tuple upon hitting one > of

[issue42128] Structural Pattern Matching (PEP 634)

Change by Pablo Galindo Salgado : -- pull_requests: +23504 pull_request: https://github.com/python/cpython/pull/24733 ___ Python tracker <https://bugs.python.org/issue42

[issue42128] Structural Pattern Matching (PEP 634)

Pablo Galindo Salgado added the comment: New changeset 0632b1012d4dfa81ffef0d686a4710f6134f77a8 by Pablo Galindo in branch 'master': bpo-42128: Add __match_args__ to structseq-based classes (GH-24732) https://github.com/python/cpython/commit/0632b1012d4dfa81ffef0d686a4710

[issue42202] Optimize function annotation

Change by Pablo Galindo Salgado : -- nosy: +pablogsal nosy_count: 7.0 -> 8.0 pull_requests: +23509 pull_request: https://github.com/python/cpython/pull/24738 ___ Python tracker <https://bugs.python.org/issu

[issue42202] Optimize function annotation

Pablo Galindo Salgado added the comment: New changeset 8747c1f233fc1a3dd5ee3d8e163317f28b4d7568 by Pablo Galindo in branch 'master': Improve the description of the improvements in bpo-42202 (GH-24738) https://github.com/python/cpython/commit/8747c1f233fc1a3dd5ee3d8e163317

[issue43410] Parser does not handle correctly some errors when parsin from stdin

New submission from Pablo Galindo Salgado : The parser crashes when there are some syntax errors from stdin: > echo "(1+34" | ./python.exe - [1]54046 doneecho "(1+34" | 54047 segmentation fault ./python.exe - -- components: In

[issue43410] Parser does not handle correctly some errors when parsin from stdin

Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +23535 stage: -> patch review pull_request: https://github.com/python/cpython/pull/24763 ___ Python tracker <https://bugs.python.org/issu

[issue43410] Parser does not handle correctly some errors when parsin from stdin

Pablo Galindo Salgado added the comment: I think we should look into having some variable holding all the text that we have parsed so far. All the workarounds to fetch the text from the file or from stdin or whatnot are getting very very complicated. -- stage: patch review

[issue43410] Parser does not handle correctly some errors when parsin from stdin

Pablo Galindo Salgado added the comment: I modified PR 24763 to implement this idea. -- ___ Python tracker <https://bugs.python.org/issue43410> ___ ___ Pytho

[issue43366] Unclosed bracket bug in code.interact prevents identifying syntax errors

Pablo Galindo Salgado added the comment: This is a change I implemented and is explicitly deactivated in the reprl: https://github.com/python/cpython/blob/master/Parser/pegen.c#L1191 The problem here is that when you call compile() there is no way to know if you are doing it to simulate a

[issue43366] Unclosed bracket bug in code.interact prevents identifying syntax errors

Pablo Galindo Salgado added the comment: > Maybe we need to add an API (e.g. a flag to compile()) so that we can ask the > actual parser the question we're interested in, rather than having to use > hacks and heuristics? I was thinking about that, but we need to fix some i

<    24   25   26   27   28   29   30   31   32   33   >