[issue42550] re库匹配问题

Change by ye andy : -- stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue42550] re库匹配问题

Karthikeyan Singaravelan added the comment: https://docs.python.org/3/howto/regex.html#more-metacharacters $ Matches at the end of a line, which is defined as either the end of the string, or any location followed by a newline character. \Z Matches only at the end of the string. >>> eth_re

[issue42550] re库匹配问题

ye andy added the comment: Okay, I just thought it was weird -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue42550] re库匹配问题

hongweipeng added the comment: Maybe you need use `eth_re.match(a, re.MULTILINE)` or `eth_re.fullmatch(a)` . -- nosy: +hongweipeng ___ Python tracker ___

[issue38630] subprocess.Popen.send_signal() should poll the process

Jack O'Connor added the comment: This change caused a crash in the Duct library in Python 3.9. Duct uses the waitid(NOWAIT) strategy that Nathaniel Smith has described in this thread. With this change, the child process is reaped by kill() in a spot we didn't expect, and a subsequent call

[issue42550] re库匹配问题

ye andy added the comment: My regulus requires the beginning of 0x, the end of 0-9A-fa-f, my ending \n, he also shows success, my expected result is failure, I wrote the problem? -- ___ Python tracker

[issue42550] re库匹配问题

ye andy added the comment: My regex requires ending with 0-9a-fa-f, and I now end with a line break, which in theory should not work. Why did it work? -- nosy: -Dennis Sweeney ___ Python tracker

[issue42550] re库匹配问题

Dennis Sweeney added the comment: Maybe you're looking for re.fullmatch: https://docs.python.org/3/library/re.html#re.fullmatch -- nosy: +Dennis Sweeney ___ Python tracker

[issue42550] re库匹配问题

ye andy added the comment: What I mean by that is that the regex That I wrote should match successfully is a 42-bit string, but it is also successful when we add more newlines -- ___ Python tracker

[issue42550] re库匹配问题

Ma Lin added the comment: This issue can be closed. '0x' 2 'd26935a5ee4cd542e8a3a7e74fb7a99855975b59' 40 '\n' 1 2+40+1 = 43 -- nosy: +malin ___ Python tracker ___

[issue42536] Iterating on a zip keeps objects alive longer than expected (test_itertools leaks sometimes references)

Brandt Bucher added the comment: Also, it appears enumerate is affected as well. -- ___ Python tracker ___ ___ Python-bugs-list

[issue42536] Iterating on a zip keeps objects alive longer than expected (test_itertools leaks sometimes references)

Brandt Bucher added the comment: (By the way, I didn't know that -F runs the tests forever... so I was waiting *almost* forever for it to finish!) -- ___ Python tracker ___

[issue42536] Iterating on a zip keeps objects alive longer than expected (test_itertools leaks sometimes references)

Brandt Bucher added the comment: It looks like Victor's original issue is unrelated to zip, though. That test run is clean after adding the same fix to: - itertools.product - itertools.combinations - itertools.combinations_with_replacement - itertools.permutations - itertools.zip_longest

[issue42536] Iterating on a zip keeps objects alive longer than expected (test_itertools leaks sometimes references)

Change by Brandt Bucher : -- keywords: +patch pull_requests: +22491 stage: -> patch review pull_request: https://github.com/python/cpython/pull/23623 ___ Python tracker ___

[issue42551] Generator `yield`s counted as primitive calls by cProfile

New submission from Matthew Suozzo : # Issue When profiling a generator function, the initial call and all subsequent yields are aggregated into the same "ncalls" metric by cProfile. ## Example >>> cProfile.run(""" ... def foo(): ... yield 1 ... yield 2 ... assert tuple(foo()) == (1, 2)

[issue42504] Failure to build with MACOSX_DEPLOYMENT_TARGET=11 on Big Sur

miss-islington added the comment: New changeset 09a698b4743c669983d606595a1b2daeff6c3cf8 by Miss Islington (bot) in branch '3.9': bpo-42504: fix for MACOSX_DEPLOYMENT_TARGET=11 (GH-23556) https://github.com/python/cpython/commit/09a698b4743c669983d606595a1b2daeff6c3cf8 --

[issue42504] Failure to build with MACOSX_DEPLOYMENT_TARGET=11 on Big Sur

Change by Ned Deily : -- versions: +Python 3.10, Python 3.8 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue42504] Failure to build with MACOSX_DEPLOYMENT_TARGET=11 on Big Sur

Change by miss-islington : -- nosy: +miss-islington nosy_count: 3.0 -> 4.0 pull_requests: +22490 pull_request: https://github.com/python/cpython/pull/23622 ___ Python tracker

[issue42504] Failure to build with MACOSX_DEPLOYMENT_TARGET=11 on Big Sur

Ned Deily added the comment: New changeset 5291639e611dc3f55a34666036f2c3424648ba50 by FX Coudert in branch 'master': bpo-42504: fix for MACOSX_DEPLOYMENT_TARGET=11 (GH-23556) https://github.com/python/cpython/commit/5291639e611dc3f55a34666036f2c3424648ba50 --

[issue31990] Pickling deadlocks in thread with python -m

Sara Kelley added the comment: After looking a little more I don't believe the extension is the problem, but it is an easier way to see the problem. When testqueuepickle3 is run as a script you don't see the error. When it is imported as a module, even from another script with valid syntax,

[issue42547] argparse: add_argument(... nargs='+', metavar=) does not work with positional arguments

paul j3 added the comment: I'll reopen it - your patch, while not a complete resolution, does take care of the immediate error. -- resolution: duplicate -> status: closed -> open ___ Python tracker

[issue42547] argparse: add_argument(... nargs='+', metavar=) does not work with positional arguments

paul j3 added the comment: Duplicate of https://bugs.python.org/issue14074 argparse allows nargs>1 for positional arguments but doesn't allow metavar to be a tuple -- resolution: -> duplicate stage: patch review -> resolved status: open -> closed

[issue42547] argparse: add_argument(... nargs='+', metavar=) does not work with positional arguments

Change by Karthikeyan Singaravelan : -- nosy: +paul.j3, rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue42550] re库匹配问题

New submission from ye andy : import re a = """0xd26935a5ee4cd542e8a3a7e74fb7a99855975b59\n""" eth_re = re.compile(r'^0x[0-9a-fA-F]{40}$') print(eth_re.match(a)) print(len(a)) # 长度43 -- components: Library (Lib) messages: 382367 nosy: andy.ye.jx priority: normal severity: normal

[issue42541] Tkinter colours wrong on MacOS universal2

Kevin Walzer added the comment: Ned, I wish I knew. Marc and I are both now members of the TCT, and have had a few conversations around the release schedule, but the release schedule is more or less determined when one or two senior members of the TCT decide things are ready. We had some

[issue42536] Iterating on a zip keeps objects alive longer than expected (test_itertools leaks sometimes references)

Brandt Bucher added the comment: Some quick benchmarks on a normal build with CPU isolation, tuned with pyperf. No PGO/LTO. $ ./python -m pyperf timeit --rigorous --setup 'i = (None,) * 10_000_000' 'for _, _ in zip(i, i): pass' # Current master. .

[issue42507] test_ttk_guionly test failures on macOS with Tcl/Tk 8.6.10

Ned Deily added the comment: Terry: > It might be the tk/tkinter build, not the tests, that is at fault. Can you elaborate? -- ___ Python tracker ___

[issue42541] Tkinter colours wrong on MacOS universal2

Ned Deily added the comment: Thanks for checking, Kevin. Is there any update on when we can expect a Tk 8.6.11? It's been over a year now since 8.6.10 and there have been so many macOS-related changes that have gone into Tk since then. It's really not fair to ask downstream packagers, like

