You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AFAIU we don't actually capture the windows version of the user anywhere in the package metadata; i.e. __win has no value, and conda info on windows yields (for example):
It's not completely lost, as it appears in the user-agent string for example, but I'm not aware this this is used anywhere, or indeed that it could be used for package metadata at all.
As was announced in 1.84.0, Windows versions prior to 10 are no longer supported.
Boost is not alone in starting to drop windows <10, and I suspect that our coverage of this is pretty bad, because the windows agents in CI are all obviously much newer already.
Our ucrt package describes itself as "Redistributable files for Windows SDK. This is only needed Windows <10", so presumably we should still be broadly compatible (also because windows API is very stable).
However, this raises two immediate questions:
how can we avoid that boost 1.87 gets installed on win<10 systems?
do we have an idea how wide-spread win<10 still is among our users, and do we want to consider dropping support at some point?
The text was updated successfully, but these errors were encountered:
AFAIU we don't actually capture the windows version of the user anywhere in the package metadata; i.e.
__win
has no value, andconda info
on windows yields (for example):It's not completely lost, as it appears in the user-agent string for example, but I'm not aware this this is used anywhere, or indeed that it could be used for package metadata at all.
The trigger for opening this issue is stumbling over the boost 1.87 release notes, which state:
Boost is not alone in starting to drop windows <10, and I suspect that our coverage of this is pretty bad, because the windows agents in CI are all obviously much newer already.
Our
ucrt
package describes itself as "Redistributable files for Windows SDK. This is only needed Windows <10", so presumably we should still be broadly compatible (also because windows API is very stable).However, this raises two immediate questions:
win<10
systems?win<10
still is among our users, and do we want to consider dropping support at some point?The text was updated successfully, but these errors were encountered: