Am 06.07.18 um 16:04 schrieb Dustin Mitchell:
I agree -- we faced similar issues in the days when py2.5 - 2.7 were
still available.
I think that if we're clear about the Python version we test on in CI,
and willing to make the effort to fix bugs when we change that (e.g.,
to 3.8), that's sufficient.
Dustin
So, if you thought that story was sad ...
brew update
brew upgrade something-else
something-else depended on python, brew updated python from 3.6.5 to
3.7.0. I did intend to not update python deliberately, but no luck.
/usr/local/Cellar/python/3.6.5/bin/python can't be used for virtualenvs,
'cause sys.executable points to /usr/local/opt/python/bin/python3.6,
which doesn't exist anymore.
... so on mac/homebrew, there's very little power over which python you
end up using.
I do think we need to run tests on at least 2.7.latest and
3.[5-7].latest. For now, the 3.x ones can probably be tier 2-3, but we
need visibility into them.
Axel
_______________________________________________
dev-builds mailing list
dev-builds@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-builds
