Skip to content

Conversation

@befeleme
Copy link
Contributor

@befeleme befeleme commented Feb 17, 2025

Co-authored-by: 🇺🇦 Sviatoslav Sydorenko (Святослав Сидоренко) <[email protected]>
Copy link
Member

@webknjaz webknjaz left a comment

Choose a reason for hiding this comment

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

Thanks!

@webknjaz webknjaz added this pull request to the merge queue Feb 17, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Feb 17, 2025
@webknjaz webknjaz added this pull request to the merge queue Feb 17, 2025
Merged via the queue into pypa:main with commit 742e281 Feb 17, 2025
7 checks passed
@befeleme befeleme deleted the document-legacy branch February 18, 2025 07:57
Make sure your preferred build backend supports :pep:`639` before
trying to apply the newer guidelines.
As of February 2025, :doc:`setuptools <setuptools:userguide/pyproject_config>`
and :ref:`flit <flit:pyproject_toml_project>` don't support :pep:`639` yet.
Copy link
Contributor

@henryiii henryiii Feb 19, 2025

Choose a reason for hiding this comment

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

Flit now (as of today) supports it in 3.11+ (single license only)

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.

PEP 639 not being supported by all backends yet

3 participants