-
Notifications
You must be signed in to change notification settings - Fork 64
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
[FEATURE] Migrate to pyproject.toml
#308
Comments
@dhrubo-os , I am willing to raise a PR for this. |
@rawwar Thank you for creating the issue. I would like you to expand this issue description a bit more, such as explaining why we should adopt pyproject.toml and what advantages we will gain over the current process, etc. |
@dhrubo-os , Would you consider this as a major change? I am wondering if we should be doing this migration as part of next major release? |
Hey @rawwar @dhrubo-os, would love to contribute to this migration to |
@bilal-aamer , that would be great. Please feel free to raise a PR. I would be happy to help and review. @dhrubo-os , do you think there are any pre-requisites before @bilal-aamer works on it? |
I don't think so. @bilal-aamer thanks for looking into this. Assigned this to you. |
@bilal-aamer , how is it going? If you need any help, please raise a draft PR with whatever you have done so far and I can try to help. |
Hey @rawwar, will do right away been looking into Will get a generic PR out right away. |
Current
opensearch-py-ml
project uses setup.py and setup.cfg to maintain project metadata.pyproject.toml
is the new standard. PEP 621, which was accepted in 2021, designatedpyproject.toml
as the standard way to specify project metadata for Python packages.setuptools
and other packaging tools now supportpyproject.toml
, and it is expected to become the de facto standard for Python packaging in the future.pyproject.toml
also supports few features that are not available insetup.cfg
, such as dynamic metadata and optional dependencies.Edit-1: Added more information on why to migrate.
The text was updated successfully, but these errors were encountered: