-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
poetry 1.1.14 RunTimeError - Poetry configuration is invalid #6143
Comments
Could the problem be |
This might be slightly off topic, but I bumped into this while checking some config settings. Something is misbehaving in config management. For example, in my dev-laptop, there seems to be an obsolete config value that I cannot remove, i.e.
The config file looks like this, from [settings]
[settings.virtualenvs]
in-project = false
[virtualenvs]
in-project = false After a manual edit to remove the block for |
Explicitly setting some additional config values did not solve the problem 😞
|
The error message tells you exactly which key it is not happy with. If you are unable / unwilling to share your pyproject.toml, I doubt that there's much more that anyone can do for you.
|
I can share the [tool.poetry.extras]
all = [
"contextily",
"descartes",
"dask-snowflake",
"distributed",
"streamz",
"geopy",
"pyepsg",
"pygeos",
"bokeh",
"folium",
"graphviz",
"ipyparallel",
"jupyterlab",
"matplotlib",
"seaborn",
"GeoAlchemy2",
"SQLAlchemy",
"pg8000",
"psycopg2-binary",
"snowflake-connector-python",
"pyarrow",
"netcdf4",
"scipy",
"xarray",
"zarr",
# redis-queue support
"arq",
"rq",
"rqmonitor",
"prefect",
"fastapi",
"strawberry-graphql",
"mangum",
"hypercorn",
"watchgod",
] The comment for |
Probably, similar to #6133 and #6135 and fixed by python-poetry/tomlkit#221 with the latest tomlkit version. |
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. |
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: docker image
python:3.7
Poetry version: 1.1.14
Link of a Gist with the contents of your pyproject.toml file: sorry, this is private
Issue
From the stack trace, I cannot tell whether there is a problem with the poetry install and config file or a problem with a pyproject.toml file, but the latter is unlikely since there are no changes to it and it has been working with all previous releases of poetry (and
poetry check
andpoetry build
are working OK).This is a log from a gitlab-CI job, which is a repeatable failure (not a one-off). Nothing has changed in the
.gitlab-ci.yml
settings for some time, only the poetry version or a pip version might be new. The gitlab CI pipelines have worked last week with poetry 1.1.14 and pip 22.2.1, so this failure is difficult to understand and replicate.The text was updated successfully, but these errors were encountered: