Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Strange result for specific number strings using Dutch locale

See original GitHub issue

Actual behavior Human sorting ['461761', '462166'] using the Dutch locale gives the wrong result ['462166', '461761'].

Expected behavior The result should be ['461761', '462166'].

Environment 1:

Python 3.8.1
Mac OS X 10.14.6
PyICU installed
Locale set to 'nl_NL'

Environment 2:

Python 3.8.0
Windows 7 SP1
PyICU not installed
Locale set to 'nl-NL'

Environment 3:

Python 3.8.1
FreeBSD 12.1
PyICU not installed
Locale set to 'nl_NL.ISO8859-1'

To reproduce

>>> import locale
>>> locale.setlocale(locale.LC_ALL, 'Dutch') # replace 'Dutch' as appropriate
>>> from natsort import humansorted
>>> humansorted(['461761', '462166'])
['462166', '461761']

Issue Analytics

State:
Created 4 years ago
Comments:11 (6 by maintainers)

Top GitHub Comments

1reaction

SethMMortoncommented, Jan 28, 2020

This fix has been released in natsort version 7.0.1.

0reactions

thijsvandiencommented, Jan 28, 2020

The Linux system I tested returns an empty string, which makes some sense, because separating thousands is optional in the Netherlands. In any case, that explains it.