Pipenv 9.0.0 always install dev packages, instead of just installing packages from [packages]
section.
Pipenv 8.3.2 works as expected.
pipenv install
should only install packages from [packages]
section
pipenv install
actually installs all packages, both from [packages]
and [dev-packages]
section
[[source]]
url = "https://pypi.python.org/simple"
verify_ssl = true
name = "pypi"
[packages]
django = "*"
[dev-packages]
ipython = "*"
$ pipenv install
$ pipenv graph
Django==2.0
- pytz [required: Any, installed: 2017.3]
ipython==6.2.1
- decorator [required: Any, installed: 4.1.2]
- jedi [required: >=0.10, installed: 0.11.0]
- parso [required: ==0.1.0, installed: 0.1.0]
- pexpect [required: Any, installed: 4.3.0]
- ptyprocess [required: >=0.5, installed: 0.5.2]
- pickleshare [required: Any, installed: 0.7.4]
- prompt-toolkit [required: >=1.0.4,<2.0.0, installed: 1.0.15]
- six [required: >=1.9.0, installed: 1.11.0]
- wcwidth [required: Any, installed: 0.1.7]
- pygments [required: Any, installed: 2.2.0]
- setuptools [required: >=18.5, installed: 38.2.4]
- simplegeneric [required: >0.8, installed: 0.8.1]
- traitlets [required: >=4.2, installed: 4.3.2]
- decorator [required: Any, installed: 4.1.2]
- ipython-genutils [required: Any, installed: 0.2.0]
- six [required: Any, installed: 1.11.0]
@jlirochon thanks for the report, I can reproduce this using the provided pipfile. This is definitely a regression and I will look at addressing it asap
Any chance this get released in a 9.0.1 soon? It can break some automated deployments.
Thank you very much for the fix BTW 鉂わ笍 !
@k4nar, we'll have a release out later today. We've been waiting to verify there aren't any other high priority bugs lurking before we bump the version. Thanks for your patience :)
No release fixing this yet.
Thanks for checking in @cailloumajor. We've had some issues with our testing infrastructure that came up as a result of our recent move to pypa. These are currently blocking the release but I'm hoping to find time to get this resolved this weekend.
Most helpful comment
Thanks for checking in @cailloumajor. We've had some issues with our testing infrastructure that came up as a result of our recent move to pypa. These are currently blocking the release but I'm hoping to find time to get this resolved this weekend.