You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
The text was updated successfully, but these errors were encountered:
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: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 withsetup.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.
The text was updated successfully, but these errors were encountered: