Oct-23-2020, 01:58 AM
Oct-23-2020, 04:37 AM
This is a rather cryptic statement. What are you trying to do?
Oct-23-2020, 10:06 AM
... a number of different syscalls that i could not find an implementation or stub for, such as pivot_root() and utimensat().
Oct-23-2020, 10:51 AM
If I understand well,
Also the butter project in Pypi claims it has
os.utime()
has a ns
argument that achieves the functionality of utimensat.Also the butter project in Pypi claims it has
pivot_root()
. I have not tried it...Oct-23-2020, 07:28 PM
i searched the Python library manual for "utimens" and found nothing that way. what should i have searched for?
Oct-23-2020, 09:27 PM
Skaperen Wrote:what should i have searched for?At some point, there was utimensat in the Python library.
Oct-24-2020, 02:47 AM
was it removed or renamed?
they could implement support for the -at functions by allowing a 2-tuple of (int,str/bytes) in place of str/bytes for the file path. then no new names would be needed. i wonder if they did that with this as a 3rd option.
they could implement support for the -at functions by allowing a 2-tuple of (int,str/bytes) in place of str/bytes for the file path. then no new names would be needed. i wonder if they did that with this as a 3rd option.
Oct-24-2020, 03:32 AM
to represent nanoseconds in float would require 61 bits of precision. but float is C double which is only 53 bits on x86/amd platforms. they just barely achieve microsecond precision (51 bits needed). so something more is needed:
just because a bunch of low numbers can be unique in float does not mean higher ones can. in platforms with 32 bits, int values for seconds can be as high as 2**31-1 (signed). that uses 31 bits of the available precision in float, leaving 22 bits for a fractional part. today is just 1 bit short of that.
i can dream of a world where the standard float size has at least 64 bits of precision. but i must wake up to review python-forum.
- C long double (64 bits)
- decimal.Decimal
- (sec,nsec)
- more function names
just because a bunch of low numbers can be unique in float does not mean higher ones can. in platforms with 32 bits, int values for seconds can be as high as 2**31-1 (signed). that uses 31 bits of the available precision in float, leaving 22 bits for a fractional part. today is just 1 bit short of that.
i can dream of a world where the standard float size has at least 64 bits of precision. but i must wake up to review python-forum.