yaml
Setting `SETUPTOOLS_USE_DISTUTILS` in `setup.py`?
Currently setup.py is setting SETUPTOOLS_USE_DISTUTILS environment variable. See snippet below:
https://github.com/yaml/pyyaml/blob/8cdff2c80573b8be8e8ad28929264a913a63aa33/setup.py#L69-L70
This has been causing us some issues when packaging PyYAML. Am curious if some other solution could be used here like...
- Could it be dropped?
- Could it check whether the environment variable is already set?
- ...?
You didn't specify what the actual issue was, and it wasn't clear from a quick scan of the linked issue...
It definitely can't be dropped entirely at the moment, since the stdlib distutils is going away and pyyaml setup is still relying on a bunch of ancient custom distutils bits for (among other things) the silent pure-Python fallback build when the extension build fails. Other folks have complained loudly about the deprecation warnings that fire when we don't set it (allowing setuptools to import stdlib distutils), and IIRC there are a couple of important bugfixes in the embedded one as well.
We could probably make it conditional on the envvar not being set, but I'd like to understand what the actual issue is before embarking down that path.
(it sounds like something to do with the universal2 compile/link flags dumpster fire, which we just punted on entirely in favor of arm64-only Mac builds because it was such a PITA)
Sorry for being unclear.
IIUC the option isn't available for older Python versions. IOW we build for Python 3.7 & 3.8 and it doesn't work until 3.9.
Here's the relevant issue ( https://github.com/conda-forge/pyyaml-feedstock/issues/38 ) and PR ( https://github.com/conda-forge/pyyaml-feedstock/issues/38 ) where we have needed to patch it out.
cc @erykoff (in case you have more thoughts here)
The problem is that the option is available for older pythons, but it is broken if you have any overrides of system default compiler flags (which we do for conda forge, particularly when cross compiling). This particular problem was fixed in python 3.9 but apparently not backported. (see https://github.com/pypa/setuptools/issues/2257 ).
Ah, so you're monkeypatching the stdlib distutils and setuptools is using it's embedded copy?
I don't believe so, though I don't know exactly how cross-python works. But in general, we just have compiler flags set that are ignored when that env variable is set to local.
cc @chrisburr (who may be able to shed more light on how cross compiling is being done here)