Skip to content

Fix DeprecationWarning: invalid escape sequence #170

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Nov 12, 2020
Merged

Fix DeprecationWarning: invalid escape sequence #170

merged 1 commit into from
Nov 12, 2020

Conversation

dhimmel
Copy link
Contributor

@dhimmel dhimmel commented Nov 12, 2020

@dhimmel
Copy link
Contributor Author

dhimmel commented Nov 12, 2020 •
edited
Loading

This should get rid of the warnings on CI in the pytest step:

=============================== warnings summary ===============================
panflute/io.py:147
  /home/runner/work/panflute/panflute/panflute/io.py:147: DeprecationWarning: invalid escape sequence \*
    """

panflute/io.py:192
  /home/runner/work/panflute/panflute/panflute/io.py:192: DeprecationWarning: invalid escape sequence \*
    """

panflute/tools.py:360
  /home/runner/work/panflute/panflute/panflute/tools.py:360: DeprecationWarning: invalid escape sequence \s
    """

tests/test_standalone.py:173
  /home/runner/work/panflute/panflute/tests/test_standalone.py:173: DeprecationWarning: invalid escape sequence \s
    tex = 'Some $x^y$ or $x_n = \sqrt{a + b}$ \textit{a}'

-- Docs: https://docs.pytest.org/en/stable/warnings.html

@ickc, for a PR like this with only 1 commit (or many messy commits), consider GitHub's squash merge option. It will avoid making a merge commit and keeps the history a bit linear and clean.

@sergiocorreia sergiocorreia merged commit 0bec22d into sergiocorreia:master Nov 12, 2020
sergiocorreia added a commit that referenced this pull request Nov 12, 2020
@sergiocorreia
Update version to 2.0.5
41b30f6 
- Fix #166
- Improve testing ( #170, #169, #164)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@sergiocorreia sergiocorreia sergiocorreia approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@dhimmel @sergiocorreia