[issue38534] Version 3.8.0 has released with a wrong MS KB number reference

Wator Sead added the comment: PR16881 I just use the right one to replaced them. -- keywords: +patch message_count: 2.0 -> 3.0 pull_requests: +16425 stage: -> patch review pull_request: https://github.com/python/cpython/pull/16881 ___ Python tracke

[issue38534] Version 3.8.0 has released with a wrong MS KB number reference

Wator Sead added the comment: I can't signe the CLA. Someone will make a new PR. -- ___ Python tracker ___ ___ Python-bugs-list mai

[issue38534] Version 3.8.0 has released with a wrong MS KB number reference

Change by Wator Sead : -- pull_requests: -16425 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue38517] functools.cached_property should support partial functions and partialmethod's

Sergey Fedoseev added the comment: issue38524 is related. -- nosy: +sir-sigurd ___ Python tracker ___ ___ Python-bugs-list mailing

[issue38524] functools.cached_property is not supported for setattr

Change by Sergey Fedoseev : -- nosy: +sir-sigurd ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue38490] statistics: add covariance, Pearson's correlation, and simple linear regression

Change by Tymek Wołodźko : -- title: statistics: add covariance and Pearson's correlation -> statistics: add covariance, Pearson's correlation, and simple linear regression ___ Python tracker

[issue38007] Regression: name of PyType_Spec::slots conflicts with Qt macro

Change by Petr Viktorin : -- nosy: +petr.viktorin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue38555] Undefined behavior in dictreviter_iternext

Serhiy Storchaka added the comment: The pointer can also go before the beginning of the array in a loop if i becomes 0. -- ___ Python tracker ___

[issue38555] Undefined behavior in dictreviter_iternext

New submission from Serhiy Storchaka : &DK_ENTRIES(k)[i] can be evaluated when i is -1. Getting the address before the beginning of the array is an undefined behavior in C. -- components: Interpreter Core messages: 355122 nosy: inada.naoki, serhiy.storchaka priority: normal severity: n

[issue38555] Undefined behavior in dictreviter_iternext

Change by Serhiy Storchaka : -- keywords: +patch pull_requests: +16427 stage: -> patch review pull_request: https://github.com/python/cpython/pull/16883 ___ Python tracker ___

[issue38556] Walrus operator in list comprehensions [Python 3.8.0]

Change by EGN : -- title: Walrus operator in Python 3.8.0 in list comprehensions -> Walrus operator in list comprehensions [Python 3.8.0] ___ Python tracker ___ __

[issue38556] Walrus operator in Python 3.8.0 in list comprehensions

New submission from EGN : Just tried to use Walrus operator in list comprehensions (for loop) and it is not possible. Is it a bug? -- messages: 355124 nosy: EGN priority: normal severity: normal status: open title: Walrus operator in Python 3.8.0 in list comprehensions type: enhanceme

[issue38556] Walrus operator in list comprehensions [Python 3.8.0]

Karthikeyan Singaravelan added the comment: Can you please post a short snippet of what you are trying to do and the issue you are facing like traceback if any? -- nosy: +xtreak ___ Python tracker _

[issue38556] Walrus operator in list comprehensions [Python 3.8.0]

Steven D'Aprano added the comment: We're not mind-readers, how do you expect us to know what you tried if you don't tell us? The walrus operator works for me: >>> [spam for c in "hello world" if (spam:=c.upper()) in 'AEIOU'] ['E', 'O', 'O'] >>> [(spam:=x**2, spam+1) for x in ran

[issue38556] Walrus operator in list comprehensions [Python 3.8.0]

Change by Steven D'Aprano : -- components: +Interpreter Core type: enhancement -> behavior ___ Python tracker ___ ___ Python-bugs-li

[issue38303] Make audioop PEP-384 compatible

miss-islington added the comment: New changeset f548a3e4a28c5496755f9f8d057fc8d031b27655 by Miss Skeleton (bot) (Tyler Kieft) in branch 'master': bpo-38303: Make audioop extension module PEP-384 compatible (GH-16497) https://github.com/python/cpython/commit/f548a3e4a28c5496755f9f8d057fc8d031b

[issue38303] Make audioop PEP-384 compatible

Change by Tyler Kieft : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___ P

[issue38556] Walrus operator in list comprehensions [Python 3.8.0]

EGN added the comment: from os import getcwd, listdir, rename import re [rename(f'{p}{n}', f"{p}{''.join([w[:3] if len(w) > 3 else w for w in re.split('[-_. ]', n)[:-1]])}.{n.split('.')[-1]}") for n in listdir(p := f"{getcwd()}\\{input('Folder: ')}\\")] When I run this code, I'm getting:

[issue38556] Walrus operator in list comprehensions [Python 3.8.0]

EGN added the comment: But if I'm taking main for loop out of the square brackets everything works fine. from os import getcwd, listdir, rename import re for n in listdir(p := f"{getcwd()}\\{input('Folder: ')}\\"): [rename(f'{p}{n}', f"{p}{''.join([w[:3] if len(w) > 3 else w for w in re

[issue38556] Walrus operator in list comprehensions [Python 3.8.0]

EGN added the comment: Even the simple code like this doesn't work: [print(p) for n in (p := ['a', 'b', 'c'])] -- ___ Python tracker ___ _

[issue33463] Can namedtuple._asdict return a regular dict instead of OrderedDict?

Batuhan added the comment: we can close this (raymond resolved this in bpo-35864) -- nosy: +BTaskaya ___ Python tracker ___ ___ Pyt

[issue28562] test_asyncio fails on Android upon calling getaddrinfo()

Xavier de Gaye added the comment: According to my last post on this issue 2 years ago, this test "does not fail on android-24-x86_64". This means that it does not fail on API level 24. IMO the issue may be closed. -- ___ Python tracker

[issue24313] json fails to serialise numpy.int64

Batuhan added the comment: What is the next step of this 4-year-old issue? I think i can prepare a patch for using __index__ (as suggested by @r.david.murray) -- nosy: +BTaskaya ___ Python tracker _

[issue38539] Update demo files

Change by Julin : -- keywords: +patch pull_requests: +16428 stage: -> patch review pull_request: https://github.com/python/cpython/pull/16890 ___ Python tracker ___ __

[issue25635] urllib2 cannot fully read FTP file

Batuhan added the comment: It works as expected on master (3.9.0a0). I think we can close this -- nosy: +BTaskaya ___ Python tracker ___ __

[issue35448] ConfigParser .read() - handling of nonexistent files

Batuhan added the comment: Adrian are you still want to work on this or can i take it? -- nosy: +BTaskaya ___ Python tracker ___ __

[issue38539] Update demo files

Julin added the comment: I've made a PR. Can you review it? -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue33463] Can namedtuple._asdict return a regular dict instead of OrderedDict?

Change by Raymond Hettinger : -- resolution: -> out of date stage: patch review -> resolved status: open -> closed ___ Python tracker ___ _

[issue38554] A fatal error in test_descr

Emmanuel Arias added the comment: I can't reproduce the error -- nosy: +eamanu ___ Python tracker ___ ___ Python-bugs-list mailing

[issue38554] A fatal error in test_descr

Emmanuel Arias added the comment: I' am using: Python 3.9.0a0 (heads/master:f548a3e4a2, Oct 22 2019, 12:02:14) [GCC 6.3.0 20170516] On Debian 9 -- ___ Python tracker ___ ___

[issue38556] Walrus operator in list comprehensions [Python 3.8.0]

Eric V. Smith added the comment: This is explicitly mentioned in PEP 572 as being disallowed: "Due to design constraints in the reference implementation (the symbol table analyser cannot easily detect when names are re-used between the leftmost comprehension iterable expression and the rest

[issue38557] PyTuple_GetSlice docs minor inaccuracy

New submission from wim glenn : https://docs.python.org/3/c-api/tuple.html#c.PyTuple_GetSlice In the c-api it says (emphasis mine): PyObject* PyTuple_GetSlice(PyObject *p, Py_ssize_t low, Py_ssize_t high)¶ Return value: New reference. Take a slice of the tuple pointed to by p from

[issue38460] 3.8 Release Notes: document asyncio exception changes

Sebastian Rittau added the comment: Also it seems there are various new arguments and methods in asyncio that are not in the release notes. (Via https://github.com/python/typeshed/issues/2313). -- ___ Python tracker

[issue24313] json fails to serialise numpy.int64

Serhiy Storchaka added the comment: We could use __index__ for serializing numpy.int64. But what to do with numpy.float32 and numpy.float128? It is a part of a much larger problem (which includes other numbers, collections, encoded strings, named tuples and data classes, etc). I am working o

[issue38460] 3.8 Release Notes: document asyncio exception changes

Andrew Svetlov added the comment: > code that incorrectly imported directly from the submodules will break That's true. Please note: incorrect code will break. The correct code keeps working. I'm personally not sure if we need to reflect *private* API change in Release Notes. Another quest

[issue38466] [Easy doc] threading.excepthook doc talks about "object"

Change by Roundup Robot : -- keywords: +patch pull_requests: +16430 stage: -> patch review pull_request: https://github.com/python/cpython/pull/16891 ___ Python tracker ___ __

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

Change by miss-islington : -- pull_requests: +16431 pull_request: https://github.com/python/cpython/pull/16892 ___ Python tracker ___ __

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

Change by miss-islington : -- pull_requests: +16432 pull_request: https://github.com/python/cpython/pull/16893 ___ Python tracker ___ __

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

STINNER Victor added the comment: New changeset 028f7349a0f6eaea0fec31becb587fcdf6e3cb28 by Victor Stinner in branch 'master': bpo-37415: Fix stdatomic.h header check for ICC compiler (GH-16717) https://github.com/python/cpython/commit/028f7349a0f6eaea0fec31becb587fcdf6e3cb28 -- __

[issue28562] test_asyncio fails on Android upon calling getaddrinfo()

STINNER Victor added the comment: Ok, thanks Xavier. If someone has an issue with test_asyncio on Android, either reopen this issue or open a new issue ;-) -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python t

[issue38447] test_multiprocessing_spawn: Dangling processes: {} on AMD64 RHEL7 Refleaks 3.7

STINNER Victor added the comment: New failure on AMD64 RHEL7 Refleaks 3.7: https://buildbot.python.org/all/#/builders/311/builds/34 0:18:35 load avg: 2.24 [414/416/1] test_multiprocessing_spawn failed (env changed) (13 min 55 sec) -- running: test_concurrent_futures (8 min 43 sec), test_asy

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

miss-islington added the comment: New changeset b102e4f05278c1b06130885eba961bd0193733b4 by Miss Skeleton (bot) in branch '3.7': bpo-37415: Fix stdatomic.h header check for ICC compiler (GH-16717) https://github.com/python/cpython/commit/b102e4f05278c1b06130885eba961bd0193733b4 -- n

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

miss-islington added the comment: New changeset dbcea39ba713cc5b31fa1a243b16a0128c231c98 by Miss Skeleton (bot) in branch '3.8': bpo-37415: Fix stdatomic.h header check for ICC compiler (GH-16717) https://github.com/python/cpython/commit/dbcea39ba713cc5b31fa1a243b16a0128c231c98 --

[issue38323] test_asyncio: test_close_kill_running() hangs on AMD64 RHEL7 Refleaks 3.x

Change by STINNER Victor : -- title: test_ayncio: test_close_kill_running() hangs on AMD64 RHEL7 Refleaks 3.x -> test_asyncio: test_close_kill_running() hangs on AMD64 RHEL7 Refleaks 3.x ___ Python tracker _

[issue38323] test_ayncio: test_close_kill_running() hangs on AMD64 RHEL7 Refleaks 3.x

