Latest poetry-core with poetry 1.0 caused pip error during tox building #3001
Comments
fredrikaverpil
added
kind/bug
|
@fredrikaverpil I believe the issue is the system default Maybe #2826 will also remove this issue for externally ( |
|
Also, this should not work unless your environment somehow already has [build-system]
requires = ["poetry-core"]
build-backend = "poetry.masonry.api" |
|
Oops, I meant to write: Changing our build system to the following solved the problem: |
|
The funny thing is this happened over night without a change in tox.ini or pyproject.toml. Ok, I will see which version of pip is in the system-Python. |
The funny thing about that, is that a colleague of mine showed me this today with exact the same words 😄 We simply update poetry to the freshly released 1.1 and the problem vanished. |
|
I am seeing this as well (not in tox, but standard poetry install), less than 1 day since the last success built, strange thing is: we have always fixed the poetry version to 1.0.5, but once updated to the latest 1.1.0, it works fine. |
|
seeing this as well, workaround is to add setuptools to requires: This way, you can still use poetry 1.1.0 |
|
@fredrikaverpil I am unable to reproduce this in a clean environment, $ podman run --rm -i --entrypoint bash python:3.7 <<EOF
> pip install --quiet --upgrade pip
> pip install --quiet poetry tox
> pushd /opt
> poetry new foobar
> pushd foobar
> cat > tox.ini <<TOXEOF
> [tox]
> minversion = 3.3.0
> isolated_build = True
> envlist = py37
>
> [testenv]
> commands =
> pip list
> TOXEOF
> cat pyproject.toml
> tox -e py37
> EOF
/opt /
Created package foobar in foobar
/opt/foobar /opt /
[tool.poetry]
name = "foobar"
version = "0.1.0"
description = ""
authors = ["Your Name <you@example.com>"]
[tool.poetry.dependencies]
python = "^3.7"
[tool.poetry.dev-dependencies]
pytest = "^5.2"
[build-system]
requires = ["poetry-core>=1.0.0"]
build-backend = "poetry.core.masonry.api"
.package create: /opt/foobar/.tox/.package
.package installdeps: poetry-core>=1.0.0
py37 create: /opt/foobar/.tox/py37
py37 inst: /opt/foobar/.tox/.tmp/package/1/foobar-0.1.0.tar.gz
py37 installed: foobar @ file:///opt/foobar/.tox/.tmp/package/1/foobar-0.1.0.tar.gz
py37 run-test-pre: PYTHONHASHSEED='2706476223'
py37 run-test: commands[0] | pip list
Package Version
---------- -------
foobar 0.1.0
pip 20.2.3
setuptools 50.3.0
wheel 0.35.1
___________________________________ summary ____________________________________
py37: commands succeeded
congratulations :) |
|
@fredrikaverpil these issues may be of relevance for you pypa/setuptools#2353 pypa/setuptools#2376 pypa/pip#6264. |
|
Hm, a lot of people complaining about setuptools 50.0, but it all worked itself out fine on my end by using the following: [build-system]
requires = ["poetry==1.0.10"]
build-backend = "poetry.masonry.api"Does the above not make use of setuptools? |
|
@abn Those tickets are from a month ago, but I saw this issue start happening specifically within the last week in a GitHub Actions workflow, without any code changes in between.
It occurs only in certain combinations. Python (3.7 | 3.8) + Poetry (1.0.2 | 1.0.5) fail, whereas the same Poetry versions work with Python (3.5 | 3.6), and Poetry (1.0.10 | 1.1.0rc1) work with all four versions of Python tested. It doesn't matter whether Poetry is installed with |
|
I'm seeing the missing Setuptools error in environments created with Conda. |
I'm not entirely sure what's causing the error. It seems to be related either to setuptools or to poetry, or maybe both. Thus, this is more or less a brute force fix. I've found the it here: python-poetry/poetry#3001
I'm not entirely sure what's causing the error. It seems to be related either to setuptools or to poetry, or maybe both. Thus, this is more or less a brute force fix. I've found the it here: python-poetry/poetry#3001
Installing the local directory from other projects using `pip` fails: ```sh $ cd chws_tools $ pip install ../east_asian_spacing ... ModuleNotFoundError: No module named 'setuptools' ``` This change can work around the problem as described at: python-poetry/poetry#3001
|
Doesn't reproduce with any modern versions -- please open a new issue if you think you're hitting this. |
neersighted
added
status/needs-reproduction
|
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. |
-vvvoption).Issue
We use tox (with
isolated_build=true) with poetry 1.0.10 and the build system in pyproject.toml looked like this:Jenkins log, from executing the tox testenv:
Changing our build system to the following solved the problem:
The text was updated successfully, but these errors were encountered: