Is here: https://bugzilla.redhat.com/show_bug.cgi?id=1672833
A review would be appreciated.
Also, we'd like to target Fedora 31 with 3.8, see
https://fedoraproject.org/wiki/Changes/Python3.8
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
p
Hi,
due to https://fedoraproject.org/wiki/Changes/Python_Extension_Flags it is no
longer correct to just call `python3 setup.py build` or `python3 setup.py
build_ext` in spec without setting the proper flags (for arched builds with
Python extension modules at least).
That is without setting
Just commited option 1 to Rawhide for python-pivy
Is it needed for other releases?
Thanks,
Richard
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Co
On 06. 02. 19 16:24, Richard Shaw wrote:
Just commited option 1 to Rawhide for python-pivy
Is it needed for other releases?
Not needed. But also not dangerous.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
python-devel mailing list -- py
Hi,
On Wed, 2019-02-06 at 15:04 +0100, Miro Hrončok wrote:
>
> I've grepped the usage and skimmed trough specs, destining the
> following list of
> packages that fail to properly set both flags.
I've also found that one of my packages was settings CFLAGS to
%{optflags} and fixed it:
https://src
On 06. 02. 19 22:16, Tadej Janež wrote:
Hi,
On Wed, 2019-02-06 at 15:04 +0100, Miro Hrončok wrote:
I've grepped the usage and skimmed trough specs, destining the
following list of
packages that fail to properly set both flags.
I've also found that one of my packages was settings CFLAGS to
%{
