Skip to content

Inconsistent Python package structure when linking to license file #1899

Description

@jdeanwallace

As discovered here, it seems like Python package's can have different structures depending on how they were packaged/built.

For example, on my macOS development machine, installing MarkupSafe==3.0.2, results in the the license file to be located at:

venv/lib/python3.9/site-packages/MarkupSafe-3.0.2.dist-info/LICENSE.txt

However, on a Raspberry Pi device, installing MarkupSafe==3.0.2, results in the the license file to be located at:

venv/lib/python3.9/site-packages/markupsafe-3.0.2.dist-info/licenses/LICENSE.txt

I suspect these differences stem from how the package is built for multiple different architectures.

As a temporary workaround, we can try link to the package's online license file.

Activity

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

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions