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
[Request] Tell pip to stop confusing the noobs with upgrade suggestions #2988
Comments
Yeah, I fear it really has come to this. Been pondering it for a while, but even though there's an FAQ entry about it, people still get too confused by it, so that needs to be done I guess. |
There were what, 2-3 separate threads on it over the break? I thought it was silly at first to do this, but obv I'm wrong. |
I know, they're just wearing us out with things-they-shouldn't-be-doing, to be honest. Granted, Christmas is a big time for buying new 3D printers and toys. |
I actually setup an FAQ entry for that a couple months back, but I guess it's not news that people don't read. |
Users get too confused by the warning the lack of it generates on plugin installs/uninstalls and updates of any kind through pip. An FAQ entry on that matter hasn't helped, so we are now pulling out the nuclear option to reduce support overhead. Implements #2988
There you go. Done through the above commit, to be part of 1.3.11. |
Thanks. People are so event-driven these days. It's based upon the constant upgrade mentality out there. I have several Macs, iPads, iPhones and they all nag me to upgrade this, that and the other thing. We're being programmed that we MUST take all updates or face some unknown consequences. |
Updating OctoPi / not a directory
🤕 |
For what it's worth, I note that this page suggests that the developer upgrade their pip. I'm not sure whether or not that this can get someone into trouble. |
I think I have related issue. I use PrusaPrint image. It is my first day, so I can start with new image if this can't be solved easily I did not remove any lines from below, so you can see when things stopped working
|
@qqgg231 that doesn't look like a related issue but rather an install that after several partial installs of something got broken. Might be fixable, but the easiest is probably to reflash since I honestly don't know what broke. |
We know that python 2.7 is about to reach end of life. We are making preparations for this in the devel branch. We don't need pip going around and alarming our users about something they cannot solve, and which pretty much is already solved anyhow. So we nuke this stupid message present in current pip versions. Hard. See also #2988
And now I've also pushed a change which will suppress pip 19.0+'s newest message of "OMG PY2.7 IS EOL!!1!" which has also already caused confusion among users. I get why they are doing this, but I'd only prefer if they were a bit less annoying about it. Anyhow... above commit is ready for 1.3.11rc2 |
Correction... 1.3.11rc3 because I fscked up a merge. Sigh. |
So what version of pip should we be using? If the pip we have is not the pip we need, can you automagically fix it a) if it is older? b) if it is newer? |
If it really needs updating, yes, I'll find a way. But rather than forcing updates of pip, for the most part OctoPrint just is built to work with pretty much every version. The only cases where that doesn't apply are broken versions (which OctoPrint will detect) and version which are too old to interact with the current iteration of the official python package index (which OctoPrint will also tell you). Long story short: in most cases you don't have to use any other version that what came with your python install and/or image, and if that changes I'll find a way to solve it ideally automatically. The problem with updating pip - which is why I don't have it set to automatically update by default - is that newer versions sometimes introduce bad breaking changes in how it's used, and that can really break things in the field at unforeseen times in a way that needs fiddling on the command line to get back into working order. |
1.3.11 was released yesterday. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Is your feature request related to a problem? Please describe.
Each and every
pip install
activity is displayed for users both in the Settings-related popup and in the logs/command line.A lot of the users seem to think that any warning is a bad thing. The warning/message in question is related to the pip suggestion that pip itself ought to be upgraded. Some of the time this results in users asking on the forum what they should do. Some of the time users then take it upon themself to attempt to "fix" their pip version, getting into trouble.
Describe the solution you'd like
pip install --disable-pip-version-check _whatever_
...or edit the
$VIRTUAL_ENV/pip.conf
with this information so that manual commands don't throw the "error".Describe alternatives you've considered
We could attempt to distribute the information in the documentation and forum but it's not usually read first, to be honest.
Additional context
They see something similar to this:
https://i.stack.imgur.com/Sedia.jpg
The text was updated successfully, but these errors were encountered: