Skip to content

Provide a 'diagnose' routine to help users inspect broken environments #461

Closed

Description

@jaraco

In python/cpython#100455, a user describes a way to inspect / diagnose the environment when importlib.metadata chokes on a corrupt or invalid environment. This gives me an idea - what if importlib provided a routine to inspect the environment and give the user hints as to what is going wrong. I'm thinking something like:

python -m importlib_metadata.diagnose
Inspecting .
Inspecting /usr/local/lib/python/site-packages
Found 13 packages (pip, backports.pdb, ..., foopkg)
Warning: foopkg has no `.name`.

Activity

  1. jaraco commented on Dec 1, 2023

    @jaraco
    MemberAuthor

    I'd like to improve this more, but since I got something working, I decided to get it out.

  2. added a commit that references this issue on Mar 7, 2024
    b3918e7
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

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions