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
We currently don't push gufe to PyPI consistently, but should do this for the purposes of having the sources listed and installable from there. gufe is foundational to the OpenFE ecosystem, and many ecosystem packages in the future may only have it as their OpenFE dependency.
The text was updated successfully, but these errors were encountered:
Ah, fair enough, though I think it can still make sense even if we can't get installation of gufe via pip to pull in all its dependencies automatically. Thoughts @ianmkenney?
What problem would this solve? If enough deps are on pypi for some sort of base install I could be convinced but I also don't like putting stuff on pypi that will give someone an import error as soon as they try and use it. If there is an operational reason to use pip, you can always do pip install git+https://https://github.com/OpenFreeEnergy/gufe.git@main (or some other tag/version) to install what would be on pypi.
We can also upload a package on pypi that just prints out a "you want to install this from conda-forge" if the issue is with the version being way out of date.
We currently don't push
gufe
to PyPI consistently, but should do this for the purposes of having the sources listed and installable from there.gufe
is foundational to the OpenFE ecosystem, and many ecosystem packages in the future may only have it as their OpenFE dependency.The text was updated successfully, but these errors were encountered: