summaryrefslogtreecommitdiff
path: root/.dockerignore
diff options
context:
space:
mode:
authorPeter Scheibel <scheibel1@llnl.gov>2021-04-09 18:10:01 -0700
committerGitHub <noreply@github.com>2021-04-09 18:10:01 -0700
commitf624ce083408d5db90ffa0714a3d2398a30a2fe3 (patch)
treedd3c2c90e148bdc65042a93fd1566dead653f1d3 /.dockerignore
parent8d52200cbcd4052d935d6960ea1de8dcf3fcc2d1 (diff)
downloadspack-f624ce083408d5db90ffa0714a3d2398a30a2fe3.tar.gz
spack-f624ce083408d5db90ffa0714a3d2398a30a2fe3.tar.bz2
spack-f624ce083408d5db90ffa0714a3d2398a30a2fe3.tar.xz
spack-f624ce083408d5db90ffa0714a3d2398a30a2fe3.zip
Build process output: handle UTF-8 for python 3.x to 3.7 (#22888)
We set LC_ALL=C to encourage a build process to generate ASCII output (so our logger daemon can decode it). Most packages respect this but it appears that intel-oneapi-compilers does not in some cases (see #22813). This reads the output of the build process as UTF-8, which still works if the build process respects LC_ALL=C but also works if the process generates UTF-8 output. For Python >= 3.7 all files are opened with UTF-8 encoding by default. Python 2 does not support the encoding argument on 'open', so to support Python 2 the files would have to be opened in byte mode and explicitly decoded (as a side note, this would be the only way to handle other encodings without being informed of them in advance).
Diffstat (limited to '.dockerignore')
0 files changed, 0 insertions, 0 deletions