Skip to content
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 v2 #4338

Open
VDuchauffour opened this issue Jan 8, 2025 · 2 comments
Open

Poetry v2 #4338

VDuchauffour opened this issue Jan 8, 2025 · 2 comments

Comments

@VDuchauffour
Copy link

Description of the JSON schema.

Since the release of Poetry v2, the schema of [tool.poetry] has been deprecated in favor of the standard [project] metadata definitions in the pyproject.toml file.

In a project that has been migrated to this new major, I get the following false positive errors (using the Even Better TOML VSCode extensions:

"name" is a required propertyEven Better TOML
"version" is a required propertyEven Better TOML
"description" is a required propertyEven Better TOML
"authors" is a required propertyEven Better TOML

I suppose the scheme needs updating? Thanks

Supporting information.

https://python-poetry.org/blog/announcing-poetry-2.0.0

Are you making a PR for this?

No, someone else must create the PR.

@ChenZhouUC
Copy link

The same here. I am looking for this, too.

@henryiii
Copy link
Contributor

henryiii commented Jan 9, 2025

It is valid (and required) to set tool.poetry.version to use poetry dynamic versioning with the new config in v2.

I think these simply need to be made non-required properties now?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants