-
Notifications
You must be signed in to change notification settings - Fork 137
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
[Bug] Installing scons via 'pip install scons' doesn't work #146
Comments
Thanks for this contribution @Obijuan! I have tested this steps. It works inside the virtualenv but then it is not fixed outside. The bug is related to the detection of the Since the virtualenv has only one version of Python, scons can detect and load the correct paths. Otherwise, if you have different versions of Python installed in your system, it can not detect the correct version for Python 3.5. A solution is to setup the Another solution is to execute the |
Since this issue is duplicated I can close it and continue there 😄 |
@Jesus89 found this alternative solution: platformio/platformio-core#279 It seems that installing scons with the following command does the trick
|
Traceback (most recent call last): i am trying to install RAT when i type command "scons" it gives this error |
This is not an Apio bug but is reported here because is affecting the apio installation
This issue is comments in the scons user list: installing scons via pip install scons doesn't work
When trying to install apio with "sudo pip install apio" there is an strange message gotten: "error: option --single-version-externally-managed not recognized"
The problem is due to the scons package. It can be reproduced just by installling scons itself with:
In windows it seems to be fixed just by updating the setuptools and wheel
(but more tests should be done)
The solution in linux is to install scons in a virtual environment. Then, if you install apio (inside or outside the virtualenv) it will work
Now you can install apio inside the virtualenv, or outside
The text was updated successfully, but these errors were encountered: