Skip to content

Commit 02bcf97

Browse files
mgornyrgommers
andauthored
Clarify that tools may override ordering/selection
Clarify that tools may override ordering/selection Signed-off-by: Michał Górny <mgorny@quansight.com> Co-authored-by: Ralf Gommers <ralf.gommers@gmail.com>
1 parent 82aa3dd commit 02bcf97

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

peps/pep-0825.rst

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -379,7 +379,8 @@ MUST obtain an ordered list of compatible features, and for every
379379
feature, an ordered list of compatible values. The method of obtaining
380380
these lists will be defined in a subsequent PEP.
381381

382-
The ordering MUST be performed equivalent to the following algorithm:
382+
The default ordering MUST be performed equivalent to the following
383+
algorithm:
383384

384385
1. Construct the ordered list of namespaces by copying the value of the
385386
``default-priorities.namespace`` key from `index-level metadata`_.
@@ -447,6 +448,11 @@ after the null variant. Multiple wheels with the same variant property
447448
set (and multiple non-variant wheels) MUST then be ordered according to
448449
their platform compatibility tags.
449450

451+
The tools MAY provide options to override the default ordering, for
452+
example by specifying a preference for specific namespaces, features
453+
or properties. The tools MAY also provide options to exclude specific
454+
variants, or to select a particular variant.
455+
450456
Alternatively, the sort algorithm for variant wheels could be described
451457
using the following pseudocode. For simplicity, this code does not
452458
account for non-variant wheels or tags.

0 commit comments

Comments
 (0)