I was under the impression that the bdist_wheel command would produce appropriately named platform wheels for Python packages (https://packaging.python.org/tutorials/distributing-packages/). I've noticed however that it doesn't behave quite as advertised. Take this sample Python project (and thanks to the creator!):
https://github.com/pypa/sampleproject
I'm using anaconda and Python 3. I create a virtual environment, and then run the bdist_wheel command.
conda create --name sampleproject python=3.6
source activate sampleproject
python setup.py bdist_wheel
The last bit of the output from the setup command is as follows:
Copying sample.egg-info to build/bdist.macosx-10.7-x86_64/wheel/sample-1.2.0-py3.6.egg-info
running install_scripts
creating build/bdist.macosx-10.7-x86_64/wheel/sample-1.2.0.dist-info/WHEEL
But the resulting platform bdist directory is actually empty:
ls -c build/bdist.macosx-10.7-x86_64 | wc -l
0
I've confirmed this behavior with two other real projects. What's the deal here? Is the bdist_wheel command just broken? I've confirmed that the wheel
module is installed:
pip (9.0.1)
setuptools (27.2.0)
wheel (0.29.0)
Is there some other requirement for building platform wheels?