Solution to issue #133 when building for 32bit and 64bit

[HanslettTheDev]

Summary

This PR solves the issue #133 when installing pillow on 64bit systems After much research, it seems it's not possible to specify the Python version type directly

What we specify in the GH yaml file is not the OS type but rather the python type. So we are running both 32bit and 64bit python versions on a 64bit processor(or GH runner).

runs-on: windows-latest
    strategy:
      fail-fast: false
      matrix:
        python-version: ["3.10"]
        targetplatform: [x86, x64]

    steps:
    - uses: actions/checkout@v2
      with:
        fetch-depth: 0
    - name: Set up Python ${{ matrix.python-version }}
      uses: actions/setup-python@v2
      with:
        python-version: ${{ matrix.python-version }}
        architecture : ${{ matrix.targetplatform }}

Based on their GH action documentation on runners, all runners run on 64bit systems.

A Walkaround is to set the requirements.txt always to use the latest version of Pillow and then change the requirements.txt file before installing the requirements on windows 32bit Python versions so it compiles successfully for 32bit builds while using the latest version for 64bit

- name: Change requirements.txt on 32bit python
      if: matrix.targetplatform == 'x86'
      run: |
        python -c "with open('requirements.txt', 'r') as file: content = file.read(); content = content.replace('Pillow>=2.0.0', 'Pillow<=9.5.0'); f = open('requirements.txt', 'w'); f.write(content)"

MANUAL TEST EVIDENCE

Pillow Installed on 32bit python don't exceed v9.5.0

while Pillow on 64bit use the latest versions

all this while ensuring the normal python 3+ tests are running

Checklist

• [x] Classes, Variables, function and methods logic ok

[HanslettTheDev]

Now here is another problem, still based on the PEP0508 Standards, when we use sys_platform, it internally calls sys.platform. Now even on 64bit computers, the expected result is also "win32". The reason is due to the fact 64bit processors can still run 32bit instructions, and for the sake of backward compatibility on 32bit python, the expected result of sys.platform regardless on whether it is 64bit or 32bit will always be "win32".

I use a 64bit computer, and here is the output below

Shows "win32" though I am running on a 64bit processor. Here is a StackOverflow question which gives insight on the behaviour

SInce you want to avoid anything with touching the requirements,txt, we can use sys.maxsize to determine if the python version runs on 64bit or 32bit