-
Notifications
You must be signed in to change notification settings - Fork 46
"setuptools_scm" could not be found #322
Comments
This bug also occurs when trying to install for example It's however not reproducible with pip 8.1.1 So this looks like it's probably not PyPI's problem but instead another fallout from pip 8.1.2's package name normalization.
|
I have run into the same issue when installing both My environment:
Steps to reproduce:
Solved by using the following sequence:
|
Looks like you have some sort of proxy between you and PyPI that's preventing download. |
I'm running into a similar problem with Python 3.6 on OS X:
|
This works with Python 3.5, but not with 3.6, both from the python.org installers. |
Does anything change if you install certifi? Sent from my iPhone
|
Yes, that works… |
Looks like it's not enough to install it system-wide; needs to be in the venv, FWIW. |
Did 3.5 link against system OpenSSL and 3.6 link against a bundled copy? Sent from my iPhone
|
Correct |
So 3.5 is getting certificates from the OS and 3.6 is not. Pip itself works because we bundle our own certificates but setup_requires is handled by setuptools and it relies on the OS unless you install certifi. Sent from my iPhone
|
thanks a lot ,it work if I upgrade the pip to 8.1.2 |
This problem looks related to packages that uses setup_requires parameter in setup.py. I think this issue is related with this one: pytest-dev/pytest-xdist#136 (comment) |
This change fixes the build failure "[SSL: CERTIFICATE_VERIFY_FAILED]" when pip tries to download setuptools_scm to satisfy a dependency of pytest-xdist-1.20.0, which happened consitently on various Cray internal SLES build slaves since Aug 09 (except on chap05, where the error never happened) Suggested by: pypi/legacy#322, search for: "I did pip install setuptools_scm and it solved the problem"
This is not a problem with PyPI. |
The self-update mechanism checks the West and manifest repositories in west/ for upstream changes and rebases them to the latest version if any are found. 'west fetch' and 'west pull' run a self-update before fetching any project data. It probably makes sense to always work with the latest version of West and the manifest there. The self-update can be suppressed with --no-update. There's also a 'west update' command for manually updating West and/or the manifest. West automatically restarts itself after a self-update, before running any commands or parsing the manifest. This makes it safe to add a new feature to West and immediately start using it in the manifest. The restarting is done with a plain exec(3). Getting this to work required a few changes: - West now uses absolute instead of relative imports, to make it possible to execute src/west/main.py directly. This also makes it a bit simpler to work on West. Relative imports seem to be discouraged when googling around a bit. __init__.py was removed from src/west. West is more of an application than a package now (though it uses some packages internally). - The internal 'cmd' package was renamed to 'commands', to avoid clashing with a module in the Python standard library. 'runner' was renamed to 'runners' as well, for consistency. Using exec(3) also allowed the argv handling to be simplified a bit. The tests now have to be run from the West repository root with 'PYTHONPATH=src/west pytest'. Maybe this could be improved. The West module and packages have to get into sys.path somehow at least. __init__.py was removed from the test directories as well. Don't think having the tests in a package helps now. A build fix and four unrelated changes are included as well: - setuptools-scm was added to test_requirements.txt to work around an issue on Python 3.4 (not sure why it didn't appear before): distutils.errors.DistutilsError: Could not find suitable distribution for Requirement.parse('setuptools-scm>=1.15.0') See pypi/legacy#322 and pytest-dev/pytest-xdist#136. I suspect the issue is related to setup_requires= using easy_install. - args.zephyr_base is no longer set to ZEPHYR_BASE, just the other way around. args.zephyr_base is currently unused except for setting ZEPHYR_BASE. I think it might be cleaner to add a new variable instead of directly modifying 'args' if the ZEPHYR_BASE value is needed elsewhere later. - WEST_TOPDIR was renamed to WEST_MARKER. The old name made me think that it was the path to the directory containing west/. - Project-related command-line arguments that are only used by a single command are now defined together with the command that uses them. - A bug was fixed in the bootstrapper's find_west_topdir(). The 'start' argument was being ignored. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
Add setuptools-scm to test_requirements.txt to work around an issue on Python 3.4: distutils.errors.DistutilsError: Could not find suitable distribution for Requirement.parse('setuptools-scm>=1.15.0') Not sure why it didn't appear before. Maybe something in CI changed. See pypi/legacy#322 and pytest-dev/pytest-xdist#136. I suspect the issue is related to setup_requires= using easy_install. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
Add setuptools-scm to test_requirements.txt to work around an issue on Python 3.4: distutils.errors.DistutilsError: Could not find suitable distribution for Requirement.parse('setuptools-scm>=1.15.0') Not sure why it didn't appear before. Maybe something in CI changed. See pypi/legacy#322 and pytest-dev/pytest-xdist#136. I suspect the issue is related to setup_requires= using easy_install. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
Originally reported by: ali raza (Bitbucket: alirz, GitHub: alirz)
The text was updated successfully, but these errors were encountered: