Try utf16 decoding if utf8 fails when reading environment yml file #10356
Conversation
from the default from open() in text mode, to 2 explicitly using utf8 and utf16 The default .to_yaml() uses utf8, but on windows platforms, redirecting the stdout to a file using `>`, which is a common way to export the environment, outputs a utf16 file instead, and so fails to be read when you try to recreate the environment
|
We require contributors to sign our Contributor License Agreement, and we don't have one on file for @saucoide. In order for us to review and merge your code, please e-sign the PDF at https://conda.io/en/latest/contributing.html#conda-contributor-license-agreement. We then need to manually verify your signature. We will ping the bot to refresh the PR status when we have confirmed your signature. |
|
Hey @saucoide I was looking into the CLA you signed, and it looks like you didn't use your real name on it. Could you please resubmit a new CLA using a correct name? Thanks! |
hi @cjmartian, that's my real name but I wasn't sure if it meant the fullname, will resubmit with the full name |
|
Thank you @saucoide |
|
@anaconda-issue-bot check |
|
Looks good, thank you @saucoide |
|
Hi there, thank you for your contribution to Conda! This pull request has been automatically locked since it has not had recent activity after it was closed. Please open a new issue or pull request if needed. |
this would fix #9749
Changes the decoding used to get the yaml string when reading from file, from the default from open() in text mode, to explicitly using utf8 and utf16
The default .to_yaml() uses utf8, but on windows platforms, redirecting the
stdout to a file using
>, which is a common way to export the environment,outputs a utf16 file instead, and so fails to be read when you try to
recreate the environment