Re: [webkit-dev] What's the rationale for not including config.h in any header files?

2017-08-07 Thread Keith Miller
> On Aug 5, 2017, at 1:48 PM, Konstantin Tokarev wrote: > 04.08.2017, 21:20, "Carlos Alberto Lopez Perez" : >> On 02/08/17 12:14, Konstantin Tokarev wrote: >>> FWIW, I use ENABLE_ALLINONE_BUILD=ON as a default build option in Qt >>> port and don't have

Re: [webkit-dev] WEB_TIMING enabled on all ports - let's remove the flag?

2017-08-07 Thread Michael Catanzaro
On Tue, Aug 1, 2017 at 8:57 AM, Dean Jackson wrote: In general I think we should be more enthusiastic about removing feature flags that are guarding core parts of the Web platform. Web Timing is a great example. Some others I see: ENABLE_CANVAS_PATH ENABLE_CSS_COMPOSITING

Re: [webkit-dev] Python

2017-08-07 Thread Michael Catanzaro
On Mon, Aug 7, 2017 at 1:17 PM, Keith Miller wrote: Out of curiosity, is this just about building or is part of the concern with development scripts? Both. ___ webkit-dev mailing list webkit-dev@lists.webkit.org

Re: [webkit-dev] Python

2017-08-07 Thread Keith Miller
Out of curiosity, is this just about building or is part of the concern with development scripts? AFAICT, we invoke all our python scripts by invoking $(PYTHON), which can be whatever path you need. I didn’t look too closely though... Cheers, Keith > On Aug 7, 2017, at 6:47 AM, Michael

Re: [webkit-dev] Python

2017-08-07 Thread Olmstead, Don
There are automated tools that will update to Python 3 while keeping compatibility with Python 2. There is future, http://python-future.org/automatic_conversion.html, and modernizer, https://python-modernize.readthedocs.io/en/latest This came up in

Re: [webkit-dev] Python

2017-08-07 Thread Michael Catanzaro
On Mon, Aug 7, 2017 at 10:56 AM, Carlos Alberto Lopez Perez wrote: That's a good thing. I believe all Linux distros we support have this, right? And all the scripts actually assume python2.7 (AFAIK). Would it work for everyone having as shebang : #!/usr/bin/env python2.7

Re: [webkit-dev] Python

2017-08-07 Thread Carlos Alberto Lopez Perez
On 07/08/17 17:44, Andy Estes wrote: >>> last I checked, macOS did not provide a python2 binary either. I am hoping >>> that has changed in the past few years. Has it? >> Nope. > macOS does have /usr/bin/python2.7, though. > That's a good thing. I believe all Linux distros we support have

Re: [webkit-dev] Python

2017-08-07 Thread Andy Estes
> On Aug 7, 2017, at 8:41 AM, Andy Estes wrote: > > > >> On Aug 7, 2017, at 6:47 AM, Michael Catanzaro > > wrote: >> >> last I checked, macOS did not provide a python2 binary either. I am hoping >> that has changed in

Re: [webkit-dev] Python

2017-08-07 Thread Andy Estes
> On Aug 7, 2017, at 6:47 AM, Michael Catanzaro wrote: > > last I checked, macOS did not provide a python2 binary either. I am hoping > that has changed in the past few years. Has it? Nope. Andy ___ webkit-dev mailing list

Re: [webkit-dev] Python

2017-08-07 Thread Michael Catanzaro
On Mon, Aug 7, 2017 at 8:47 AM, Michael Catanzaro wrote: This has not really been a problem until now because none of Igalia's developers use Arch, and occasional contributions rarely need to use the Python scripts. I stand corrected: we have one developer who has

Re: [webkit-dev] Python

2017-08-07 Thread Konstantin Tokarev
07.08.2017, 16:47, "Michael Catanzaro" : > Hi, > > As you're probably already aware, in Arch Linux /usr/bin/python has > been a symlink to /usr/bin/python3 for a long time now. In practice > this means that Arch users are not going to be able to use basically > any of our

[webkit-dev] Python

2017-08-07 Thread Michael Catanzaro
Hi, As you're probably already aware, in Arch Linux /usr/bin/python has been a symlink to /usr/bin/python3 for a long time now. In practice this means that Arch users are not going to be able to use basically any of our Python scripts, since our scripts use the shebang #!/usr/bin/env python