so, i have learned how to solve my python versioni...
# troubleshooting
f
so, i have learned how to solve my python versioning thanks to you friendly folks here--the main takeaway was i uninstalled things in the wrong order and the right order is crucial to it working. i have a new problem concerning an extractor. when i run
meltano add extractor tap-nhl
the error i get is:
ERROR: Package 'tap-nhl' requires a different Python: 3.8.2 not in '<3.9,>=3.8.12'
python 3.8.2 is greater than 3.8.12, is it not? My suspicion is this is one of those weird situations i've run into before where there's a different error behind the error, because as far as i can tell, i do have the right python installed for this extractor.
a
Hey I remember you from Coalesce! No in semantic versioning, each component can be separated as such MAJOR . MINOR . PATCH major = 3 minor = 8 patch = 2 vs patch = 12
v
3.8.16
is the lastest version of 3.8 that's out today so you should be on that if you're going to run 3.8! re https://www.python.org/downloads/
a
Also I cant recommend pyenv enough for your local machine.
For managing multiple python versions easily (not to be confused with virtual environments despite the env in the name)
m
Seconding pyenv, I adore it
f
@alexander_butler ay yo what’s up stranger!! Thank you for the education, I was going off decimal rules and not the actual rules that govern versioning! Thank you I’m gonna update and try again!
v
Note with pipx if you have issues, the easiest fix is to delete the directory those venvs are stored at (I think ~/.local or something) and then just re install your package ie
python -m pipx install meltano
) or https://gabnotes.org/how-use-pipx-pyenv/ , `
Copy code
PIPX_DEFAULT_PYTHON
`is the key if you want to continue using pipx. The thing that's hard is there's so many options for new folks its hard. Another good solution if you want to avoid
pipx
is to set
Copy code
export PIP_REQUIRE_VIRTUALENV=true
so you have to set up a
venv
everytime. There's tons of options here 🤷 if you use
pyenv
and not
pipx
I'd recommend using a
venv
every time which is why I bring up this env var
c
For managing multiple python versions easily (not to be confused with virtual environments despite the env in the name)
Faith is on Windows, where
pyenv
is not needed, because Python on windows has
py.exe
Note with pipx if you have issues, the easiest fix is to delete the directory those venvs are stored at
Trying to fix
pipx
when working across multiple different Python versions will involve a bit more than that. I jotted down my understanding of dealing with
pipx
and
meltano
across potentially multiple different Python installations here: https://meltano.slack.com/archives/C01TCRBBJD7/p1672810869216909?thread_ts=1672790262.255449&amp;cid=C01TCRBBJD7
a
I used WSL back when I was on windows. I have no idea how windows manages the concept of PATHs or precedence of executables from a terminal (like when you type
python
) EDIT: I am a noob there
a
The docs always come in with 🧠 and gold nuggets like this from that same link you sent. https://github.com/marcelotduarte/cx_Freeze
c
Oh. I didn't realise that
cx_freeze
adds support for MSI and DMG compared to other alternatives ....