Janek's Computers

Memories

Debugging

• thinkpad
• venv via .\venv\Scripts\Activate.ps1
• pip -V → Fatal error inlc. roelkint path
• https://realpython.com/python-virtual-environments-a-primer/#the-virtualenv-project
• venv via .\venv\Scripts\activate
• without venv

• WSL? → seems not necesary for now/anymore

• farthest so far: install pysoem’s non-python windows-specific dependency, then install all deps via pip or even python -m individually
• → getting stuck on a werkzeug error, prob caused by version mismatch
Install these specific versions?

• mac
• wanted to have a more comfortable environment to debug venv stuff and python versions, but it didn’t help super much
• then https://github.com/bnjmnp/pysoem/issues/59 means it’s blocked

• editing start.bat to provide venv python path and correct other thing path

• import _socket
• found a minimal test i.e. import psutil
• known issue, should be solvable with googling
• google for venv specifically?
• https://github.com/pypa/virtualenv/issues/1069
• brute forced solution: copypaste the _socket.pyd file
• leads to a _select error → copypaste all DLLs from (…)/Python311/DLLs
• theoretically there should be a good solution by setting PYTHONPATH better, but there are also posts saying it should be removed

• next import problem is with psutil._psutil.windows - but it seems like we can just remove this dependency from the

• next import problem is pysoem again
• was it ever working? I thought it did after installing that windows-specific dependency
• seems to be installed without venv, but doesn’t seem to be working with or without venv
• python -m pip install is now broken for some reason

Call with Gabor

• the program that’s running the thing is in Python

• gabor would keep getting different errors on mac

• eventually hit a problem with a package that would only works on Windows

• maybe we should clone the drive just in case