-
Notifications
You must be signed in to change notification settings - Fork 0
Create python package and publish to PyPI #62
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
Comments
As an operator, when I want to install metgenc, I can use pip to install it from PyPI. As a developer, when I want to make a release of metgenc, I can run a command that will trigger a build of the package, and, if successful, publish the new version to PyPI. As an operator or developer or project manager, when I want to see what was in a new release, I can view the project's CHANGELOG in GitHub. |
I'm not sure how best to test this since I already have metgenc installed and I don't know enough to feel confident I can avoid clobbering/wrecking something and getting myself into a pickle. If you have suggestions for how to be brave and go for it, I'll listen and follow. I took a look at the PyPi site and easily found nsidc-metgenc by searching for "metgenc". There's currently a discrepancy between the GitHub README contents and those on the PyPi nsidc-metgenc page. Is it safe to assume synchronizing those are just on pause during the flurry of development work, and they'll ultimately be unified to match? |
Since your previous install was via Poetry, this should work:
I'm going to update the README to reflect the |
Thanks Kevin! I was able to get it installed via...long story short: a new virtual environment. Anyhoo, I did indeed install it from pip ✅, and it's functional (I tested validate and process -d)
I've verified that the change log / PyPi versions jive ✅ |
Yeah, the fix for the extra spaces is not yet in a released version, that is, a version that is installable via PyPI. |
Oh, same with the README change. It is not in a release. |
All duly noted. I'll consider this testing complete, because for the point of the issue, it is!! |
👍 |
No description provided.
The text was updated successfully, but these errors were encountered: