Skip to content
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

buildPythonPackage: always export LANG=C.UTF-8 #55826

Closed
wants to merge 420 commits into from

Conversation

FRidh
Copy link
Member

@FRidh FRidh commented Feb 15, 2019

Motivation for this change

Now that C.UTF-8 is available, let's use it in Python packages.

#20192

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Assured whether relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@FRidh
Copy link
Member Author

FRidh commented Feb 15, 2019

Note I will need to clean up the expressions a bit (used git grep and sed here).

@FRidh FRidh changed the title buildPythonPackage: always export LANG=UTF-8 buildPythonPackage: always export LANG=C.UTF-8 Feb 15, 2019
@Mic92
Copy link
Member

Mic92 commented Feb 15, 2019

As I said in #54485 (comment) we also need to support this for the macOS stdenv as well or else we would break macOS support horrible (because C.UTF-8 is not a valid locale there as well). It is probably just a simple patch. However I can not test it, since I don't have access to the hardware/software. If somebody wants to help me out on that, let me know. Also I would move this to stdenv actually since also other application can profit from that.

@FRidh
Copy link
Member Author

FRidh commented Feb 16, 2019

I see, so we're blocked then.

@FRidh FRidh force-pushed the python-unstable branch 3 times, most recently from 9a0618e to 9445255 Compare February 17, 2019 13:41
@FRidh FRidh added this to the 19.03 milestone Feb 21, 2019
@FRidh
Copy link
Member Author

FRidh commented Feb 22, 2019

For Darwin we can use the approach as in 8220b5b for now.

@FRidh
Copy link
Member Author

FRidh commented Feb 23, 2019

Included 1fccd25 in staging-next. Cleaning up expressions is for another time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants