Closed ssbarnea closed 2 years ago
We've gotten burned enough trying to support Homebrew detection by default, only to break a bunch of other stuff in the process (or when homebrew changes something) that I'm kinda over that. The PyYAML setup code (most of which is over 20 years old!) has to get rewritten against modern setuptools pretty soon, since Cython 3.0 will irrecoverably break it. At that point, I'll also simplify and document the mechanisms to override build config for people that want to run the build themselves and bring their own libyaml (I don't really want to treat homebrew "specially" here, since it used to be Macports, and tomorrow it could be ?).
Meantime, the 3.11 wheels are up, so the original pressing need that triggered the ask should also be solved. :laughing:
@nitzmahone A really big thanks for doing this! MacOS and pyyaml are both very important so we cannot really afford to ignore them. I will try to find some time after the summit to give hand with setuptools refactoring to modernize it, even if I do not have a lot of experience with cython stuff. I wonder if @webknjaz may be able to give us a hand here as I know he more experience compiling cython libs, maybe he already did this kind of upgrade for other library.
PS. Homebrew was a source of issues many years ago, but become much more stable these days. I think that last time I seen macports being used was like... a decade ago?
As
libyaml
is included with brew, the command below it should succeed in compiling it with libyaml and installing it:As we can see there was a failure to locate
yaml.h
, but I am looking locally and I can see it as being present in standard locations:Solution
In order to prevent the build failure, user must define:
In order to avoid this manual step, we should automatically defined these if they are not already present.