| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
function instead of the getentropy() function. The getentropy() function is
blocking to generate very good quality entropy, os.urandom() doesn't need such
high-quality entropy.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
On the x86 OpenBSD 5.8 buildbot, the integer overflow check is ignored. Copy
the tv_sec variable into a Py_time_t variable instead of "simply" casting it to
Py_time_t, to fix the integer overflow check.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
OpenBSD", I'm not sure that the change was really needed. I read the test
result of an old build because the OpenBSD was 100 builds late.
|
| | | |
| | | |
| | | |
| | | | |
Patch written by Remi Pointel.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
It looks like the check for integer overflow doesn't work on x86 OpenBSD 5.8.
|
|\ \ \ \
| |/ / / |
|
| | | |
| | | |
| | | |
| | | | |
the line number and col offset of the AST node (closes #25131)
|
| | | |
| | | |
| | | |
| | | |
| | | | |
_PyTime_Divide() rounding was wrong: copy code from Python default which has
now much better unit tests.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
On Windows, the tv_sec field of the timeval structure has the type C long,
whereas it has the type C time_t on all other platforms. A C long has a size of
32 bits (signed inter, 1 bit for the sign, 31 bits for the value) which is not
enough to store an Epoch timestamp after the year 2038.
Add the _PyTime_AsTimevalTime_t() function written for datetime.datetime.now():
convert a _PyTime_t timestamp to a (secs, us) tuple where secs type is time_t.
It allows to support dates after the year 2038 on Windows.
Enhance also _PyTime_AsTimeval_impl() to detect overflow on the number of
seconds when rounding the number of microseconds.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
use ast_error instead of PyErr_SetString.
|
| | | |
| | | |
| | | |
| | | | |
character and format_spec are checked. This allows for error messages that more closely match what a user would expect.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Documentation is still needed, I'll open an issue for that.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
function instead of the getentropy() function. The getentropy() function is
blocking to generate very good quality entropy, os.urandom() doesn't need such
high-quality entropy.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
On Windows, the tv_sec field of the timeval structure has the type C long,
whereas it has the type C time_t on all other platforms. A C long has a size of
32 bits (signed inter, 1 bit for the sign, 31 bits for the value) which is not
enough to store an Epoch timestamp after the year 2038.
Add the _PyTime_AsTimevalTime_t() function written for datetime.datetime.now():
convert a _PyTime_t timestamp to a (secs, us) tuple where secs type is time_t.
It allows to support dates after the year 2038 on Windows.
Enhance also _PyTime_AsTimeval_impl() to detect overflow on the number of
seconds when rounding the number of microseconds.
|
|\ \ \ \
| |/ / / |
|
| | | |
| | | |
| | | |
| | | | |
import_init() imports the "_imp" module, not the "imp" module.
|
|\ \ \ \
| |/ / / |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Overflow test in test_FromSecondsObject() fails on FreeBSD 10.0 buildbot which
uses clang. clang implements more aggressive optimization which gives
different result than GCC on undefined behaviours.
Check if a multiplication will overflow, instead of checking if a
multiplicatin had overflowed, to avoid undefined behaviour.
Add also debug information if the test on overflow fails.
|
| | | |
| | | |
| | | |
| | | | |
Use volatile keyword in _PyTime_AsSecondsDouble()
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
3.x" buildbot
Use volatile keyword in _PyTime_Round()
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* Filter values which would overflow on conversion to the C long type
(for timeval.tv_sec).
* Adjust also the message of OverflowError on PyTime conversions
* test_time: add debug information if a timestamp conversion fails
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Drop all hardcoded tests. Instead, reimplement each function in Python, usually
using decimal.Decimal for the rounding mode.
Add much more values to the dataset. Test various timestamp units from
picroseconds to seconds, in integer and float.
Enhance also _PyTime_AsSecondsDouble().
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
datetime.datetime now round microseconds to nearest with ties going to nearest
even integer (ROUND_HALF_EVEN), as round(float), instead of rounding towards
-Infinity (ROUND_FLOOR).
pytime API: replace _PyTime_ROUND_HALF_UP with _PyTime_ROUND_HALF_EVEN. Fix
also _PyTime_Divide() for negative numbers.
_PyTime_AsTimeval_impl() now reuses _PyTime_Divide() instead of reimplementing
rounding modes.
|
|\ \ \ \
| |/ / / |
|
| |\ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | | |
by the warnings.warn(stacklevel=) parameter.
|
| | | | |
| | | | |
| | | | |
| | | | | |
It is very unlikely that they can occur in real code for now.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
datetime.datetime.fromtimestamp() and datetime.datetime.utcfromtimestamp().
microseconds sign should be kept before rounding.
|
|\ \ \ \ \
| |/ / / / |
|
| |\ \ \ \
| | | |/ /
| | |/| | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Issue #24891: Fix a race condition at Python startup if the file descriptor
of stdin (0), stdout (1) or stderr (2) is closed while Python is creating
sys.stdin, sys.stdout and sys.stderr objects. These attributes are now set
to None if the creation of the object failed, instead of raising an OSError
exception. Initial patch written by Marco Paolini.
|
| | | | |
| | | | |
| | | | |
| | | | | |
Patch by Louis Dassy.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Only use it on the most important number. This change fixes also a compiler
warning on modf().
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Ensure that the tv_nsec field is set, even if the function fails
with an overflow.
|
|\ \ \ \ \
| |/ / / / |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Handle PyCapsule_Import() failure (exception) in PyCodec_NameReplaceErrors():
return immedialty NULL.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Clear PyObject_Str() exception if it failed, ast_error() should not be called
with an exception set.
|
|\ \ \ \ \
| |/ / / / |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
I was not supposed to commit the function with the name pymonotonic_new(). I
forgot to rename it.
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Don't check anymore at runtime that the monotonic clock doesn't go backward.
Yes, it happens. It occurs sometimes each month on a Debian buildbot slave
running in a VM.
The problem is that Python cannot do anything useful if a monotonic clock goes
backward. It was decided in the PEP 418 to not fix the system, but only expose
the clock provided by the OS.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
with ties going away from zero (ROUND_HALF_UP), as Python 2 and Python older
than 3.3, instead of rounding to nearest with ties going to nearest even
integer (ROUND_HALF_EVEN).
|
|\ \ \ \
| |/ / / |
|
| | | | |
|