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
* Use `multi_value=False` for locally-defined properties
Use `multi_value=False` rather than `True` for AoT properties.
As Jonathan pointed out, multi-value properties only make sense
for filtering, given that the system may support only a subset of all
properties. However, AoT properties are always supported, so there
is no real difference between a wheel built with multiple values
for a given property, and one built with just the highest value.
Signed-off-by: Michał Górny <mgorny@quansight.com>
* Use a dedicated AoT plugin for testing
Use a dedicated AoT plugin rather than piggy-backing on a regular
plugin, where independent changes can trigger test failures.
Signed-off-by: Michał Górny <mgorny@quansight.com>
* Make a random test property multi-value for better testing
Signed-off-by: Michał Górny <mgorny@quansight.com>
* Validate that AoT plugins don't return multi-value features
Signed-off-by: Michał Górny <mgorny@quansight.com>
---------
Signed-off-by: Michał Górny <mgorny@quansight.com>
0 commit comments