Poetry tries to remove setuptools and then complains it can't find it #4242

0xallie · 2021-07-01T20:30:57Z

I am on the latest Poetry version.
I have searched the issues of this repo and believe that this is not a duplicate.
If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).

OS version and name: Debian 10
Poetry version: 1.1.7
Link of a Gist with the contents of your pyproject.toml file: https://gist.github.com/nyuszika7h/238727b812cfce957e0e34e1143b160f

Issue

When running poetry install, Poetry tries to remove setuptools, and then later complains that setuptools is not found when trying to install future.

I suspect this may be because win10toast depends on setuptools, but that package is skipped due to the platform not being Windows.

❯ poetry install -vvv
Creating virtualenv test in /home/nyuszika7h/test/.venv
Using virtualenv: /home/nyuszika7h/test/.venv
Installing dependencies from lock file

Finding the necessary packages for the current system

Package operations: 7 installs, 0 updates, 1 removal, 6 skipped

  • Removing importlib-metadata (4.6.0): Pending...
  • Removing importlib-metadata (4.6.0): Skipped for the following reason: Not currently installed
  • Removing pypiwin32 (223): Pending...
  • Removing pypiwin32 (223): Skipped for the following reason: Not currently installed
  • Removing pywin32 (301): Pending...
  • Removing pywin32 (301): Skipped for the following reason: Not currently installed
  • Removing win10toast (0.9): Pending...
  • Removing win10toast (0.9): Skipped for the following reason: Not currently installed
  • Removing typing-extensions (3.10.0.0): Pending...
  • Removing typing-extensions (3.10.0.0): Skipped for the following reason: Not currently installed
  • Removing zipp (3.4.1): Pending...
  • Removing zipp (3.4.1): Skipped for the following reason: Not currently installed
  • Removing setuptools (57.0.0): Pending...
  • Removing setuptools (57.0.0): Removing...
  • Removing setuptools (57.0.0)
  • Installing soupsieve (2.2.1): Pending...
  • Installing soupsieve (2.2.1): Installing...
  • Installing soupsieve (2.2.1)
  • Installing beautifulsoup4 (4.9.3): Pending...
  • Installing beautifulsoup4 (4.9.3): Installing...
  • Installing cssutils (2.3.0): Pending...
  • Installing cssutils (2.3.0): Installing...
  • Installing future (0.18.2): Pending...
  • Installing future (0.18.2): Installing...
  • Installing future (0.18.2): Failed

  EnvCommandError

  Command ['/home/nyuszika7h/test/.venv/bin/pip', 'install', '--no-deps', 'file:///home/nyuszika7h/.cache/pypoetry/artifacts/f8/58/55/86be1f567b212fdd98854d12815964a49db8fb1bcff725018e5f95c61d/future-0.18.2.tar.gz'] errored with the following return code 1, and output:
  Processing /home/nyuszika7h/.cache/pypoetry/artifacts/f8/58/55/86be1f567b212fdd98854d12815964a49db8fb1bcff725018e5f95c61d/future-0.18.2.tar.gz
      ERROR: Command errored out with exit status 1:
       command: /home/nyuszika7h/test/.venv/bin/python -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-req-build-1yncrz1a/setup.py'"'"'; __file__='"'"'/tmp/pip-req-build-1yncrz1a/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(__file__) if os.path.exists(__file__) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base /tmp/pip-pip-egg-info-gd9atrnx
           cwd: /tmp/pip-req-build-1yncrz1a/
      Complete output (3 lines):
      Traceback (most recent call last):
        File "<string>", line 1, in <module>
      ModuleNotFoundError: No module named 'setuptools'
      ----------------------------------------
  WARNING: Discarding file:///home/nyuszika7h/.cache/pypoetry/artifacts/f8/58/55/86be1f567b212fdd98854d12815964a49db8fb1bcff725018e5f95c61d/future-0.18.2.tar.gz. Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.
  ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.
  WARNING: You are using pip version 21.1.2; however, version 21.1.3 is available.
  You should consider upgrading via the '/home/nyuszika7h/test/.venv/bin/python -m pip install --upgrade pip' command.


  at ~/.local/share/pypoetry/venv/lib/python3.9/site-packages/poetry/utils/env.py:1101 in _run
      1097│                 output = subprocess.check_output(
      1098│                     cmd, stderr=subprocess.STDOUT, **kwargs
      1099│                 )
      1100│         except CalledProcessError as e:
    → 1101│             raise EnvCommandError(e, input=input_)
      1102│
      1103│         return decode(output)
      1104│
      1105│     def execute(self, bin, *args, **kwargs):

  • Installing lxml (4.6.3): Pending...
  • Installing lxml (4.6.3): Installing...
  • Installing six (1.16.0): Pending...
  • Installing six (1.16.0): Installing...
  • Installing six (1.16.0)
  • Installing cssutils (2.3.0)
  • Installing future (0.18.2): Pending...
  • Installing future (0.18.2): Installing...
  • Installing future (0.18.2): Failed

  EnvCommandError

  Command ['/home/nyuszika7h/test/.venv/bin/pip', 'install', '--no-deps', 'file:///home/nyuszika7h/.cache/pypoetry/artifacts/f8/58/55/86be1f567b212fdd98854d12815964a49db8fb1bcff725018e5f95c61d/future-0.18.2.tar.gz'] errored with the following return code 1, and output:
  Processing /home/nyuszika7h/.cache/pypoetry/artifacts/f8/58/55/86be1f567b212fdd98854d12815964a49db8fb1bcff725018e5f95c61d/future-0.18.2.tar.gz
      ERROR: Command errored out with exit status 1:
       command: /home/nyuszika7h/test/.venv/bin/python -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-req-build-1yncrz1a/setup.py'"'"'; __file__='"'"'/tmp/pip-req-build-1yncrz1a/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(__file__) if os.path.exists(__file__) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base /tmp/pip-pip-egg-info-gd9atrnx
           cwd: /tmp/pip-req-build-1yncrz1a/
      Complete output (3 lines):
      Traceback (most recent call last):
        File "<string>", line 1, in <module>
      ModuleNotFoundError: No module named 'setuptools'
      ----------------------------------------
  WARNING: Discarding file:///home/nyuszika7h/.cache/pypoetry/artifacts/f8/58/55/86be1f567b212fdd98854d12815964a49db8fb1bcff725018e5f95c61d/future-0.18.2.tar.gz. Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.
  ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.
  WARNING: You are using pip version 21.1.2; however, version 21.1.3 is available.
  You should consider upgrading via the '/home/nyuszika7h/test/.venv/bin/python -m pip install --upgrade pip' command.


  at ~/.local/share/pypoetry/venv/lib/python3.9/site-packages/poetry/utils/env.py:1101 in _run
      1097│                 output = subprocess.check_output(
      1098│                     cmd, stderr=subprocess.STDOUT, **kwargs
      1099│                 )
      1100│         except CalledProcessError as e:
    → 1101│             raise EnvCommandError(e, input=input_)
      1102│
      1103│         return decode(output)
      1104│
      1105│     def execute(self, bin, *args, **kwargs):

  • Installing lxml (4.6.3): Pending...
  • Installing lxml (4.6.3): Installing...
  • Installing lxml (4.6.3)
  • Installing six (1.16.0): Pending...
  • Installing six (1.16.0): Installing...
  • Installing six (1.16.0)
  • Installing beautifulsoup4 (4.9.3)
  • Installing cssutils (2.3.0): Pending...
  • Installing cssutils (2.3.0): Installing...
  • Installing cssutils (2.3.0)
  • Installing future (0.18.2): Pending...
  • Installing future (0.18.2): Installing...
  • Installing future (0.18.2): Failed

  EnvCommandError

  Command ['/home/nyuszika7h/test/.venv/bin/pip', 'install', '--no-deps', 'file:///home/nyuszika7h/.cache/pypoetry/artifacts/f8/58/55/86be1f567b212fdd98854d12815964a49db8fb1bcff725018e5f95c61d/future-0.18.2.tar.gz'] errored with the following return code 1, and output:
  Processing /home/nyuszika7h/.cache/pypoetry/artifacts/f8/58/55/86be1f567b212fdd98854d12815964a49db8fb1bcff725018e5f95c61d/future-0.18.2.tar.gz
      ERROR: Command errored out with exit status 1:
       command: /home/nyuszika7h/test/.venv/bin/python -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-req-build-1yncrz1a/setup.py'"'"'; __file__='"'"'/tmp/pip-req-build-1yncrz1a/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(__file__) if os.path.exists(__file__) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base /tmp/pip-pip-egg-info-gd9atrnx
           cwd: /tmp/pip-req-build-1yncrz1a/
      Complete output (3 lines):
      Traceback (most recent call last):
        File "<string>", line 1, in <module>
      ModuleNotFoundError: No module named 'setuptools'
      ----------------------------------------
  WARNING: Discarding file:///home/nyuszika7h/.cache/pypoetry/artifacts/f8/58/55/86be1f567b212fdd98854d12815964a49db8fb1bcff725018e5f95c61d/future-0.18.2.tar.gz. Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.
  ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.
  WARNING: You are using pip version 21.1.2; however, version 21.1.3 is available.
  You should consider upgrading via the '/home/nyuszika7h/test/.venv/bin/python -m pip install --upgrade pip' command.


  at ~/.local/share/pypoetry/venv/lib/python3.9/site-packages/poetry/utils/env.py:1101 in _run
      1097│                 output = subprocess.check_output(
      1098│                     cmd, stderr=subprocess.STDOUT, **kwargs
      1099│                 )
      1100│         except CalledProcessError as e:
    → 1101│             raise EnvCommandError(e, input=input_)
      1102│
      1103│         return decode(output)
      1104│
      1105│     def execute(self, bin, *args, **kwargs):

  • Installing lxml (4.6.3): Pending...
  • Installing lxml (4.6.3): Installing...
  • Installing lxml (4.6.3)
  • Installing six (1.16.0): Pending...
  • Installing six (1.16.0): Installing...
  • Installing six (1.16.0)

To clarify: Running poetry lock from Poetry 1.2.0a1 seems to cause the lock file to include setuptools, which triggers the issue with Poetry <= 1.1.7. Running poetry lock from Poetry 1.1.7 makes it exclude setuptools and there is no issue.

	Install with Poetry 1.1.7	Install with Poetry 1.2.0a1
Lock file from Poetry 1.1.7	✅	✅
Lock file from Poetry 1.2.0a1	❌	✅

Also, both lock files were generated on Linux. I have not tested on Windows yet.

The text was updated successfully, but these errors were encountered:

TheElectronWill · 2021-07-07T09:08:08Z

Can reproduce on windows and linux: poetry 1.2.0a1 generates a lock file that, when installed, sometimes, removes setuptools and makes some packages fail to install.

nyanpasu64 · 2021-07-13T23:57:38Z

Does editing your pyproject.toml to add "setuptools" to the [build-system] requires stop the error from occurring? I don't know if it's a fix or a workaround.

[build-system]
-requires = ["poetry_core>=1.0"]
+requires = ["setuptools", "poetry_core>=1.0"]
build-backend = "poetry.core.masonry.api"

dimaqq · 2021-07-21T07:49:17Z

The delta between 1.2.0 prerelease and 1.1.7 stable:
(that is going back to stable)

