Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Wrong package version

See original GitHub issue

Using pipreqs I got: Django==2.1.5 while my version was Django==2.0.

Issue Analytics

State:
Created 5 years ago
Comments:6

Top GitHub Comments

5reactions

neopostmoderncommented, Mar 28, 2019

I’d strongly recommend to change the behavior to what @pastet89 suggests, I’d guess that this is what most people assume when saving requirements. The goal most people pursue is probably to have a reproducible install on another machine.

2reactions

imlisoncommented, Jul 24, 2019

I think using the --use-local option is the safest.

Top Results From Across the Web

wrong package version loaded from cache if version numbers ...

As a result different versions of the same package have the same version number, but they can be differentiated by installation source (GitHub ......

npm - Angular - Wrong package versions? - Stack Overflow

I've an angular app. In the package.json I defined for all angular packages the version 12.2.

Orchestrator running the wrong package version - UiPath Forum

Orchestrator is running the wrong package version for a process. Has anyone had this problem before, know why it happens, and how to...

apt-cache shows wrong package version available - Ask Ubuntu

From the output of apt-cache policy openssl , in the lines 1.1.1j-1ubuntu0~20.10.sav0 500 or 1.1.1f-1ubuntu4.3 1000 , the number at the end of ......

Implicit package version updates incorrectly after upgrade ...

Implicit package version updates incorrectly after upgrade/downgrade/remove packages. 2. Is duplicated by 3. Is duplicated by 3 issues (0 unresolved).