Fix package build failure when the compiler types not defined (Fixes #20428)#20429
Fix package build failure when the compiler types not defined (Fixes #20428)#20429ilevkivskyi merged 2 commits intopython:masterfrom
Conversation
|
I will sync this to librt (and make a new release) tomorrow, unless @hauntsaninja you want to try doing the |
|
Would be open to trying over the weekend! |
|
@hauntsaninja Great! I just sent you an invite to mypyc org. Please follow instructions in README in https://github.com/mypyc/librt. If you are not sure about anything, please ask either here or on Discord, I will be around for most of the weekend. |
|
@hauntsaninja Are you still interested in doing this? |
|
Yes! I only got the GitHub invite, not the PyPi invite — meant to ask you about it |
|
You don't need any PyPI permissions for this, PyPI publishing is done using trusted publishing. |
|
Okay great! 0.7.5 is released with this change. Was very straightforward :-) |
|
Thank you both - I just tried installing it and it's working great again! |
This fixes the install issue #20428 by adding a default value when a compiler type is not defined. While this fix is specifically for z/OS, it should also fix other platforms that have their compiler_type changed in distutils/setuptools such as mingw32.
I tested this with installing the librt package. I've added no testcases as there's no new functionality.