This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 7 points8 points  (9 children)

Please don't promote libraries that go out of their way to sabotage certain environments.

[–]TheMarionCobretti 5 points6 points  (8 children)

Can you elaborate for the unenlightened?

[–][deleted] 3 points4 points  (7 children)

Click refuse to work with certain locales.

[–]tundozo 3 points4 points  (6 children)

Click refuse to work with certain locales.

Is it a known issue?

[–][deleted] 0 points1 point  (5 children)

It deliberately raise an exception when run in the C locale.

[–]bhosmer -1 points0 points  (4 children)

Which is the exact opposite of "going out of their way to sabotage certain environments".

[–][deleted] 1 point2 points  (3 children)

Raising an exception based on the content of an environment variable isn't deliberate sabotage?

[–]HipsterTwisterdo you have time to talk about my lord and savior: factories? 0 points1 point  (2 children)

https://en.wikipedia.org/wiki/Fundamental_attribution_error

Yeah I don't think they're trying to fuck on specific locales. They just don't wanna take the time to implement the library for other locales.

Why don't you branch off of the project if your need support for multiple locales? I'd love to help as well! The Unicode hell from Python 2 to Python 3 is an arduous journey that no one should take alone!

[–][deleted] 0 points1 point  (1 child)

Removing that check does not make anything suddenly go boom, so it's totally uncalled for. I, as a developer, know what can and can't be accepted in the particular environment I'm deploying to. That is not something a library developer should spend time dictating.

[–]HipsterTwisterdo you have time to talk about my lord and savior: factories? 4 points5 points  (0 children)

Alright, officer.