[Python-Dev] nanosecond stat fields, but not os.path methods ?

2020-12-07 Thread Mats Wichmann
there are stat fields now for ns precision, e.g. st_mtime now has an analogue st_mtime_ns. But os.path didn't grow corresponding methods - there's an os.path.getmtime but not _ms. Was that intentional? The wrappers in genericpath.py are trivial and arguably aren't particularly needed, but

[Python-Dev] Re: nanosecond stat fields, but not os.path methods ?

2020-12-07 Thread David Mertz
Are there any filesystems that can actually record a meaningful ns modification time? I find discussions claiming this: - XFS and EXT3: second precision - EXT4: millisecond precision - NTFS: 100ns precision - APFS: 1 ns precision But also notes that the precision is likely to exceed the accuracy

[Python-Dev] Re: TypedDict behavior

2020-12-07 Thread Guido van Rossum
I suspect a bug. Can you report on bugs.python.org and CC me? On Sun, Dec 6, 2020 at 10:16 PM Paul Bryan wrote: > Is this the expected behavior? > > Python 3.9.0 (default, Oct 7 2020, 23:09:01) > > [GCC 10.2.0] on linux > > Type "help", "copyright", "credits" or "license" for more information.

[Python-Dev] Re: nanosecond stat fields, but not os.path methods ?

2020-12-07 Thread Gregory P. Smith
If the precision is available via OS APIs, this is mostly an issue+PR away from being implemented by someone who cares. FAT32 has a two billion nanosecond resolution IIRC. :P -gps On Mon, Dec 7, 2020 at 8:22 AM David Mertz wrote: > Are there any filesystems that can actually record a meaningfu

[Python-Dev] Re: nanosecond stat fields, but not os.path methods ?

2020-12-07 Thread Antoine Pitrou
On Mon, 7 Dec 2020 16:19:02 + David Mertz wrote: > Are there any filesystems that can actually record a meaningful ns > modification time? I find discussions claiming this: > > - XFS and EXT3: second precision > - EXT4: millisecond precision > - NTFS: 100ns precision > - APFS: 1 ns precision

[Python-Dev] Re: nanosecond stat fields, but not os.path methods ?

2020-12-07 Thread Dan Stromberg
On Mon, Dec 7, 2020 at 10:52 AM Antoine Pitrou wrote: > On Mon, 7 Dec 2020 16:19:02 + > David Mertz wrote: > > Are there any filesystems that can actually record a meaningful ns > > modification time? I find discussions claiming this: > > > > - XFS and EXT3: second precision > > - EXT4: mil

[Python-Dev] SC 2020 recommendation for PEP 634

2020-12-07 Thread Brett Cannon
After much deliberation, the 2020 SC will be making a recommendation to the 2021 SC to accept PEP 634 (although this was not a unanimous decision). This is in no way a binding recommendation to the 2021 SC (even if a majority of current council members get re-elected), but we felt we should pass on

[Python-Dev] Re: nanosecond stat fields, but not os.path methods ?

2020-12-07 Thread Victor Stinner
Le lun. 7 déc. 2020 à 17:22, David Mertz a écrit : > Are there any filesystems that can actually record a meaningful ns > modification time? I find discussions claiming this: > > EXT4: millisecond precision EXT4 and BTRFS have a resolution of 1 nanosecond. > XFS and EXT3: second precision XFS

[Python-Dev] Re: SC 2020 recommendation for PEP 634

2020-12-07 Thread Ethan Furman via Python-Dev
On 12/7/20 11:29 AM, Brett Cannon wrote: After much deliberation, the 2020 SC will be making a recommendation to the 2021 SC to accept PEP 634 (although this was not a unanimous decision). This seems very odd. The Steering Council is elected to make decisions, but it feels like the current SC

[Python-Dev] Re: nanosecond stat fields, but not os.path methods ?

2020-12-07 Thread Victor Stinner
Le lun. 7 déc. 2020 à 19:52, Antoine Pitrou a écrit : > > But also notes that the precision is likely to exceed the accuracy by many > > times on real systems. > > Even if the accuracy is much lower than that, it can be important to > reproduce exact timestamps. Sure, while my initial attempt to

[Python-Dev] Re: SC 2020 recommendation for PEP 634

2020-12-07 Thread Bernat Gabor
This opens the door for people voting on A or B depending on if they would accept or reject the PEP. Is this something we're willing to accept? On Mon, Dec 7, 2020 at 9:29 PM Ethan Furman via Python-Dev < python-dev@python.org> wrote: > On 12/7/20 11:29 AM, Brett Cannon wrote: > > > After much de

[Python-Dev] Re: SC 2020 recommendation for PEP 634

2020-12-07 Thread Thomas Wouters
On Mon, Dec 7, 2020, 22:34 Ethan Furman via Python-Dev < python-dev@python.org> wrote: > On 12/7/20 11:29 AM, Brett Cannon wrote: > > > After much deliberation, the 2020 SC will be making a recommendation to > the 2021 SC to accept PEP 634 (although this was > > not a unanimous decision). > > This

[Python-Dev] Re: SC 2020 recommendation for PEP 634

2020-12-07 Thread Thomas Wouters
On Mon, Dec 7, 2020, 23:10 Bernat Gabor wrote: > This opens the door for people voting on A or B depending on if they would > accept or reject the PEP. Is this something we're willing to accept? > The SC is, and I tried to make that clear in my earlier post about these PEPs ( https://mail.python

[Python-Dev] [RELEASE] Python 3.9.1 is now available, together with 3.10.0a3 and 3.8.7rc1

2020-12-07 Thread Pablo Galindo Salgado
It's starting to get very cold (at least on the Northern hemisphere) so we have been carefully packaging a total of three new Python releases to keep you warm these days! Python 3.9.1 is the first maintenance release of Python 3.9, and also the first version of Python to support macOS 11 Big Sur n

[Python-Dev] Re: Ideas for improving the contribution experience

2020-12-07 Thread Alfred Perlstein
On 10/16/20 3:29 PM, Tal Einat wrote: (Context: Continuing to prepare for the core dev sprint next week. Since the sprint is near, *I'd greatly appreciate any quick comments, feedback and ideas!*) Following up my collection of past beginning contributor experiences, I've collected these expe