build(deps): bump pywin32 from 301 to 304

[dependabot[bot]]

Bumps pywin32 from 301 to 304.

Release notes

Sourced from pywin32's releases.

Release 304

The changes

If you use pip: pip install pywin32 --upgrade

A number of things don't work via pip, so you may choose to install binaries - but you must choose both the correct Python version and "bittedness". Note that due to changes in Python there are no binary installers for version 3.10 32bit and later, so pypi is your only option there.

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".

Release 303

The changes

If you use pip: pip install pywin32 --upgrade

A number of things don't work via pip, so you may choose to install binaries - but you must choose both the correct Python version and "bittedness". Note that due to changes in Python there are no binary installers for version 3.10 32bit, so pypi is your only option there.

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".

Release 302

The changes

If you use pip: pip install pywin32 --upgrade

A number of things don't work via pip, so you may choose to install binaries - but 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".

Changelog

Sourced from pywin32's changelog.

A changelog for recent builds:

Generally created by hand after running: git log -rb3xx: However contributors are encouraged to add their own entries for their work.

Note that build 228 was the last version supporting Python 2.

Since build 303:

• Fixed Unicode issues in the dde module (#1861, @​markuskimius )

• Add PRINTER_INFO_6 support for Set/GetPrinter (#1853, @​CristiFati)

• Fixed codepage/mojibake issues when non-ascii characters were included in COM exceptions raised by Python apps. This should be invisible, but might break any workarounds which were used, such as using specific encodings in these strings. (#1823, #1833)

• Fixed a bug triggering win32print.SetJob to fail due to data type (char* / wchar_t*) mismatch (#1849, @​CristiFati)

• Fix eventlog initialization (#1845, #1846, @​kxrob)

Since build 302:

• Tweaks to how DLLs are loaded and our installation found, which should improve virtualenv support and version mismatch issues (#1787, #1794)

• Fixed a bug where win32clipboard.GetClipboardData() may have returned extra data.

• Binary installers for 32-bit 3.10+ are no longer released (#1805)

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)

[dependabot[bot]]

Superseded by #56.