The new functionality introduced in #368 to deploy wheels did not introduce the right naming convention for wheels - PyPi for example will decline packages not naming according to the PIP491.
This PR restricts the assemble_pip to only produce py3 type archives, which can then be deployed with the required naming convention.
What are the changes implemented in this PR?
Restrict assemble_pip to only allow Python-3 compatibility
deploy_pip produces wheels that conform to {name}-{version}-{pyversion}-{abi}-{platform} by hardcoding it to {name}-{version}-py3-none-any
What is the goal of this PR?
The new functionality introduced in #368 to deploy wheels did not introduce the right naming convention for wheels - PyPi for example will decline packages not naming according to the PIP491.
This PR restricts the
assemble_pip
to only producepy3
type archives, which can then be deployed with the required naming convention.What are the changes implemented in this PR?
assemble_pip
to only allow Python-3 compatibilitydeploy_pip
produces wheels that conform to{name}-{version}-{pyversion}-{abi}-{platform}
by hardcoding it to{name}-{version}-py3-none-any