I have here a package on pypi that was published by command line, but no-one can download it (except on the laptop I packaged it up on):
pip install webdriver_chauffeur
Collecting webdriver_chauffeur
Could not find a version that satisfies the requirement webdriver_chauffeur (from versions: )
No matching distribution found for webdriver_chauffeur
pip install webdriver-chauffeur
Collecting webdriver-chauffeur
Could not find a version that satisfies the requirement webdriver-chauffeur (from versions: )
No matching distribution found for webdriver-chauffeur
It is here https://pypi.python.org/pypi?%3Aaction=pkg_edit&name=webdriver_chauffeur
Pretty sure I followed this one https://axiacore.com/blog/basic-steps-publish-python-package/
Why is this package not installable?
I maintain a package on pypi and just hit this issue. I resolved it by hitting "update release" on the pypi version page of my package. If this problem persists you might consider letting the package maintainer know about the workaround.
I know it's an old thread, but I ran into a similar issue and this thread popped up on Google.
I faced the same error message. The problem was, that I set a Python version constraint of >=3.9. because that's the version I develop in. However, the environment where I tried to run pip install <...> was using Python 3.7. By relaxing the constraint in setup.py (or pyproject.toml in my case) the issue was resolved.
Dozens of people have the same issue, it seems pypi isn't stable and you should run your own pip server to use your packages
Related
We use a pipeline that first uses pip wheel to collect all the packages that are needed in the project and then it creates a docker image that calls to pip install on the collected wheels.
The issue I am encountering is that when calling pip wheel, pip is collecting 2 different versions of a package. This has started occurring once a new version of the package is available.
The project has a requirement for an internal library ecs-deployer==10.1.2 and that library has in turn a requirement in the form of: elb-listener>=3.2.1+25,<4
The relevant output of pip wheel with the verbose option says:
Collecting elb-listener>=3.2.1+25,<4
Created temporary directory: /tmp/pip-unpack-zr930807
File was already downloaded /home/user/path/dist/elb_listener-3.2.2+26-py3-none-any.whl
Added elb-listener>=3.2.1+25,<4 from https://internal-repository.com/path/elb_listener/3.2.2%2B26/elb_listener-3.2.2%2B26-py3-none-any.whl#md5=foo (from ecs-deployer==10.1.2->service==1.0.0) to build tracker '/tmp/pip-req-tracker-1tz9t5ls'
Removed elb-listener>=3.2.1+25,<4 from https://internal-repository.com/path/elb_listener/3.2.2%2B26/elb_listener-3.2.2%2B26-py3-none-any.whl#md5=blabla (from ecs-deployer==10.1.2->service==1.0.0) to build tracker '/tmp/pip-req-tracker-1tz9t5ls'
And also:
Collecting elb-listener>=3.2.1+25,<4
Created temporary directory: /tmp/pip-unpack-yfnxim_u
File was already downloaded /home/user/path/dist/elb_listener-3.2.3+27-py3-none-any.whl
Added elb-listener>=3.2.1+25,<4 from https://internal-repository.com/path/elb_listener/3.2.3%2B27/elb_listener-3.2.3%2B27-py3-none-any.whl#md5=bar (from ecs-deployer==10.1.2->service==1.0.0) to build tracker '/tmp/pip-req-tracker-1tz9t5ls'
Then when the pip install is called I get this:
ERROR: Cannot install elb-listener 3.2.2+26 (from /opt/elb_listener-3.2.2+26-py3-none-any.whl) and cad-aws-elb-listener-target-group-builder 3.2.3+27 (from /opt/elb_listener-3.2.3+27-py3-none-any.whl) because these package versions have conflicting dependencies.
The conflict is caused by:
The user requested elb-listener 3.2.2+26 (from /opt/elb_listener-3.2.2+26-py3-none-any.whl)
The user requested elb-listener 3.2.3+27 (from /opt/elb_listener-3.2.3+27-py3-none-any.whl)
We use pip 20.2.3 with the option --use-feature=2020-resolver
Is it normal that pip wheel collects several versions of the same package?
If so, can I indicate in any way to either pip wheel to only collect one of the versions or to pip install to only use the latest version?
If not, is there any way to solve this problem? I guess changing the requirement to elb-listener>=3.2.1+27,<4 would solve it, but we don't have direct access to that library and it would take a while for other team to change it.
As per #sinoroc comment, upgrading the python to 3.10 and pip version to 21.2.4 solved this particular issue.
As far as I understood, "local version identifiers" such as 3.2.1+25 are far from usual, apparently they are not meant to be used anywhere public (like PyPI), and that might be the reason for all the trouble here. I am really not sure how well they are supported by Python packaging tools and maybe they confuse the dependency resolution.
Local version identifiers SHOULD NOT be used when publishing upstream projects to a public index server, but MAY be used to identify private builds created directly from the project source. Local version identifiers SHOULD be used by downstream projects when releasing a version that is API compatible with the version of the upstream project identified by the public version identifier, but contains additional changes (such as bug fixes). As the Python Package Index is intended solely for indexing and hosting upstream projects, it MUST NOT allow the use of local version identifiers.
-- "Local version identifiers" section of _PEP 440
I'm trying to install a package called pyeto. Their website (https://pyeto.readthedocs.io/en/latest/) does not mention any problems regarding the installation and I can't find any installation related problems of other users. I'm doubting what solution I should look for (I would appreciate it to not have to reinstall python). I'm running python version 3.6.8 and the errors are presented below.
If you have an idea on how to solve this issue please let me know. I'm not an expert on how python runs in the background and how packages are installed through pip. Thanks in advance! B.
ERROR: Could not find a version that satisfies the requirement pyeto (from versions: none)
ERROR: No matching distribution found for pyeto
EDIT: pip --version
pip 20.2.2 from c:\users\user\anaconda3\lib\site-packages\pip (python 3.6)
The author hasn't put it on pypi, so pip is treating it as an unknown package.
See https://github.com/woodcrafty/PyETo/issues/3
Check on the website on what version it is supported.
I'm trying to install django-trumbowyg https://github.com/sandino/django-trumbowyg to my app
When I did pip install django-trumbowyg, it returned this error:
Could not find a version that satisfies the requirement django-trumbowyg (from versions: )
No matching distribution found for django-trumbowyg
Does anyone know what this means? And how I can fix it?
As https://pypi.python.org/pypi/django-trumbowyg#downloads shows, there's only a binary package for Python2 at PyPI.
So, you have to install the package directly from the official sources as pointed out by Rishav in the meantime.
Then ask the developer to upload a source package to PyPI and/or build the wheel as universal.
You may also get this error if your company firewall doesnt allow any package from external source. you might need to add a proxy in that case.
for example: pip install django-trumbowyg --proxy=proxy.companydomain.com:
Python n00b here trying to install decoder.py via pip.
I see it exists when I search for it
$ pip search decoder.py
decoder.py (1.5XB) - Cross-platform Python module for decoding compressed audio files
But i can't seem to install it.
$ pip install decoder.py
Collecting decoder.py
Could not find a version that satisfies the requirement decoder.py (from versions: )
No matching distribution found for decoder.py
$ pip install decoder.py==1.5XB
Collecting decoder.py==1.5XB
Could not find a version that satisfies the requirement decoder.py==1.5XB (from versions: )
No matching distribution found for decoder.py==1.5XB
Any ideas?
This package doesn't provide any downloadable source code on PyPI.
You can download it from http://www.brailleweb.com/cgi-bin/python.py (this link was provided by authors on pypi, proceed with caution).
Author of decoder.py here. :D
I am sorry for inconvenience. pip was able to grab decoder.py from brailleweb.com before. It was unable to install it though because I didn't provide a setup script. I didn't do it primarily because people might like to choose which external decoders they would like to use and perhaps don't want to install them into their's Python site-packages directory on Windows.
So I settled for manual installation instead. You aren't first who complained about it and that's why next version will have the setup script at least.
The new version is coming out soon. I am sorry to say development is slower than I anticipated but new version will be ready sooner or later. :D
Cheers!
This is a very simple problem, but I’m completely stuck on how to solve it. I couldn’t even found a way for just downloading.
The website don’t give anything for downloading it outside pypi and without smug.
$ pip install --allow-external gitlib gitlib
Collecting gitlib
Could not find a version that satisfies the requirement gitlib (from versions: )
Some insecure and unverifiable files were ignored (use --allow-unverified gitlib to allow).
No matching distribution found for gitlib
Using the required options doesn’t solve the problem.
$ pip install --allow-all-external --allow-unverified gitlib gitlib==0.5
Collecting gitlib==0.5
Could not find a version that satisfies the requirement gitlib==0.5 (from versions: )
No matching distribution found for gitlib==0.5
Pypi is only a list of registered projects -- if the package is listed at a download URL, you will need to follow that path to get the actual code to install.
In your case, you could git clone or pip install from git://mcnabbs.org/smug.git. If there's issues cloning or downloading, that's not something anyone here would be able to help you out with -- the package maintainer has decided to self-host his code.
More generally, pip interacts with pypi. Pypi is a package index for code that is not in the standard library. Much of this code is third-party/non-official. It's important to note that there is no promise of quality, functionality, or ability to install this code directly from pip.
In the case of "Gitlab" as per pypi, there's no promise that the code is actually true to its marketing of being a "Pythonic low-level Git library", there's no guarantee that the download URL is direct (or correct or even working), and it's a perfect example of the value of knowing that this information is maintained by the person that registered that package on pypi.