All commit authors signed the Contributor License Agreement.

Most changes to Pythonrequire a NEWS entry. Add one using theblurb_it web app or theblurb command-line tool.

If this change has little impact on Python users, wait for a maintainer to apply theskip news label instead.

Could anyone mark this with skip news label to get the CI green?

This should have a NEWS entry, please can you add one?

@hugovk, it looks like generating files inMisc/News.d/next is automated somehow.
It there any guide on how do I add an entry atop of the existing PR?

UPD: managed to do this by myself, sorry for disturbing.

NB: this is not the only patch needed to build CPython with this define.

I will have to dig through our patch set to get the remaining ones.

@hugovk, the CI is green, so two questions arise.

1. Can we proceed with merging this PR?
2. Is there a chance for this PR to be backported to 3.12 branch? Updating to 3.13 is a huge amount of work in our case and we would like to remove as many patches as possible prior to doing that.

1. Can we proceed with merging this PR?

I'll leave it to a Windows expert to review.

2. Is there a chance for this PR to be backported to 3.12 branch? Updating to 3.13 is a huge amount of work in our case and we would like to remove as many patches as possible prior to doing that.

Generally, bug fixes can be backported for all bugfix branches -- seehttps://devguide.python.org/versions/ -- currently 3.11 and 3.12. Again, I'll leave it to a Windows expert to decide.

This one is fine. But no promises that the rest will be fine - I've definitely fixed issues recently by removingLEAN_AND_MEAN specifications, and I'd rather keep them in than start referencing non-top-level header files directly.

I see no reason to backport, as this doesn't fix a bug (neither us nor Microsoft make any promises about things being buildable withWIN32_LEAN_AND_MEAN). Keep the patches up and you may be able to drop all your own patches for 3.13 onwards, but you'll want to hang onto them for 3.12 and prior.