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
As per https://pip.pypa.io/en/stable/reference/build-system/pyproject-toml/?#fallback-behaviour setup.py is already just fallback behavior and it looks like support for pyproject.toml in pip is pretty mature right now. We've already encountered issues with #2404 and I think in the future there is a high chance of further issues as pyproject.toml becomes the standard and support for setuptools slowly becomes obsolete.
As such we should
update our pyproject.toml to contain all the relevant information from our setup.py, with most likely poetry as the build system
add config that's outside setup.py to the pyproject.toml (e.g. pytest.ini config) where possible
have a transitional phase where we still have setup.py, by automatically converting from poetry to setup.py using something like Dephell in a Github action.
Benefits of switching to Poetry for me are faster dependency resolution and more control over pinning packages (similar to how pipenv does it without having all the baggage pipenv has).
The text was updated successfully, but these errors were encountered:
As per https://pip.pypa.io/en/stable/reference/build-system/pyproject-toml/?#fallback-behaviour setup.py is already just fallback behavior and it looks like support for
pyproject.toml
in pip is pretty mature right now. We've already encountered issues with #2404 and I think in the future there is a high chance of further issues aspyproject.toml
becomes the standard and support forsetuptools
slowly becomes obsolete.As such we should
pyproject.toml
to contain all the relevant information from our setup.py, with most likely poetry as the build systemAnd alternative would be to add all settings to pyproject.toml but still use setuptools as the build system (see https://setuptools.pypa.io/en/latest/build_meta.html#how-to-use-it ). This is the a bit more conservative approach.
Benefits of switching to Poetry for me are faster dependency resolution and more control over pinning packages (similar to how pipenv does it without having all the baggage pipenv has).
The text was updated successfully, but these errors were encountered: