Pip2 Fails to install the latest api spec version

When using pip2 to install the linode cli, it installs the correct version, but seems to install the wrong Spec version (4.0.8, instead of the latest 4.1.0).

This issue has been documented by customers via https://www.linode.com/community/questions/18361/linode-cli-version-mismatch and reproduced.

I have some theories why this might be happening, and will follow up in this ticket. However, for now, if you encounter this issue, installing the linode cli with pip3 will fix the issue.

[Dorthu]

Thanks for the feedback! It sounds like the warning itself is helpful and desirable as long as there is actually a new CLI version ready to update to in all cases. It also looks like PyPI has an API that can retrieve current package versions… I’m going to experiment with fetching the most recent version from PyPI and only presenting the warning if there is in fact a new version to upgrade to. If that doesn’t add too much overhead I’ll put up a PR for it.

[gpfjeff]

Sounds like a reasonable approach to me. I’m not opposed to the client-side check to PyPI, although like @Dorthu I can foresee someone out there being a little antsy about it. (Overly paranoid folks who obsessively watch their traffic with Wireshark, maybe? It’s nothing compared to everything Microsoft that phones home to the mothership…)

Thanks for looking into this, guys. Been a Linode customer for eight years now, and while I’ve had the occasional rough patch here and there, I’ve stuck with you longer than I’ve been with any other host. Keep up the great work.