Skip to content

Open dotenv_path with UTF-8 encoding - #75

Closed
earlbread wants to merge 4 commits into
theskumar:masterfrom
earlbread:open_file_with_utf8
Closed

Open dotenv_path with UTF-8 encoding#75
earlbread wants to merge 4 commits into
theskumar:masterfrom
earlbread:open_file_with_utf8

Conversation

@earlbread

Copy link
Copy Markdown
Contributor

This resolves #74.
I think it is better to specify the encoding when opening the .env file.

@theskumar

Copy link
Copy Markdown
Owner

It seems like tests are failing, can you look into it.

@earlbread

Copy link
Copy Markdown
Contributor Author

Ok, I'll look into it and submit again. Thank you!

@coveralls

coveralls commented Nov 11, 2017

Copy link
Copy Markdown

Coverage Status

Coverage increased (+0.07%) to 85.354% when pulling bb1a28b on earlbread:open_file_with_utf8 into 05d123b on theskumar:master.

@earlbread

Copy link
Copy Markdown
Contributor Author

@theskumar I fixed my code. Thank you!

@alanjds

alanjds commented Jan 15, 2018

Copy link
Copy Markdown
Contributor

Is #60 (comment) related with this PR?

@metalcamp

Copy link
Copy Markdown

Obviously not appropriate place to discuss this, but why this still hasn't been merged?

@theskumar
theskumar force-pushed the master branch 2 times, most recently from d541b6c to fe35be1 Compare March 16, 2018 19:55
@uranusjr

Copy link
Copy Markdown

We’re hitting this in pypa/pipenv#1963 as well. Either the file should always be decoded with UTF-8, or there should be an additional argument in fine_dotenv etc. to allow users to specify a custom encoding.

@theskumar
theskumar force-pushed the master branch 2 times, most recently from f628767 to f9863d3 Compare December 16, 2018 13:18
@theskumar

Copy link
Copy Markdown
Owner

This will be superseded by #144

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

Labels

None yet

6 participants