This is due to the fact that uninstalling a distutils project will only partially uninstall the project. It is a distutils installed project and thus we cannot accurately determine which files belong to it which would lead to only a partial uninstall. It was marked with a pip10 deprecation error so this was not unreasonable. There's all the Windows users, for whom there's no distro package manager. Is there a way to uninstall this version with distutils? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
It is a distutils installed project and thus we cannot accurately determine which files belong to it which would lead to only a partial uninstall. Have you guys talked to that team about this? Or at least any way to tell pip that there is numpy installed? It is a distutils installed project and thus we cannot accurately determine which files belong to it which would lead to only a partial uninstall. I came across the same problem thank goodness for this post! Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Have you guys talked to that team about this? Installing collected packages: six Found existing installation: six 1. We've previously removed the installation metadata, so that it looks like we did the install, but we've had to leave files behind. As a pip maintainer, the question I'd have to ask here is how much pressure have users put on the major distros for them to solve this issue? Check out the further reading section below to learn more. Installations are being broken because of some religion-like believing.
It would be great if this would eventually happen. We may elect to work around it and push the date for this back further, but realistically things need to stop relying on plain distutils. It is a distutils installed project and thus we cannot accurately determine which files belong to it which would lead to only a partial uninstall. I don't think pip is going to change on this. Have a question about this project? With the --ignore-installed flag, the uninstall step is skipped and the new version is simply installed on top of the old one.
The answer to that is: because there are packages that are not installable by pip. I cannot do anything now. While I'm no fan of sudo pip install. It's now later, and quite obviously by the fact folks are asking for it, people didn't listen to the warnings and get their systems fixed so that packages are installed with the appropriate metadata or they're using something isolated from places where incorrect metadata has been installed. Are you doing this installation in a system environment? And presumably the behaviour was deprecated because it had caused issues prior to that? Not that I know of, and no we haven't talked to them about it.
Note: we are using python 2. Turns out I had installed it via apt, so doing apt remove --autoremove python-wxgtk3. The actual breakage from pip not being able to uninstall distro-packaged libraries was mostly mitigated on Debian derivatives because they didn't share the same file tree and so the location where pip installed modules was hit earlier in the import search path than those provided by distro packages, forming a sieve of sorts granted that did still pose some issues, e. Please check the permissions and owner of that directory. I'd probably have to suggest the answer is no.
So No, I don't think it's too late, but any proposal would need to include the above plan for finally being able to remove this. I'd probably have to suggest the answer is no. A variation of this, where a virtualenv is being used also occurs - this shouldn't have been warning ever, since the virtualenv means we won't uninstall, we'll just shadow it. It overwrites files managed by the package manager and we know that. For mine, the best course would be to determine this, revert but with a deprecation time-frame that's fact based on when users can reasonably be expected to not require it p.
If so, why is pip trying to install upgrade them? However, when we install on an equivalent RedHat 7. This is due to the fact that uninstalling a distutils project will only partially uninstall the project. I thought it might be a way out of this, but if the primary concern from pip maintainers is how quickly they'll be able to rip it back out then it's not going to help for any actually useful ~7-year timeframe. I was getting this error for wxPython Cannot uninstall 'wxPython'. This discussion has been closed.
This means that whenever we uninstall these, we don't actually uninstall any files we simply remove the record that something has been installed and then overwrite files. For information on how to perform authorization in a web application, see. So what would you recommend for a team that automates their pip installations? And we still get the netaddr error. Thank you for those of you who supplied workarounds. Also its not possible to use --ignore-installed command for all packages. Thanks for the quick answer! I'm fairly new to python and pip, so any pointers would be most helpful. It's entirely intentional behavior, and as discussed previously any attempt to provide a workaround in pip seems to need to come with a timeline for the pip maintainers removing said workaround I have provided one at though I did not provide a recommended deprecation timeframe, and it may also need minor rebasing at this point.
We set up our server using terraform, so we automatically call pip install for smart-open and boto3 and then we have numpy, scipy, boto, sklearn, and datadog in a requirements. Sign up for a free GitHub account to open an issue and contact its maintainers and the community. That said, also maybe these are less likely to be updated? It is the uninstall step that fails for distutils packages. For what it's worth, I completely agree one shouldn't mix package managers in the same context, certainly at least for production scenarios. . If smart-open is somehow installing urllib3 in a way that triggers this issue, that sounds like a smart-open problem. This is rather inconvenient because most of the packages come installed as dependencies and we do not manage it ourselves.