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
This means I cannot use pip/poetry to update minor changes (by SemVer definition) automatically.
I know asking for Unit (or some form of) testing before merging to master is too much, but versioning or packaging should be free and relatively easier as a stop gap I hope.
The text was updated successfully, but these errors were encountered:
My apologies! I made those changes, but only committed and pushed half of them. Should be better now. I'll tag a version once I get a few more things ironed out. That is a very good suggestion.
From: Otieno Anyango ***@***.***>
Sent: Monday, August 21, 2023 10:01 AM
To: BGSU-RNA/fr3d-python ***@***.***>
Cc: Subscribed ***@***.***>
Subject: [EXTERNAL] [BGSU-RNA/fr3d-python] Versioning and Publishing to PyPI (Issue #31)
Thank you for the beautiful work done in maintaining this very useful tool.
I was wondering if you could implement versioning via tags. This is in lieu of packaging and publishing on PyPI as a pip installable package.
Some of the changes done yesterday, Sunday 20th Aug, broke the pip install. I am forced to fix the version to a git commit sha on poetry like
fr3d = { git = "https://github.com/BGSU-RNA/fr3d-python.git", rev = "9702751c42bac3c7f655ce070f94a8ceb1ab0747" }
This means I cannot use pip/poetry to update minor changes (by SemVer definition) automatically.
I know asking for Unit (or some form of) testing before merging to master is too much, but versioning or packaging should be free and relatively easier as a stop gap I hope.
-
Reply to this email directly, view it on GitHub<#31>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAHQ7EZB7R5DEL2I4VD2GE3XWNSY7ANCNFSM6AAAAAA3YOAYEI>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.******@***.***>>
Thank you for the beautiful work done in maintaining this very useful tool.
I was wondering if you could implement versioning via tags. This is in lieu of packaging and publishing on PyPI as a pip installable package.
Some of the changes done yesterday, Sunday 20th Aug, broke the pip install. I am forced to fix the version to a git commit sha on poetry like
This means I cannot use pip/poetry to update minor changes (by SemVer definition) automatically.
I know asking for Unit (or some form of) testing before merging to master is too much, but versioning or packaging should be free and relatively easier as a stop gap I hope.
The text was updated successfully, but these errors were encountered: