Hi all,

There's some issue with the Windows CI job when it does the python build.
It's a change in behavior somewhere that makes even previously working
releases fail.

It seems related to cmake inducing a pip dependency, but we're really not
sure.

Because even previously working versions fail, IMHO it's hard to treat this
as a blocking issue for future pushes or releases. We'll keep trying to
poke at it, but I don't think it should halt any other work, including
merges or releases.

Feel free to disagree, of course. But in that case please also volunteer to
work on a fix :)

  jon

Reply via email to