Skip to content

Fix error message for ntpath.commonpath #117381

Description

@nineteendo

Bug report

Bug description:

>>> import ntpath
>>> ntpath.commonpath(["/foo", "foo"])
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "<frozen ntpath>", line 808, in commonpath
ValueError: Can't mix absolute and relative paths

/foo is not an absolute path, but a rooted path, which can't be mixed with not-rooted paths.

CPython versions tested on:

CPython main branch

Operating systems tested on:

Windows

Linked PRs

Activity

  1. aisk commented on Mar 30, 2024

    @aisk
    Member

    I did some googling and found that Microsoft has a document which describes "relative rooted path": https://learn.microsoft.com/en-us/dotnet/api/system.io.path.ispathrooted?view=net-8.0#remarks

    A relative rooted path specifies a drive, but its fully qualified path is resolved against the current directory.

    So I think the relative rooted path should be something like C:foo (please notice that it's not C:/foo), but /foo still is an absolute path. And ntpath.isabs('/foo') returns True, so I think it's an absolute path.

  2. nineteendo commented on Mar 30, 2024

    @nineteendo
    ContributorAuthor

    ntpath.isabs('/foo') returns True

    That was recently changed:

    The error message could also be "Can't mix rooted and not-rooted paths" as /foo is rooted and foo is not.

  3. zooba commented on Apr 2, 2024

    @zooba
    Member

    How does this change make life better or easier for those encountering this message?

    At first glance, it appears to be getting into overly precise terminology that doesn't help educate or correct the caller.

  4. nineteendo commented on Apr 2, 2024

    @nineteendo
    ContributorAuthor

    The error message states: "Can't mix absolute and relative paths".
    But /foo & foo are both relative according to ntpath.isabs():

    Path Rooted? Absolute?
    c:/foo Yes Yes
    c:foo Yes No
    /foo Yes No
    foo No No

    So, this error message is factually incorrect.
    But /foo is rooted and foo is not, so that's what the new error message is in that case.
    On a side note, it could be useful to add os.path.isrooted.

  5. added a commit that references this issue on Apr 3, 2024
  6. added a commit that references this issue on Apr 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    OS-windowstype-bugAn unexpected behavior, bug, or error

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions