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

Try poetry #10

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Try poetry #10

wants to merge 4 commits into from

Conversation

dazza-codes
Copy link

This is a by-product of attempting to create a dev-env for this project, using poetry. It's thrown up as a PR in case it is useful to others too.

@coveralls
Copy link

coveralls commented Jun 3, 2019

Coverage Status

Coverage remained the same at 97.674% when pulling 6166c9b on darrenleeweber:try-poetry into ab0e964 on omarkohl:master.

@dazza-codes dazza-codes force-pushed the try-poetry branch 2 times, most recently from 3cdce5d to b8a7426 Compare June 3, 2019 21:47
- update pyproject.toml
- update travis-CI
@omarkohl
Copy link
Owner

Sorry for the looooooong delay in reacting to this. Are you still interested in this pull request? If yes, could you explain the benefit this has over the current approach?

@ssbarnea
Copy link

ssbarnea commented Dec 2, 2022

Avoid poetry, or flit, use setuptools-scm...

@omarkohl
Copy link
Owner

I am no longer doing much development with Python so I am not up to date with the latest best practices. I need some justification why poetry (or setuptools-scm) is the way to go, ideally some list of advantages and disadvantages with sources.

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

Successfully merging this pull request may close these issues.

4 participants