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

Migrate to Rye for dependency management #307

Open
Sachin-Bhat opened this issue Jul 17, 2024 · 3 comments
Open

Migrate to Rye for dependency management #307

Sachin-Bhat opened this issue Jul 17, 2024 · 3 comments

Comments

@Sachin-Bhat
Copy link
Contributor

Hey @eyurtsev,

I was wondering if you would consider migrating from poetry to rye for dependency management. Rye seems to be much more lightweight and a lot easier to configure. I found some issues while working with the current poetry config. I was not able to get a few packages to install and had to manually increase the python version and play with the package versions to get it to install. I feel that the dependency resolution of poetry seems quite wishy-washy to me.

Rye on the other hand could handle this using rye pin <python-version>. Do let me know if migrating is something that you are interested in. I can send a PR.

@eyurtsev
Copy link
Owner

I don't have much time to investigate at the moment. I'd need to be used to also update the workflows on CI + for publishing to pypi

@Sachin-Bhat
Copy link
Contributor Author

I completely understand. Whenever you have time you can visit the following documentation. https://rye.astral.sh/guide/publish/#publish

The advantage with this is that it has builtin support for linting, formatting, testing and more out of the box. This could potentially replace both poethepoet and poetry.

@Sachin-Bhat
Copy link
Contributor Author

I have some experience with using it. If it interests you I can always send a PR.

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

No branches or pull requests

2 participants