Closed foolip closed 2 years ago
@jgraham that's great to know. Not what I was hoping, but nonetheless :)
One option is to just move to testing on Python 3.7 on macOS, but keep Python 3.6 on Linux?
I believe Gecko is currently using 3.6 in CI.
FWIW, Gecko uses 3.6 only for Linux CI work - Mac and Windows work uses 3.7+ (unsure if WPT is using Gecko Mac/Win workers or not, though :smile:)
There's two developments here which may affect this ticket:
So it sounds like for Gecko bumping the Mac version to 3.7 in wpt CI should be fine; that will match Gecko CI. But we should keep Linux on 3.6 for now, with the hope of requiring 3.7+ by the time 3.6 is EOL (@mitchhentges feel free to CC me on any bugs related to this work, and I can be proactive about ensuring wpt tasks are using a more modern Python :) ).
Also the likelihood of breaking Python 3.6 on macOS while Python 3.6 on Linux still works is low, even if we do marginally care.
OK, so it sounds like what we should do is stop supporting 3.6 on macOS and Windows now (for convenience in Azure Pipelines, really) and then stop supporting 3.6 entirely in early 2022.
I have now updated this to reduce the scope to just macOS and Windows. r?
Closing this, I no longer want to upgrade just macOS and Windows.
I believe Gecko is currently using 3.6 in CI. @mitchhentges or @ahal might know if we have plans to require 3.7+.