Skip to content

Expose _NamespacePath #119668

Closed
Closed

Description

@FFY00

Feature or enhancement

Proposal:

Currently, _NamespacePath is prefixed as a private type, but since it's exposed, it should be marked as public API. I have a specific case in mind where I want to do an instance check.

I vaguely remember a discussion somewhere with @warsaw where this was mentioned, but I can't find it.

Has this already been discussed elsewhere?

This is a minor feature, which does not need previous discussion elsewhere

Links to previous discussion of this feature:

No response

Linked PRs

Activity

  1. added a commit that references this issue on May 28, 2024
  2. warsaw commented on May 28, 2024

    @warsaw
    Member

    I'll have to look around to see if I can dig up the previous discussion, but +1!

  3. ericvsmith commented on May 30, 2024

    @ericvsmith
    Member

    I don't think we thought it should be hidden, rather there was just no reason to expose it. What's the need for accessing it? If it's at all compelling, then I'm +1.

  4. FFY00 commented on May 30, 2024

    @FFY00
    MemberAuthor

    For my specific case, I am loading data from a namespace package, or rather, I need to point to the directories containing said data. This could also be solved by importlib.resources in MultiplexedPath, I have opened python/importlib_resources#309 too.

  5. added a commit that references this issue on Nov 1, 2025
  6. added a commit that references this issue on Dec 6, 2025
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

    stdlibStandard Library Python modules in the Lib/ directorytopic-importlibtype-featureA feature request or enhancement

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions