Skip to content

feat: Change depencendies.poetry to optional.#4434

Closed
ya7010 wants to merge 1 commit into
SchemaStore:masterfrom
ya7010:update_poetry
Closed

feat: Change depencendies.poetry to optional.#4434
ya7010 wants to merge 1 commit into
SchemaStore:masterfrom
ya7010:update_poetry

Conversation

@ya7010
Copy link
Copy Markdown
Contributor

@ya7010 ya7010 commented Feb 11, 2025

In poetry v2, the python version is now specified in project.requires-python,

so tool.poetry.dependencies.python is no longer required.

@github-actions
Copy link
Copy Markdown
Contributor

Thanks for the PR!

This section of the codebase is owned by @madskristensen and @hyperupcall - if they write a comment saying "LGTM" then it will be merged.

@hyperupcall
Copy link
Copy Markdown
Member

Thanks! Looks like a dupe of #4413 - I'll be merging that one since it was first and keeps the python key for backwards compatibility

}
},
"patternProperties": {
"^(?!python$)[a-zA-Z-_.0-9]+$": {
Copy link
Copy Markdown
Member

@hyperupcall hyperupcall Feb 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you think this change should be a separate PR? I wouldn't be surprised if this fixes validation errors when a person wants to specify a non-cpython version of Python. But I'm just speculating

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it is required.

With python no longer required, it is simpler to write.

And another problem is that some libraries do not support lookahead regular expressions, so this fix is more desirable.

Create another PR.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see, thank you for the info

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Successfully merging this pull request may close these issues.

2 participants