STINNER Victor added the comment: Also on x86 Gentoo Refleaks 3.x: https://buildbot.python.org/all/#/builders/1/builds/754 6:11:43 load avg: 1.44 [419/419/2] test_asyncio crashed (Exit code 1) beginning 6 repetitions 123456 Timeout (3:15:00)! Thread 0xb7c4d700 (most recent call first): File

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

STINNER Victor added the comment: According to Adam J. Stewart, my PR 16717 fix the Python build on ICC: https://github.com/python/cpython/pull/16717#issuecomment-544812182 So I merged it in 3.7, 3.8 and master branches. Adam saw other failures, but it's unrelated issues which should be repor

[issue38558] Data Structures documentation out of sync with new Walrus operator

New submission from Matt Ward : The 3.8 documentation still includes the text. ```Note that in Python, unlike C, assignment cannot occur inside expressions. C programmers may grumble about this, but it avoids a common class of problems encountered in C programs: typing = in an expression when

[issue38466] [Easy doc] threading.excepthook doc talks about "object"

Change by miss-islington : -- pull_requests: +16433 pull_request: https://github.com/python/cpython/pull/16894 ___ Python tracker ___ __

[issue38466] [Easy doc] threading.excepthook doc talks about "object"

STINNER Victor added the comment: New changeset 91528f40c30717563a478920861c81d18da5bf63 by Victor Stinner (Daniel Baskal) in branch 'master': bpo-38466: Fix threading.excepthook doc (GH-16891) https://github.com/python/cpython/commit/91528f40c30717563a478920861c81d18da5bf63 -- ___

[issue38466] [Easy doc] threading.excepthook doc talks about "object"

miss-islington added the comment: New changeset 6329a56ca7f99075caa95a075024736a90ad2857 by Miss Skeleton (bot) in branch '3.8': bpo-38466: Fix threading.excepthook doc (GH-16891) https://github.com/python/cpython/commit/6329a56ca7f99075caa95a075024736a90ad2857 -- nosy: +miss-isling

[issue38538] dictobject dictviews don't return NotImplemented for unrecognized types.

Julien Palard added the comment: > It is not strange since dict.keys() in Python 2.7 returns list. Oh, ok thanks :) Do you think that it should be fixed? As it works with sets, I think so: >>> set() | Ror() set() but it's not that simple as the __or__ of dictviews is less strict that the _

[issue35448] ConfigParser .read() - handling of nonexistent files

Adrian Wielgosik added the comment: Yeah, I lost steam on this issue, sorry. Go ahead :) -- ___ Python tracker ___ ___ Python-bugs-

[issue38323] test_asyncio: test_close_kill_running() hangs on AMD64 RHEL7 Refleaks 3.x

STINNER Victor added the comment: I'm able to reproduce the issue locally using the command: ./python -m test test_asyncio --match=test.test_asyncio.test_subprocess.SubprocessMultiLoopWatcherTests.test_close_kill_running -v -F -j20 --timeout=30.0 Example: ... 0:00:47 load avg: 14.35 [287]

[issue38323] asyncio: MultiLoopWatcher has a race condition (test_asyncio: test_close_kill_running() hangs on AMD64 RHEL7 Refleaks 3.x)

Change by STINNER Victor : -- title: test_asyncio: test_close_kill_running() hangs on AMD64 RHEL7 Refleaks 3.x -> asyncio: MultiLoopWatcher has a race condition (test_asyncio: test_close_kill_running() hangs on AMD64 RHEL7 Refleaks 3.x) ___ Python

[issue38559] async generators aclose() behavior in 3.8

New submission from Yury Selivanov : I believe I might have discovered a problem with asynchronous generators in 3.8. # Prelude In Python prior to 3.8 it was possible to overlap running of "asend()" and "athrow()" methods for the same asynchronous generator. In plain English, it was possibl

[issue38323] asyncio: MultiLoopWatcher has a race condition (test_asyncio: test_close_kill_running() hangs on AMD64 RHEL7 Refleaks 3.x)

STINNER Victor added the comment: It seems like MultiLoopChildWatcher doesn't respect the PEP 475: siginterrupt(False) must not be used. But the following change isn't enough to fix this issue (test_close_kill_running hang). diff --git a/Lib/asyncio/unix_events.py b/Lib/asyncio/unix_events.p

[issue38559] async generators aclose() behavior in 3.8

Yury Selivanov added the comment: Just discussed this issue off-list with Nathaniel. Maybe this isn't as severe as I thought it is. If we cancel all asyncio tasks before calling `loop.shutdown_asyncgens()` this *probably* becomes a non-issue. And "asyncio.run()" does just that [1]. Any as

[issue38466] [Easy doc] threading.excepthook doc talks about "object"

STINNER Victor added the comment: Thanks Daniel Baskal for the fix and Sebastian Rittau for the bug report. The doc is now fixed in 3.8 and master branches. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python

[issue32526] Closing async generator while it is running does not raise an exception

Yury Selivanov added the comment: Was fixed as part of #30773. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ _

[issue38554] A fatal error in test_descr

Change by STINNER Victor : -- nosy: +vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue38559] async generators aclose() behavior in 3.8

Nathaniel Smith added the comment: I think conceptually, cancelling all tasks and waiting for them to exit is the right thing to do. That way you run as much shutdown code as possible in regular context, and also avoid this problem – if there are no tasks, then there can't be any tasks blocke

[issue12598] Move sys variable initialization from import.c to sysmodule.c

STINNER Victor added the comment: No activity for 7 years, I close the issue. -- nosy: +vstinner resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker

[issue38559] async generators aclose() behavior in 3.8

Yury Selivanov added the comment: > So I think asyncio.run is actually totally fine with the 3.8.0 behavior. Yes. Looks like it. > It's only explicit calls to shutdown_asyncgens that might run into this, and > I think that's probably OK? Yes. Calling shutdown_asyncgens after all tasks are

[issue17978] Python crashes if Py_Initialize/Py_Finalize are called multiple times

STINNER Victor added the comment: Program described in msg189250 does not crash on the master branch of Python. The PEP 587 deeply reworked Python initialization code. There is now a preinitialization phase, for example. Moreover, Programs/_testembed.c has a test calling Py_Initialize()+Py_

[issue38234] The value of Py_SetPath is not used to populate the configuration

STINNER Victor added the comment: The initial issue has been fixed, I close the issue. > I would like to keep the issue open since I plan to do one more change: use > PyWideStringList in _PyPathConfig for module_search_paths to support paths > which contains DELIM (":" on Unix). I may use b

[issue12232] embedded python import cmath

STINNER Victor added the comment: No activity since 2011, I close the issue. -- nosy: +vstinner resolution: -> out of date stage: test needed -> resolved status: open -> closed ___ Python tracker __

[issue13562] Notes about module load path

STINNER Victor added the comment: No activity since 2012, I close the issue. Moreover, the PEP 587 now provides a clean C API to configure sys.path. https://docs.python.org/dev/c-api/init_config.html#c.PyConfig.module_search_paths -- nosy: +vstinner resolution: -> out of date stage:

[issue15047] Cygwin install (regen) problem

STINNER Victor added the comment: No activity since 2012, I close the issue. -- nosy: +vstinner resolution: -> out of date stage: patch review -> resolved status: open -> closed ___ Python tracker _

[issue8787] warnings inside PyRun_SimpleString() display argv[1]

STINNER Victor added the comment: Fixed in bpo-33375. commit 11a896652ee98aa44e59ed25237f9efb56635dcf Author: Thomas Kluyver Date: Fri Jun 8 21:28:37 2018 +0200 bpo-33375: Get filename for warnings from frame.f_code.co_filename (GH-6622) More consistent with how other parts of

[issue8787] warnings inside PyRun_SimpleString() display argv[1]

Change by STINNER Victor : -- resolution: fixed -> duplicate superseder: -> warnings: get filename from frame.f_code.co_filename ___ Python tracker ___

[issue33375] warnings: get filename from frame.f_code.co_filename

STINNER Victor added the comment: I closed bpo-8787 as a duplicate of this issue. -- versions: +Python 3.8 ___ Python tracker ___ _

[issue12919] Control what module is imported first

STINNER Victor added the comment: I close the issue since I see disagreement on the feature request. Modules/getpath.c and PC/getpathp.c use Lib/os.py to detect the stdlib directory. _PyUnicode_InitEncodings() is the first function importing modules: to import the Python codec of the filesy

[issue17922] Crash in clear_weakref

STINNER Victor added the comment: There is no activity since 2013. I guess that the user found a way to workaround this crash, or managed to get it fixed. I close the issue. -- nosy: +vstinner resolution: -> out of date stage: -> resolved status: open -> closed

[issue9098] MSYS build fails with `S_IXGRP' undeclared

STINNER Victor added the comment: No activity since 2012, I close the issue. -- nosy: +vstinner resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker __

[issue22139] python windows 2.7.8 64-bit did not install

STINNER Victor added the comment: No activity since 2016, I close the issue. -- nosy: +vstinner resolution: works for me -> out of date status: open -> closed ___ Python tracker _

[issue31074] Startup failure if executable is a \\?\ path on Windows

STINNER Victor added the comment: I got the same bug recently and I fixed it: commit dec39716ca93ee2e8d9b94915ece33014eb58e9e Author: Victor Stinner Date: Mon Sep 30 14:49:34 2019 +0200 bpo-38322: Fix gotlandmark() of PC/getpathp.c (GH-16489) Write the filename into a temporar

[issue13986] ValueError: cannot convert float NaN to integer

STINNER Victor added the comment: The issue has not been seen since 2017-03-04, I close the issue as out of date. -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker

[issue33384] Build does not work with closed stdin on NetBSD

STINNER Victor added the comment: I'm quite that this issue has been fixed by bpo-30225 which is part Python 3.7.4, Python 3.8.0 and newer. I mark the issue as duplicate of bpo-30225. Please reopen the bug if these versions still fail on NetBSD. commit 1c4670ea0cc3d208121af11b9b973e6bb268e5

[issue3367] Uninitialized value read in parsetok.c

STINNER Victor added the comment: I close the issue, it has been fixed. I'm no longer able to reproduce the initial issue: $ ./configure --with-pydebug --with-valgrind $ make clean $ make $ valgrind --suppressions=Misc/valgrind-python.supp ./python ==2670== Memcheck, a memory error detecto

[issue30060] Crash with subinterpreters and Py_NewInterpreter()

Change by STINNER Victor : -- nosy: +eric.snow title: Crash on Py_Finalize if Py_NoSiteFlag is used -> Crash with subinterpreters and Py_NewInterpreter() ___ Python tracker __

[issue34309] Trouble when reloading extension modules.

Change by STINNER Victor : -- nosy: +vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue16353] add function to os module for getting path to default shell

STINNER Victor added the comment: This issue has been fixed. The subprocess module now uses '/system/bin/sh' by default on Android thanks to Xavier de Gaye! -- nosy: +vstinner resolution: -> fixed stage: needs patch -> resolved status: open -> closed

[issue23496] Steps for Android Native Build of Python 3.4.2

STINNER Victor added the comment: It seems like attached patches are outdated: Python has been fixed to support Android. For example, Python now uses the UTF-8 codec rather than mbstowcs() to decode byte strings. I'm quite sure that there are still corner cases which are not well supported o

[issue12806] argparse: Hybrid help text formatter

David Steele added the comment: I came across this thread after making a simple argparse formatter for preserving paragraphs. The submissions here look better than that effort. Here is a quick, hacky look at the patches from one perspective. I wanted to prefer ParagraphFormatterML, but didn'

[issue38419] The path of check-c-globals.py on README is wrong

