1.0.10 -> 1.1 regression: EnvCommandError: 'No module named setuptools' on Python 3.7 #3153
Comments
gitpushdashf
added
kind/bug
|
@gitpushdashf looks like this is an issue with the version of Another possibility is, if you are using an Ubuntu distro, the distutils version installed might be interfering with your install. |
|
Thanks for replying! This is using the python:3.7 and python3.8 Docker images which I believe are Debian based. With that image should I be doing |
|
@gitpushdashf fwiw; I cannot reproduce this in a container, any chance you can provide some steps to reproduce this? Typically the containers should have $ podman run --rm -i --entrypoint bash python:3.7 -c 'pip --version'
pip 20.2.3 from /usr/local/lib/python3.7/site-packages/pip (python 3.7) |
|
Also this indicates you are using the old I would recommend you try moving to the standalone build backend. |
|
I am also getting this error and I can reproduce it. https://github.com/jonapich/test-poetry-setuptools Clone that repo, and try "poetry install" in the test-functools folder, you will get the same stacktrace as in the bug report. This seems pretty serious 🤔 I'm on 1.1.3, Windows, using powershell. I installed using the get-poetry bootstrap. I have confirmed that this bug appears when going from 1.0.10 -> 1.1 and it was also working in 1.0.9 Also, I never used python 3.7; only 3.6 and 3.8. |
|
I can confirm this is a problem and affects anything that ultimately still depends on calling
I can confirm the problem with Python 3.6, 3.7 and 3.8 alike. And this is really hard to debug because even if you literally copy and paste the command it's trying to run, it just works, in my case for a sample package: But if I simply copy and paste the command below, it runs ok: To make this "work" I had to install bogus from setuptools import setup
setup(name="packb")Yet it still fails when running from within poetry. |
|
@jonapich based on your description I have attempted to recreate the scenario (minus the windows environment). Let me know what needs to be changed to reproduce the issue. podman run --rm -i --entrypoint bash python:3.8 <<EOF
set -ex
curl -sSL https://raw.githubusercontent.com/python-poetry/poetry/master/get-poetry.py | python - --version 1.0.10
source ~/.poetry/env
poetry --version
git clone https://github.com/jonapich/test-poetry-setuptools.git
pushd test-poetry-setuptools/test-functools/
poetry lock
poetry install
poetry self update
poetry install
rm -rf \$(poetry env info -p)
poetry --version
poetry install
rm -rf \$(poetry env info -p)
git checkout poetry.lock
poetry install
EOFConsole Output
+ curl -sSL https://raw.githubusercontent.com/python-poetry/poetry/master/get-poetry.py
+ python - --version 1.0.10
Retrieving Poetry metadata
# Welcome to Poetry!
This will download and install the latest version of Poetry,
a dependency and package manager for Python.
It will add the `poetry` command to Poetry's bin directory, located at:
$HOME/.poetry/bin
This path will then be added to your `PATH` environment variable by
modifying the profile file located at:
$HOME/.profile
You can uninstall at any time by executing this script with the --uninstall option,
and these changes will be reverted.
Installing version: 1.0.10
- Downloading poetry-1.0.10-linux.tar.gz (29.66MB)
Poetry (1.0.10) is installed now. Great!
To get started you need Poetry's bin directory ($HOME/.poetry/bin) in your `PATH`
environment variable. Next time you log in this will be done
automatically.
To configure your current shell run `source $HOME/.poetry/env`
+ source /root/.poetry/env
++ export PATH=/root/.poetry/bin:/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
++ PATH=/root/.poetry/bin:/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
+ poetry --version
Poetry version 1.0.10
+ git clone https://github.com/jonapich/test-poetry-setuptools.git
Cloning into 'test-poetry-setuptools'...
+ pushd test-poetry-setuptools/test-functools/
/test-poetry-setuptools/test-functools /
+ poetry lock
Creating virtualenv test-functools-HE92XDqH-py3.8 in /root/.cache/pypoetry/virtualenvs
The lock file might not be compatible with the current version of Poetry.
Upgrade Poetry to ensure the lock file is read properly or, alternatively, regenerate the lock file with the `poetry lock` command.
Updating dependencies
Resolving dependencies...
Writing lock file
+ poetry install
Installing dependencies from lock file
Package operations: 15 installs, 0 updates, 0 removals
- Installing pyparsing (2.4.7)
- Installing six (1.15.0)
- Installing attrs (20.2.0)
- Installing iniconfig (1.1.1)
- Installing packaging (20.4)
- Installing pluggy (0.13.1)
- Installing py (1.9.0)
- Installing toml (0.10.1)
- Installing mypy-extensions (0.4.3)
- Installing pytest (6.1.1)
- Installing typed-ast (1.4.1)
- Installing typing-extensions (3.7.4.3)
- Installing inflection (0.5.1)
- Installing mypy (0.790)
- Installing test-testing (0.1.4 ../test-testing)
- Installing test-functools (0.1.4)
+ poetry self update
Updating to 1.1.3
- Downloading poetry-1.1.3-linux.tar.gz 0%
- Downloading poetry-1.1.3-linux.tar.gz 10%
- Downloading poetry-1.1.3-linux.tar.gz 20%
- Downloading poetry-1.1.3-linux.tar.gz 30%
- Downloading poetry-1.1.3-linux.tar.gz 40%
- Downloading poetry-1.1.3-linux.tar.gz 50%
- Downloading poetry-1.1.3-linux.tar.gz 60%
- Downloading poetry-1.1.3-linux.tar.gz 70%
- Downloading poetry-1.1.3-linux.tar.gz 80%
- Downloading poetry-1.1.3-linux.tar.gz 90%
- Downloading poetry-1.1.3-linux.tar.gz 100%
Poetry (1.1.3) is installed now. Great!
+ poetry install
Installing dependencies from lock file
No dependencies to install or update
Installing the current project: test-functools (0.1.4)
++ poetry env info -p
+ rm -rf /root/.cache/pypoetry/virtualenvs/test-functools-HE92XDqH-py3.8
+ poetry --version
Poetry version 1.1.3
+ poetry install
Creating virtualenv test-functools-HE92XDqH-py3.8 in /root/.cache/pypoetry/virtualenvs
Installing dependencies from lock file
Package operations: 15 installs, 0 updates, 0 removals
• Installing pyparsing (2.4.7)
• Installing six (1.15.0)
• Installing attrs (20.2.0)
• Installing iniconfig (1.1.1)
• Installing packaging (20.4)
• Installing pluggy (0.13.1)
• Installing py (1.9.0)
• Installing toml (0.10.1)
• Installing mypy-extensions (0.4.3)
• Installing pytest (6.1.1)
• Installing typed-ast (1.4.1)
• Installing typing-extensions (3.7.4.3)
• Installing inflection (0.5.1)
• Installing mypy (0.790)
• Installing test-testing (0.1.4 /test-poetry-setuptools/test-testing)
Installing the current project: test-functools (0.1.4)
++ poetry env info -p
+ rm -rf /root/.cache/pypoetry/virtualenvs/test-functools-HE92XDqH-py3.8
+ git checkout poetry.lock
+ poetry install
Creating virtualenv test-functools-HE92XDqH-py3.8 in /root/.cache/pypoetry/virtualenvs
Installing dependencies from lock file
Package operations: 15 installs, 0 updates, 0 removals
• Installing pyparsing (2.4.7)
• Installing six (1.15.0)
• Installing attrs (20.2.0)
• Installing iniconfig (1.1.1)
• Installing packaging (20.4)
• Installing pluggy (0.13.1)
• Installing py (1.9.0)
• Installing toml (0.10.1)
• Installing mypy-extensions (0.4.3)
• Installing pytest (6.1.1)
• Installing typed-ast (1.4.1)
• Installing typing-extensions (3.7.4.3)
• Installing inflection (0.5.1)
• Installing mypy (0.790)
• Installing test-testing (0.1.4 /test-poetry-setuptools/test-testing)
Installing the current project: test-functools (0.1.4) |
|
I was able to make it work on a clean windows 2019 server as well... 🤔 But you need py3.8 or below, because there's no wheels for typed_ast in 3.9 and you'll need to install the vs c++ build tools. I'll have to investigate what's different on my system. |
|
So far, I can still reproduce the issue when going through poetry, but not when going through pip. My issue matches the OP's behavior: Console Output
|
|
I went through the trouble of removing everything python and poetry off my system. I then reinstalled py3.8 using the latest installer and then reinstalled poetry using the Invoke-Webrequest method from the docs. The behavior is still the same. Some observations:
This is where poetry breaks it for me even though python/pip can handle it:
Additional note: The dependencies in |
|
I wasn't able to find the cause of the problem. After a fresh install of Windows 10, I am no longer experiencing the issue and I can install the test repo that I created for this issue. |
|
Did something change between 1.1.3 and 1.1.4 that may have fixed this? Python 3.7 Docker container: |
|
The repo reproduced the issue on my system only. Then I had to reformat for a non related reason, and I could not reproduce the issue anymore. Sorry I cannot be of any more help. This issue is resolved as far as I'm concerned. Is your original issue still happening? Did you try to repo in a container or VM? |
|
I can't reproduce this now. I'll close it out unless someone else runs into it on 1.1.4. |
|
@gitpushdashf Would you mind reopening this issue - I'm seeing this on 1.1.4 (and 1.1.3). Here's a minimal project where I'm able to reproduce the $ poetry install
Creating virtualenv reproduce-issue-QXZ_ZScA-py3.7 in /Users/kristofferb/Library/Caches/pypoetry/virtualenvs
Installing dependencies from lock file
Installing the current project: reproduce-issue (0.1.0)
$ poetry env info
Virtualenv
Python: 3.7.6
Implementation: CPython
Path: /Users/kristofferb/Library/Caches/pypoetry/virtualenvs/reproduce-issue-QXZ_ZScA-py3.7
Valid: True
System
Platform: darwin
OS: posix
Python: /Users/kristofferb/.pyenv/versions/3.7.6
$ poetry run pip install -e .
Obtaining file:///Users/kristofferb/Code/temp/gist-reproduce-3153
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing wheel metadata ... done
Installing collected packages: reproduce-issue
Attempting uninstall: reproduce-issue
Found existing installation: reproduce-issue 0.1.0
Uninstalling reproduce-issue-0.1.0:
Successfully uninstalled reproduce-issue-0.1.0
Running setup.py develop for reproduce-issue
ERROR: Command errored out with exit status 1:
command: /Users/kristofferb/Library/Caches/pypoetry/virtualenvs/reproduce-issue-QXZ_ZScA-py3.7/bin/python -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/Users/kristofferb/Code/temp/gist-reproduce-3153/setup.py'"'"'; __file__='"'"'/Users/kristofferb/Code/temp/gist-reproduce-3153/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' develop --no-deps
cwd: /Users/kristofferb/Code/temp/gist-reproduce-3153/
Complete output (3 lines):
Traceback (most recent call last):
File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'setuptools'
----------------------------------------
Rolling back uninstall of reproduce-issue
Moving to /Users/kristofferb/Library/Caches/pypoetry/virtualenvs/reproduce-issue-QXZ_ZScA-py3.7/lib/python3.7/site-packages/reproduce_issue-0.1.0.dist-info/
from /Users/kristofferb/Library/Caches/pypoetry/virtualenvs/reproduce-issue-QXZ_ZScA-py3.7/lib/python3.7/site-packages/~eproduce_issue-0.1.0.dist-info
Moving to /Users/kristofferb/Library/Caches/pypoetry/virtualenvs/reproduce-issue-QXZ_ZScA-py3.7/lib/python3.7/site-packages/reproduce_issue.pth
from /private/var/folders/3j/l__gnf4n6t73fpcg8nk3tqhc0000gn/T/pip-uninstall-cz50uscc/reproduce_issue.pth
ERROR: Command errored out with exit status 1: /Users/kristofferb/Library/Caches/pypoetry/virtualenvs/reproduce-issue-QXZ_ZScA-py3.7/bin/python -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/Users/kristofferb/Code/temp/gist-reproduce-3153/setup.py'"'"'; __file__='"'"'/Users/kristofferb/Code/temp/gist-reproduce-3153/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' develop --no-deps Check the logs for full command output.
$ poetry --version
Poetry version 1.1.4I'm on MacOS 10.15.7 fwiw. |
|
I don't understand completely what's going on here. But the root cause seems to be, that So the problem is not, that So at it stands now, it looks to me a |
|
In #1135 (comment) @NeilGirdhar pointed out that one would need to change pyproject.toml to include setuptools: [build-system]
-requires = ["poetry_core>=1.0"]
+requires = ["setuptools", "poetry_core>=1.0"]
build-backend = "poetry.core.masonry.api"With this added in my above example (reproduce-3153.zip) it now builds: poetry run pip install -e .
Obtaining file:///Users/kristofferb/Code/temp/gist-reproduce-3153
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing wheel metadata ... done
Installing collected packages: reproduce-issue
Attempting uninstall: reproduce-issue
Found existing installation: reproduce-issue 0.1.0
Uninstalling reproduce-issue-0.1.0:
Successfully uninstalled reproduce-issue-0.1.0
Running setup.py develop for reproduce-issue
Successfully installed reproduce-issueAnd indeed, as others have mentioned in #34, this is not a |
abey79
added a commit
to abey79/vpype
that referenced
this issue
Nov 14, 2020
|
When I had black as a dependency I also had to add setuptools-scm and wheel manually because they had that in their build requires.
|
1 task
Yes, a poetry workaround would be perfect. I can also reproduce this error in the setting of #2015 (comment). I got that it is caused by build isolation but I am afraid that keeping things to the minimal will end up having a lot of boilerplate text in pyproject.toml. |
2 tasks
|
Hi, if I understood the status of this issue correctly, a workaround (for the obscure setuptools problem, which will not go away until poetry no longer uses setuptools) is on main, but not released yet, and for a package which is built by poetry, but which has a setup.py (for example, setup.py which is used to install the sdist), one can workaround until the next release, by adding as suggested by @kbakk. Is this correct? |
jwg4
added a commit
to jwg4/exact_cover
that referenced
this issue
Jan 12, 2021
nyanpasu64
added a commit
to corrscope/corrscope
that referenced
this issue
Jul 14, 2021
corrscope uses poetry, while pip expects a setuptools project and will create package name UNKNOWN if run without setup.py or pyproject.toml [build-system]. This adds an up-to-date pyproject.toml [build-system] tag. "setuptools" is required to make `pip install .` work, due to python-poetry/poetry#3153 (comment) Right now, `pip install [--editable] .` and `pipx install .` work, but `pipx install --editable .` fails with message "No apps associated with package UNKNOWN or its dependencies." I'm not aware of how to fix this.
|
For me it seems like the issue went away once I removed |
|
i am also getting same issue even with this setup |
|
same issue, wrapt depends on it, diff --git a/poetry.lock b/poetry.lock
index c8f8357..f858bfe 100644
--- a/poetry.lock
+++ b/poetry.lock
@@ -868,18 +868,6 @@ botocore = ">=1.12.36,<2.0a.0"
[package.extras]
crt = ["botocore[crt] (>=1.20.29,<2.0a.0)"]
-[[package]]
-name = "setuptools"
-version = "57.4.0"
-description = "Easily download, build, install, upgrade, and uninstall Python packages"
-category = "main"
-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"]
-
[[package]]
name = "six"
version = "1.16.0"
@@ -1555,10 +1543,6 @@ s3transfer = [
{file = "s3transfer-0.5.0-py3-none-any.whl", hash = "sha256:9c1dc369814391a6bda20ebbf4b70a0f34630592c9aa520856bf384916af2803"},
{file = "s3transfer-0.5.0.tar.gz", hash = "sha256:50ed823e1dc5868ad40c8dc92072f757aa0e653a192845c94a3b676f4a62da4c"},
]
-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.16.0-py2.py3-none-any.whl", hash = "sha256:8abb2f1d86890a2dfb989f9a77cfcfd3e47c2a354b01111771326f8aa26e0254"},
{file = "six-1.16.0.tar.gz", hash = "sha256:1e61c37477a1626458e36f7b1d82aa5c9b094fa4802892072e49de9c60c4c926"}, |
|
@jtzero yes after removing |
|
I ran into this issue with Poetry 1.2.0a2 as it adds |
|
Deleting |
|
I get the exact same error when building a docker image based on |
|
@generalpiston can you please provide a bit more information on the error please?
If at build time the package requires As to why |
3 tasks
|
@abn see below. poetry 1.1.11. ReproductionDockerfile: pyproject.toml:
|
|
@generalpiston looks like I can only reproduce it if the lock file was generated with a I believe the issue here is that since Try either regenerating the lock file using |
|
@abn good point. Apparently I have |
|
I'm going to close this issue as poetry no longer depends on using the venv provided setuptools not pip. And the only case this seems to be triggered is when lock file was generated with a pre-release version and installed using an older release. |
abn
removed
kind/bug
3 tasks
apjanco
added a commit
to HCDigitalScholarship/intervals
that referenced
this issue
Jan 3, 2022
srevinsaju
added a commit
to srevinsaju/pyuploadtool
that referenced
this issue
Jan 16, 2022
pyuploadtool now generates changelog for GitHub releases which is opt-in. Changelogs will be generated only when GENERATE_CHANGELOG=true feat: prepend the metadata.description with the generated changelog fix: rename get_changelog to render_to_markdown its a more intuitive function name and clearly explains that the output is a string of markdown data fix: do not replace the existing metadata description, but append to it feat: expose get_changelog this function can in be future be replaced by a a changelog handling object feat: add support for restrictive conventional commit spec fix: remove redundant comment style: add more blank lines feat: restructure changelog generator style: format with black fix: circular imports on changelog docs: update documentation to show CHANGELOG support refactor: complete refactor from Parser to ChangelogParser fix: refactor to use attributes for Commit object instead of dict.get fix: for github releases, set the commit_prefix_link style: lint with black style: move ReleaseUpdate below .. imports (pep8) fix: convert Changelog.structure to staticmethod feat: use NamedTuple instead of complicating the implementation style: remove redundant _ prefixes to local variables style: remove redundant line feat: do not edit metadata in the release provider fix: docstrings for Changelog.changelog, Changelog.structure fix: use type annotations instead of type in docstrings refactor: ChangelogCommit to ChangelogEntry to make it more general fix: allow providing lowercase values for CHANGELOG_TYPE env variable feat: remove the need to specify CHANGELOG_GENERATE environment variable. Automatically generate changelog if CHANGELOG_TYPE is defined to 'standard' or 'conventional' docs: improve docstrings of MarkdownChangelogParser.render_to_markdown docs: improve docstrings of Changelog.structure Add support for scheduled and manual builds Print non-string types properly Improve logging Convert metadata to correct types Fix comparison (and show intention more clearly) Check code format with black Run checks on PRs as well Use poetry to manage dependencies in CI Debug dependencies installatino Forgot to check out the code Format YAML properly Add incomplete list of projects using pyuploadtool Pin poetry version Workaround for python-poetry/poetry#3153. Fix type issue When calling sanitize on an int, e.g., the pipeline run number, it might fail as the passed type is not iterable. This little fix makes sure whatever is passed is interpreted as a string. fix: remove redundant imports fix: do not attempt to generate changelog if the previous tag is missing fix: changelog.structure is not a property fix: ChangelogEntry should not be a tuple, because it needs to be edited runtime
srevinsaju
added a commit
to srevinsaju/pyuploadtool
that referenced
this issue
Jan 16, 2022
pyuploadtool now generates changelog for GitHub releases which is opt-in. Changelogs will be generated only when GENERATE_CHANGELOG=true feat: prepend the metadata.description with the generated changelog fix: rename get_changelog to render_to_markdown its a more intuitive function name and clearly explains that the output is a string of markdown data fix: do not replace the existing metadata description, but append to it feat: expose get_changelog this function can in be future be replaced by a a changelog handling object feat: add support for restrictive conventional commit spec fix: remove redundant comment style: add more blank lines feat: restructure changelog generator style: format with black fix: circular imports on changelog docs: update documentation to show CHANGELOG support refactor: complete refactor from Parser to ChangelogParser fix: refactor to use attributes for Commit object instead of dict.get fix: for github releases, set the commit_prefix_link style: lint with black style: move ReleaseUpdate below .. imports (pep8) fix: convert Changelog.structure to staticmethod feat: use NamedTuple instead of complicating the implementation style: remove redundant _ prefixes to local variables style: remove redundant line feat: do not edit metadata in the release provider fix: docstrings for Changelog.changelog, Changelog.structure fix: use type annotations instead of type in docstrings refactor: ChangelogCommit to ChangelogEntry to make it more general fix: allow providing lowercase values for CHANGELOG_TYPE env variable feat: remove the need to specify CHANGELOG_GENERATE environment variable. Automatically generate changelog if CHANGELOG_TYPE is defined to 'standard' or 'conventional' docs: improve docstrings of MarkdownChangelogParser.render_to_markdown docs: improve docstrings of Changelog.structure Add support for scheduled and manual builds Print non-string types properly Improve logging Convert metadata to correct types Fix comparison (and show intention more clearly) Check code format with black Run checks on PRs as well Use poetry to manage dependencies in CI Debug dependencies installatino Forgot to check out the code Format YAML properly Add incomplete list of projects using pyuploadtool Pin poetry version Workaround for python-poetry/poetry#3153. Fix type issue When calling sanitize on an int, e.g., the pipeline run number, it might fail as the passed type is not iterable. This little fix makes sure whatever is passed is interpreted as a string. fix: remove redundant imports fix: do not attempt to generate changelog if the previous tag is missing fix: changelog.structure is not a property fix: ChangelogEntry should not be a tuple, because it needs to be edited runtime
|
It worked for me by upgrading setuptools and pip to the latest versions |
|
This still happens on a fresh install of Poetry (1.1.13) with Python 3.10.2 (on Arch Linux, at least). I tried to follow the Adding Update: Actually the problem may be with |
TheAssassin
pushed a commit
to TheAssassin/pyuploadtool
that referenced
this issue
Jun 14, 2022
pyuploadtool now generates changelog for GitHub releases which is opt-in. Changelogs will be generated only when GENERATE_CHANGELOG=true feat: prepend the metadata.description with the generated changelog fix: rename get_changelog to render_to_markdown its a more intuitive function name and clearly explains that the output is a string of markdown data fix: do not replace the existing metadata description, but append to it feat: expose get_changelog this function can in be future be replaced by a a changelog handling object feat: add support for restrictive conventional commit spec fix: remove redundant comment style: add more blank lines feat: restructure changelog generator style: format with black fix: circular imports on changelog docs: update documentation to show CHANGELOG support refactor: complete refactor from Parser to ChangelogParser fix: refactor to use attributes for Commit object instead of dict.get fix: for github releases, set the commit_prefix_link style: lint with black style: move ReleaseUpdate below .. imports (pep8) fix: convert Changelog.structure to staticmethod feat: use NamedTuple instead of complicating the implementation style: remove redundant _ prefixes to local variables style: remove redundant line feat: do not edit metadata in the release provider fix: docstrings for Changelog.changelog, Changelog.structure fix: use type annotations instead of type in docstrings refactor: ChangelogCommit to ChangelogEntry to make it more general fix: allow providing lowercase values for CHANGELOG_TYPE env variable feat: remove the need to specify CHANGELOG_GENERATE environment variable. Automatically generate changelog if CHANGELOG_TYPE is defined to 'standard' or 'conventional' docs: improve docstrings of MarkdownChangelogParser.render_to_markdown docs: improve docstrings of Changelog.structure Add support for scheduled and manual builds Print non-string types properly Improve logging Convert metadata to correct types Fix comparison (and show intention more clearly) Check code format with black Run checks on PRs as well Use poetry to manage dependencies in CI Debug dependencies installatino Forgot to check out the code Format YAML properly Add incomplete list of projects using pyuploadtool Pin poetry version Workaround for python-poetry/poetry#3153. Fix type issue When calling sanitize on an int, e.g., the pipeline run number, it might fail as the passed type is not iterable. This little fix makes sure whatever is passed is interpreted as a string. fix: remove redundant imports fix: do not attempt to generate changelog if the previous tag is missing fix: changelog.structure is not a property fix: ChangelogEntry should not be a tuple, because it needs to be edited runtime
7 tasks
1 task
|
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This may because it's installing a nested package. Python 3.8 doesn't have this issue but 3.7 does. I don't have a reduced test case yet. I'm hoping the traceback is helpful and someone knows what's going on from it. Python 3.7 and 3.8 are fine with Poetry 1.0.10, everything else being identical. Python 3.8 with Poetry 1.1.2 is fine as well, just not Python 3.7 with Poetry 1.1.2.
The text was updated successfully, but these errors were encountered: