Skip to content

Modernize package metadata in pyproject.toml #11

@minrk

Description

@minrk

Problem Statement

As a JupyterHub package installer, I want to trust that the JupyterHub packages I install can be installed by all standard Python tooling, which requires implementing modern standards. Support for some of the old 'setup.py' ways are slowing being removed.

Proposed Solution

Make sure that all JupyterHub packages implement the current standards of package installation and are fully up-to-date.

Proposed Implementation

Audit packages for PEP517/518 ([build-system]) information and PEP621 project metadata, adding where needed. This includes updating from the License Trove classifier to using SPDX strings in the License field.

Specifically, this does not propose changing any build systems or tooling, only encoding the standardized fields that are becoming required. Installing with setup.py still works fine with the setuptools build backend.

How will this fit in the ecosystem?

Supporting current standards ensures our projects are installable with all the various tools in the Python ecosystem.

Endorsements

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Proposed

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions