grpc: [setuptools] [distutils] Python builds failed on master
https://source.cloud.google.com/results/invocations/baba7e4f-6421-4b0c-8cb7-b106b252191d/log
It started failing yesterday, when setuptools releases 50.0.0. It’s highly likely that their latest build broke us.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 17 (15 by maintainers)
~I don’t think pinning back
setuptoolsis sufficient. Right now, if someone on Debian or Ubuntu doespip install grpcio, it won’t work.~Just tested the
debian:latestDocker image withsetuptools50.0.0. It worked with no modifications. A Debian user would have to explicitly update their setuptools to hit this problem, so I agree that pinning back in CI should be sufficient for now. If we receive any user issues about this, we can just recommend theSETUPTOOLS_USE_DISTUTILSenvironment variable.It’s worth mentioning the PR removing wrap-memory hack. This would be helpful to stay with setuptool 50 in future. Note that it sill has another problem with Windows Python,
TypeError: _commandfile_spawn() got an unexpected keyword argument 'env'. (test)Interesting. Whatever changed in
setuptools, it’s causing the__wrap_memcpyhack to fail: