Henry Schreiner
Henry Schreiner
Thanks for the tips! I regularly use Xcode, and haven't had a problem with the `EXCLUDE_FROM_ALL` on `add_subdirectory`; on macOS, it's pretty easy (and necessary) to keep a modern CMake...
I was just looking for this. :'(
> not every NumPy minor version increment introduces a binary incompatibility I think you mean patch, not minor. The NumPy team test `oldest-supported-numpy` against each patch release. Binary release automatically...
Also, on the `numpy
Nice! Looks like there's hope for this yet: https://github.blog/changelog/2022-01-25-github-actions-reusable-workflows-can-be-referenced-locally/
This would probably not work with yesqa, though.
This is broken with flake8 v5. Anthony will try to kill any attempt to support pyproject.toml, so best not to make this fragile.
FYI, ```bash brew install openblas OPENBLAS="$(brew --prefix openblas)" cibuildwheel ... ``` was listed as a solution. The "best" solution would be for NumPy to provide macOS PyPy wheels. Though, of...
You do very much need the CMakeLists.txt & LICENSE for the SDist, those are part of the source. I thought `include_package_data` would only include things inside packages, but I know...
Yeah, `include_package_data` is basically useless and breaks things. The correct thing to do is to explicitly list `package_data`. Most other backends are smart enough to to know automatic package data...