[issue42536] Iterating on a zip keeps objects alive longer than expected (test_itertools leaks sometimes references)

Brandt Bucher added the comment: Simple demo: >>> import gc >>> gc.disable() >>> z = zip([[]]) >>> gc.is_tracked(next(z)) True >>> z = zip([[]]) >>> gc.collect() 0 >>> gc.is_tracked(next(z)) False -- ___ Python tracker

[issue42536] Iterating on a zip keeps objects alive longer than expected (test_itertools leaks sometimes references)

Brandt Bucher added the comment: It looks like the GC untracks the None-filled result tuple in untrack_tuples, and it's never re-tracked again. This can also happen if it's filled with atomic values on an early iteration and the GC visits it. Perhaps a simple fix is to call

[issue42536] Iterating on a zip keeps objects alive longer than expected (test_itertools leaks sometimes references)

Change by Raymond Hettinger : -- assignee: rhettinger -> ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue42536] Iterating on a zip keeps objects alive longer than expected (test_itertools leaks sometimes references)

Raymond Hettinger added the comment: Adding Brandt because he recently worked on the zip() code. -- nosy: +brandtbucher ___ Python tracker ___

[issue31990] Pickling deadlocks in thread with python -m

Sara Kelley added the comment: https://docs.python.org/3/using/cmdline.html#cmdoption-m The documentation says you must not give a file extension with the module option. Because the extension was given the thread is deadlocking in importlib._bootstrap when trying to acquire the module lock.

[issue38520] There is no proper way to know if a process is the main one

Change by Zackery Spytz : -- keywords: +patch nosy: +ZackerySpytz nosy_count: 4.0 -> 5.0 pull_requests: +22489 stage: -> patch review pull_request: https://github.com/python/cpython/pull/23621 ___ Python tracker

[issue42536] Iterating on a zip keeps objects alive longer than expected (test_itertools leaks sometimes references)

STINNER Victor added the comment: > The GC is supposed to be able to break such cycle, no? In zip_new(), lz->result tuple is *not* always tracked by the GC. -- ___ Python tracker

[issue42536] Iterating on a zip keeps objects alive longer than expected (test_itertools leaks sometimes references)

STINNER Victor added the comment: Raymond Hettinger: > If this is new, pairwise() is the most likely cause. I reproduced the issue without involving the itertools module. It seems to be a zip_next() micro-optimization which keeps an object alive longer than epxected. This micro-optimization

[issue42536] Iterating on a zip keeps objects alive longer than expected (test_itertools leaks sometimes references)

Change by STINNER Victor : -- title: test_itertools leaks sometimes references -> Iterating on a zip keeps objects alive longer than expected (test_itertools leaks sometimes references) ___ Python tracker

[issue42536] test_itertools leaks sometimes references

STINNER Victor added the comment: I reproduce the leak with attached test_zip.py by running: $ ./python -m test -R 3:3 test_zip_leak -j4 -m test.test_zip_leak.TestGC.test_permutations -m test.test_zip_leak.TestGC.test_zip The problem is that the builtin zip class keeps an internal tuple

[issue42324] Doctest: directives

Julien Palard added the comment: Thanks for reporting! This will be fixed soon: https://github.com/python/cpython/pull/23620 I'm marking issue42324 as duplicate of issue36675. -- nosy: +mdk resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Doctest

[issue42549] "quopri" line endings not standard conform

New submission from Dieter Maurer : RFC 1521 and "https://tools.ietf.org/html/rfc2045#section-6.7; stipulate that the quoted printable encoding uses CRLF line endings. Python's "quopri" implementation does not honor this. -- components: Library (Lib) messages: 382354 nosy: dmaurer

[issue36675] Doctest directives and comments missing from code samples

Change by Julien Palard : -- pull_requests: +22488 pull_request: https://github.com/python/cpython/pull/23620 ___ Python tracker ___

[issue35342] email "default" policy raises exception iterating over unparseable date headers

Irit Katriel added the comment: I get this. Was the bug fixed? >>> email.message_from_string('Date: not a parseable date', >>> policy=email.policy.default).items() [('Date', 'not a parseable date')] -- nosy: +iritkatriel status: open -> pending

[issue8535] passing optimization flags to the linker required for builds with gcc -flto

Change by Irit Katriel : -- resolution: -> fixed stage: -> resolved status: pending -> closed ___ Python tracker ___ ___

[issue42541] Tkinter colours wrong on MacOS universal2

Kevin Walzer added the comment: This bug is not present in IDLE 3.9.0 when built against the tip of Tk core-8-6-branch. Marc Culler has done some work to fix the visual artifacts, and the work continues. The problem here is that Apple's API churn continually breaks parts of Tk with each new

[issue42548] debugger stops at breakpoint of `pass` that is not actually reached

New submission from Andy S : The python (3.6) doc states (https://docs.python.org/3/reference/simple_stmts.html#the-pass-statement): pass is a null operation... So since this is still an operation one could expect that it can be used as an op to breakpoint on while debugging some scripts.

[issue42531] importlib.resources.path() raises TypeError for packages without __file__

Jason R. Coombs added the comment: Thanks William for the detailed problem description. If the issue has been fixed on Python 3.9 but not on 3.8, then it was likely a redesign that enabled the improved behavior, a redesign that won't be ported back to Python 3.8 and earlier. In these

[issue23805] _hashlib compile error?

Irit Katriel added the comment: Freddy, this issue is 5 years old with no activity and no indicated action for the python devs, so I am closing it. If you are still seeing compilation errors, please create a new one and update it with more details. -- nosy: +iritkatriel stage: ->

[issue42521] Debug (-d) mode not working in 3.9

miss-islington added the comment: New changeset 9b34f34aa929941576a69a6f7de77f1fb0b96ed6 by Miss Islington (bot) in branch '3.9': bpo-42521: Add note about 'Python -d' only working on debug builds (GH-23607) https://github.com/python/cpython/commit/9b34f34aa929941576a69a6f7de77f1fb0b96ed6

[issue42545] Check that all symbols in the limited ABI are exported

Change by Pablo Galindo Salgado : -- nosy: +vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue42546] copy - Allow dict.copy(deep=True) alongside copy.deepcopy() for easier usage and zen

Irit Katriel added the comment: Deprecating an API is a big project. To justify the time people would have to put into this, it needs to have significant benefits. I don't see them and the OP didn't explain what they are. Suggestions like this should ideally be brought up for discussion on

[issue36964] `python3 -m venv NAME`: virtualenv is not portable

Marco Sulla added the comment: The PR will probably be rejected... you can do something like this: 1. in the venv on our machine, do `pip freeze`. This gives you the whole list of installed dependencies 2. download all the packages using `pip download` 3. copy all the packages on the cloud,

[issue38283] sys._getframe(1).f_lineno changed behavior in 3.8

Change by Irit Katriel : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue42546] copy - Allow dict.copy(deep=True) alongside copy.deepcopy() for easier usage and zen

Daniel Rose added the comment: My apologies. I worded that wrong, I meant adding `deep=True` to `dict.copy()`. Otherwise, you're absolutely right. -- ___ Python tracker ___

[issue42546] copy - Allow dict.copy(deep=True) alongside copy.deepcopy() for easier usage and zen

Change by Daniel Rose : -- title: copy - Allow .copy(deep=True) alongside .deepcopy() for easier usage and zen -> copy - Allow dict.copy(deep=True) alongside copy.deepcopy() for easier usage and zen ___ Python tracker

[issue42536] test_itertools leaks sometimes references

Raymond Hettinger added the comment: Thanks. I'll work on it this evening. If this is new, pairwise() is the most likely cause. -- assignee: -> rhettinger ___ Python tracker

