Fixed invalid escape sequences in docstring. #142
Conversation
austin-bingham-4ss
requested review from
ali-cetin-4ss and
wojciech-bochniarz-4ss
and removed request for
ali-cetin-4ss
|
There are failing tests that need to be fixed before we can merge this change |
|
Do you see any way in which my change is causing the test failures? |
|
FWIW, I see the same failure when I run the tests locally, both for my branch and for master. It looks like some authentication endpoint has changed or something. In any event, unless there's some indication that my change has something to do with that, I don't know what to do. |
|
Im looking into it and it seems that those test break when running in isolated environment, I will try to fix this issue and let you know when its done |
|
@austin-bingham-4ss You can merge changes from master that will fix tests. There were some problems after pytest upgraded its package and it broke some tests |
austin-bingham-4ss
force-pushed
the
fixed-invalid-escape-sequences
branch
from
7a5036a to
b73c5af
Compare
|
@wojciech-bochniarz-4ss I'm not authorized to merge the PR (and don't want to be), so feel free to merge this in if it's ready. |
Description
Fix a few invalid escape sequences that were printing warnings during import.
This was happening because of changes in Python 3.12. https://docs.python.org/3/whatsnew/3.12.html#other-language-changes