I have a situation in which "which -a python" is not showing execution order when run on CentOS 6 with Python 3.7

Question

Does anyone know where to begin with debugging this?

[chuck@vmlnx-tacx32 openssl-1.1.0h]$ which -a python
/usr/local/bin/python
/usr/bin/python
[chuck@vmlnx-tacx32 openssl-1.1.0h]$ /usr/local/bin/python
Python 3.7.6 (default, Feb 23 2022, 13:10:48)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-23)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> exit()
[chuck@vmlnx-tacx32 openssl-1.1.0h]$ python
Python 2.6.6 (r266:84292, Jul 23 2015, 14:41:34)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-11)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> exit()

Did you add /usr/local/bin/python very recently? has your shell perhaps hashed /usr/bin/python? See also Why not use "which"? What to use then? — steeldriver, Feb 23 '22 at 21:47
@steeldriver yeah, hash table shows that /usr/bin/python is hashed, but i don't know what to do with that information. i'll check out the link — seanmus, Feb 23 '22 at 22:05
I don't think you mentioned which shell you are using, however see How do I clear Bash's cache of paths to executables? — steeldriver, Feb 23 '22 at 22:09
That cleared up my problem. Thank you so much, I really appreciate it. If you break the comment off into an answer, I'll accept it. — seanmus, Feb 23 '22 at 22:17

I have a situation in which "which -a python" is not showing execution order when run on CentOS 6 with Python 3.7

0 Answers0