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
The first question if is something like this possible in rye? I didn't find [tool.rye.version] or something similar in documentation or questions.
With the above setup, If I run rye version it correctly gives:
> rye version
0.0.6
If I run
> rye version --bump patch
if adds version: 0.0.7 to pyproject.toml and certainly doesn't change __about__.py
So here is another question. How to correctly handle the version so it is written in one place, both the package code and rye is aware of the version and rye is in control of the package version (or something is in control)?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The package I am developing should know its version (like for print outs, etc).
Currently I am using
__about__.py
as the main version source and use inpyproject.toml
:about.py :
The first question if is something like this possible in rye? I didn't find
[tool.rye.version]
or something similar in documentation or questions.With the above setup, If I run
rye version
it correctly gives:> rye version 0.0.6
If I run
if adds
version: 0.0.7
to pyproject.toml and certainly doesn't change__about__.py
So here is another question. How to correctly handle the version so it is written in one place, both the package code and rye is aware of the version and rye is in control of the package version (or something is in control)?
Beta Was this translation helpful? Give feedback.
All reactions