[webkit-dev] Moving to Python 3

[Alexey Proskuryakov]

> 15 июля 2019 г., в 23:04, Fujii Hironori <fujii.hironori at gmail.com> написал(а):
> 
> 
> On Sun, Jul 14, 2019 at 7:44 AM Ryosuke Niwa <rniwa at webkit.org <mailto:rniwa at webkit.org>> wrote:
> 
> I don’t think anyone is arguing that we’d eventually need to move to Python3. I’m arguing that it’s not okay to require random WebKit contributor to know some obscure python insanity to install Python 3, or have a script that installs Python 3 and breaks all other python scripts in the system.
> 
> 
>  Just out of curiosity. As far as I know, installing Python 3 breaks nothing. What and why are they got broken?

As always, it will be up to the people doing the work to decide how it's done. The feedback is clear:

- They shouldn't make it excessively difficult to do WebKit engineering on older versions of macOS.

"Excessively" is not clearly defined, but it seems obvious that there is a tradeoff between tools work difficulty, and difficulty for engineers who go back to older macOS versions (and implicitly, difficulty for people who set up bots, QA engineers, and others involved).

I don't think that anyone ever suggested that it will be up to each engineer to figure out the best way to install Python 3.

- virtualenv works great for some projects.

Definitely worth looking at it as one of the primary paths forward. It's not just Python itself, but we don't want to pollute the system with modules either. Although the latter already has a pretty nice solution in WebKit with autoinstall.

- virtualenv shouldn't be required when building WebKit, and dynamic dependencies in general are not OK in this scenario.

- Alexey

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20190716/9b19a9f8/attachment-0003.html>