* Julien Cristau , 2016-01-28, 14:01:
import subprocess
rv = subprocess.Popen(['locale', '-a'], stdout=subprocess.PIPE,
... stderr=subprocess.PIPE).communicate()[0]
type(rv)
For Python 3, try adding `universal_newlines=True` to any subprocess
call. You'll get back a s
On Mon, Jan 25, 2016 at 23:13:49 -0500, Barry Warsaw wrote:
> On Jan 26, 2016, at 01:12 AM, Ben Hutchings wrote:
>
> >That's not the problem at all. Read the error message again. Read the
> >source line it points to. Now look at where rv comes from:
> >
> import subprocess
> rv = sub
On Mon, Jan 25, 2016 at 8:12 PM, Ben Hutchings wrote:
> On Tue, 2016-01-26 at 11:49 +1100, Brian May wrote:
import subprocess
rv = subprocess.Popen(['locale', '-a'], stdout=subprocess.PIPE,
> ... stderr=subprocess.PIPE).communicate()[0]
type(rv)
>
>
> This is
❦ 26 janvier 2016 11:57 +1100, Brian May :
> I probably should change the line from:
>
> LANG=C.UTF-8 mkdocs build && mv site docs.debian/html
>
> To something like:
>
> LANG=C.UTF-8 LC_CTYPE= LC_ALL= mkdocs build && mv site docs.debian/html
This may not apply to your case, but there is a loca
On Jan 26, 2016, at 01:12 AM, Ben Hutchings wrote:
>That's not the problem at all. Read the error message again. Read the
>source line it points to. Now look at where rv comes from:
>
import subprocess
rv = subprocess.Popen(['locale', '-a'], stdout=subprocess.PIPE,
>...
On Tue, Jan 26, 2016 at 1:23:19 +, Ben Hutchings wrote:
> On Tue, 2016-01-26 at 12:16 +1100, Brian May wrote:
> > Ben Hutchings writes:
> >
> > > That's not the problem at all. Read the error message again. Read the
> > > source line it points to. Now look at where rv comes from:
> >
> >
Ben Hutchings writes:
> Oh, well that's probably because you only set LANG and it's being
> overridden by LC_ALL. Use a bigger hammer: set LC_ALL yourself.
Yes, somebody mentioned this on the BTS also. I very much suspect this
will be the solution.
Thanks
--
Brian May
On Tue, 2016-01-26 at 12:16 +1100, Brian May wrote:
> Ben Hutchings writes:
>
> > That's not the problem at all. Read the error message again. Read the
> > source line it points to. Now look at where rv comes from:
>
> Yes, that is how it would appear.
>
> However, all this code does is try
Ben Hutchings writes:
> That's not the problem at all. Read the error message again. Read the
> source line it points to. Now look at where rv comes from:
Yes, that is how it would appear.
However, all this code does is try to work out the appropriate fatal
error message that should get disp
On Tue, 2016-01-26 at 11:49 +1100, Brian May wrote:
> Ben Hutchings writes:
>
> > C.UTF-8 is built into glibc so I believe you can assume it's present in
> > all Debian installations (from wheezy onward).
>
> Ok, this is getting more and more complicated. The only reason I can see
> for the FTBF
Adam Borowski writes:
> My guess as to the cause of #812672 is that you have LC_CTYPE or LC_ALL set
> to an ancient locale. These variables override LANG, the order is
> LC_ALL>LC_CTYPE>LANG.
Interesting thought. Unfortunately, I can't tell from the supplied build
logs what these are set to.
I
Ben Hutchings writes:
> C.UTF-8 is built into glibc so I believe you can assume it's present in
> all Debian installations (from wheezy onward).
Ok, this is getting more and more complicated. The only reason I can see
for the FTBFS in #812672 is because the C.UTF-8 locale doesn't exist. It
shoul
On Tue, Jan 26, 2016 at 11:29:07AM +1100, Brian May wrote:
> python3-click has checks to ensure it is called with a non-ASCII
> locale. Or if it is an ASCII locale, it raises a fatal error. Or at
> least it tries to raise a fatal error.
[...]
> The problem is that when building djangorestframework,
On Tue, 2016-01-26 at 11:29 +1100, Brian May wrote:
[...]
> The problem is that when building djangorestframework, I need to have a
> utf8 locale available. C.UTF-8 is fine. However, I don't think there is
> any guarantee (??) that a utf8 locale will be available when building
> packages. This I be
14 matches
Mail list logo
