[Python-bugs-list] [ python-Bugs-432786 ] Python 2.1 test_locale fails

noreply@sourceforge.net noreply@sourceforge.net
Mon, 25 Jun 2001 14:10:05 -0700


Bugs item #432786, was opened at 2001-06-13 07:58
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=432786&group_id=5470

Category: Extension Modules
Group: None
Status: Closed
Resolution: Wont Fix
Priority: 5
Submitted By: Paul M. Dubuc (dubuc)
Assigned to: Nobody/Anonymous (nobody)
Summary: Python 2.1 test_locale fails

Initial Comment:
I'm building Python 2.1 on Solaris 2.6.  When I 'make
test', the
test_locale module is the only one that fails:

    test test_locale failed -- Writing: "'%f' % 1024 ==
'1024.000000' !=
'1,024.000000'", expected: ''
    ...
    The actual stdout doesn't match the expected
stdout.
    This much did match (between asterisk lines):

**********************************************************************
    test_locale

**********************************************************************
    Then ...
    We expected (repr): ''
    But instead we got: "'%f' % 1024 == '1024.000000'
!= '1,024.000000'"



----------------------------------------------------------------------

Comment By: Robert Minsk (rminsk)
Date: 2001-06-25 14:10

Message:
Logged In: YES 
user_id=132786

The SGI has the same locale problem as Solaris.  Is this a
bug with the locale defination on linux?

----------------------------------------------------------------------

Comment By: Martin v. Löwis (loewis)
Date: 2001-06-16 00:53

Message:
Logged In: YES 
user_id=21627

That appears to be a bug in Solaris 2.6. To see the 
problem, please try the following program

import locale
locale.setlocale(locale.LC_ALL,"en_US")
c=locale.localeconv()
print c['grouping'],repr(c['thousands_sep'])

In the en_US locale, the thousands separator *should* be a 
comma, but Solaris 2.6 reports that this locale has no 
thousands separator. For locale information, Python relies 
on what the operating system reports.

As it is an OS bug, I'm closing the report as "won't fix".


----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=432786&group_id=5470