You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Any interest in swapping out pipenv for poetry (https://python-poetry.org/)? Poetry is arguably a better project in a number of ways, not the least of which is it's better maintained with regular releases:
Poetry:
Supports using a standard (PEP 518) pyproject.toml file to hold project metadata, including tool configuration (i.e., can replace setup.cfg, tox.ini, etc.).
Understands how to build an sdist and wheel (poetry build) so you don't need to maintain a separate setup.py file.
Understands how to publish a package to pypi (poetry publish).
Does a better job at dependency resolution.
Aside from just working better, using pyproject.toml is a really big win for consolidating tooling and build configuration. For example, tox understands how to read the build-system (PEP 517) config and use it to build the project which lessens the number of hoops you need to jump through when trying to define tox environments to test against a range of dependency versions.
I can open a pull request showing what the conversion looks like but no worries if you'd prefer to stick with pipenv.
The text was updated successfully, but these errors were encountered:
Closes#10
- Adds a .gitignore with some standard python excludes and also excludes
the lockfile since this is a library and we don't need to pin
dependencies for maintainers.
Any interest in swapping out pipenv for poetry (https://python-poetry.org/)? Poetry is arguably a better project in a number of ways, not the least of which is it's better maintained with regular releases:
Poetry:
pyproject.toml
file to hold project metadata, including tool configuration (i.e., can replacesetup.cfg
,tox.ini
, etc.).poetry build
) so you don't need to maintain a separatesetup.py
file.poetry publish
).Aside from just working better, using
pyproject.toml
is a really big win for consolidating tooling and build configuration. For example, tox understands how to read thebuild-system
(PEP 517) config and use it to build the project which lessens the number of hoops you need to jump through when trying to define tox environments to test against a range of dependency versions.I can open a pull request showing what the conversion looks like but no worries if you'd prefer to stick with pipenv.
The text was updated successfully, but these errors were encountered: