Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Align Pip package metadata with the current specification #155

Open
popescu-v opened this issue Feb 23, 2024 · 0 comments
Open

Align Pip package metadata with the current specification #155

popescu-v opened this issue Feb 23, 2024 · 0 comments
Assignees
Labels
Priority/2-Low To do after P1 Status/ReadyForDev The issue is ready to be developed or to be investigated deeply Type/DevChore Repository maintainance, CI/CD or non user-facing refactorings

Comments

@popescu-v
Copy link
Collaborator

Description

Currently, Pip package metadata is specified in the setup.py file and contains a set of metadata fields, some of which are in line with the current Python package core metadata specification: https://packaging.python.org/en/latest/specifications/core-metadata/ .

The goal of this issue is to make all metadata fields conformant to the Python package core metadata specification.

Questions/Ideas

  • Also, one should investigate whether the pyproject.toml file could completely supersede the setup.py file
    • A particular attention point here is the usage of versioneer as a way of calculating the current package version, based on its state in the Git repository.
  • Solving this issue would allow e.g. pip show khiops to show correct and complete information regarding the khiops pure Python package.
@popescu-v popescu-v added Status/ReadyForDev The issue is ready to be developed or to be investigated deeply Type/Feature A new feature request or an improvement of a feature labels Feb 23, 2024
@folmos-at-orange folmos-at-orange added Type/DevChore Repository maintainance, CI/CD or non user-facing refactorings Priority/2-Low To do after P1 and removed Type/Feature A new feature request or an improvement of a feature labels Mar 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority/2-Low To do after P1 Status/ReadyForDev The issue is ready to be developed or to be investigated deeply Type/DevChore Repository maintainance, CI/CD or non user-facing refactorings
Projects
None yet
Development

No branches or pull requests

2 participants