You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Another good reason is that some python lib devs are no longer building win32 wheels, so when we bump the python version we will start seeing issues with some libraries having to be compiled.
For instance pyscard stopped shipping win32 wheels starting with v2.0.1, which is a problem because v2.0.0 did not ship a python3.9 wheel for MacOS and v2.0.1 no longer ships a python 3.8 wheel for MacOS, so bumping python to 3.9 for binaries is going to be tricky (dependency on swig to compile pyscard) if we don't support 64-bit windows soon.
The text was updated successfully, but these errors were encountered:
… env var
Partial backport of spesmilo@f1f584c
related to #259 but does not address it entirely: the win64 build still fails due to an OpenSSL compilation error
Test Plan:
```
WIN_ARCH=win32 GIT_REPO=`pwd` contrib/build-wine/build.sh HEAD
WIN_ARCH=win64 GIT_REPO=`pwd` contrib/build-wine/build.sh HEAD
```
See spesmilo#6598 for one good reason.
Another good reason is that some python lib devs are no longer building win32 wheels, so when we bump the python version we will start seeing issues with some libraries having to be compiled.
For instance
pyscard
stopped shipping win32 wheels starting with v2.0.1, which is a problem because v2.0.0 did not ship a python3.9 wheel for MacOS and v2.0.1 no longer ships a python 3.8 wheel for MacOS, so bumping python to 3.9 for binaries is going to be tricky (dependency onswig
to compile pyscard) if we don't support 64-bit windows soon.The text was updated successfully, but these errors were encountered: