Closed kriek closed 3 years ago
Tsk, now Python's criticising my ASCII art. That's a bit surprising as I'm sure the tests pass in Python 3.8 (though I tested with bitstring 3.1.7, but that shouldn't make a difference here). I'll try to reproduce the issue and get a fix in for the next release. Thanks.
Not everyone can appreciate the beauty of ASCII art :) pylint itself does not show the problem. But when it is called from pytest, pytest will collect warnings (and optionally turn them into errors). Steps to reproduce:
pytest --pylint -m pylint import_bitstring.py
Hi,
the top-level docstring in bitstring v3.1.6 should be raw because it uses backslashes in its ASCII art diagram:
Running pylint via pytest-pylint on code using bitstring (python 3.8 if that matters) results in a SyntaxError:
Making the docstring a raw one ("r" prefix) is fixing the issue.
By the way, nice job writing this library, it is my go to choice when dealing with serialization/deserialization protocols !