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.
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.