Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

AttributeError getsitepackages on Appveyor with Python 2.7 32-bit #1946

Closed
andy-maier opened this issue Nov 12, 2019 · 2 comments
Closed

AttributeError getsitepackages on Appveyor with Python 2.7 32-bit #1946

andy-maier opened this issue Nov 12, 2019 · 2 comments
Assignees
@andy-maier
Labels
area: setup resolution: fixed roll back/forward done Roll back or roll forward has been done type: bug
Milestone
1.0.0b1

Comments

@andy-maier
Copy link
Contributor

andy-maier commented Nov 12, 2019 •
edited

On Appveyor with native Windows on Python 2.7 32-bit, we get the following issue since a few days, during make check:

[376] C:\projects\pywbem$ 'C:\ProgramData\chocolatey\bin\make.EXE' check
Traceback (most recent call last):
  File "C:\projects\pywbem\.tox\win64_py27_32\lib\site.py", line 703, in <module>
    main()
  File "C:\projects\pywbem\.tox\win64_py27_32\lib\site.py", line 683, in main
    paths_in_sys = addsitepackages(paths_in_sys)
  File "C:\projects\pywbem\.tox\win64_py27_32\lib\site.py", line 282, in addsitepackages
    addsitedir(sitedir, known_paths)
  File "C:\projects\pywbem\.tox\win64_py27_32\lib\site.py", line 204, in addsitedir
    addpackage(sitedir, name, known_paths)
  File "C:\projects\pywbem\.tox\win64_py27_32\lib\site.py", line 173, in addpackage
    exec(line)
  File "<string>", line 1, in <module>
  File "C:\projects\pywbem\.tox\win64_py27_32\lib\site-packages\win32\lib\pywin32_bootstrap.py", line 14, in <module>
    for maybe in site.getsitepackages():
AttributeError: 'module' object has no attribute 'getsitepackages'
Traceback (most recent call last):
  File "C:\projects\pywbem\.tox\win64_py27_32\lib\site.py", line 703, in <module>
    main()
  File "C:\projects\pywbem\.tox\win64_py27_32\lib\site.py", line 683, in main
    paths_in_sys = addsitepackages(paths_in_sys)
  File "C:\projects\pywbem\.tox\win64_py27_32\lib\site.py", line 282, in addsitepackages
    addsitedir(sitedir, known_paths)
  File "C:\projects\pywbem\.tox\win64_py27_32\lib\site.py", line 204, in addsitedir
    addpackage(sitedir, name, known_paths)
  File "C:\projects\pywbem\.tox\win64_py27_32\lib\site.py", line 173, in addpackage
    exec(line)
  File "<string>", line 1, in <module>
  File "C:\projects\pywbem\.tox\win64_py27_32\lib\site-packages\win32\lib\pywin32_bootstrap.py", line 14, in <module>
    for maybe in site.getsitepackages():
AttributeError: 'module' object has no attribute 'getsitepackages'
Traceback (most recent call last):
  File "C:\projects\pywbem\.tox\win64_py27_32\lib\site.py", line 703, in <module>
    main()
  File "C:\projects\pywbem\.tox\win64_py27_32\lib\site.py", line 683, in main
    paths_in_sys = addsitepackages(paths_in_sys)
  File "C:\projects\pywbem\.tox\win64_py27_32\lib\site.py", line 282, in addsitepackages
    addsitedir(sitedir, known_paths)
  File "C:\projects\pywbem\.tox\win64_py27_32\lib\site.py", line 204, in addsitedir
    addpackage(sitedir, name, known_paths)
  File "C:\projects\pywbem\.tox\win64_py27_32\lib\site.py", line 173, in addpackage
    exec(line)
  File "<string>", line 1, in <module>
  File "C:\projects\pywbem\.tox\win64_py27_32\lib\site-packages\win32\lib\pywin32_bootstrap.py", line 14, in <module>
    for maybe in site.getsitepackages():
AttributeError: 'module' object has no attribute 'getsitepackages'
Traceback (most recent call last):
  File "C:\projects\pywbem\.tox\win64_py27_32\lib\site.py", line 703, in <module>
    main()
  File "C:\projects\pywbem\.tox\win64_py27_32\lib\site.py", line 683, in main
    paths_in_sys = addsitepackages(paths_in_sys)
  File "C:\projects\pywbem\.tox\win64_py27_32\lib\site.py", line 282, in addsitepackages
    addsitedir(sitedir, known_paths)
  File "C:\projects\pywbem\.tox\win64_py27_32\lib\site.py", line 204, in addsitedir
    addpackage(sitedir, name, known_paths)
  File "C:\projects\pywbem\.tox\win64_py27_32\lib\site.py", line 173, in addpackage
    exec(line)
  File "<string>", line 1, in <module>
  File "C:\projects\pywbem\.tox\win64_py27_32\lib\site-packages\win32\lib\pywin32_bootstrap.py", line 14, in <module>
    for maybe in site.getsitepackages():
AttributeError: 'module' object has no attribute 'getsitepackages'
del /f /q pip_upgrade_py.done
Could Not Find C:\projects\pywbem\pip_upgrade_py.done
python -m pip install --upgrade pip
Traceback (most recent call last):
  File "C:\projects\pywbem\.tox\win64_py27_32\lib\site.py", line 703, in <module>
    main()
  File "C:\projects\pywbem\.tox\win64_py27_32\lib\site.py", line 683, in main
    paths_in_sys = addsitepackages(paths_in_sys)
  File "C:\projects\pywbem\.tox\win64_py27_32\lib\site.py", line 282, in addsitepackages
    addsitedir(sitedir, known_paths)
  File "C:\projects\pywbem\.tox\win64_py27_32\lib\site.py", line 204, in addsitedir
    addpackage(sitedir, name, known_paths)
  File "C:\projects\pywbem\.tox\win64_py27_32\lib\site.py", line 173, in addpackage
    exec(line)
  File "<string>", line 1, in <module>
  File "C:\projects\pywbem\.tox\win64_py27_32\lib\site-packages\win32\lib\pywin32_bootstrap.py", line 14, in <module>
    for maybe in site.getsitepackages():
AttributeError: 'module' object has no attribute 'getsitepackages'
make: *** [makefile:383: pip_upgrade_py.done] Error 1
@andy-maier andy-maier added this to the 1.0.0 milestone Nov 12, 2019
@andy-maier andy-maier added investigation needed roll back needed Roll back into latest fix branch is needed labels Nov 12, 2019
@andy-maier
Copy link
Contributor Author

andy-maier commented Nov 12, 2019 •
edited

The same issue has been reported to the pywin32 project: mhammond/pywin32#1439.
A workaround seems to be to pin the pywin32 package to version 225.

andy-maier added a commit that referenced this issue Nov 12, 2019
@andy-maier
Workaround for pywin32 issue on Appveyor python 2.7 32-bit
1c55171 
Details:
- Represented the dependency to the pywin32 package for Windows in
  minimum-constraints.txt and dev-requirements.txt. It is used
  (at least) by jupyter.
- Added pinning to version 225 as a workaround for pywbem issue #1946.

Signed-off-by: Andreas Maier <andreas.r.maier@gmx.de>
@andy-maier
Copy link
Contributor Author

andy-maier commented Nov 12, 2019 •
edited

A workaround of pinning the version of pywbem32 to 225 has been provided in PR #1947 for master and PR #1948 for 0.15.0. The pinning workaround is marked with a TODO, so we can consider this issue here done.

@andy-maier andy-maier self-assigned this Nov 12, 2019
andy-maier added a commit that referenced this issue Nov 12, 2019
@andy-maier
Workaround for pywin32 issue on Appveyor python 2.7 32-bit
daf1018 
Details:

- Represented the dependency to the pywin32 package for Windows in
  minimum-constraints.txt and dev-requirements.txt. It is used
  (at least) by jupyter.

- Added pinning to version 225 as a workaround for pywbem issue #1946.

Signed-off-by: Andreas Maier <andreas.r.maier@gmx.de>
andy-maier added a commit that referenced this issue Nov 13, 2019
@andy-maier
Workaround for pywin32 issue on Appveyor python 2.7 32-bit
d735a46 
Details:

- Represented the dependency to the pywin32 package for Windows in
  minimum-constraints.txt and dev-requirements.txt. It is used
  (at least) by jupyter.

- Added pinning to version 225 as a workaround for pywbem issue #1946.

Signed-off-by: Andreas Maier <andreas.r.maier@gmx.de>
andy-maier added a commit that referenced this issue Nov 13, 2019
@andy-maier
Workaround for pywin32 issue on Appveyor python 2.7 32-bit
124b648 
Details:

- Represented the dependency to the pywin32 package for Windows in
  minimum-constraints.txt and dev-requirements.txt. It is used
  (at least) by jupyter.

- Added pinning to version 225 as a workaround for pywbem issue #1946.

Signed-off-by: Andreas Maier <andreas.r.maier@gmx.de>
@andy-maier andy-maier added area: setup resolution: fixed roll back/forward done Roll back or roll forward has been done type: bug and removed resolution: partly fixed roll back needed Roll back into latest fix branch is needed labels Nov 13, 2019
andy-maier added a commit that referenced this issue Nov 13, 2019
@andy-maier
Workaround for pywin32 issue on Appveyor python 2.7 32-bit
47b5abf 
Details:

- Represented the dependency to the pywin32 package for Windows in
  minimum-constraints.txt and dev-requirements.txt. It is used
  (at least) by jupyter.

- Added pinning to version 225 as a workaround for pywbem issue #1946.

Signed-off-by: Andreas Maier <andreas.r.maier@gmx.de>
andy-maier added a commit that referenced this issue Nov 13, 2019
@andy-maier
Workaround for pywin32 issue on Appveyor python 2.7 32-bit
8692ac6 
Details:

- Represented the dependency to the pywin32 package for Windows in
  minimum-constraints.txt and dev-requirements.txt. It is used
  (at least) by jupyter.

- Added pinning to version 225 as a workaround for pywbem issue #1946.

Signed-off-by: Andreas Maier <andreas.r.maier@gmx.de>
This was referenced Nov 13, 2019
Merged
Merged
@andy-maier andy-maier mentioned this issue Nov 28, 2019
Closed
andy-maier added a commit that referenced this issue Nov 29, 2019
@andy-maier
Fixed version issues with pywin32 on native Windows
8356b5b 
Details:

- The simple minded version requirement 'pywin32>=222,<225' introduced in PR #1947
  fails on Python 3.7 64-bit with PACKAGE_LEVEL=minimum, and on Python 3.8,
  because version 222 is not provided for these Python versions. This fix makes
  the minimum version dependent on the Python version.

- An additional issue for Python 3.8 support of pywin32 is the fact that pywin32
  starting with version 225 provides wheel files on Pypi, but does not advertise
  Python 3.8 support. This confuses pip such that it is able to install to
  Python 3.8 with a constraint pywin32>=225, but not with pywin32==225.
  To accomodate this, our minimum-constraints.txt file now specifies pywin32>=225.

- Meanwhile, pywin32 fixed the issue that lead to pinning it to '<225'
  (see pywbem issue #1946) in its version 227. Therefore, this change turns the
  pinning into a permanent fix by just excluding version 226.

Signed-off-by: Andreas Maier <andreas.r.maier@gmx.de>
andy-maier added a commit that referenced this issue Nov 29, 2019
@andy-maier
Fixed version issues with pywin32 on native Windows
4db990b 
Details:

- The simple minded version requirement 'pywin32>=222,<225' introduced in PR #1947
  fails on Python 3.7 64-bit with PACKAGE_LEVEL=minimum, and on Python 3.8,
  because version 222 is not provided for these Python versions. This fix makes
  the minimum version dependent on the Python version.

- An additional issue for Python 3.8 support of pywin32 is the fact that pywin32
  starting with version 225 provides wheel files on Pypi, but does not advertise
  Python 3.8 support. This confuses pip such that it does not find a matching
  distribution as soon as there is any specification of pywin32 in the minimum
  constraints file (neither pywin32==225 nor pywin32>=225 works). Pip does
  find it when there is pywin>=225 in the requirements file, and no specification
  in the constraints file.
  To accomodate this, our minimum-constraints.txt file now omits a statement for
  pywin32 in case of py38.

- Meanwhile, pywin32 fixed the issue that lead to pinning it to '<225'
  (see pywbem issue #1946) in its version 227. Therefore, this change turns the
  pinning into a permanent fix by just excluding version 226.

Signed-off-by: Andreas Maier <andreas.r.maier@gmx.de>
andy-maier added a commit that referenced this issue Nov 29, 2019
@andy-maier
Fixed version issues with pywin32 on native Windows
077cc9c 
Details:

- The simple minded version requirement 'pywin32>=222,<225' introduced in PR #1947
  fails on Python 3.7 64-bit with PACKAGE_LEVEL=minimum, and on Python 3.8,
  because version 222 is not provided for these Python versions. This fix makes
  the minimum version dependent on the Python version.

- An additional issue for Python 3.8 support of pywin32 is the fact that pywin32
  starting with version 225 provides wheel files on Pypi, but does not advertise
  Python 3.8 support. This confuses pip such that it does not find a matching
  distribution as soon as there is any specification of pywin32 in the minimum
  constraints file (neither pywin32==225 nor pywin32>=225 works). Pip does
  find it when there is pywin>=225 in the requirements file, and no specification
  in the constraints file.
  To accomodate this, our minimum-constraints.txt file now omits a statement for
  pywin32 in case of py38.

- Meanwhile, pywin32 fixed the issue that lead to pinning it to '<225'
  (see pywbem issue #1946) in its version 227. Therefore, this change turns the
  pinning into a permanent fix by just excluding version 226.

Signed-off-by: Andreas Maier <andreas.r.maier@gmx.de>
andy-maier added a commit that referenced this issue Nov 29, 2019
@andy-maier
Fixed version issues with pywin32 on native Windows
e2ba34b 
Details:

- The simple minded version requirement 'pywin32>=222,<225' introduced in PR #1947
  fails on Python 3.7 64-bit with PACKAGE_LEVEL=minimum, and on Python 3.8,
  because version 222 is not provided for these Python versions. This fix makes
  the minimum version dependent on the Python version.

- An additional issue for Python 3.8 support of pywin32 is the fact that pywin32
  starting with version 225 provides wheel files on Pypi, but does not advertise
  Python 3.8 support. This confuses pip such that it does not find a matching
  distribution as soon as there is any specification of pywin32 in the minimum
  constraints file or in the requirements file.
  To accomodate this, our minimum-constraints.txt and dev-requirements.txt files
  now omit a statement for pywin32 in case of py38, causing the latest version
  227 to be installed on py38, for both minimum and latest package levels.

- Meanwhile, pywin32 fixed the issue that lead to pinning it to '<225'
  (see pywbem issue #1946) in its version 227. Therefore, this change turns the
  pinning into a permanent fix by just excluding version 226.

Signed-off-by: Andreas Maier <andreas.r.maier@gmx.de>
andy-maier added a commit that referenced this issue Nov 29, 2019
@andy-maier
Fixed version issues with pywin32 on native Windows
ddd936c 
Details:

- The simple minded version requirement 'pywin32>=222,<225' introduced in PR #1947
  fails on Python 3.7 64-bit with PACKAGE_LEVEL=minimum, and on Python 3.8,
  because version 222 is not provided for these Python versions. This fix makes
  the minimum version dependent on the Python version.

- An additional issue for Python 3.8 support of pywin32 is the fact that pywin32
  starting with version 225 provides wheel files on Pypi, but does not advertise
  Python 3.8 support. This confuses pip such that it does not find a matching
  distribution as soon as there is any specification of pywin32 in the minimum
  constraints file or in the requirements file.
  To accomodate this, our minimum-constraints.txt and dev-requirements.txt files
  now omit a statement for pywin32 in case of py38, causing the latest version
  227 to be installed on py38, for both minimum and latest package levels.

- Meanwhile, pywin32 fixed the issue that lead to pinning it to '<225'
  (see pywbem issue #1946) in its version 227. Therefore, this change turns the
  pinning into a permanent fix by just excluding version 226.

Signed-off-by: Andreas Maier <andreas.r.maier@gmx.de>
andy-maier added a commit that referenced this issue Nov 29, 2019
@andy-maier
Fixed version issues with pywin32 on native Windows
7a0b985 
Details:

- The simple minded version requirement 'pywin32>=222,<225' introduced in PR #1947
  fails on Python 3.7 64-bit with PACKAGE_LEVEL=minimum, and on Python 3.8,
  because version 222 is not provided for these Python versions. This fix makes
  the minimum version dependent on the Python version.

- An additional issue for Python 3.8 support of pywin32 is the fact that pywin32
  starting with version 225 provides wheel files on Pypi, but does not advertise
  Python 3.8 support. This confuses pip such that it does not find a matching
  distribution as soon as there is any specification of pywin32 in the minimum
  constraints file or in the requirements file.
  To accomodate this, our minimum-constraints.txt and dev-requirements.txt files
  now omit a statement for pywin32 in case of py38, causing the latest version
  227 to be installed on py38, for both minimum and latest package levels.

- Meanwhile, pywin32 fixed the issue that lead to pinning it to '<225'
  (see pywbem issue #1946) in its version 227. Therefore, this change turns the
  pinning into a permanent fix by just excluding version 226.

Signed-off-by: Andreas Maier <andreas.r.maier@gmx.de>
andy-maier added a commit that referenced this issue Nov 29, 2019
@andy-maier
Fixed version issues with pywin32 on native Windows
df159dc 
Details:

- The simple minded version requirement 'pywin32>=222,<225' introduced in PR #1947
  fails on Python 3.7 64-bit with PACKAGE_LEVEL=minimum, and on Python 3.8,
  because version 222 is not provided for these Python versions. This fix makes
  the minimum version dependent on the Python version.

- An additional issue for Python 3.8 support of pywin32 is the fact that pywin32
  starting with version 225 provides wheel files on Pypi, but does not advertise
  Python 3.8 support. This confuses pip such that it does not find a matching
  distribution as soon as there is any specification of pywin32 in the minimum
  constraints file or in the requirements file.
  To accomodate this, our minimum-constraints.txt and dev-requirements.txt files
  now omit a statement for pywin32 in case of py38, causing the latest version
  227 to be installed on py38, for both minimum and latest package levels.

- Meanwhile, pywin32 fixed the issue that lead to pinning it to '<225'
  (see pywbem issue #1946) in its version 227. Therefore, this change turns the
  pinning into a permanent fix by just excluding version 226.

Signed-off-by: Andreas Maier <andreas.r.maier@gmx.de>
andy-maier added a commit that referenced this issue Nov 29, 2019
@andy-maier
Fixed version issues with pywin32 on native Windows
e376aa5 
Details:

- The simple minded version requirement 'pywin32>=222,<225' introduced in PR #1947
  fails on Python 3.7 64-bit with PACKAGE_LEVEL=minimum, and on Python 3.8,
  because version 222 is not provided for these Python versions. This fix makes
  the minimum version dependent on the Python version.

- An additional issue for Python 3.8 support of pywin32 is the fact that pywin32
  starting with version 225 provides wheel files on Pypi, but does not advertise
  Python 3.8 support. This confuses pip such that it does not find a matching
  distribution as soon as there is any specification of pywin32 in the minimum
  constraints file or in the requirements file.
  To accomodate this, our minimum-constraints.txt and dev-requirements.txt files
  now omit a statement for pywin32 in case of py38, causing the latest version
  227 to be installed on py38, for both minimum and latest package levels.

- Meanwhile, pywin32 fixed the issue that lead to pinning it to '<225'
  (see pywbem issue #1946) in its version 227. Therefore, this change turns the
  pinning into a permanent fix by just excluding version 226.

Signed-off-by: Andreas Maier <andreas.r.maier@gmx.de>
andy-maier added a commit that referenced this issue Nov 29, 2019
@andy-maier
Fixed version issues with pywin32 on native Windows
c9c48a4 
Details:

- The simple minded version requirement 'pywin32>=222,<225' introduced in PR #1947
  fails on Python 3.7 64-bit with PACKAGE_LEVEL=minimum, and on Python 3.8,
  because version 222 is not provided for these Python versions. This fix makes
  the minimum version dependent on the Python version.

- An additional issue for Python 3.8 support of pywin32 is the fact that pywin32
  starting with version 225 provides wheel files on Pypi, but does not advertise
  Python 3.8 support. This confuses pip such that it does not find a matching
  distribution as soon as there is any specification of pywin32 in the minimum
  constraints file or in the requirements file.
  To accomodate this, our minimum-constraints.txt and dev-requirements.txt files
  now omit a statement for pywin32 in case of py38, causing the latest version
  227 to be installed on py38, for both minimum and latest package levels.

- Meanwhile, pywin32 fixed the issue that lead to pinning it to '<225'
  (see pywbem issue #1946) in its version 227. Therefore, this change turns the
  pinning into a permanent fix by just excluding version 226.

Signed-off-by: Andreas Maier <andreas.r.maier@gmx.de>
andy-maier added a commit that referenced this issue Nov 29, 2019
@andy-maier
Fixed version issues with pywin32 on native Windows
ea941ed 
Details:

- The simple minded version requirement 'pywin32>=222,<225' introduced in PR #1947
  fails on Python 3.7 64-bit with PACKAGE_LEVEL=minimum, and on Python 3.8,
  because version 222 is not provided for these Python versions. This fix makes
  the minimum version dependent on the Python version.

- An additional issue for Python 3.8 support of pywin32 is the fact that pywin32
  starting with version 225 provides wheel files on Pypi, but does not advertise
  Python 3.8 support. This confuses pip such that it does not find a matching
  distribution as soon as there is any specification of pywin32 in the minimum
  constraints file or in the requirements file.
  To accomodate this, our minimum-constraints.txt and dev-requirements.txt files
  now omit a statement for pywin32 in case of py38, causing the latest version
  227 to be installed on py38, for both minimum and latest package levels.

- Meanwhile, pywin32 fixed the issue that lead to pinning it to '<225'
  (see pywbem issue #1946) in its version 227. Therefore, this change turns the
  pinning into a permanent fix by just excluding version 226.

Signed-off-by: Andreas Maier <andreas.r.maier@gmx.de>
andy-maier added a commit that referenced this issue Nov 29, 2019
@andy-maier
Fixed version issues with pywin32 on native Windows
b8db27f 
Details:

- The simple minded version requirement 'pywin32>=222,<225' introduced in PR #1947
  fails on Python 3.7 64-bit with PACKAGE_LEVEL=minimum, and on Python 3.8,
  because version 222 is not provided for these Python versions. This fix makes
  the minimum version dependent on the Python version.

- An additional issue for Python 3.8 support of pywin32 is the fact that pywin32
  starting with version 225 provides wheel files on Pypi, but does not advertise
  Python 3.8 support. This confuses pip such that it does not find a matching
  distribution as soon as there is any specification of pywin32 in the minimum
  constraints file or in the requirements file.
  To accomodate this, our minimum-constraints.txt and dev-requirements.txt files
  now omit a statement for pywin32 in case of py38, causing the latest version
  227 to be installed on py38, for both minimum and latest package levels.

- Meanwhile, pywin32 fixed the issue that lead to pinning it to '<225'
  (see pywbem issue #1946) in its version 227. Therefore, this change turns the
  pinning into a permanent fix by just excluding version 226.

Signed-off-by: Andreas Maier <andreas.r.maier@gmx.de>
andy-maier added a commit that referenced this issue Nov 29, 2019
@andy-maier
Fixed version issues with pywin32 on native Windows
43829c7 
Details:

- The simple minded version requirement 'pywin32>=222,<225' introduced in PR #1947
  fails on Python 3.7 64-bit with PACKAGE_LEVEL=minimum, and on Python 3.8,
  because version 222 is not provided for these Python versions. This fix makes
  the minimum version dependent on the Python version.

- An additional issue for Python 3.8 support of pywin32 is the fact that pywin32
  starting with version 225 provides wheel files on Pypi, but does not advertise
  Python 3.8 support. This confuses pip such that it does not find a matching
  distribution as soon as there is any specification of pywin32 in the minimum
  constraints file or in the requirements file.
  To accomodate this, our minimum-constraints.txt and dev-requirements.txt files
  now omit a statement for pywin32 in case of py38, causing the latest version
  227 to be installed on py38, for both minimum and latest package levels.

- Meanwhile, pywin32 fixed the issue that lead to pinning it to '<225'
  (see pywbem issue #1946) in its version 227. Therefore, this change turns the
  pinning into a permanent fix by just excluding version 226.

Signed-off-by: Andreas Maier <andreas.r.maier@gmx.de>
andy-maier added a commit that referenced this issue Nov 29, 2019
@andy-maier
Fixed version issues with pywin32 on native Windows
1ef1317 
Details:

- The simple minded version requirement 'pywin32>=222,<225' introduced in PR #1947
  fails on Python 3.7 64-bit with PACKAGE_LEVEL=minimum, and on Python 3.8,
  because version 222 is not provided for these Python versions. This fix makes
  the minimum version dependent on the Python version.

- An additional issue for Python 3.8 support of pywin32 is the fact that pywin32
  starting with version 225 provides wheel files on Pypi, but does not advertise
  Python 3.8 support. This confuses pip such that it does not find a matching
  distribution as soon as there is any specification of pywin32 in the minimum
  constraints file or in the requirements file.
  To accomodate this, our minimum-constraints.txt and dev-requirements.txt files
  now omit a statement for pywin32 in case of py38, causing the latest version
  227 to be installed on py38, for both minimum and latest package levels.

- Meanwhile, pywin32 fixed the issue that lead to pinning it to '<225'
  (see pywbem issue #1946) in its version 227. Therefore, this change turns the
  pinning into a permanent fix by just excluding version 226.

Signed-off-by: Andreas Maier <andreas.r.maier@gmx.de>
andy-maier added a commit that referenced this issue Nov 30, 2019
@andy-maier
Fixed version issues with pywin32 on native Windows
41f37de 
Details:

- The simple minded version requirement 'pywin32>=222,<225' introduced in PR #1947
  fails on Python 3.7 64-bit with PACKAGE_LEVEL=minimum, and on Python 3.8,
  because version 222 is not provided for these Python versions. This fix makes
  the minimum version dependent on the Python version.

- An additional issue for Python 3.8 support of pywin32 is the fact that pywin32
  starting with version 225 provides wheel files on Pypi, but does not advertise
  Python 3.8 support. This confuses pip such that it does not find a matching
  distribution as soon as there is any specification of pywin32 in the minimum
  constraints file or in the requirements file.
  To accomodate this, our minimum-constraints.txt and dev-requirements.txt files
  now omit a statement for pywin32 in case of py38, causing the latest version
  227 to be installed on py38, for both minimum and latest package levels.

- Meanwhile, pywin32 fixed the issue that lead to pinning it to '<225'
  (see pywbem issue #1946) in its version 227. Therefore, this change turns the
  pinning into a permanent fix by just excluding version 226.

Signed-off-by: Andreas Maier <andreas.r.maier@gmx.de>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@andy-maier andy-maier

Labels
area: setup resolution: fixed roll back/forward done Roll back or roll forward has been done type: bug
Projects
None yet
Milestone
1.0.0b1
Development

No branches or pull requests
1 participant
@andy-maier