Closed ahmadiesa-abu closed 2 years ago
all in all the best idea is probably to just drop the 5.1-compat hack, because passing in the --supported-platform
correctly means that plugins that need to be 5.1-compatible, can just be built with the override passed in
this wont work because in the simple case of platform =
manylinux_2_5_x86_64
(which is a pep600 alias formanylinux1_x86_64
), the platform here ends up beinglinux_2_5_x86_64
, which isn't valid (linux_x86_64
is)
I have added another snippet that handles these extreme cases
all in all the best idea is probably to just drop the 5.1-compat hack, because passing in the
--supported-platform
correctly means that plugins that need to be 5.1-compatible, can just be built with the override passed in
I agree , that is why we fixed the create function to pass in supported-platform
, but we also need to be able to handle it , if the user doesn't pass it also
this PR address platform issue in case of new manylinux wheel naming convention [pep600 concatenate]