asdf global python 3.8.0 2.7.16which python-> ~/.asdf/shims/pythonwhich python2 -> ~/.asdf/shims/python2which python3-> ~/.asdf/shims/python3asdf current -> python 3.8.0 2.7.16 (set by ~/.tool-versions)asdf where pythonasdf where python2asdf where python3asdf where python -> ~/.asdf/shims/pythonasdf where python2 -> ~/.asdf/shims/python2asdf where python3 -> ~/.asdf/shims/python3asdf where python -> Version not installedasdf where python2 -> No such plugin: python2asdf where python3 -> No such plugin: python3Note: This seems similar to issue #349 which is marked (correctly) as fixed
OS: PopOS 19.10 / Linux 5.3.0-7642-generic #34~1584408018~19.10~21df4b1-Ubuntu
asdf version: v0.7.8-4a3e3d6
asdf where only works with plugin names. The name of your plugin is python. Just as in the asdf global python 3.8.0 2.7.16 command you ran.
If you want a command that returns the path to the executable use asdf which python3. If you want the path to the shim just use which python3.
asdf where python => Version not installed is the only bug I see here. But it is definitely a bug.
Yeah I thought that may be the case due to the plugin name being simply 'python'. Thanks for the explanation and review.
I came here to file an issue but see this behavior has already been recorded as a bug:
===================
# ~/.tool-versions
python 3.7.9
===================
➤ asdf where python
/Users/foo/.asdf/installs/python/3.7.9
===================
# ~/.tool-versions
python 3.7.9 3.8.5
===================
➤ asdf where python
Version not installed
Any chance this could be added to the v0.8.0 milestone? 😅
Hopefully, #790 should fix this.
Most helpful comment
Hopefully, #790 should fix this.