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

fix windows utf8 encoding part 3/3 #203

Merged
merged 4 commits into from
Jun 19, 2020
Merged

Conversation

phaustin
Copy link
Contributor

@codecov
Copy link

codecov bot commented Jun 18, 2020

Codecov Report

Merging #203 into master will not change coverage.
The diff coverage is 83.33%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #203   +/-   ##
=======================================
  Coverage   85.49%   85.49%           
=======================================
  Files           9        9           
  Lines         834      834           
=======================================
  Hits          713      713           
  Misses        121      121           
Flag Coverage Δ
#pytests 85.49% <83.33%> (ø)
Impacted Files Coverage Δ
myst_nb/nb_glue/utils.py 73.01% <0.00%> (ø)
myst_nb/cache.py 78.44% <100.00%> (ø)
myst_nb/converter.py 77.69% <100.00%> (ø)
myst_nb/nb_glue/domain.py 90.64% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 962d535...72e5f47. Read the comment docs.

@phaustin
Copy link
Contributor Author

@choldgraf -- I reverted one change to get the file_regression test to pass -- the open statement
in the notebook artifact should also specify encoding="utf8":
i.e. this commit

@choldgraf
Copy link
Member

@phaustin re: the file regression, I'm not quite sure what you mean by reverted. do you mean there's one part in this codebase that doesn't use utf-8 now?

@phaustin
Copy link
Contributor Author

I mean that if I add encoding="utf8" to the ipynb version of this file
pytest fails with a "file regression" error.

@choldgraf
Copy link
Member

could you post the error?

@phaustin
Copy link
Contributor Author

reran with the same command line arguments as the CI, and all tests pass locally on my mac, I think it was a timeout issue, so I think this is ready to merge. On my local windows there are still about half a dozen pytest failures, but several of those are related to the windows path problem. I've isolated that issue to app.env.doc2path in cache.py (and also in jupyter-book/toc.py) and we can retest once I've pushed those PRs.

@choldgraf
Copy link
Member

ok cool! let's merge this in and see how things go :-) thanks for the improvement!

@choldgraf choldgraf merged commit f61ba07 into executablebooks:master Jun 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants