Poetry: "poetry install" when everything is already installed is very slow

[boxed]

• [X ] I am on the latest Poetry version.

• [X ] I have searched the issues of this repo and believe that this is not a duplicate.

• OS version and name: macOS Mojave 10.14.3

• Poetry version: 0.12.11

Issue

Did this:

poetry new foo
cd foo
poetry install

so far it's fine, but if I do poetry install, it says there is nothing to do but it still takes 7 seconds. I was looking into poetry because I was frustrated with pip being slow when it did nothing, but it seem poetry is even slower :(

[drunkwcodes]

How long does it take by pip and the acceptable overhead when you don't want poetry serving more than that?

[pmav99]

If memory serves, poetry asks PyPi for metadata. If the metadata are not available, then poetry downloads the package from PyPi to check it out. That's what takes time.

[boxed]

pip is dog slow in general. Try doing "pip --version"!

Going out on the network when the package is already installed seems pretty silly.

[drunkwcodes]

@boxed It might be another issue.

Please close this and reproduce the silliness in your another issue.

[boxed]

@drunkwcodes sorry, I didn't understand what you just said. Why would I close this ticket when it's still a real thing?

[drunkwcodes]

@boxed No it's not.

[boxed]

Why not? Am I having hallucinations or what are you saying?

[drunkwcodes]

Wait a minute... let me sign up a PayPal account to continue this conversation...

[hangtwenty]

Let’s stop the snarkiness @drunkwcodes, it is not helpful.

@boxed It would be good to have instructions for reproducing - can you share a snapshot of your reqs/pyproject.toml, pip and poetry versions, and output of your issue when installing (max verbose ideally)

[boxed]

Just try installing any package you already have installed. Now, I am aware the reason it's slow is because it just calls pip which is slow. It's not poetrys fault, but it does mean it's just as bad as pip at something pip is very bad at.

[drunkwcodes]

Wrong guy was mentioned, @hangtwenty.

[exhuma]

I can't reproduce this issue. First install is ~23s, subsequent installs are ~3s (using poetry 0.12.16 and pip 19.2.3)

Console output:

┌─[9:11:46] malbert@BBS-nexus
└─~/work/tmp/pspeed› time poetry install
Creating virtualenv pspeed-py3.5 in /home/users/malbert/.cache/pypoetry/virtualenvs
Updating dependencies
Resolving dependencies... (1.9s)

Writing lock file


Package operations: 9 installs, 0 updates, 0 removals

  - Installing markupsafe (1.1.1)
  - Installing click (7.0)
  - Installing itsdangerous (1.1.0)
  - Installing jinja2 (2.10.1)
  - Installing werkzeug (0.15.6)
  - Installing flask (1.1.1)
  - Installing marshmallow (3.0.3)
  - Installing msgpack (0.6.1)
  - Installing pyyaml (5.1.2)
poetry install  16.94s user 1.43s system 77% cpu 23.711 total
┌─[9:12:11] malbert@BBS-nexus
└─~/work/tmp/pspeed› time poetry install
Installing dependencies from lock file

Nothing to install or update

poetry install  2.24s user 0.21s system 80% cpu 3.052 total
┌─[9:12:17] malbert@BBS-nexus
└─~/work/tmp/pspeed› time poetry install
Installing dependencies from lock file

Nothing to install or update

poetry install  2.08s user 0.18s system 88% cpu 2.545 total
┌─[9:12:22] malbert@BBS-nexus
└─~/work/tmp/pspeed›

pyproject.toml

[tool.poetry]
name = "pspeed"
version = "0.1.0"
description = ""
license = "MIT"

[tool.poetry.dependencies]
python = "^3.5"
flask = "^1.1"
pyyaml = "^5.1"
msgpack = "^0.6.1"
marshmallow = "^3.0"

[tool.poetry.dev-dependencies]

[build-system]
requires = ["poetry>=0.12"]
build-backend = "poetry.masonry.api"

[boxed]

3 seconds counts. It should really be >100ms, ideally >10

[stale[bot]]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[boxed]

It is still relevant.