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

When running unitests with prettytable, got DeprecationWarning #43

Closed
saroad2 opened this issue Apr 17, 2020 · 3 comments
Closed

When running unitests with prettytable, got DeprecationWarning #43

saroad2 opened this issue Apr 17, 2020 · 3 comments

Comments

@saroad2
Copy link

saroad2 commented Apr 17, 2020

I am using prettytable in my uint tests and I get the following warnings:

venv\lib\site-packages\prettytable-0.7.2-py3.7.egg\prettytable.py:74
venv\lib\site-packages\prettytable-0.7.2-py3.7.egg\prettytable.py:74
  C:\Users\saroa\repositories\eddington_core\venv\lib\site-packages\prettytable-0.7.2-py3.7.egg\prettytable.py:74: DeprecationWarning: invalid escape sequence \[

venv\lib\site-packages\prettytable-0.7.2-py3.7.egg\prettytable.py:800
venv\lib\site-packages\prettytable-0.7.2-py3.7.egg\prettytable.py:800
  C:\Users\saroa\repositories\eddington_core\venv\lib\site-packages\prettytable-0.7.2-py3.7.egg\prettytable.py:800: DeprecationWarning: invalid escape sequence \{

venv\lib\site-packages\prettytable-0.7.2-py3.7.egg\prettytable.py:801
venv\lib\site-packages\prettytable-0.7.2-py3.7.egg\prettytable.py:801
  C:\Users\saroa\repositories\eddington_core\venv\lib\site-packages\prettytable-0.7.2-py3.7.egg\prettytable.py:801: DeprecationWarning: invalid escape sequence \{

venv\lib\site-packages\prettytable-0.7.2-py3.7.egg\prettytable.py:802
venv\lib\site-packages\prettytable-0.7.2-py3.7.egg\prettytable.py:802
  C:\Users\saroa\repositories\eddington_core\venv\lib\site-packages\prettytable-0.7.2-py3.7.egg\prettytable.py:802: DeprecationWarning: invalid escape sequence \{

Maybe I can fix that.

@hugovk
Copy link
Member

hugovk commented Apr 17, 2020

Already fixed in #1?

@saroad2
Copy link
Author

saroad2 commented Apr 17, 2020

Yes, sorry. I saw that you fixed that on the master branch, but the fix not yet available in the pip package.

Can you publish a new release with this fix?

@hugovk
Copy link
Member

hugovk commented Apr 18, 2020

#18 is the release issue. It's pretty much ready to go, unfortunately I don't have PyPI access and I think the others are swamped with other projects.

In the meantime, I suggest installing from Git or ignoring the warnings.

@hugovk hugovk closed this as completed May 29, 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

No branches or pull requests

2 participants