Different package versions show up in different contexts that appear to be using the same environment

[troyraen]

I'm confused about the package versions I'm seeing in different contexts (notebook vs bash prompt vs ipython prompt) when I appear to be using the same environment ("notebook"). I expect to see the same version no matter what context I'm in, but that's not what happens. Can someone help me understand what's going on here?

In a notebook, using the "notebook" kernel, the astroquery version is 0.4.8.dev9474:

In a terminal:

• in a bash prompt, with the "notebook" environment activated, the astroquery version is 0.4.7 (line 2 in screenshot below)
• if I immediately switch to an ipython prompt the version changes to 0.4.8.dev9474

[zoghbi-a]

Thanks for the report.
We are aware of a known issue (and others) in the consistency between conda and pip versions. However, I am not sure it is relevant here. Although pip reports version 0.4.7, if you run python -c 'import astroquery; print(astroquery.__version__)', it uses the correct version 0.4.8.dev9474.

We want to find why pip is reporting the wrong version, but for this case, running python whichever way seems to be using the correct version. Are you seeing something different?

[troyraen]

Thanks @zoghbi-a, yes I think that's right. I was getting confused about which version I was actually running because I was checking that from a bash prompt while the notebook was running and was getting unexpected errors/warnings in the notebook. I'll remember next time that I need to get into a python prompt to check.

Not sure if you want to leave this open for tracking but this answers my question, so ok with me to close.