| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
help (GH-117035)
Fix error introduced in 4be9fa896117bf07dc944a29c98dd18b71dd6c74.
|
| |
|
|
|
|
|
|
|
|
|
| |
* document equivalent command-line options for all environment variables
* document equivalent environment variables for all command-line options
* reduce the size of variable and option descriptions to minimum
* remove the ending period in single-sentence descriptions
(cherry picked from commit b85572c47dc7a8c65fc366a87a3660fc7a3ed244)
Co-authored-by: Éric <merwok@netwok.org>
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
|
| |
|
|
|
| |
(#116873)
[3.12] gh-116735: Use `MISSING` for `CALL` event if argument is absent (GH-116737)
|
| |
|
|
|
| |
(cherry picked from commit 20578a1f68c841a264b72b00591b11ab2fa77b43)
Co-authored-by: Donghee Na <donghee.na@python.org>
|
| |
|
|
|
| |
(GH-116732)
Backport of GH-116627
|
| |
|
|
|
| |
(GH-116797)
(cherry picked from commit 19ac28bd08fdb16795e6f82ea7bfac73e8f3791b)
|
| |
|
|
|
| |
CLI help (GH-116756) (GH-116786)
(cherry picked from commit 8c6db45ce34df7081d7497e638daf3e130303295)
|
| |
|
|
|
| |
(GH-116739) (GH-116766)
(cherry picked from commit e54bdeab9ce2958a22ba08c1f1f1431c5e8056bd)
|
| |
|
|
|
|
|
| |
* Fix the description of the "-b" option.
* Add references to environment variables for "-s" and "-X dev" options.
(cherry picked from commit 33662d4e01d73cd4f29a25efc2ef09288129023f)
Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
|
| |
|
|
|
|
|
|
| |
(#116496)
gh-116447: Fix possible UB in `arraymodule` and `getargs` (GH-116459)
(cherry picked from commit fdb2d90a274158aee23b526d972172bf41bd4b7e)
Co-authored-by: Nikita Sobolev <mail@sobolevn.me>
|
| |
|
|
|
|
|
|
| |
`sysmodule` (GH-116339) (#116354)
* gh-116326: Handler errors correctly in `getwindowsversion` in `sysmodule` (GH-116339)
(cherry picked from commit c91bdf86ef1cf9365b61a46aa2e51e5d1932b00a)
Co-authored-by: Nikita Sobolev <mail@sobolevn.me>
|
| |
|
|
|
|
|
|
| |
errors (GH-115321) (#116323)
gh-115320: Refactor `get_hash_info` in `sysmodule.c` not to swallow errors (GH-115321)
(cherry picked from commit 207030f5527d405940b79c10c1413c1e8ff696c1)
Co-authored-by: Nikita Sobolev <mail@sobolevn.me>
|
| | |
|
| |
|
|
|
| |
(cherry picked from commit 2e92ffd7fa89e3bd33ee2f31541d3dc53aaa2d12)
Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
|
| |
|
|
|
|
|
| |
'symtable_extend_namedexpr_scope' (GH-96561) (GH-115603)
(cherry picked from commit 664965a1c141e8af5eb465d29099781a6a2fc3f3)
Co-authored-by: wookie184 <wookie1840@gmail.com>
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
unsigned integer type (GH-115029) (GH-115294)
Setters for members with an unsigned integer type now support
the same range of valid values for objects that has a __index__()
method as for int.
Previously, Py_T_UINT, Py_T_ULONG and Py_T_ULLONG did not support
objects that has a __index__() method larger than LONG_MAX.
Py_T_ULLONG did not support negative ints. Now it supports them and
emits a RuntimeWarning.
(cherry picked from commit d9d6909697501a2604d5895f9f88aeec61274ab0)
|
| |
|
|
|
|
|
|
| |
(GH-115139) (#115140)
gh-114828: Fix __class__ in class-scope inlined comprehensions (GH-115139)
(cherry picked from commit fedbf77191ea9d6515b39f958cc9e588d23517c9)
Co-authored-by: Carl Meyer <carl@oddbird.net>
|
| |
|
|
|
|
|
|
|
|
| |
(GH-114391) (GH-115001)
* Fix a RuntimeWarning emitted when assign an integer-like value that
is not an instance of int to an attribute that corresponds to a C
struct member of type T_UINT and T_ULONG.
* Fix a double RuntimeWarning emitted when assign a negative integer value
to an attribute that corresponds to a C struct member of type T_UINT.
(cherry picked from commit 3ddc5152550ea62280124c37d0b4339030ff7df4)
|
| |
|
|
|
|
|
| |
(GH-114700)
(cherry picked from commit 1ac1b2f9536a581f1656f0ac9330a7382420cda1)
Co-authored-by: Nikita Sobolev <mail@sobolevn.me>
|
| |
|
|
| |
__getattr__ (GH-113359) (#114173)
|
| |
|
|
|
|
|
| |
implementation (GH-114385) (#114386)
(cherry picked from commit 38768e4cdd1c4b6e03702da8a94e1c22479d6ed3)
Co-authored-by: Nikita Sobolev <mail@sobolevn.me>
|
| | |
|
| |
|
|
|
|
|
| |
Python/symtable.c (GH-113843) (GH-113851)
(cherry picked from commit fda901a1ff94ea6cc338b74928acdbc5ee165ed7)
Co-authored-by: Yan Yanchii <yyanchiy@gmail.com>
|
| |
|
|
|
|
|
|
|
| |
PyAST_mod2obj call. (GH-113035) (GH-113472)
(cherry picked from commit 48c49739f5502fc7aa82f247ab2e4d7b55bdca62)
Co-authored-by: Yilei Yang <yileiyang@google.com>
Co-authored-by: Gregory P. Smith [Google LLC] <greg@krypto.org>
|
| |
|
|
| |
context managers (#113327) (#113404)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
gh-113343: Fix error check on mmap(2) (GH-113342)
Fix error check on mmap(2)
It should check MAP_FAILED instead of NULL for error.
On mmap(2) man page:
RETURN VALUE
On success, mmap() returns a pointer to the mapped area.
On error, the value MAP_FAILED (that is, (void *) -1) is
returned, and errno is set to indicate the error.
(cherry picked from commit 6b70c3dc5ab2f290fcdbe474bcb7d6fdf29eae4c)
Co-authored-by: Namhyung Kim <namhyung@gmail.com>
|
| |
|
|
|
|
|
|
|
| |
(GH-112770) (GH-113103)
It was raised in two cases:
* in the import statement when looking up __import__
* in pickling some builtin type when looking up built-ins iter, getattr, etc.
(cherry picked from commit 1161c14e8c68296fc465cd48970b32be9bee012e)
|
| |
|
|
|
| |
tokenize module (GH-112949) (#112957)
(cherry picked from commit a135a6d2c6d503b186695f01efa7eed65611b04e)
|
| |
|
|
|
|
|
|
|
|
|
|
| |
(#112651)
gh-106560: Fix redundant declarations in Python/frozen.c (#112612)
Avoid duplicated declarations of "extern" functions in
Python/frozen.c.
Compiler warnings seen by building Python with gcc -Wredundant-decls.
(cherry picked from commit d9e444dbb86e173ee5b8491e3facbd447b91eaed)
|
| |
|
|
|
|
|
| |
(#112590)
(cherry picked from commit a73aa48e6bec900be7edd3431deaa5fc1d809e6f)
Signed-off-by: Pablo Galindo <pablogsal@gmail.com>
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(gh-110311) (gh-110714)
We do the following:
* add a per-interpreter XID registry (PyInterpreterState.xidregistry)
* put heap types there (keep static types in _PyRuntimeState.xidregistry)
* clear the registries during interpreter/runtime finalization
* avoid duplicate entries in the registry (when _PyCrossInterpreterData_RegisterClass() is called more than once for a type)
* use Py_TYPE() instead of PyObject_Type() in _PyCrossInterpreterData_Lookup()
The per-interpreter registry helps preserve isolation between interpreters. This is important when heap types are registered, which is something we haven't been doing yet but I will likely do soon.
(cherry-picked from commit 80dc39e1dc2abc809f448cba5d2c5b9c1c631e11)
|
| |
|
|
|
|
|
|
|
| |
(gh-109921) (gh-110707)
The existence of background threads running on a subinterpreter was preventing interpreters from getting properly destroyed, as well as impacting the ability to run the interpreter again. It also affected how we wait for non-daemon threads to finish.
We add PyInterpreterState.threads.main, with some internal C-API functions.
(cherry-picked from commit 1dd9dee45d2591b4e701039d1673282380696849)
|
| |
|
|
|
| |
(gh-109794) (gh-110705)
Essentially, we should check the thread ID rather than the thread state pointer.
|
| |
|
|
|
|
|
|
|
| |
(gh-110713)
We tried this before with a dict and for all interned strings. That ran into problems due to interpreter isolation. However, exclusively using a per-interpreter cache caused some inconsistency that can eliminate the benefit of interning. Here we circle back to using a global cache, but only for statically allocated strings. We also use a more-basic _Py_hashtable_t for that global cache instead of a dict.
Ideally we would only have the global cache, but the optional isolation of each interpreter's allocator means that a non-static string object must not outlive its interpreter. Thus we would have to store a copy of each such interned string in the global cache, tied to the main interpreter.
(cherry-picked from commit b72947a8d26915156323ccfd04d273199ecb870c)
|
| |
|
|
|
|
|
| |
This change makes sure sys.path[0] is set properly for subinterpreters. Before, it wasn't getting set at all.
This change does not address the broader concerns from gh-109853.
(cherry-picked from commit a040a32ea2f13f16172394d3e3e3f80f47f25a68)
|
| |
|
|
|
|
| |
(gh-109556) (gh-112288)
This fixes some crashes in the _xxinterpchannels module, due to a race between interpreters.
(cherry picked from commit fd7e08a6f35581e1189b9bf12feb51f7167a86c5)
|
| |
|
|
|
|
|
| |
tuples in PyArg_Parse (gh-112439) (GH-112460)
(cherry picked from commit 4eea1e82369fbf7a795d1956e7a8212a1b58009f)
Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
|
| |
|
|
|
| |
(cherry picked from commit 29af7369dbbbba8cefafb196e977bce8189a527d)
Co-authored-by: AN Long <aisk@users.noreply.github.com>
|
| | |
|
| |
|
| |
PyFrame_GetCode() returns a strong reference.
|
| |
|
|
|
|
|
| |
(GH-111655) (#111674)
(cherry picked from commit 3a1b09e6d070778d78d81084f88d37377d38ee9b)
Co-authored-by: AN Long <aisk@users.noreply.github.com>
|
| |
|
|
|
|
| |
line number (GH-111548) (#111551)
.
(cherry picked from commit abb15420c11d9dda9c89f74eac8417240b321109)
|
| |
|
|
| |
(#111346)
|
| | |
|
| |
|
|
|
|
| |
gh-110514: Add PY_THROW to `sys.setprofile` events (GH-110524)
(cherry picked from commit dd4bb0529e44ac6f75a9ebbfcbf5d73dc251b7a7)
Co-authored-by: Tian Gao <gaogaotiantian@hotmail.com>
|
| |
|
|
|
|
|
|
| |
(GH-110238) (#110511)
gh-110237: Check `PyList_Append` for errors in `_PyEval_MatchClass` (GH-110238)
(cherry picked from commit dd9d781da30aa3740e54c063a40413c542d78c25)
Co-authored-by: denballakh <47365157+denballakh@users.noreply.github.com>
|
| |
|
|
|
|
|
|
| |
HAVE_PTHREAD_STUBS` (GH-110487) (GH-110491)
GH-110455: Guard `assert(tstate->thread_id > 0)` with `GH-ifndef HAVE_PTHREAD_STUBS` (GH-110487)
(cherry picked from commit 5fd8821cf8eb1fe2e8575f8c7cc747cf78855a88)
Co-authored-by: Brett Cannon <brett@python.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(#110342)
* gh-108987: Fix _thread.start_new_thread() race condition (#109135)
Fix _thread.start_new_thread() race condition. If a thread is created
during Python finalization, the newly spawned thread now exits
immediately instead of trying to access freed memory and lead to a
crash.
thread_run() calls PyEval_AcquireThread() which checks if the thread
must exit. The problem was that tstate was dereferenced earlier in
_PyThreadState_Bind() which leads to a crash most of the time.
Move _PyThreadState_CheckConsistency() from thread_run() to
_PyThreadState_Bind().
(cherry picked from commit 517cd82ea7d01b344804413ef05610934a43a241)
* gh-109795: `_thread.start_new_thread`: allocate thread bootstate using raw memory allocator (#109808)
(cherry picked from commit 1b8f2366b38c87b0450d9c15bdfdd4c4a2fc3a01)
---------
Co-authored-by: Radislav Chugunov <52372310+chgnrdv@users.noreply.github.com>
|