Re: [webkit-dev] Moving to Python 3

2019-07-12 Thread Jonathan Bedard
I would agree that if we move to Python 3, we need a script which installs Python 3 in an impossible to mess-up way on Mojave and High Sierra. I don’t think the clang comparison is fair here. Python 2 is officially deprecated in 2020, we can’t expect security updates to the language or any libr

Re: [webkit-dev] Moving to Python 3

2019-07-12 Thread Maciej Stachowiak
> On Jul 12, 2019, at 3:23 PM, Ryosuke Niwa wrote: > >  >> On Fri, Jul 12, 2019 at 1:04 PM Jonathan Bedard wrote: > >> >> > On Jul 12, 2019, at 12:49 PM, Michael Catanzaro >> > wrote: >> > >> > On Fri, Jul 12, 2019 at 2:18 PM, Jonathan Bedard wrote: >> >> The trouble I foresee us encoun

Re: [webkit-dev] Moving to Python 3

2019-07-12 Thread Ryosuke Niwa
On Fri, Jul 12, 2019 at 7:03 PM Michael Catanzaro wrote: > On Fri, Jul 12, 2019 at 5:22 PM, Ryosuke Niwa wrote: > > I frequently do WebKit development in older versions of macOS to > > diagnose old OS specific regressions, and having to install Python 3 > > each time I install an old OS is too m

Re: [webkit-dev] Moving to Python 3

2019-07-12 Thread Michael Catanzaro
On Fri, Jul 12, 2019 at 5:22 PM, Ryosuke Niwa wrote: I frequently do WebKit development in older versions of macOS to diagnose old OS specific regressions, and having to install Python 3 each time I install an old OS is too much of a trouble. I understand it would be a hassle. :/ But please c

Re: [webkit-dev] Moving to Python 3

2019-07-12 Thread Ryosuke Niwa
On Fri, Jul 12, 2019 at 1:04 PM Jonathan Bedard wrote: > > > On Jul 12, 2019, at 12:49 PM, Michael Catanzaro > wrote: > > > > On Fri, Jul 12, 2019 at 2:18 PM, Jonathan Bedard > wrote: > >> The trouble I foresee us encountering with any scheme which attempts a > conversion which retains both Pyt

Re: [webkit-dev] Moving to Python 3

2019-07-12 Thread Jonathan Bedard
> On Jul 12, 2019, at 1:07 PM, Keith Rollin wrote: > >> On Jul 12, 2019, at 13:37, Tim Horton wrote: >> >> See "Migrating to the common subset of Python 2 and 3” — you define >> different iteritems() helpers in the two cases. Seems pretty reasonable to >> me. > > I did something like this

Re: [webkit-dev] Moving to Python 3

2019-07-12 Thread Jonathan Bedard
> On Jul 12, 2019, at 12:49 PM, Michael Catanzaro wrote: > > On Fri, Jul 12, 2019 at 2:18 PM, Jonathan Bedard wrote: >> The trouble I foresee us encountering with any scheme which attempts a >> conversion which retains both Python 2.7 and Python 3 compatibility is code >> like this: > > Is

Re: [webkit-dev] Moving to Python 3

2019-07-12 Thread Adrian Perez de Castro
Hello, On Fri, 12 Jul 2019 12:37:43 -0700, Tim Horton wrote: > > On Jul 12, 2019, at 12:18 PM, Jonathan Bedard wrote: > > > > Hello WebKit developers, > > > > Now that the Catalina developer seeds are available, it is official that > > the new Mac developer tools come with Python 3. As a resu

Re: [webkit-dev] Moving to Python 3

2019-07-12 Thread Jonathan Bedard
> On Jul 12, 2019, at 12:45 PM, Robert Ma wrote: > > Any thoughts on bytes and Unicode strings, especially the string literals in > the code base? My experience with this has been you mostly have to pay attention to where your code interfaces with other processes. In webkitpy, I suspect that

Re: [webkit-dev] Moving to Python 3

2019-07-12 Thread Michael Catanzaro
On Fri, Jul 12, 2019 at 2:18 PM, Jonathan Bedard wrote: The trouble I foresee us encountering with any scheme which attempts a conversion which retains both Python 2.7 and Python 3 compatibility is code like this: Is python2 support required for a well-motivated transitional purpose? I had p

Re: [webkit-dev] Moving to Python 3

2019-07-12 Thread Robert Ma
Any thoughts on bytes and Unicode strings, especially the string literals in the code base? On Fri, Jul 12, 2019 at 3:38 PM Tim Horton wrote: > > > On Jul 12, 2019, at 12:18 PM, Jonathan Bedard wrote: > > Hello WebKit developers, > > Now that the Catalina developer seeds are available, it is of

Re: [webkit-dev] Moving to Python 3

2019-07-12 Thread Don . Olmstead
Mentioned this on the other thread but here’s it again. https://python-modernize.readthedocs.io/en/latest/ and http://python-future.org/automatic_conversion.html might be of use considering the sheer amount of code. They’re both mentioned in https://docs.python.org/3/howto/pyporting.html for mi

Re: [webkit-dev] Moving to Python 3

2019-07-12 Thread Tim Horton
> On Jul 12, 2019, at 12:18 PM, Jonathan Bedard wrote: > > Hello WebKit developers, > > Now that the Catalina developer seeds are available, it is official that the > new Mac developer tools come with Python 3. As a result, we need to continue > the ongoing discussion about migrating our Pyt

[webkit-dev] Moving to Python 3

2019-07-12 Thread Jonathan Bedard
Hello WebKit developers, Now that the Catalina developer seeds are available, it is official that the new Mac developer tools come with Python 3. As a result, we need to continue the ongoing discussion about migrating our Python 2.7 scripts to Python 3. I propose that, over the next 9 months, w

Re: [webkit-dev] What's the current Safari UA?

2019-07-12 Thread Michael Catanzaro
I received a good answer and will upgrade our versions accordingly. Thanks. ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev

[webkit-dev] What's the current Safari UA?

2019-07-12 Thread Michael Catanzaro
Hi, Relevant to [1], could someone please check what Safari's current UA string is, please? This is important to help me make sure WebKitGTK fakes the Safari user agent as well as possible. In particular, I'd like to know the version numbers used in the UA. I had thought we were frozen on: