Skip to content

Add Windows version comments to the python manifest. #127439

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.

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

Merged
merged 2 commits into from
Dec 24, 2024
Merged

Conversation

AraHaan
Copy link
Contributor

@AraHaan AraHaan commented Nov 30, 2024

This is so it becomes easier to add or remove future values as time passes and when support for older versions of Windows gets dropped from python. MSVC's vNEXT (V18) will soon drop all but Windows 8.1 so if and when Python migrates to that version of MSVC that means support for Windows older than 8.1 would need to be dropped then.

This is a followup PR to the change from 7 years ago (#2328) as I felt that leaving comments for the versions of windows for each specific compatibility entry is needed. It is also a trivial change as well.

@AraHaan AraHaan requested a review from a team as a code owner November 30, 2024 09:05
@@ -9,10 +9,15 @@
</trustInfo>
<compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">
<application>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we add a comment linking to the docs for others?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree

@zooba
Copy link
Member

zooba commented Dec 13, 2024

Not opposed to adding the comments, though I'm not sure how valuable it is to drop entries over time. If Python happens to be run on a newer system that isn't in the manifest, Windows should use the compatibility mode for the latest version it recognises, and running in Win7 mode is better than WinXP mode (though neither are likely, tbqh).

This is so it becomes easier to add or remove future values as time passes and when support for older versions of Windows gets dropped from python. MSVC's vNEXT (V18) will soon drop all but Windows 8.1 so if and when Python migrates to that version of MSVC that means support for Windows older than 8.1 would need to be dropped then.
@zooba
Copy link
Member

zooba commented Dec 24, 2024

Decided I'd rather take this without the URL. The reason being that this file is directly embedded (unmodified) inside the binaries that we ship, and it's entirely likely that embedded URLs may be treated as suspicious.

If someone wants to mention this file in the devguide, that would be a suitable place to link to the docs.

@zooba zooba merged commit bd3e200 into python:main Dec 24, 2024
36 checks passed
@AraHaan AraHaan deleted the patch-3 branch December 25, 2024 00:12
srinivasreddy pushed a commit to srinivasreddy/cpython that referenced this pull request Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants