Bump pywin32 from 304 to 306

[dependabot]

Bumps pywin32 from 304 to 306.

Release notes

Sourced from pywin32's releases.

Release 306

The changes

You should use pip:

pip install pywin32 --upgrade

More details in the README

.exe installers are now deprecated, but while they still exist, you must choose both the correct Python version and "bittedness". Even if you have a 64bit computer, if you installed a 32bit version of Python you must install the 32bit version of pywin32.

There is one binary per-version, per-bittedness. To determine what version of Python you have, start Python and look at the first line of the banner. Compare these 2:

Python 2.7.2+ ... [MSC v.1500 32 bit (Intel)] on win32
Python 2.7.2+ ... [MSC v.1500 64 bit (AMD64)] on win32
                              ^^^^^^^^^^^^^^

If the installation process informs you that Python is not found in the registry, it almost certainly means you have downloaded the wrong version - either for the wrong version of Python, or the wrong "bittedness".

But as above: .exe installers are deprecated - please use pip.

Release 305

The changes

You should use pip:

pip install pywin32 --upgrade

More details in the README

.exe installers are now deprecated, but while they still exist, you must choose both the correct Python version and "bittedness". Even if you have a 64bit computer, if you installed a 32bit version of Python you must install the 32bit version of pywin32.

There is one binary per-version, per-bittedness. To determine what version of Python you have, start Python and look at the first line of the banner. Compare these 2:

Python 2.7.2+ ... [MSC v.1500 32 bit (Intel)] on win32
Python 2.7.2+ ... [MSC v.1500 64 bit (AMD64)] on win32
                              ^^^^^^^^^^^^^^

If the installation process informs you that Python is not found in the registry, it almost certainly means you have downloaded the wrong version - either for the wrong version of Python, or the wrong "bittedness".

But as above: .exe installers are deprecated - please use pip.

Changelog

Sourced from pywin32's changelog.

Build 306, released 2023-03-26

• Add GetSystemPowerStatus (#2010, @​CristiFati)

• Add CascadeWindows (#1999, @​CristiFati)

• Add win32gui.ResetDC

• Fix leak in win32pdh.GetFormattedCounterArray

• Fix IIS on later python versions (#2025)

• Fix for service registration code updated in build 305 (#1985)

• Support for Python 3.6 was dropped, support for later versions was improved.

Build 305, released 2022-11-06

• Installation .exe files were deprecated.

• @​kxrob put a lot of work towards removing use of the deprecated Unicode API so we can build on Python 3.12. This should be largely invisible, but please report any unintended consequences.

• odbc: Handle varchar(max)/nvarchar(max) column sizes (#1954)

• win32api.GetTickCount() now returns an unsigned 64bit integer (@​kxrob, #1946)

• win32pipe.GetNamedPipeHandleState() now takes a 3rd optional param indicating whether the username should be returned, and related constants added. (@​kxrob, #1946)

• Add win32gui.GetTopWindow() and win32gui.GetAncestor() (#1928, @​CristiFati)

• Tweaks to how pywintypes searches for DLLs to better support virtualenvs created with --system-site-packages. (@​saaketp, #1933)

• Added win32event.CreateWaitableTimerExW (#1945, @​zariiii9003)

• Changes in PARAM handling. Some functions which returned a WPARAM or LPARAM allowed you to return a pointer to a Python buffer object or a PyUnicode. These functions now only accept a Python long to be returned. Note that this DOES NOT apply to functions with accept WPARAM or LPARAM as arguments, only when they are being returned. Impacted functions are OnNotify handler, LV_ITEM/TV_ITEM objects, PyIContextMenu3::HandleMenuMsg2, and the result of a WNDPROC/DLGPROC (#1927).

• service registration had an overhaul, avoiding a complicated, and ultimately unnecessary "single globally registered service runner" concept. Now, when registering a service, the host pythonservice.exe runner will be

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[jarikmarwede]

@dependabot rebase

[dependabot]

Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry!

If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

[jarikmarwede]

@dependabot recreate