-
Notifications
You must be signed in to change notification settings - Fork 226
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[install] Development installation fails #287
Comments
That's strange... I tried reproducing it here, and was able to install it without problems. I checked out
All good. |
Have you tried with Python >= 3.8? I have 3.9 installed. |
Tried WSL at work. It had Python 3.8 installed and WireViz installation worked smoothly with the steps you describe, except for using |
Now, I've tried in Windows 10 with Python 3.9.13, and this similar installation procedure seems to work there: ver
echo %COMSPEC%
dot -V
git clone https://github.com/formatc1702/WireViz.git clean-WireViz
cd clean-WireViz/
git checkout refactor/big-refactor
python3 -m venv venv
venv\Scripts\activate.bat
python -V
pip3 install -e . I still don't understand why the installation fails in my WSL1 environment. For many years I've done most of my Python coding (including WireViz contributions) in this WSL1 environment. One difference I can see, is that the global Python environment in WSL1 has more than 200 packages installed. A lot of these packages are due to my ROS installation that I need for another project, and I therefore cannot just uninstall them for testing the WireViz installation. However, I still have a virtual environment in my original WSL1 WireViz workspace that works together with the current Running |
Yes, I highly recommend using Also, I am planning to drop Python 3.7 since that version will stop receiving security fixes next year and the new version of |
I try to install the development version to try out PR #251, but the installation seems to fail.
Commands I try from Ubuntu bash in WSL1/Windows 10:
Output:
The text was updated successfully, but these errors were encountered: