| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
or builtins for importing submodules or "from import". Fixed handling an
error of non-string package name.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
(closes #27514)
Patch by Ammar Askar.
|
| | |
| | |
| | |
| | | |
generated by Argument Clinic. Patch by Petr Viktorin.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Issue #27278. It should fix a conversion warning.
In practice, the Linux kernel doesn't return more than 32 MB per call to the
getrandom() syscall.
|
| | | |
|
| | |
| | |
| | |
| | | |
Casting Py_ssize_t to Py_ssize_t is useless.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Issue #27278: Fix os.urandom() implementation using getrandom() on Linux.
Truncate size to INT_MAX and loop until we collected enough random bytes,
instead of casting a directly Py_ssize_t to int.
|
| | |
| | |
| | |
| | |
| | | |
function with generalized unpacking (PEP 448) and conflicting keyword names
could cause undefined behavior.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Issue #26839: On Linux, os.urandom() now calls getrandom() with GRND_NONBLOCK
to fall back on reading /dev/urandom if the urandom entropy pool is not
initialized yet. Patch written by Colm Buckley.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Most fixes to Doc/ and Lib/ directories by Ville Skyttä.
|
| | |
| | |
| | |
| | | |
format unit.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Issue #27057: Fix os.set_inheritable() on Android, ioctl() is blocked by
SELinux and fails with EACCESS. The function now falls back to fcntl().
Patch written by Michał Bednarski.
|
| | | |
|
| | |
| | |
| | |
| | | |
Patch by Xiang Zhang.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Patch by Ofer Schwarz.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
This affects documentation, code comments, and a debugging messages.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Issue #26735: Fix os.urandom() on Solaris 11.3 and newer when reading more than
1,024 bytes: call getrandom() multiple times with a limit of 1024 bytes per
call.
|
| | |
| | |
| | |
| | | |
in places where Py_DECREF was used.
|
| | |
| | |
| | |
| | | |
error handler for stdin and stdout.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Issue #26161: Use Py_uintptr_t instead of void* for atomic pointers in
pyatomic.h. Use atomic_uintptr_t when <stdatomic.h> is used.
Using void* causes compilation warnings depending on which implementation of
atomic types is used.
|
| | |
| | |
| | |
| | |
| | | |
Issue #26563: Py_FatalError: disable faulthandler before trying to flush
sys.stdout and sys.stderr.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Issue #26558: If Py_FatalError() is called without the GIL, don't try to print
the current exception, nor try to flush stdout and stderr: only dump the
traceback of Python threads.
|
| | |
| | |
| | |
| | | |
Issue #25888
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
'level' is specified but no __package__.
This brings the function inline with builtins.__import__(). Thanks to
Manuel Jacob for the patch.
|
| | |
| | |
| | |
| | | |
if the stack is too deep.
|
| | |
| | |
| | |
| | |
| | | |
Fixed the documented about buffer overflow error for "es#" and "et#" format
units.
|
| | |
| | |
| | |
| | | |
Based on patch by Hagen Fürstenau and Daniel Urban.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Issue #25843: When compiling code, don't merge constants if they are equal but
have a different types. For example, "f1, f2 = lambda: 1, lambda: 1.0" is now
correctly compiled to two different functions: f1() returns 1 (int) and f2()
returns 1.0 (int), even if 1 and 1.0 are equal.
Add a new _PyCode_ConstantKey() private function.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Issue #26154: Add a new private _PyThreadState_UncheckedGet() function which
gets the current thread state, but don't call Py_FatalError() if it is NULL.
Python 3.5.1 removed the _PyThreadState_Current symbol from the Python C API to
no more expose complex and private atomic types. Atomic types depends on the
compiler or can even depend on compiler options. The new function
_PyThreadState_UncheckedGet() allows to get the variable value without having
to care of the exact implementation of atomic types.
Changes:
* Replace direct usage of the _PyThreadState_Current variable with a call to
_PyThreadState_UncheckedGet().
* In pystate.c, replace direct usage of the _PyThreadState_Current variable
with the PyThreadState_GET() macro for readability.
* Document also PyThreadState_Get() in pystate.h
|
|\ \ \
| |/ / |
|
| |\ \
| | |/ |
|
| | | |
|
| | |
| | |
| | |
| | | |
robust (closes #25973)
|
| | |
| | |
| | |
| | |
| | | |
This patch is manually crafted and contains changes that couldn't be handled
automatically.
|
| | |
| | |
| | |
| | | |
The patch is automatically generated, it replaces the code that uses Py_CLEAR.
|
| | |
| | |
| | |
| | | |
macro Py_SETREF.
|