Re: mkdocs locale error building djangorestframework

2016-01-25 Thread Ben Hutchings
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

Re: mkdocs locale error building djangorestframework

2016-01-25 Thread Brian May
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

Re: mkdocs locale error building djangorestframework

2016-01-25 Thread Ben Hutchings
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

Re: mkdocs locale error building djangorestframework

2016-01-25 Thread Brian May
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

Re: mkdocs locale error building djangorestframework

2016-01-25 Thread Ben Hutchings
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

Re: mkdocs locale error building djangorestframework

2016-01-25 Thread Brian May
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

Re: mkdocs locale error building djangorestframework

2016-01-25 Thread Michael Tautschnig
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: > > > >

Re: mkdocs locale error building djangorestframework

2016-01-25 Thread Barry Warsaw
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, >... 

Re: Python Policy: Things to consider for Stretch

2016-01-25 Thread Ben Finney
Ben Finney writes: > Scott Kitterman writes: > > > At this point I think internal consistency is probably more > > important, so if someone wants to go through and make all the > > python's that should be python2, etc then please send in a patch. > > I'll take that on. I'm planning to provide c

Re: Python Policy: Things to consider for Stretch

2016-01-25 Thread Ben Finney
Ben Finney writes: > I'm planning to provide changes in two bundles: > > * Go through the whole document and tidy it up for consistency, source > style, markup, and language style. This should not change the meaning > of anything, but will change the wording of numerous passages. > > My pro