> On 17 Oct 2019, at 08:13, Inada Naoki wrote:
>
> Thank you for your response.
> And I'm sorry about ignoring this. Gmail marked it as spam.
>
> On Tue, Oct 15, 2019 at 6:20 PM Ned Deily wrote:
>>
>> We currently do not use those options to build the binaries for the
>> python.org macOS
Thank you for your response.
And I'm sorry about ignoring this. Gmail marked it as spam.
On Tue, Oct 15, 2019 at 6:20 PM Ned Deily wrote:
>
> We currently do not use those options to build the binaries for the
> python.org macOS installers. The main reason is that the Pythons we provide
> are
On Tue, Oct 15, 2019 at 10:57 PM Victor Stinner wrote:
>
> Hi Inada-san,
>
> You can query the sysconfig module to check how Python has been built.
Thank you for pointing it out. It seems official macOS binary doesn't use
--enable-optimizations and --with-lto options...
Python 3.8.0
Hi Inada-san,
You can query the sysconfig module to check how Python has been built.
Example:
pyvstinner@apu$ python3
Python 3.7.4 (default, Jul 9 2019, 16:32:37)
[GCC 9.1.1 20190503 (Red Hat 9.1.1-1)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import
On Oct 15, 2019, at 04:54, Inada Naoki wrote:
> I want Homebrew uses `--enable-optimizations` and `--with-lto` option
> for building Python. But maintainer said:
>
>> Given this is not a default option, probably not, unless it is done in
>> upstream (“official”) binaries.
>
>
