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.

pipenv install progress bar doesn't take dev dependencies into account

See original GitHub issue

Als-MacBook-Pro # cat Pipfile
[[source]]
url = "https://pypi.python.org/simple"
verify_ssl = true

[packages]

[dev-packages]

pytest = "*"
coverage = "*"
coveralls = "*"
pep8 = "*"
twine = "*"

Als-MacBook-Pro # pipenv install
No package provided, installing all dependencies.
Installing dependencies from Pipfile.lock…
  🐍   ❒❒❒❒❒❒❒❒❒❒❒❒❒❒❒❒❒❒❒❒❒❒❒❒❒❒❒❒❒❒❒❒ 0/0 — 00:00:00
To activate this project's virtualenv, run the following:
 $ pipenv shell

Notice the 0/0 next to the progress bar.

Issue Analytics

State:
Created 6 years ago
Comments:9 (8 by maintainers)

Top GitHub Comments

2reactions

uranusjrcommented, Sep 21, 2017

Optimising for development is generally a bad idea because it’s too easy to miss things. You should allow as little by default as possible, and require explicit instruction to allow things on dev. Every development best practice guide will tell you this. Not every project is doing it right, even prominent ones (see MongoDB and MySQL), but I hope Pipenv will continue to do this the right way.

1reaction

kennethreitzcommented, Sep 21, 2017

we’re not changing it.