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

Transition from using setup.py to pyroject.toml to specify project metadata #1801

Closed
gsheni opened this issue Feb 20, 2024 · 0 comments · Fixed by #1827
Closed

Transition from using setup.py to pyroject.toml to specify project metadata #1801

gsheni opened this issue Feb 20, 2024 · 0 comments · Fixed by #1827
Assignees
Labels
internal The issue doesn't change the API or functionality maintenance Tasks related to infrastructure & dependencies
Milestone

Comments

@gsheni
Copy link
Contributor

gsheni commented Feb 20, 2024

Problem Description

  • We currently use setup.py and setup.cfg to specify the project metadata. This includes requirements which are scatter in apt.txt, requirements.txt, and tox.ini.
  • The Python community selected pyproject.toml as a standard way of specifying project metadata, removing the need for all these files. All the project metadata should go in this file.
  • Other modern packaging and dependency management projects, like Python Poetry, only support the more declarative way of using a pyproject.toml file.

Expected behavior

  • Use pyproject.toml as the one file for managing project metadata
@gsheni gsheni added internal The issue doesn't change the API or functionality maintenance Tasks related to infrastructure & dependencies labels Feb 20, 2024
@gsheni gsheni assigned gsheni and unassigned gsheni Feb 20, 2024
@frances-h frances-h added this to the 1.11.0 milestone Mar 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
internal The issue doesn't change the API or functionality maintenance Tasks related to infrastructure & dependencies
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants