On Thu, Jun 01, 2017 at 11:02:25PM +0200, Miro Hrončok wrote:
>
>
> On 1.6.2017 20:49, Zbigniew Jędrzejewski-Szmek wrote:
> >On Thu, Jun 01, 2017 at 11:26:55AM -0700, Toshio Kuratomi wrote:
> >>I think it is better if the build system sets LANG=C.UTF-8, not the
> >>python specific macros.
> >
> >
On 1.6.2017 20:49, Zbigniew Jędrzejewski-Szmek wrote:
On Thu, Jun 01, 2017 at 11:26:55AM -0700, Toshio Kuratomi wrote:
I think it is better if the build system sets LANG=C.UTF-8, not the
python specific macros.
Yeah, setting it through python macros would mean that e.g. any
python program in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2017-06-01 at 17:56 +0200, Miro Hrončok wrote:
> Hi Pythonistas.
>
> Regarding our Python 3 C.UTF-8 locale coercing [1], aka PEP 538 [2].
>
> As you probably know, we build RPM packages with the C locale. So
> everytime we use python3 in t
On Thu, Jun 01, 2017 at 11:26:55AM -0700, Toshio Kuratomi wrote:
> I think it is better if the build system sets LANG=C.UTF-8, not the
> python specific macros.
Yeah, setting it through python macros would mean that e.g. any
python program invoked during the build would see the obsolete non-utf8
e
I think it is better if the build system sets LANG=C.UTF-8, not the
python specific macros.
On Thu, Jun 1, 2017 at 8:56 AM, Miro Hrončok wrote:
> Hi Pythonistas.
>
> Regarding our Python 3 C.UTF-8 locale coercing [1], aka PEP 538 [2].
>
> As you probably know, we build RPM packages with the C loc
Hi Pythonistas.
Regarding our Python 3 C.UTF-8 locale coercing [1], aka PEP 538 [2].
As you probably know, we build RPM packages with the C locale. So
everytime we use python3 in the spec file, the coercing message is
shown. This can be more problematic than just spamming the build logs,
see
