-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tests/test_specials.py::test_slash_l* fail with non-en_US locale #140
Labels
Comments
@mgorny Thank you for pointing out the problem. If you feel like submitting a PR, that would be welcome too! |
I'll try but I'm not a postgres expert, so I'm not sure if I'll get it right. |
mgorny
added a commit
to mgorny/pgspecial
that referenced
this issue
Apr 3, 2023
Update the tests to expect the current locale rather than `en_US`. While technically this isn't 100% guaranteed to be the same locale as the database is running on, I think we can reasonably assume that for the purpose of testing they are the same. Non-UTF-8 locales still are not supported but the other tests seem to be unable to handle them well anyway. Fixes dbcli#140
3 tasks
j-bennet
pushed a commit
that referenced
this issue
Oct 28, 2023
* Fix test_slash_l* to support non-en_US locales Update the tests to expect the current locale rather than `en_US`. While technically this isn't 100% guaranteed to be the same locale as the database is running on, I think we can reasonably assume that for the purpose of testing they are the same. Non-UTF-8 locales still are not supported but the other tests seem to be unable to handle them well anyway. Fixes #140 * GHA: set locale matching the postgres locale
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We're running the test suite with
C.UTF-8
locale (because unlikeen_US
it's guaranteed to be available on all Gentoo systems), and this results in the following test failures:Could you perhaps use the values from
LANG
/LC_*
variables rather than hardcodingen_US
? Also, the canonical IANA encoding name isUTF-8
, notUTF8
— using the latter could result in weird problems e.g. on BSD systems.The text was updated successfully, but these errors were encountered: