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

Switch from poetry to plain setuptools and build #21

Open
timofurrer opened this issue Mar 24, 2024 · 3 comments
Open

Switch from poetry to plain setuptools and build #21

timofurrer opened this issue Mar 24, 2024 · 3 comments

Comments

@timofurrer
Copy link
Member

I don't feel there is a need for poetry for this project, especially because it's a library supporting many Python versions.

Lets switch modern setuptools / build setup.

@sisp
Copy link
Contributor

sisp commented Mar 24, 2024

IMO, Poetry's advantages also for library projects are a unified CLI, dev dependencies, and a lock file (which is a matter of taste for libraries, but it helps in making a dev environment reproducible).

@timofurrer
Copy link
Member Author

I don't have strong feelings about it actually, we could leave as-is. However, last time I used poetry it was a pain to test for multiple Python versions and maintain multiple venvs with it.

@timofurrer
Copy link
Member Author

Oh and yes, we'd still need a lock file :)

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

2 participants