diff --git a/poetry.lock b/poetry.lock
index dc6b6820f..f0e8e3fdd 100644
--- a/poetry.lock
+++ b/poetry.lock
@@ -499,7 +499,6 @@
 pickleshare = "*"
 prompt-toolkit = ">=2.0.0,<3.0.0 || >3.0.0,<3.0.1 || >3.0.1,<3.1.0"
 pygments = "*"
-setuptools = ">=18.5"
 traitlets = ">=4.2"

 [package.extras]
@@ -1020,18 +1019,6 @@

-[[package]]
-name = "setuptools"
-version = "57.4.0"
-description = "Easily download, build, install, upgrade, and uninstall Python packages"
-category = "dev"
-optional = false
-python-versions = ">=3.6"
-
-[package.extras]
-docs = ["sphinx", "jaraco.packaging (>=8.2)", "rst.linker (>=1.9)", "jaraco.tidelift (>=1.4)", "pygments-github-lexers (==0.0.5)", "sphinx-inline-tabs", "sphinxcontrib-towncrier", "furo"]
-testing = ["pytest (>=4.6)", "pytest-checkdocs (>=2.4)", "pytest-flake8", "pytest-cov", "pytest-enabler (>=1.0.1)", "mock", "flake8-2020", "virtualenv (>=13.0.0)", "pytest-virtualenv (>=1.2.7)", "wheel", "paver", "pip (>=19.1)", "jaraco.envs", "pytest-xdist", "sphinx", "jaraco.path (>=3.2.0)", "pytest-black (>=0.3.7)", "pytest-mypy"]
-
@@ -1082,7 +1069,6 @@
 packaging = "*"
 Pygments = ">=2.0"
 requests = ">=2.0.0"
-setuptools = "*"
 six = ">=1.5"
 snowballstemmer = ">=1.1"
 sphinxcontrib-websupport = "*"
@@ -1994,10 +1980,6 @@
-setuptools = [
-    {file = "setuptools-57.4.0-py3-none-any.whl", hash = "sha256:a49230977aa6cfb9d933614d2f7b79036e9945c4cdd7583163f4e920b83418d6"},
-    {file = "setuptools-57.4.0.tar.gz", hash = "sha256:6bac238ffdf24e8806c61440e755192470352850f3419a52f26ffe0a1a64f465"},
-]
 six = [
     {file = "six-1.15.0-py2.py3-none-any.whl", hash = "sha256:8b74bedcbbbaca38ff6d7491d76f2b06b3592611af620f8426e82dddb04a5ced"},
     {file = "six-1.15.0.tar.gz", hash = "sha256:30639c035cdb23534cd4aa2dd52c3bf48f06e5f4a941509c8bafd8ce11080259"},

In other words, 1.2.0 pre includes setuptools into poetry.lock while 1.1.7 does not.

I guess that 1.1.7 wants to build [package wheel? of a] dependency in a clean environment, and that's why it tries to [temporarily] remove setuptools...

apollo13 · 2021-09-03T11:14:44Z

So the only issue here is that an older poetry cannot read a lock file generated by the newer version? If that is the case then I think this is expected behavior.

0xallie · 2021-09-03T11:20:11Z

Breaking backwards compatibility in a minor release is not the best experience. Is there really no way to make any required changes in a way that it doesn't lead to mysterious breakage on earlier versions?

apollo13 · 2021-09-03T11:22:19Z

I don't think so. In this special case it was actually a bug fix (1.1 was broken in the sense that it did not properly record setuptools in the lockfile). There is really no good way that an old version could ever cope with that I think.

0xallie · 2021-09-12T15:16:33Z

Does editing your pyproject.toml to add "setuptools" to the [build-system] requires stop the error from occurring? I don't know if it's a fix or a workaround.
[build-system]
-requires = ["poetry_core>=1.0"]
+requires = ["setuptools", "poetry_core>=1.0"]
build-backend = "poetry.core.masonry.api"

Sorry for the late reply about this. I think that fixed my issues before, but with 1.2.0 -> 1.1.x it does not fix the issue. But poetry add setuptools seems to fix it. So I guess the workaround is either that, or not using Poetry 1.2.0 on my end until it's stable, and telling users to upgrade once it is. But it would be nice if there was a way to tell users that this project requires a specific version of Poetry rather than a scary error message. requires = ['poetry-core>=1.2.0'] does not seem to change anything,

abn · 2021-11-18T12:05:55Z

The build-system.requires part is something poetry itself does not use at the moment. This is used by the non-poetry PEP 517 frontends (eg: pip, build etc.)

See also #2789.

As to why setuptools appear in the lockfile, this is related to #2826. This change meant that it is no longer excluded from dependency resolution. This means if a dependency in your project's dependency tree requires setuptools it will be added to the lock file.

#3153 (comment)

As you identify, since a project in your tree requires setuptools and that is not enabled for the platform, setuptools get removed as it is not required.

Additionally, changes in #3835 should now mean that pip install now adds --use-pep517 when building a depdency from an sdist.

I'd recommend you try using poetry from master.

rafalkrupinski · 2021-12-25T22:15:43Z

I'm on poetry 1.1.12
I've removed my poetry.lock and recreated it
and I'm still facing the issue

rr- · 2022-01-17T01:28:19Z

For me having explicit dependency on setuptools in normal dependencies does not make a difference, it still removes it.

It completely breaks our Cython builds.

realabja · 2022-03-31T09:20:30Z

I have the same problem as well that trying to slowly write my poetry plugins, but this issue with incompatibility between 1.1 and 1.2 would not allow me to use 1.2 and plugins.

danielloader · 2022-04-13T10:44:46Z

I've just bitten the bullet and tested 1.2.0b1 and wholly moved over to it - gambling a bit but half way house between the two isn't feasible any more. Especially with the --dev becoming --group dev and the subsequent trying to parse the group key in pyproject.toml

abn · 2022-05-10T09:53:05Z

I am going to close this as it seems this will be resolved in 1.2 and is already on mater.

emilhe · 2022-07-18T09:05:53Z

In case anyone are looking for a workaround to make a .lock file generated with Poetry 1.2.x compatible with Poetry 1.1.x, I created a small gist to do so,

curl https://gist.githubusercontent.com/emilhe/0c7b1a33b2d02f17331242bf4fffd07c/raw/8da0665a58f469c980e7661d7f8c36f3bd3af992/strip_setuptools.py | python - && poetry install

In my case, I needed it because I am using Poetry 1.2.x locally (I am having various issues with 1.1.x), while my cloud provider supports only 1.1.x.

antonakospanos · 2022-09-07T11:03:17Z

In my case the issue is reproduced using poetry 1.2.0. The new versions adds in poetry.lock the following lines:

[package.dependencies]
setuptools = "*"

[[package]]
name = "setuptools"
version = "63.4.3"
description = "Easily download, build, install, upgrade, and uninstall Python packages"
category = "main"
optional = false
python-versions = ">=3.7"

Which when a another colleague (or our CI) runs poetry install using poetry 1.1.14 fails as follows:

Installing typing-extensions (4.3.0)
..
EnvCommandError
  Preparing metadata (setup.py): started
  Preparing metadata (setup.py): finished with status 'error'
  error: subprocess-exited-with-error
  × python setup.py egg_info did not run successfully.
  exit code: 1
  ╰─> [1 lines of output]
ERROR: Can not execute `setup.py` since setuptools is not available in the build environment.

python-poetry/poetry#4242 (comment)

* refactor github action to perform linting before testing and use a typical poetry installation workflow * fix syntax errors in github action config * reformatted files with black * reorganized imports with isort * ignore swap files so we don't accidentally commit them * create user group, add python executables to path, and upgrade pip. I changed the default CMD to 'bash' because 'poetry shell' wasn't working and I couldn't figure out why... * simplify github workflow into just one job there's no reason to separate concerns between linting and testing now, plus I didn't want to have repetetitive jobs (although I could eventually templatize the setup steps) * changed to an available python version on github runners * workaround bug in snok/install-poetry action that gives 'poetry: command not found' for the latest version (1.2.0) * went back to poetry 1.2.0 but added ~/.local/bin to the system path in the github action the reason for this reversion is described in more detail here: python-poetry/poetry#4242 essentially there isn't backwards compatibility with 1.2.0 lock files and old poetry versions (like the 1.1.14 I switched it to before in the github action), and it couldn't find 'setuptools' because of this * explicitly list directory, maybe because /home/tristan isn't resolved correctly? * update poetry in dev dockerfile, lock updates with this new version, and upgrade the poetry-core version for building these were recommended from the issue with the snok/install-poetry github action documented at snok/install-poetry#89 * add path logging so i can figure out what's going on in the github action * add env variable to hopefully prevent issues with upgrade * maybe this is caused by 3.6 being deprecated? comments in the previously linked issue suggested this could be why * run linting and testing steps in the github action job in a poetry shell otherwise, the job will fail because the tools are libraries aren't actually available in the environment * poetry run wasn't accepted by github as valid for the 'shell' field so I added a bash -c to see if that works * that didn't work either so calling poetry run on every command separately * fix spacing in run command * remove 3.10 runtime because I realized I didn't actually test this works * take out pointless echos and exclude poetry .venv from flake8 linting because otherwise it will lint dependency source files we have no control over * fix a bunch of linting errors * reformat files and fix a couple remaining linting errors * make isort compatible with black so they don't keep reformatting endlessly -- had to sacrifice some comments because I couldn't figure out how to get it to work without this (will try later) * fix recursive import by importing tqdm modules from the library directly * fix permissions on parent directory of the devcontainer's working directory to allow for the unit testing module to download some testing data from https://github.com/pyrfume/pyrfume-data * add back the line that I thought was a pointless import but actually has relevant logic... * fix last lingering linting error, left as a TODO * drop support for python 3.6 (not even tested in actions and losing support anyways soon) to upgrade pandas to a compatible version so that tests fully pass * remove macos runtime because for some reason it can't install public files from api.github.com/repos, even though I tested the same install locally on macOS with all of the failing python versions * don't fail fast so we can see the results of runs on all python distributions. also I reincluded macos just to see how far they get

Looks like this is not needed. This will allow to workaround some problems with build tools like this one python-poetry/poetry#4242

jomach · 2022-11-30T22:03:14Z

I still have this problem on 1.2.x

`poetry install` removes untracked packages by default in 1.3, among them setuptools. This causes all subsequent Python invocations (including the one poetry uses to get the system tags from a virtual environment) to fail with e.g. ``` Error processing line 1 of /opt/homebrew/Caskroom/miniforge/base/envs/test/lib/python3.10/site-packages/distutils-precedence.pth: Traceback (most recent call last): File "/opt/homebrew/Caskroom/miniforge/base/envs/test/lib/python3.10/site.py", line 186, in addpackage exec(line) File "<string>", line 1, in <module> ModuleNotFoundError: No module named '_distutils_hack' ``` As a workaround, make setuptools an explicit dev dependency so `poetry install` works by default. This is similar, but possibly not identical, to python-poetry/poetry#4242

qkponton · 2023-02-23T12:24:33Z

Having same or similar issue with Poetry (version 1.3.2)
Anyone found a fix for this?

Command ['/home/visitor/afm/bin/python', '-m', 'pip', 'install', '--use-pep517', '--disable-pip-version-check', '--isolated', '--no-input', '--prefix', '/home/visitor/afm', '--no-deps', '/home/visitor/.cache/pypoetry/artifacts/dd/72/1c/1fb84326375a883f33f9419395a2175a0608c799d63478062ef3b3c7d8/future-0.18.3.tar.gz'] errored with the following return code 1, and output:
Processing /home/visitor/.cache/pypoetry/artifacts/dd/72/1c/1fb84326375a883f33f9419395a2175a0608c799d63478062ef3b3c7d8/future-0.18.3.tar.gz
Installing build dependencies: started
Installing build dependencies: still running...
Installing build dependencies: still running...
Installing build dependencies: still running...
Installing build dependencies: still running...
Installing build dependencies: still running...
Installing build dependencies: still running...
Installing build dependencies: finished with status 'error'
error: subprocess-exited-with-error
× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> [7 lines of output]
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ConnectTimeoutError(<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7fbfa837a2b0>, 'Connection to pypi.org timed out. (connect timeout=15)')': /simple/setuptools/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ConnectTimeoutError(<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7fbfa837a5b0>, 'Connection to pypi.org timed out. (connect timeout=15)')': /simple/setuptools/
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ConnectTimeoutError(<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7fbfa837a7c0>, 'Connection to pypi.org timed out. (connect timeout=15)')': /simple/setuptools/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ConnectTimeoutError(<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7fbfa837a8e0>, 'Connection to pypi.org timed out. (connect timeout=15)')': /simple/setuptools/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ConnectTimeoutError(<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7fbfa837aa60>, 'Connection to pypi.org timed out. (connect timeout=15)')': /simple/setuptools/
ERROR: Could not find a version that satisfies the requirement setuptools>=40.8.0 (from versions: none)
ERROR: No matching distribution found for setuptools>=40.8.0
[end of output]

And I'm also wondering why pip is trying to reach "pypi.org" although I've defined a private index...

poetry env info

Virtualenv
Python: 3.9.11
Implementation: CPython
Path: /home/visitor/afm
Executable: /home/visitor/afm/bin/python
Valid: True

/home/visitor/afm/bin/pip config -v list
For variant 'global', will try loading '/etc/xdg/pip/pip.conf'
For variant 'global', will try loading '/etc/pip.conf'
For variant 'user', will try loading '/home/visitor/.pip/pip.conf'
For variant 'user', will try loading '/home/visitor/.config/pip/pip.conf'
For variant 'site', will try loading '/home/visitor/afm/pip.conf'
global.index='http://my-private/repository/PyPI/'
global.index-url='http://my-private/repository/PyPI/simple/'
global.trusted-host='my-private'

qkponton · 2023-02-23T14:23:58Z

I found the related topic: #3249
thanks

github-actions · 2024-02-29T18:06:30Z

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

0xallie added kind/bug Something isn't working as expected status/triage This issue needs to be triaged labels Jul 1, 2021

sdispater added this to the 1.2 milestone Jul 7, 2021

0xallie mentioned this issue Jul 8, 2021

1.0.10 -> 1.1 regression: EnvCommandError: 'No module named setuptools' on Python 3.7 #3153

Closed

martinxsliu mentioned this issue Aug 23, 2021

Poetry 1.2.0a2 - discrepancy in lockfile generation (compared to 1.1.x) #4384

Closed

3 tasks

abn closed this as completed May 10, 2022

abn mentioned this issue May 10, 2022

1.2.0 Release #5586

Closed

jason990420 mentioned this issue Jun 6, 2022

[Question] Failed to upgrade PySimpleGUI from Github PySimpleGUI/PySimpleGUI#5572

Closed

7 tasks

mkniewallner removed the status/triage This issue needs to be triaged label Jun 11, 2022

ChewieCB mentioned this issue Jun 21, 2022

AMB-1137: Added tests to be run manually to check CIS2 refresh token expiry NHSDigital/identity-service-api#290

Merged

7 tasks

mattsta mentioned this issue Jul 29, 2022

Fix poetry python version limits krasserm/perceiver-io#16

Closed

chimaerase mentioned this issue Aug 24, 2022

Install removes dependencies of non-installed extras #6229

Closed

sryabkov mentioned this issue Aug 24, 2022

Poetry is extremely slow when resolving the dependencies #2094

Closed

3 tasks

sryabkov mentioned this issue Sep 1, 2022

after poetry 1.2.0 release, poetry 1.1 installation is broken when it is installed with pip install #6300

Closed

2 tasks

javiber mentioned this issue Sep 2, 2022

Fix dependency on older version of rich tryolabs/norfair#160

Merged

neersighted mentioned this issue Sep 7, 2022

Poetry install with version 1.1.6 fails with file not found errors #4143

Closed

3 tasks

glennmatthews mentioned this issue Sep 19, 2022

Bump oauthlib from 3.2.0 to 3.2.1 nautobot/nautobot-app-bgp-models#64

Merged

goodwanghan mentioned this issue Sep 20, 2022

Fugue Integration whylabs/whylogs#839

Merged

1 task

neersighted mentioned this issue Sep 20, 2022

On install, poetry removes setuptools + pip even if listed in deps - resulting in broken virtualenv #6575

Closed

4 tasks

This was referenced Sep 20, 2022

Update poetry to 1.2.1 ThePalaceProject/circulation#540

Merged

Update poetry to 1.2.1 ThePalaceProject/library-registry#68

Merged

inducer added a commit to inducer/relate that referenced this issue Sep 21, 2022

Upgrade poetry installed in Github Actions to 1.2.1

87dcd98

python-poetry/poetry#4242 (comment)

tomwatson1024 mentioned this issue Sep 22, 2022

Poetry 1.2 lockfiles can't always be installed by Poetry 1.1 #6593

Closed

joaoe mentioned this issue Sep 27, 2022

Installation fails: ModuleNotFoundError: No module named 'setuptools' sdispater/pendulum#619

Open

2 tasks

inducer added a commit to inducer/relate that referenced this issue Sep 29, 2022

Upgrade poetry installed in Github Actions to 1.2.1

4cb6857

python-poetry/poetry#4242 (comment)

cpcloud mentioned this issue Oct 2, 2022

nixpkgs#poetry is broken at nixpkgs-unstable NixOS/nixpkgs#193657

Closed

janbaykara mentioned this issue Nov 8, 2022

Tailwind configuration hotosm/hotosm-website-commonknowledge#32

Merged

4 tasks

UncleGoogle added a commit to UncleGoogle/zope.dottedname that referenced this issue Nov 10, 2022

Remove setuptools dependency

67d3b9d

Looks like this is not needed. This will allow to workaround some problems with build tools like this one python-poetry/poetry#4242

UncleGoogle added a commit to UncleGoogle/zope.dottedname that referenced this issue Nov 10, 2022

Remove setuptools dependency

3a64c1d

Looks like this is not needed. This will allow to workaround some problems with build tools like this one python-poetry/poetry#4242

UncleGoogle mentioned this issue Nov 10, 2022

Remove setuptools dependency zopefoundation/zope.dottedname#9

Closed

UncleGoogle added a commit to UncleGoogle/zope.dottedname that referenced this issue Nov 10, 2022

Remove setuptools dependency

734fedb

Looks like this is not needed. This will allow to workaround some problems with build tools like this one python-poetry/poetry#4242

larsyencken mentioned this issue Nov 22, 2022

Can not execute setup.py since setuptools is not available in the build environment owid/etl#625

Closed

purva-thakre mentioned this issue May 24, 2023

Installation issues vprusso/toqito#150

Closed

github-actions bot locked as resolved and limited conversation to collaborators Feb 29, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Poetry tries to remove setuptools and then complains it can't find it #4242

Poetry tries to remove setuptools and then complains it can't find it #4242

0xallie commented Jul 1, 2021 •

edited

TheElectronWill commented Jul 7, 2021 •

edited

nyanpasu64 commented Jul 13, 2021

dimaqq commented Jul 21, 2021

apollo13 commented Sep 3, 2021

0xallie commented Sep 3, 2021

apollo13 commented Sep 3, 2021

0xallie commented Sep 12, 2021

abn commented Nov 18, 2021

rafalkrupinski commented Dec 25, 2021

rr- commented Jan 17, 2022

realabja commented Mar 31, 2022

danielloader commented Apr 13, 2022

abn commented May 10, 2022

emilhe commented Jul 18, 2022

antonakospanos commented Sep 7, 2022

jomach commented Nov 30, 2022

qkponton commented Feb 23, 2023

qkponton commented Feb 23, 2023

github-actions bot commented Feb 29, 2024

Poetry tries to remove setuptools and then complains it can't find it #4242

Poetry tries to remove setuptools and then complains it can't find it #4242

Comments

0xallie commented Jul 1, 2021 • edited

Issue

TheElectronWill commented Jul 7, 2021 • edited

nyanpasu64 commented Jul 13, 2021

dimaqq commented Jul 21, 2021

apollo13 commented Sep 3, 2021

0xallie commented Sep 3, 2021

apollo13 commented Sep 3, 2021

0xallie commented Sep 12, 2021

abn commented Nov 18, 2021

rafalkrupinski commented Dec 25, 2021

rr- commented Jan 17, 2022

realabja commented Mar 31, 2022

danielloader commented Apr 13, 2022

abn commented May 10, 2022

emilhe commented Jul 18, 2022

antonakospanos commented Sep 7, 2022

jomach commented Nov 30, 2022

qkponton commented Feb 23, 2023

qkponton commented Feb 23, 2023

github-actions bot commented Feb 29, 2024

0xallie commented Jul 1, 2021 •

edited

TheElectronWill commented Jul 7, 2021 •

edited