Closed LKay closed 5 years ago
This package never explicitly supported that as I have no idea that comment existed. So I'll have to take a look. There are no tests for that behavior.
Also, same as my reply to the other one. Can you give me a pip freeze or something to help me recreate the issue.
3.1.4
released with support for that comment added.
This might be related to #40 but violation is different, so I'm making new issue.
Our builds on CI server started to fail just when
3.1.3
was released. Seems like inline# nopep8
comment has no effect anymore and on such line:results in violation error:
It was just bump of patch part of semver so CI server fetched the most recent version and older version was present on my local machine. Took me a while to track down what was causing this, but everything seems to be working fine wit
3.1.1
.