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

Upgrade packaging setup #275

Open
whyscream opened this issue Nov 8, 2022 · 0 comments
Open

Upgrade packaging setup #275

whyscream opened this issue Nov 8, 2022 · 0 comments

Comments

@whyscream
Copy link
Contributor

whyscream commented Nov 8, 2022

The current setup for packaging is a bit dated, we use setup.py and don't use nide features like extras etc. What we could achieve:

  • Use pyproject.toml for configuring the whole package
  • Use extras to install optional packages: pip install mollie-api-python[examples] would install flask, mollie-api-python[test] would install pytest etc. This is better than using separate requirement.txt files, or write things in documentation.
  • We could setup minimum and maximum versions for dependencies, ensuring that we automatically upgrade a dependency for which a vulnerability was found to a newer version (or trigger a conflict for the vulnerable version).
  • Minimum/maximum version specifiers for dependencies can also be used by @dependabot to inform us automatically about vulnerabilities we're not aware of.
  • Specify supported python versions for the package, helping our users to use the correct package for their environment.

Reference docs: https://packaging.python.org/en/latest/tutorials/packaging-projects/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant