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
When installing a python package locally via pip that I actively develop on I prefer doing so via pip install -e/--editable <path-to-local-git-repo>. This allows me to being able to import the package from anywhere without having to reinstall it after every change.
setuptools / setup.py is being deprecated. pip recommends switching to a pyproject.toml.
I don't think this is necessarily urgent, but maybe something to keep in the back of our heads.
Putting together another package and making it ready for distribution I came across this: https://hatch.pypa.io/1.8/
Might be useful for creating the pyproject.toml (see more details here: https://hatch.pypa.io/1.8/intro/#existing-project).
As far as I understand it it should be able to just use a preexisting setup.py and essentially translates that into a pyproject.toml which will be the way pip will be installing software in the future.
Activity
ymahlich commentedon Oct 28, 2024
Putting together another package and making it ready for distribution I came across this: https://hatch.pypa.io/1.8/
Might be useful for creating the pyproject.toml (see more details here: https://hatch.pypa.io/1.8/intro/#existing-project).
As far as I understand it it should be able to just use a preexisting setup.py and essentially translates that into a pyproject.toml which will be the way pip will be installing software in the future.
jjacobson95 commentedon Nov 13, 2024
We will have to update scripts/push_to_pypi.py.py as well. This is where the package is built before pushing it to pypy in the build_all.py script