You are probably a perfect customer for supports_environment
On Thu, Jan 30, 2014 at 1:40 PM, Ronald Oussoren <ronaldousso...@mac.com> wrote: > > On 30 Jan 2014, at 19:36, Daniel Holth <dho...@gmail.com> wrote: > >> On Thu, Jan 30, 2014 at 1:29 PM, Ronald Oussoren <ronaldousso...@mac.com> >> wrote: >>> >>> On 30 Jan 2014, at 19:19, Daniel Holth <dho...@gmail.com> wrote: >>> >>>> Your best bet currently is to execute the "mv" command to change the >>>> filename of the wheel. >>>> >>>> I think bdist_wheel should probably accept a setup() argument to set >>>> the tags. Currently you can just set a "universal" flag which means >>>> pure 2+3 python. >>> >>> There's also --plat-name argument for the setuptools command, but that >>> doesn't work. >>> >>> I'd have to rename the platform tag from "any" to a list of supported >>> platforms, is that correct? >>> >>> That would give a pretty convoluted filename, because the platform tag >>> doesn't allow for wildcards. That is, there is no way to specify "any >>> linux", only something like "linux_x86_64" (to borrow a tag from PEP 425). >> >> My position has been that if there is no alternative that works on a >> different platform, then at least the wheel metadata should say >> nothing. It's only there to allow the installer to pick among the best >> of several alternatives. > > The py2app setup.py file currently hardcodes a platform check because users > did install py2app on other platforms (mostly Windows) and then complained > that it didn't work. It is much nicer to tell the user that a package won't > work during installation. > > Ronald _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
