Consider adding support for more wheel tags.

[arnavb]

• I have searched the issues of this repo and believe that this is not a duplicate. (tangentially related to Incorrect wheel tag for platform-dependent packages on PyPy #1820)
• I have searched the documentation and believe that my question is not covered.

Context: https://stackoverflow.com/q/60243191/6525260

For the package I'm currently developing, I'm considering switching to Poetry from setuptools. This package minimally supports Python 3.6, and I'd like to specify that in the wheel name. Currently, despite the python dependency in pyproject.toml being Python 3.6, the generated wheel still has a py3-none-any.whl tag. I want there to be a py36-none-any.whl tag instead. With setuptools, I would have specified this using

[bdist_wheel]
python-tag = py36

in setup.cfg. There doesn't seem to be an equivalent for Poetry. Is it possible that a config option could be added to support this use case?

Edit:

It seems that this should be generalized to other tags as well. Poetry lacks support for platform specific tags and feature support in that regard would be useful.

Perhaps there should be a simple string config option where you can manually specify what the tags should be?

[filmor]

Overriding platform tags would also be useful. Currently, if any build.py script is used, poetry just assumes the most specific tags, in all other cases just py3-none-any.

[Kaiser1989]

Having the same problem, as we want to distribute already built binaries via poetry. Therefore we need to set these tags manually.
This is what I we came up with to workaround:

pyproject.toml

...
[tool.poetry.build]
script = "build.py"
...

build.py

import setuptools, os

def build(setup_kwargs):
    # Run targeted build separately as poetry does not support target builds yet
    try:
        setuptools.setup(
            **setup_kwargs, 
            script_args = ['bdist_wheel'],
            options = { 
                'bdist_wheel': { 'plat_name': os.getenv('PP_PYTHON_TARGET', 'any') },
                'egg_info': { 'egg_base': './build/' }
            }
        )
    except:
        print("Failed to create targeted wheel")

This will trigger an additional wheel build with given target (here we check for environment variable), leadings to 2 different wheels in dist folder, where one was created by poetry with host information and one created by this build script.