On 12 March 2017 at 08:36, Jakub Wilk wrote:
> This is a very bad idea.
>
> It seems to based on an assumption that the C locale is always some kind
> of pathology. Admittedly, it sometimes is a result of misconfiguration or a
> mistake. (But I don't see why it's the interpreter's job to correct
To whom it may concern,
I was about to use Markdown to verify or indicate any changes to the files
when I was directed to c python and pep, however I have reached my
abilities in understanding or contributing. I will have to broden my
knowledge and insight into python. That is why I am asking for
Hello Ryan,
Welcome!
My response is below.
On Sun, Mar 12, 2017 at 10:49:13AM -0700, Ryan James Kenneth Murray wrote:
> To whom it may concern,
>
> I was about to use Markdown to verify or indicate any changes to the files
> when I was directed to c python and pep, however I have reached my
> a
On 12 March 2017 at 22:57, Nick Coghlan wrote:
> However, I'm also open to having [PYTHONCOERCECLOCALE=0] also disable the
> runtime warning from the shared library.
>
Considering this a little further, I think this is going to be necessary in
order to sensibly handle the build time "--with[out]