Carol Willing added the comment: New changeset 20bf8e08a18c0f1eab49c54f3bd56f8364a2f5cc by Carol Willing (AMIR) in branch 'master': bpo-38419: fix "check-c-globals" path (GH-16680) https://github.com/python/cpython/commit/20bf8e08a18c0f1eab49c54f3bd56f8364a2f5cc -- nosy: +willingc

[issue26693] Exception ignored in: in _shutdown, assert tlock.locked()

Change by STINNER Victor : -- nosy: +eric.snow ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue26693] Exception ignored in: in _shutdown, assert tlock.locked()

STINNER Victor added the comment: Extract of test2.C: --- // in main thread Py_Initialize(); PyEval_InitThreads(); PyEval_SaveThread(); // creating a new sub-interpreter, in my real app, this would be created // in a sub-thread. PyInterpreterState* const mainInterpreterState =

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

STINNER Victor added the comment: I tested on the master branch of Python: --- #include void func() { Py_Initialize(); Py_Finalize(); Py_ssize_t cnt = _Py_GetRefTotal(); printf("sys.gettotalrefcount(): %zd\n", cnt); } int main(int argc, char *argv[]) { Py_SetProgramName(L"./_

[issue6741] Garbage collector release method

STINNER Victor added the comment: That's basically a duplicate of bpo-1635741. -- nosy: +vstinner resolution: -> duplicate stage: test needed -> resolved status: open -> closed superseder: -> Py_Finalize() doesn't clear all Python objects at exit

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

STINNER Victor added the comment: I marked bpo-6741 as a duplicate of this issue. -- ___ Python tracker ___ ___ Python-bugs-list

[issue24770] Py_Finalize() doesn't stop daemon threads

Change by STINNER Victor : -- title: Py_Finalize not cleaning up all threads -> Py_Finalize() doesn't stop daemon threads ___ Python tracker ___ __

[issue26888] Multiple memory leaks after raw Py_Initialize and Py_Finalize.

STINNER Victor added the comment: That's basically a duplicate of bpo-1635741. -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Py_Finalize() doesn't clear all Python objects at exit ___ Python tracker

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

STINNER Victor added the comment: I marked bpo-26888 as a duplicate of this issue. -- ___ Python tracker ___ ___ Python-bugs-list

[issue21387] Memory leaks when embedded interpreter is reinitialized

STINNER Victor added the comment: Duplicate of bpo-1635741. -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Py_Finalize() doesn't clear all Python objects at exit ___ Python tracker

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

STINNER Victor added the comment: I marked bpo-21387 as a duplicate of this issue. -- ___ Python tracker ___ ___ Python-bugs-list

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

STINNER Victor added the comment: One part of this issue is that all C extensions of the stdlib should be updated to implement the PEP 489 "Multi-phase extension module initialization". -- ___ Python tracker

[issue38560] Allow iterable argument unpacking after a keyword argument?

New submission from Brandt Bucher : Calls of the form f(name=value, *args) are currently legal syntax. The resulting argument binding is awkward, and almost never does what you want/expect it to: >>> def f(x, y, z): ... print(x, y, z) ... >>> f(x=0, *(1, 2)) Traceback (most recent call

[issue36107] aarch64 python3 buffer overflow with stack protector on rpi3 (alpine linux)

STINNER Victor added the comment: > It seems like python 3.7.2 works. So yeah, use Python 3.7 or newer. Python 3.8 has been released ;-) > Any idea which commit(s) may have fixed it? I have no idea. -- nosy: +vstinner resolution: -> fixed stage: -> resolved status: open -> closed

[issue12179] Race condition using PyGILState_Ensure on a new thread

STINNER Victor added the comment: Bug report in 2011. I close this old issue. -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker ___

[issue38419] The path of check-c-globals.py on README is wrong

Dong-hee Na added the comment: Thank you for your contribution AMIR! @willingc Thank you for merging PR 16680 Carol :) I am now closing this issue. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

  1   2   >