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.

Sign up for GitHub

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

Jump to bottom

manage deps with poetry instead of requirements file #217

Open

kernelsam opened this issue Jan 29, 2025 · 0 comments

Assignees

Contributor

kernelsam commented Jan 29, 2025 •

edited

Loading

If we are to re-evaluate tooling I highly recommend we look at ruff and uv. There are some concerns in the Python community about a company owning these tools but they are MIT licensed currently so if the company pulls any nasty tricks they can be forked.

Both written in rust, they're also working on a new type checker right now.
There are people in the python community upset though because they took all the work of the existing open source python tools and haven't acknowledged the original creators and maintainers.

https://peps.python.org/pep-0631/#optional-dependencies
https://python-poetry.org/docs/managing-dependencies/
https://python-poetry.org/docs/pyproject/#dependencies
https://setuptools.pypa.io/en/latest/userguide/dependency_management.html
https://packaging.python.org/en/latest/guides/writing-pyproject-toml/

https://github.com/DerwenAI/kleptosyn

kernelsam self-assigned this

github-actions bot added the triage label

jamietypovsky removed the triage label

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