[issue30701] Exception parsing certain invalid email address headers

Irit Katriel added the comment: I don't see the error now, I think this has been fixed. -- nosy: +iritkatriel status: open -> pending ___ Python tracker ___

[issue42547] argparse: add_argument(... nargs='+', metavar=) does not work with positional arguments

Change by Mikhail Khvoinitsky : -- keywords: +patch pull_requests: +22485 stage: -> patch review pull_request: https://github.com/python/cpython/pull/23617 ___ Python tracker

[issue42536] test_itertools leaks sometimes references

Serhiy Storchaka added the comment: You can get a list of all tests with --list-cases and then run them in separate processes. -- ___ Python tracker ___

[issue42547] argparse: add_argument(... nargs='+', metavar=) does not work with positional arguments

New submission from Mikhail Khvoinitsky : Example which works: parser.add_argument('--test', nargs='+', metavar=('TEST', 'TEST2')) Example which doesn't work: parser.add_argument('test', nargs='+', metavar=('TEST', 'TEST2')) it raises: Traceback (most recent call last):

[issue42536] test_itertools leaks sometimes references

STINNER Victor added the comment: > nosy: + rhettinger, serhiy.storchaka I wanted to bisect this test before annoying too many people with this random issue. So far, I managed to simplified test_itertools to: def test_main(verbose=None): test_classes = ( TestBasicOps,

[issue42546] copy - Allow .copy(deep=True) alongside .deepcopy() for easier usage and zen

Steven D'Aprano added the comment: This would be a classic example of the "Flag argument" anti-pattern: https://www.martinfowler.com/bliki/FlagArgument.html -- nosy: +steven.daprano ___ Python tracker

[issue42546] copy - Allow .copy(deep=True) alongside .deepcopy() for easier usage and zen

New submission from Daniel Rose : It would be convenient and cleaner/more in line with the Python zen to allow `.copy()` to allow a `deep=True` argument, to use `.deepcopy()` in a simpler way. This is easier to read, and brings some more usefulness to `.copy()`. `.deepcopy()` would be kept

[issue42545] Check that all symbols in the limited ABI are exported

Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +22484 stage: -> patch review pull_request: https://github.com/python/cpython/pull/23616 ___ Python tracker

[issue40939] Remove the old parser

Pablo Galindo Salgado added the comment: Opened https://bugs.python.org/issue42545 for that -- ___ Python tracker ___ ___

[issue42545] Check that all symbols in the limited ABI are exported

New submission from Pablo Galindo Salgado : >From the discussion at the end of https://bugs.python.org/issue40939 is >important to add a check to the CI that can tell us if we mistakenly remove a >symbol of the limited ABI. -- components: Tests messages: 382336 nosy: pablogsal

[issue42544] In windows, asyncio.run_in_executor strips logger class information from modified logging.Logger objects

New submission from Alex Sherman : IN WINDOWS asyncio's loop.run_in_executor(pool, callback, logger, *args) strips the subclass information about logging.Loggers when passed into concurrent.futures.ProcessPoolExecutor. The logger behaves as a default logging.Logger object as far as I can

[issue36964] `python3 -m venv NAME`: virtualenv is not portable

Cameron Hudson added the comment: @MarcoSulla thank you for opening this issue, it is a very necessary improvement. My use case: I install packages one machine inside VPN, which downloads from a private pypi repo. I then package this as a zip file and deploy it on a cloud-hosted VM. I

[issue42541] Tkinter colours wrong on MacOS universal2

E. Paine added the comment: It seems to be some weird internal mismatch. Code modified from https://wiki.tcl-lang.org/page/Tk+differences+on+Mac+OS+X (see following) suggests that dark mode is not enabled for the window (and yet we are getting white foreground colours) import tkinter as tk

[issue42541] Tkinter colours wrong on MacOS universal2

Ronald Oussoren added the comment: With some luck it might be possible to work around this. If it isn’t we should at least opt out of dark mode for IDLE by changing its Info.plist.

[issue42521] Debug (-d) mode not working in 3.9

Change by Pablo Galindo Salgado : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue41625] Add splice() to the os module

Change by Pablo Galindo Salgado : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue41625] Add splice() to the os module

Pablo Galindo Salgado added the comment: New changeset dedc2cd5f02a2e2fc2c995a36a3dccf9d93856bb by Pablo Galindo in branch 'master': bpo-41625: Do not add os.splice on AIX due to compatibility issues (GH-23608) https://github.com/python/cpython/commit/dedc2cd5f02a2e2fc2c995a36a3dccf9d93856bb

[issue42521] Debug (-d) mode not working in 3.9

Change by miss-islington : -- nosy: +miss-islington nosy_count: 4.0 -> 5.0 pull_requests: +22483 pull_request: https://github.com/python/cpython/pull/23615 ___ Python tracker

[issue42521] Debug (-d) mode not working in 3.9

Pablo Galindo Salgado added the comment: New changeset 99b594404d364b363c184f48338d6ee81bee26dd by Pablo Galindo in branch 'master': bpo-42521: Add note about 'Python -d' only working on debug builds (GH-23607) https://github.com/python/cpython/commit/99b594404d364b363c184f48338d6ee81bee26dd

[issue40939] Remove the old parser

Pablo Galindo Salgado added the comment: > On Windows there is PC/python3dll.c. Even that is severely out of date, unfortunately. There are many functions that were removed in 3.8 and 3.7 that are still listed there. -- ___ Python tracker

[issue42531] importlib.resources.path() raises TypeError for packages without __file__

Change by Brett Cannon : -- nosy: +barry, jaraco -brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue42507] test_ttk_guionly test failures on macOS with Tcl/Tk 8.6.10

Terry J. Reedy added the comment: It might be the tk/tkinter build, not the tests, that is at fault. That is my current conclusion for #42508 (regarding IDLE as a test). -- nosy: +terry.reedy ___ Python tracker

[issue42508] macOS IDLE with Tk 8.6.10 in 3.9.1rc1 universal2 installer fails smoke test

Terry J. Reedy added the comment: The new tk/tkinter bug in the macOS11 U2 build, other than those reported in #42507 and #42541, is that pressing F5 causes the corresponding pseudoevent handler, run_module_event, to be called twice. (Its code is above.) The interval between calls is

[issue42541] Tkinter colours wrong on MacOS universal2

E. Paine added the comment: I just compiled Tk 8.6.10 and it has the same problems. So the question now is whether we work-around it in Tkinter/IDLE or close this issue as third party. -- ___ Python tracker

[issue40939] Remove the old parser

Nikita Nemkin added the comment: > Unfortunately there is no official maintained list if those symbols, so is > taking a while On Windows there is PC/python3dll.c. -- ___ Python tracker

[issue40939] Remove the old parser

Igor Skochinsky added the comment: > I am currently working on test that checks that the stable API symbols are > correctly exported. Thank you very much! For added motivation, the 3.8.0 release was unusable thanks to issue37633 which was somewhat similar (also in pythonrun). For

[issue40939] Remove the old parser

Pablo Galindo Salgado added the comment: I am currently working on test that checks that the stable API symbols are correctly exported. Unfortunately there is no official maintained list if those symbols, so is taking a while -- ___ Python

[issue42543] case sensitivity in open() arguments

New submission from Sean Grogan : I was stuck on a problem today using an open statement where I was trying to open a file for writing e.g. with open("RESULTS.CSV", "W") as csvfile: csvwriter = csv.writer(csvfile) csvwriter.writerow(["X", "Y"])

[issue42541] Tkinter colours wrong on MacOS universal2

Ronald Oussoren added the comment: The problem seems to be that the window background doesn't adjust to dark mode, while the window contents does. I don't know if we should do something in Tkinter for this. -- ___ Python tracker

[issue14111] IDLE Debugger should handle interrupts

Terry J. Reedy added the comment: Mark, since you are working on redoing the debugger gui, do you have any opinion on this? The basic idea is that ^C when debugging should just interrupt the remote process, not end it, just as when there is no debugger. I agree. I just updated the PR to

[issue42542] weakref documentation does not fully describe proxies

New submission from Ryan Govostes : The documentation for weakref.proxy() does not describe how the proxy object behaves when the object it references is gone. The apparent behavior is that it raises a ReferenceError when an attribute of the proxy object is accessed. It would probably be a

[issue42541] Tkinter colours wrong on MacOS universal2

E. Paine added the comment: Sorry, that was an important piece of information. It is worth noting that Text widgets correctly change background to black. -- ___ Python tracker

[issue42541] Tkinter colours wrong on MacOS universal2

E. Paine added the comment: > Are you running in dark mode? Yes. It works fine in light mode. -- ___ Python tracker ___ ___

[issue42541] Tkinter colours wrong on MacOS universal2

Ronald Oussoren added the comment: Are you running in dark mode? -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue42541] Tkinter colours wrong on MacOS universal2

Change by E. Paine : Added file: https://bugs.python.org/file49646/Screenshot-2020-12-02-at-12-46-06.png ___ Python tracker ___ ___

[issue42541] Tkinter colours wrong on MacOS universal2

New submission from E. Paine : When using tkinter from the universal2 package, the colours are completely confused. Most text tries to white, even though the background is light and this makes text in Entries completely unreadable (where the background is white). This affects both Tk and

[issue42540] Debug pymalloc crash when using os.fork() [regression]

New submission from CendioOssman : A python equivalent of the classical daemon() call started throwing an error from 3.8 when the debug hooks are active for pymalloc. If the tracing is also active it segfaults. This simple example triggers it: import os def daemon(): pid = os.fork()

[issue42539] Missing parenthesis in `platform._sys_version_parser`

New submission from Mingchii Suen : in `platform.py`, `_sys_version_parser` the last part of regex is `r'\[([^\]]+)\]?'` which should be `r'(?:\[([^\]]+)\])?' without this change, the question mark only make the last `\]` optional, not the whole part optional this will cause unable to detect

[issue42500] crash with unbounded recursion in except statement

Change by Mark Shannon : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue42246] Implement PEP 626

Mark Shannon added the comment: New changeset 5977a7989d49c3e095c7659a58267d87a17b12b1 by Mark Shannon in branch 'master': bpo-42246: Make sure that line number is correct after a return, as required by PEP 626 (GH-23495)

[issue42500] crash with unbounded recursion in except statement

Mark Shannon added the comment: New changeset 4e7a69bdb63a104587759d7784124492dcdd496e by Mark Shannon in branch 'master': bpo-42500: Fix recursion in or after except (GH-23568) https://github.com/python/cpython/commit/4e7a69bdb63a104587759d7784124492dcdd496e --

[issue42538] AsyncIO strange behaviour

Alexander Greckov added the comment: Thanks! That's resolved my problem, but this thing wasn't really obvious as for me. Probably it would be better to write about this explicitly in docs for the create_task. All in all this issue can be closed. --

[issue42536] test_itertools leaks sometimes references

Change by Serhiy Storchaka : -- nosy: +rhettinger, serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue42537] Implement built-in shorthand b() for breakpoint()

Change by Serhiy Storchaka : -- nosy: +barry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue42538] AsyncIO strange behaviour

Andrew Svetlov added the comment: I understand the issue as the following: 1. You don't save the result of `asyncio.create_task()` somewhere. The task object is dereferenced and thus you see a warning. 2. With PYTHONASYNCIODEBUG on the task is referenced also by internal debug structure,

  1   2   >