[issue47247] Default arguments for access 'mode' parameters in pathlib and os should display as octal literals

Eric V. Smith added the comment: I think this is a duplicate of #46782. -- nosy: +eric.smith ___ Python tracker ___ ___

[issue47247] Default arguments for access 'mode' parameters in pathlib and os should display as octal literals

: 416921 nosy: AidanWoolley, docs@python priority: normal severity: normal status: open title: Default arguments for access 'mode' parameters in pathlib and os should display as octal literals type: enhancement versions: Python 3.10, Python 3.11 ___ Python tracker

[issue47161] pathlib method relative_to doesnt work with // in paths

Change by Barney Gale : -- nosy: +barneygale ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue47161] pathlib method relative_to doesnt work with // in paths

Eryk Sun added the comment: > Hmm..., I get it, but Im not gonna lie it's pretty confusing given > that in other places `//` works as a substitute for `/`. Maybe it > should be mentioned in the documentation? In Linux, the system resolves "//" as just "/". In other POSIX systems, such as

[issue47161] pathlib method relative_to doesnt work with // in paths

Change by Oleg Iarygin : -- keywords: +patch pull_requests: +30271 stage: -> patch review pull_request: https://github.com/python/cpython/pull/32193 ___ Python tracker ___

[issue47161] pathlib method relative_to doesnt work with // in paths

Jan Bronicki added the comment: Hmm..., I get it, but Im not gonna lie it's pretty confusing given that in other places `//` works as a substitute for `/`. Maybe it should be mentioned in the documentation? -- ___ Python tracker

[issue47161] pathlib method relative_to doesnt work with // in paths

Oleg Iarygin added the comment: > But shouldn't it just work with `//` as a `/`? It seems like this is the > behavior elsewhere. It works elsewhere because empty directory names are impossible so can be dropped. But if `//` is placed in the beginning, it gets a special meaning that totally

[issue47161] pathlib method relative_to doesnt work with // in paths

Jan Bronicki added the comment: But shouldn't it just work with `//` as a `/`? It seems like this is the behavior elsewhere. Sure I get that it cannot be done for 3.8. But the new error message implies that either `//` is not a subpath of `/` which it is, or that one is relative and the

[issue47161] pathlib method relative_to doesnt work with // in paths

Oleg Iarygin added the comment: Also, the error message cannot be fixed because for 3.8 only security fixes are accepted since May 2021. For 3.9 and later, the message is already corrected. -- ___ Python tracker

[issue47161] pathlib method relative_to doesnt work with // in paths

Oleg Iarygin added the comment: As I found out, any path starting with two double slashes is treated as an UNC (network) path: root \\machine\mountpoint\directory\etc\... directory ^ So "/Library/Video" and "/" are directories

[issue47161] pathlib method relative_to doesnt work with // in paths

Oleg Iarygin added the comment: I started to investigate and found that a double slash in the beginning cancels any parsing of a path: >>> Path("//Library/Video")._parts ['Library\\Video\\'] vs >>> Path("/Library/Video")._parts ['\\', 'Library', 'Video'] Investigating

[issue47161] pathlib method relative_to doesnt work with // in paths

New submission from Jan Bronicki : The `//` path should be equivalent to `/`, and in some ways, it does behave like that in pathlib. But in the `relative_to` method on a `Path` object, it does not work This is causing our CI pipeline to fail. In the documentation here you can see `//` being

[issue44136] Remove pathlib flavours

Change by Barney Gale : -- pull_requests: +29813 pull_request: https://github.com/python/cpython/pull/31691 ___ Python tracker ___

[issue43455] pathlib mistakenly assumes os.getcwd() is a resolved path in Windows

Tzu-ping Chung added the comment: I believe this has been fixed in https://github.com/python/cpython/pull/25264 -- ___ Python tracker ___

[issue44136] Remove pathlib flavours

Barney Gale added the comment: ^ just to bring my previous comment up-to-date: I'm no longer pursuing adding `os.path.isreserved()` and `os.path.fileuri()` functions, or modifying `normpath()`. At least, not for now! Instead, my plan is to move flavour functionality as follows (as

[issue42234] pathlib relative_to behaviour change

Change by Socob <206a8...@opayq.com>: -- nosy: +Socob ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue32442] Result of pathlib Path.resolve() with UNC path is not very useful

Mike Auty added the comment: Sorry for the spam, thought I was in a different text box. 5:( -- nosy: +ikelos title: file_open unc -> Result of pathlib Path.resolve() with UNC path is not very useful ___ Python tracker <https://bugs.pyth

[issue43012] Remove pathlib accessors

Change by Éric Araujo : -- nosy: +petr.viktorin resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue43012] Remove pathlib accessors

miss-islington added the comment: New changeset 08f8301b21648d58d053e1a513db8ed32fbf37dd by Barney Gale in branch 'main': bpo-43012: remove `pathlib._Accessor` (GH-25701) https://github.com/python/cpython/commit/08f8301b21648d58d053e1a513db8ed32fbf37dd -- nosy: +miss-islington

[issue46514] Pathlib Path.touch() seems to ignore groups write bit for mode parameter

Ronald Oussoren added the comment: The touch method combines the mode you specify with the active umask (set by os.umask()). This is fairly standard behaviour for Unix APIs that accept a file mode. This is documented at: https://docs.python.org/3/library/pathlib.html#pathlib.Path.touch

[issue46514] Pathlib Path.touch() seems to ignore groups write bit for mode parameter

New submission from Savo Vuksan : The touch function of the Path Object in the Pathlib module seems to ignore the write bit for the second octal number for the groups permission in the mode parameter In the provided script you can see that the output prints -rwxr-xr-- but it should

[issue43012] Remove pathlib accessors

Barney Gale added the comment: Thank you Éric! -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43012] Remove pathlib accessors

Éric Araujo added the comment: PR looks good, just needs a look by a pathlib expert. -- nosy: +eric.araujo, eric.smith, eryksun, pitrou ___ Python tracker <https://bugs.python.org/issue43

[issue46148] Optimize pathlib

Change by Kumar Aditya : -- nosy: -kumaraditya303 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46148] Optimize pathlib

Change by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46148] Optimize pathlib

Change by Barney Gale : -- nosy: +barneygale nosy_count: 8.0 -> 9.0 pull_requests: +28697 pull_request: https://github.com/python/cpython/pull/30492 ___ Python tracker ___

[issue46148] Optimize pathlib

Éric Araujo added the comment: A note about benchmarks: I think timeit is not the right tool for them, but https://github.com/python/pyperformance is -- nosy: +eric.araujo ___ Python tracker

[issue46148] Optimize pathlib

Change by Kumar Aditya : -- resolution: -> postponed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue46148] Optimize pathlib

Kumar Aditya added the comment: I am withdrawing this for now and since there is already a bpo for vectorcall I am closing this. -- ___ Python tracker ___

[issue46148] Optimize pathlib

Change by Dennis Sweeney : -- pull_requests: +28560 pull_request: https://github.com/python/cpython/pull/27828 ___ Python tracker ___

[issue44136] Remove pathlib flavours

Change by Barney Gale : -- pull_requests: +28537 pull_request: https://github.com/python/cpython/pull/30321 ___ Python tracker ___

[issue44136] Remove pathlib flavours

Change by Barney Gale : -- pull_requests: +28536 pull_request: https://github.com/python/cpython/pull/30320 ___ Python tracker ___

[issue41593] pathlib PermissionError problem

Andrei Kulakov added the comment: Cannot reproduce on 3.9 and 3.11; the quoted fragment of code is no longer in pathlib. Closing as fixed as it seems that it was fixed in 3.9 or earlier. Please comment if you think it should be reopened. -- nosy: +andrei.avk, kj resolution

[issue46148] Optimize pathlib

Change by Filipe Laíns : -- nosy: +FFY00 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46148] Optimize pathlib

Dennis Sweeney added the comment: I have https://github.com/python/cpython/pull/27828 open already to add vectorcall to itemgetter and attrgetter -- nosy: +Dennis Sweeney ___ Python tracker

[issue46148] Optimize pathlib

Guido van Rossum added the comment: > Note: attrgetter could easily be made faster by migrating it to use > vectorcall. Sure, though code that *doesn't* use attrgetter is usually easier to read -- attrgetter is rare enough in my experience that I usually have to look it up. So making

[issue46148] Optimize pathlib

Josh Rosenberg added the comment: Note: attrgetter could easily be made faster by migrating it to use vectorcall. -- nosy: +josh.r ___ Python tracker ___

[issue46148] Optimize pathlib

Change by Raymond Hettinger : -- nosy: +pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46148] Optimize pathlib

Guido van Rossum added the comment: I presume https://github.com/faster-cpython/ideas/discussions/194 is also relevant. -- ___ Python tracker ___

[issue46148] Optimize pathlib

Kumar Aditya added the comment: Benchmarks for attrgetter is provided in the PR. -- ___ Python tracker ___ ___ Python-bugs-list

[issue46148] Optimize pathlib

Kumar Aditya added the comment: Optimizations include: - Remove redundant check for functools lru_cache - Replace attrgetter as it is slower than direct access -- ___ Python tracker

[issue46148] Optimize pathlib

Christian Heimes added the comment: Please provide benchmarks and reasons in the ticket. A BPO issue should contain all relevant information for a change. -- nosy: +christian.heimes ___ Python tracker

[issue46148] Optimize pathlib

Change by Kumar Aditya : -- keywords: +patch pull_requests: +28449 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30226 ___ Python tracker ___

[issue46148] Optimize pathlib

New submission from Kumar Aditya : Issue for tracking improving performance of pathlib module. -- components: Library (Lib) messages: 409015 nosy: gvanrossum, kumaraditya303 priority: normal severity: normal status: open title: Optimize pathlib type: performance versions: Python 3.11

[issue46050] [pathlib] Option so that OSError does not block glob in pathlib library

false by default?! -- components: Library (Lib) messages: 408314 nosy: matt32106 priority: normal severity: normal status: open title: [pathlib] Option so that OSError does not block glob in pathlib library type: enhancement versions: Python 3.8 ___ Python

[issue45889] pathlib: Path.match does not work on paths

Nick Papior added the comment: Ok, I can accept a no-fix ;) I'll close this. -- resolution: -> wont fix stage: -> resolved status: open -> closed ___ Python tracker ___

[issue45889] pathlib: Path.match does not work on paths

Eric V. Smith added the comment: I agree with Éric and Ronald. -- nosy: +eric.smith ___ Python tracker ___ ___ Python-bugs-list

[issue45889] pathlib: Path.match does not work on paths

Éric Araujo added the comment: FWIW I think in the same way as Ronald. A pattern is not a path, it’s a string expressing rules. If it matches, the results are paths, but that does not make the pattern a path. -- nosy: +eric.araujo ___ Python

[issue45889] pathlib: Path.match does not work on paths

Nick Papior added the comment: Thanks for the discussion. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue45889] pathlib: Path.match does not work on paths

Ronald Oussoren added the comment: I don't think our opinions about this will converge, I'm therefore leaving this discussion. >> would ``Path("dir/some.py").match(Path("*.py"))`` return? > > str(Path("*.py")) == "*.py" > > So no problems here. I do think this is a problem, treating a Path

[issue45889] pathlib: Path.match does not work on paths

Nick Papior added the comment: It basically checks that some part of the path is the same as some part of a reference path, they need not have the same complete parent which is why the resolve command would negate this comparison always. -- As for your last example, that will be quite

[issue45889] pathlib: Path.match does not work on paths

Ronald Oussoren added the comment: I'm not sure what your code tries to accomplish, does it check that ``f.parent`` refers to the same location as ``ref_file``? A clearer solution for that would be ``f.parent.resolve() == ref_file.resolve()``. The argument to match, glob and rglob

[issue45889] pathlib: Path.match does not work on paths

Nick Papior added the comment: > Because of this I don't agree with your idea that anything that can match a > path is a sub-path. Why not? If a match is True, it means that what is matched must be some kind of valid path matching a glob specification. Whether it is a regular expression,

[issue45889] pathlib: Path.match does not work on paths

