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

Please unlock issue about pyproject.toml support #1598

Closed
septatrix opened this issue May 23, 2022 · 0 comments
Closed

Please unlock issue about pyproject.toml support #1598

septatrix opened this issue May 23, 2022 · 0 comments

Comments

@septatrix
Copy link

describe the request

If you close this as a duplicate please unlock #234

Recently a few issues about pyproject.toml support were closed as duplicates though there is no way to continue the discussion on the original issue. The main issue got locked as "too heated" but the stated blockers there no longer apply as far as I can see:

If you want this, I'd suggest lobbying for the following:

  • pip to change its behaviour so mere presence of the file does not change functionality
    • this probably involves a PEP, or at least a discussion on the various pypa mailing lists
  • python to consider adding a standard library toml implementation

the first one is a hard blocker for me accepting this as it imposes technical limitations on users which are outside of the control of this project. For example, consider the frustration due to the exact opposite issue on black

Originally posted by @asottile in #234 (comment)

First of all tomllib is now included in the stdlib as of Python 3.11 or PEP-0680. Regarding the first point about pip: Unless configured otherwise it will use the legacy backend (setuptools.build_meta:__legacy__) to maintain compatibility with setup.py-based build (which for the record are officially declared legacy and have no stability guarantees any longer).

As the landscape has changed in the recent year it is time to again unlock the original issue to continue discussing about the way forward.

@PyCQA PyCQA locked and limited conversation to collaborators May 23, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants