| 1 |
On Sun, 17 Feb 2013 13:48:28 -0500 |
| 2 |
Mike Gilbert <floppym@g.o> wrote: |
| 3 |
|
| 4 |
> This issue seems to keep coming up in bug reports, especially those |
| 5 |
> filed by Diego from his tinderbox. Basically, the way I/O is handled |
| 6 |
> in python3 often causes build failures or test failures if you do not |
| 7 |
> have a UTF-8 locale set. Ideally, upstream developers would write |
| 8 |
> their code to deal with this, but that's a bit of a pipe dream. |
| 9 |
> |
| 10 |
> Gentoo as a whole can't seem to make its mind up, but can the python |
| 11 |
> team come to a rough consensus as to whether we want to support |
| 12 |
> non-UTF-8 locales for python packages? |
| 13 |
> |
| 14 |
> I'm sitting on the fence at the moment: I tend to fix issues if they |
| 15 |
> cause build failures, but I ignore any test failures. |
| 16 |
> |
| 17 |
Well, I tend to fix issues, be they builds of tests. |
| 18 |
|
| 19 |
> If we decide to support non-UTF-8 locales, we need to stop leaving |
| 20 |
> bugzilla comments like "please use a sane locale". |
| 21 |
> |
| 22 |
> If we decide against supporting non-UTF-8 locales, I think we should |
| 23 |
> begin to close such bugs as WONTFIX on a consistent basis. |
| 24 |
> |
| 25 |
> My vote would be to not support non-UTF-8 locales -- it just isn't |
| 26 |
> worth the effort. |
| 27 |
> |
| 28 |
> Thoughts? |
| 29 |
> |
| 30 |
|
| 31 |
Firstly, thumbs up for floating the issue. "please use a sane locale" |
| 32 |
fundamentally undermines the merit of the tinderbox meister making such |
| 33 |
bugs. He deliberately makes such locales to flush out such packages |
| 34 |
supporting only the utf8. He's clearly convinced of the righteousness |
| 35 |
of the bug submissions, but then again, so to for everything else he |
| 36 |
does under the banner of working gentoo. |
| 37 |
|
| 38 |
The ignoring of such tests to me implies it's not really a bug, and |
| 39 |
frankly this notion has obvious merit. If there are utf and non utf |
| 40 |
locales and the utf makes it work, then arguably the package is |
| 41 |
buildable and installable. The selection of a normative locale across |
| 42 |
the board has obvious merit. If not utf8 simply einfo the user to set |
| 43 |
one. |
| 44 |
|
| 45 |
One statement arguing against I could cite from am upstream dev who, |
| 46 |
lumbered with this exact task, agreed in principal they should not |
| 47 |
assume a utf locale, and a fix for it has been made already by a few |
| 48 |
maintainers of other packages, e.g. ipython. Trouble is, he's one of a |
| 49 |
very long queue of upstream devs. |
| 50 |
|
| 51 |
to not support non-UTF-8 locales -- it just isn't |
| 52 |
> worth the effort. |
| 53 |
|
| 54 |
This is more or less the assumed and invisible policy, and |
| 55 |
frankly on that basis I go along with Mike's selection. Making this a |
| 56 |
formal issue and declaring a python team policy is afaict the only |
| 57 |
legitimate method of 'informing' the tinderbox meister these are not |
| 58 |
bugs, these just further spam bugzilla. Then we can close such bugs |
| 59 |
as WONTFIX on a consistent basis without anticipation of the next dose |
| 60 |
o' the long ago banned whip. After all, these bug submissions come |
| 61 |
almost exclusively from him. |
| 62 |
|
| 63 |
-- |
| 64 |
kind regards |
| 65 |
|
| 66 |
Ian Delaney |
Archives