Ronald Oussoren added the comment: Match doesn't match paths, but basically does a regular expression match on the textual representation (using glob syntax instead of normal regular expression syntax). Because of this I don't agree with your idea that anything that can match a path is a

[issue45889] pathlib: Path.match does not work on paths

Nick Papior added the comment: Ok, I see this a feature. :) As for why it is desirable. A part of a path is still a path, and matching for something must mean that you are matching a partial path. Even if you use '*.py' as the pattern this would still make sense as a path: path =

[issue45889] pathlib: Path.match does not work on paths

Ronald Oussoren added the comment: This would definitely be a new feature and not something that can be back ported. That said, I don't understand why it is desirable to use a Path as the match argument. That argument is a glob pattern (such as "*.py") and not a file name . --

[issue45889] pathlib: Path.match does not work on paths

New submission from Nick Papior : The documentation of Path.match only says it will match a pattern. But quite often this pattern may be desirable to have as a Path as well. import pathlib as pl path = pl.Path("foo/bar") print(path.match("bar")) print(path.match(pl.Pa

[issue22276] pathlib glob ignores trailing slash in pattern

Andrei Kulakov added the comment: Generally if Path is created with a trailing separator, I think it should error out for all methods that apply to files, for example `.touch()`, `read*()`, `write*()`, others. This is consistent with shell commands: touch xyz/

[issue22276] pathlib glob ignores trailing slash in pattern

Andrei Kulakov added the comment: I meant to say: path.glob('myfile/') => [PosixPath('myfile')] -- ___ Python tracker ___ ___

[issue22276] pathlib glob ignores trailing slash in pattern

Andrei Kulakov added the comment: I have also run into this when looking into path.glob('dangling_symlink') issue. I can add a few things (in the examples, *myfile* is a file, not a directory): This is probably more common / less obscure than '*/': path.glob('myfile/') => True This is

[issue25625] "chdir" Contex manager for pathlib

Cameron Simpson added the comment: On 15Nov2021 01:04, Python Bug Reports wrote: >Can you share the link? I haven't seen anything recent. Is it under >other thread? It's in the discuss-ideas part of discuss.python.org during a discussions about a possible new context manager to atomically

[issue25625] "chdir" Contex manager for pathlib

Filipe Laíns added the comment: Can you share the link? I haven't seen anything recent. Is it under other thread? -- ___ Python tracker ___

[issue25625] "chdir" Contex manager for pathlib

Éric Araujo added the comment: There is renewed discussion on python-dev about placing this in contextlib. -- nosy: +eric.araujo ___ Python tracker ___

[issue31842] pathlib: "Incorrect function" during resolve()

Change by Eryk Sun : -- stage: -> needs patch type: -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue31842] pathlib: "Incorrect function" during resolve()

Eryk Sun added the comment: > perfectly valid redirected paths (winfsp ram drives for example) I mounted a WinFsp MEMFS filesystem on a directory, which set a mountpoint that targets the root path of a volume device in the native "\Device" object directory. It didn't create a volume GUID

[issue31842] pathlib: "Incorrect function" during resolve()

Erik Aronesty added the comment: bug is worse than that: perfectly valid redirected paths (winfsp ram drives for example) now break in python 3.9.6 (maybe fixed in later version?) >>> import pathlib >>> p=pathlib.Path('C:\\Users\\erik\\Atakama') >>> p.resolve()

[issue25625] "chdir" Contex manager for pathlib

Change by desbma : -- nosy: -desbma ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue25625] "chdir" Contex manager for pathlib

Łukasz Langa added the comment: New changeset a774285e7d3e63c24dbaaee0b0d9e59ded5c49bf by Thomas Grainger in branch 'main': bpo-25625: [doc] fix async/aync typo (GH-29091) https://github.com/python/cpython/commit/a774285e7d3e63c24dbaaee0b0d9e59ded5c49bf --

[issue25625] "chdir" Contex manager for pathlib

Change by Thomas Grainger : -- nosy: +graingert nosy_count: 10.0 -> 11.0 pull_requests: +27360 pull_request: https://github.com/python/cpython/pull/29091 ___ Python tracker

[issue25625] "chdir" Contex manager for pathlib

Łukasz Langa added the comment: Thanks for perservering, Filipe! ✨  ✨ Per Steering Council decision, the context manager is approved: https://github.com/python/steering-council/issues/77 -- resolution: rejected -> fixed versions: +Python 3.11 -Python 3.9

[issue25625] "chdir" Contex manager for pathlib

Łukasz Langa added the comment: New changeset 3592980f9122ab0d9ed93711347742d110b749c2 by Filipe Laíns in branch 'main': bpo-25625: add contextlib.chdir (GH-28271) https://github.com/python/cpython/commit/3592980f9122ab0d9ed93711347742d110b749c2 -- nosy: +lukasz.langa

[issue25625] "chdir" Contex manager for pathlib

Change by Cameron Simpson : -- nosy: +cameron ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue38222] pathlib Path objects should support __format__

Antoine Pitrou added the comment: I would be in favour of adding Path.__format__, even though I'm not terribly convinced by the use case presented. -- ___ Python tracker ___

[issue38222] pathlib Path objects should support __format__

Eric V. Smith added the comment: > log_dir = Path('logs/{date}') > log_file = Path(str(path).format(time.strftime('%Y-%m-%d')) / 'log.txt' (I think you're missing "date=" in the call to .format().) Could you show what you think this would look like if Path.__format__ existed? I don't think

[issue38222] pathlib Path objects should support __format__

Richard added the comment: Sorry, that should have been: log_dir = Path('logs/{date}') -- ___ Python tracker ___ ___

[issue38222] pathlib Path objects should support __format__

Richard added the comment: I would like for this to be reconsidered. Yes, you can use str(), but converting back and forth becomes really clunky: log_dir = 'logs/{date}' log_file = Path(str(path).format(time.strftime('%Y-%m-%d')) / 'log.txt' -- nosy: +nyuszika7h

[issue25625] "chdir" Contex manager for pathlib

Change by Filipe Laíns : -- pull_requests: +26691 pull_request: https://github.com/python/cpython/pull/28271 ___ Python tracker ___

[issue45009] Get last modified date of Folders and Files using pathlib module

Vedran Čačić added the comment: It probably has nothing to do with your bug, but your title is wrong. You are _not_ getting mtime using pathlib (but using os.path instead). That is done like using this approach: https://docs.python.org/3/library/pathlib.html#pathlib.Path.stat Just

[issue45009] Get last modified date of Folders and Files using pathlib module

Gopesh Singh added the comment: Adding further details: // from os.path import getmtime from datetime import datetime from pathlib import Path import time // System: Operating System: Ubuntu 18.04.5 LTS Python: 3.8.8 -- ___ Python tracker <ht

[issue45009] Get last modified date of Folders and Files using pathlib module

her portal: https://stackoverflow.com/questions/68917983/get-last-modified-date-of-folders-and-files-in-azure-databricks -- components: Library (Lib) messages: 400312 nosy: gopeshsingh priority: normal severity: normal status: open title: Get last modified date of Folders and Files usi

[issue44979] pathlib: support relative path construction

Antoine Pitrou added the comment: I am rejecting this for the reasons explained in the Github PR: """This seems like an extremely specific API. Perhaps you want to propose it for inclusion in pytest, but I don't think it belongs in pathlib. (also, it's not difficult to

[issue44979] pathlib: support relative path construction

Eric V. Smith added the comment: To be clear, by "file", you mean python source file, or I guess .pyc file if only that exists. I can't say I've given it much thought. What about built-in modules? Or frozen modules? I'm not sure this is a great idea. In general, we've frowned on code that

[issue44979] pathlib: support relative path construction

Change by Kirill Pinchuk : -- keywords: +patch pull_requests: +26344 stage: -> patch review pull_request: https://github.com/python/cpython/pull/27890 ___ Python tracker ___

[issue44979] pathlib: support relative path construction

ilename).parent return (base / path).resolve() ``` -- components: Library (Lib) messages: 400075 nosy: cybergrind priority: normal severity: normal status: open title: pathlib: support relative path construction type: enhancement versions: Python 3.11

[issue27827] pathlib is_reserved fails for some reserved paths on Windows

Łukasz Langa added the comment: Barney, thanks for pushing this across the finish line! ✨  ✨ And of course, Eryk for the report and original patch. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.11 -Python 3.8

[issue27827] pathlib is_reserved fails for some reserved paths on Windows

Łukasz Langa added the comment: New changeset debb751f11f5221eafcdf07a14c7e9408350ad9a by Miss Islington (bot) in branch '3.9': bpo-27827: identify a greater range of reserved filename on Windows. (GH-26698) (#27422)

[issue27827] pathlib is_reserved fails for some reserved paths on Windows

Łukasz Langa added the comment: New changeset 8789add99164177f29a8cd319a834187c65ab16c by Miss Islington (bot) in branch '3.10': bpo-27827: identify a greater range of reserved filename on Windows. (GH-26698) (GH-27421)

[issue27827] pathlib is_reserved fails for some reserved paths on Windows

Change by miss-islington : -- pull_requests: +25950 pull_request: https://github.com/python/cpython/pull/27422 ___ Python tracker ___

[issue27827] pathlib is_reserved fails for some reserved paths on Windows

Łukasz Langa added the comment: New changeset 56c1f6d7edad454f382d3ecb8cdcff24ac898a50 by Barney Gale in branch 'main': bpo-27827: identify a greater range of reserved filename on Windows. (GH-26698) https://github.com/python/cpython/commit/56c1f6d7edad454f382d3ecb8cdcff24ac898a50

[issue27827] pathlib is_reserved fails for some reserved paths on Windows

Change by miss-islington : -- nosy: +miss-islington nosy_count: 8.0 -> 9.0 pull_requests: +25949 pull_request: https://github.com/python/cpython/pull/27421 ___ Python tracker

[issue44040] Update broken link in pathlib source

Change by Pablo Galindo Salgado : -- pull_requests: -25777 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44040] Update broken link in pathlib source

Change by Pablo Galindo Salgado : -- nosy: +pablogsal nosy_count: 4.0 -> 5.0 pull_requests: +25777 pull_request: https://github.com/python/cpython/pull/27228 ___ Python tracker

[issue42464] Pathlib resolve() resolves non-existent ".." components with strict=False

Andrei Kulakov added the comment: Another solution would be to base it on `strict` parameter: - strict=True, subpath exists => resolve `..` - strict=True, subpath doesn't exist => throw OSError - strict=False => never resolve `..` This would avoid extra `lstat()` calls but would be a much

[issue42464] Pathlib resolve() resolves non-existent ".." components with strict=False

Andrei Kulakov added the comment: Adding a patch that fixes this issue, for future reference. I'm not too sure this would be the right way to solve this. The patch also causes 5 failures in test_posixpath.py that would have to be fixed (most likely all can be fixed by creating respective

[issue42234] pathlib relative_to behaviour change

Change by Serhiy Storchaka : -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> pathlib's relative_to should behave like os.path.relpath ___ Python tracker

[issue44136] Remove pathlib flavours

Barney Gale added the comment: Depends: bpo-39899, bpo-43757, bpo-44316, bpo-44403, bpo-44412 -- ___ Python tracker ___ ___

[issue44136] Remove pathlib flavours

Change by Barney Gale : -- pull_requests: +25297 pull_request: https://github.com/python/cpython/pull/26708 ___ Python tracker ___

[issue27827] pathlib is_reserved fails for some reserved paths on Windows

Barney Gale added the comment: I've put Eryk's patch up as a PR: https://github.com/python/cpython/pull/26698 -- ___ Python tracker ___

[issue27827] pathlib is_reserved fails for some reserved paths on Windows

Change by Barney Gale : -- nosy: +barneygale nosy_count: 6.0 -> 7.0 pull_requests: +25283 stage: -> patch review pull_request: https://github.com/python/cpython/pull/26698 ___ Python tracker

[issue29249] Pathlib glob ** bug

Change by Christian Heimes : -- nosy: -christian.heimes ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

  1   2   3   4   5   6   7   8   9   10   >