Skip to content

Commit 0059f93

Browse files
authored
Merge pull request #12534 from konstin/remove-outdated-metadata-2-0-comments
Update outdated comment referring to Metadata 2.0
2 parents b647ed5 + 220123a commit 0059f93

File tree

2 files changed

+4
-6
lines changed

2 files changed

+4
-6
lines changed

news/12533.trivial.rst

Whitespace-only changes.

src/pip/_internal/operations/install/wheel.py

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -288,17 +288,15 @@ def get_console_script_specs(console: Dict[str, str]) -> List[str]:
288288
# the wheel metadata at build time, and so if the wheel is installed with
289289
# a *different* version of Python the entry points will be wrong. The
290290
# correct fix for this is to enhance the metadata to be able to describe
291-
# such versioned entry points, but that won't happen till Metadata 2.0 is
292-
# available.
293-
# In the meantime, projects using versioned entry points will either have
291+
# such versioned entry points.
292+
# Currently, projects using versioned entry points will either have
294293
# incorrect versioned entry points, or they will not be able to distribute
295294
# "universal" wheels (i.e., they will need a wheel per Python version).
296295
#
297296
# Because setuptools and pip are bundled with _ensurepip and virtualenv,
298-
# we need to use universal wheels. So, as a stopgap until Metadata 2.0, we
297+
# we need to use universal wheels. As a workaround, we
299298
# override the versioned entry points in the wheel and generate the
300-
# correct ones. This code is purely a short-term measure until Metadata 2.0
301-
# is available.
299+
# correct ones.
302300
#
303301
# To add the level of hack in this section of code, in order to support
304302
# ensurepip this code will look for an ``ENSUREPIP_OPTIONS`` environment

0 commit comments

Comments
 (0)