-
Notifications
You must be signed in to change notification settings - Fork 9
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
Add Github Action for pushing sdist, wheel on new release to PyPI #350
Comments
@dotsdl we can't because we depend on some OpenFF things that aren't on pypi and as far as I'm aware aren't going to go on there. |
Ah, fair enough, though I think it can still make sense even if we can't get installation of |
I'm not super keen on partial installs over pypi, but I want to hear/discuss more. |
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 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: