-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Create alias for MAJOR and MAJOR.MINOR python install versions #2424
Comments
This has been requested for a long time this way or another. We have plans to implement this (and use the donated money for its development, for the first time).
So given the pros and cons, I'm currently gravitating to the 2nd implementation. |
I was going to scout what other language managers do before making a final decision -- didn't allocate time for that yet. |
Let me help on that, because my current job made me pass to mostly all env-like tooling. Let me present state of Node, Go, Rust, PHP and Ruby ( i linked the installer page directions )
[root@fedora_docker /]# nvm ls-remote
v0.1.14
v0.1.15
...
v8.16.2 (LTS: Carbon)
v8.17.0 (Latest LTS: Carbon)
...
[root@fedora_docker /]# rvm list known
# MRI Rubies
[ruby-]1.8.6[-p420]
[ruby-]1.8.7[-head] # security released on head
[ruby-]1.9.1[-p431]
...
[ruby-]2.6[.6]
[ruby-]2.7[.2]
[ruby-]3[.0.0]
ruby-head
...
# JRuby
jruby-1.6[.8]
jruby-1.7[.27]
...
[root@fedora_docker ~]# rbenv install -L
1.8.5-p52
1.8.5-p113
1.8.5-p114
1.8.5-p115
1.8.5-p231
1.8.6
...
3.0.4
3.1.0-dev
3.1.0-preview1
3.1.0
3.1.1
3.1.2
3.2.0-dev
3.2.0-preview1
...
[root@fedora_docker ~]# phpenv install -l
Available versions:
5.2.17
5.3.2
5.3.3
...
8.1.7
8.1.8
8.1snapshot
8.2snapshot
...
[root@fedora_docker ~]# gvm listall
gvm gos (available)
go1
go1.0.1
go1.0.2
go1.0.3
go1.1
...
go1.18
go1.18beta1
go1.18beta2
go1.18rc1
go1.18.1
go1.18.2
go1.18.3
go1.18.4
go1.19beta1
go1.19rc1
go1.19rc2
release.r56
release.r57
... |
|
I'm not sure what you can help with... so I'll let you decide. The plan is to make it the same way as There's probably going to be a significant overlap in version comparison logic. We'll probably need to split off the common part into a library (rvm can show how these can be organized) or (probably preferrable) a separate internal subcommand. |
When considering other "version managers", it might also be worth looking at:
There is also Plenv which I think is mostly a clone of Rbenv/Pyenv. |
Implemented auto-resolving micro versions in #2487 |
Apparently |
Too many issues will kill our team's development velocity, drastically.
Make sure you have checked all steps below.
Prerequisite
pyenv
and the defaultpython-build
plugin only. Please refrain from reporting issues of other plugins here.Description
Current install list has no alias for latest each version.
So a proposed alias for latest stable <major> and <major>.<minor> would be an well accepted solution.
Using -dev would not be an option due the lack of stability
How this could work:
3.10.5
as this will be the alias3.6.15
2.5.6
This is an small enhancement that will simplify installation when we don't need to care with **<patchlevel>**version, but only with <major> and <minor>
The text was updated successfully, but these errors were encountered: