-
Notifications
You must be signed in to change notification settings - Fork 12
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
[BUG] Version inconsistency on installation from GitHub #30
Comments
|
Thank you for your feedback. Why some works and some don't ? |
Some repositories inject the version only with a GitHub actions stage on release. Others keep it in the codebase itself. |
Ok, personally I wouldn't trust the automatic number scheme of a GitHub Actions, but hey, why not. Will see with "Pypi" released version considered "stable", hope these are not too old. |
The version numbers aren't automatically chosen, I pick them when I click the "Publish release" button 😄. |
Ok for Maybe a consistent way of installation might be set across all modules, maybe allowing "dev" installation though. |
Hi, doing that :
Getting (with decoration for readability) :
Full installation log (quite long)
Why the following "errors" :
Ok so far...
Why
0.0.0
forzigpy-cli
? Why not at least0.0.0.dev0
?Why replacing
zigpy-0.54.0.dev0
withzigpy-0.54.0
?Why
0.0.0
forzigpy-znp
? Why not at least0.0.0.dev0
?Why uninstalling
zigpy-znp-0.10.0
then immediately installingzigpy-znp-0.0.0
instead ?Why this :
zigpy-cli 0.0.0 requires zigpy-znp>=0.8.0, but you have zigpy-znp 0.0.0 which is incompatible.
Let's continue...
Why this again :
zigpy-cli 0.0.0 requires zigpy-znp>=0.8.0, but you have zigpy-znp 0.0.0 which is incompatible.
Doing a
pip freeze
gives :Any reason for the
0.0.0
version forzigpy-cli
andzigpy-znp
?Where if the
0.54.0.dev0
forzigpy
?Where if the
0.35.0.dev0
forbellows
?Pretty strange...
Regards.
The text was updated successfully, but these errors were encountered: