You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
stefanor opened this issue
Jan 20, 2024
· 2 comments
· May be fixed by #296
Labels
C: styleRelates to docstring format style (e.g., Google, NumPy, Sphinx)P: bugPEP 257 violation or existing functionality that doesn't work as documentedU: mediumA relatively medium urgency issue
weibullguy
added
P: bug
PEP 257 violation or existing functionality that doesn't work as documented
C: style
Relates to docstring format style (e.g., Google, NumPy, Sphinx)
and removed
fresh
This is a new issue
labels
Jan 30, 2024
As far as I could debug it, it looks that something has changed (fixed?) in the ast parsing 🤷♂ Removing the whitespaces should be fine, because they don't really belong to the string under test.
C: styleRelates to docstring format style (e.g., Google, NumPy, Sphinx)P: bugPEP 257 violation or existing functionality that doesn't work as documentedU: mediumA relatively medium urgency issue
Debian has started transitioning to add support for Python 3.12, and docformatter's tests fail. See: Debian bug #1056469.
That was on 1.7.5, and I can't reproduce those failures exactly under your tox. But I do get these failures on the current git HEAD (504107b):
The text was updated successfully, but these errors were encountered: