Since PyCharm 2.7 you can hover over the inspected code and use the to Ignore errors like this. Further more you can manage the ignored errors at Settings > Editor > Inspections > Python > PEP 8 naming convention violation > Ignored errors Tested in PyCharm Community Edition 2016.3.2 Edit: To remove the modification later … Read more
The documentation for unittest suggests, e.g.: class TestSequenceFunctions(unittest.TestCase): def test_shuffle(self): … def test_choice(self): … commenting The three individual tests are defined with methods whose names start with the letters test. This naming convention informs the test runner about which methods represent tests.
You can replace i with _ to make it an ‘invisible’ variable. See related: What is the purpose of the single underscore “_” variable in Python?.
You can change it to 4 whitespaces through settings: Tools > Settings > Editor > Indentation width in spaces > Select 4
On module level the second: ReferenceToClass = MyClass As a function argument, the first: reference_to_class = MyClass
Using PyCharm 5 (community edition), you can do the following: Code –> Inspect Code. Then select the required inspection error, and click on the “Suppress” option or “Ignore errors like this” option on right hand side. Please look at the screenshot below: When you choose the “Suppress” option, it adds a comment as shown in … Read more
If we consult the documentation on flake 8 we see: Anti-pattern Note: Despite being in the anti-pattern section, this will soon be considered the best practice. income = (gross_wages + taxable_interest) Best practice Note: Despite being in the best practice section, this will soon be considered an anti-pattern. income = (gross_wages + taxable_interest) So the … Read more
I’ve figured out a possible solution to this, but there might be something better. If you write a comment that will raise an E501 error, i.e. it is too long, you can append that line with # noqa: E501, and flake8 will ignore it. For example: # This is a really really long comment that … Read more
Don’t break the url: Some other good reasons to ignore a particular guideline: When applying the guideline would make the code less readable, even for someone who is used to reading code that follows this PEP. … Source: # A Foolish Consistency is the Hobgoblin of Little Minds [1] # [1]: http://www.python.org/dev/peps/pep-0008/#a-foolish-consistency-is-the-hobgoblin-of-little-minds You can use … Read more
Your Vim plugin was wrong when you asked in 2013… but right in 2010, when it was authored. PEP 8 has changed on several occasions, and the answer to your question has changed as well. Originally, PEP 8 contained the phrase: Use spaces around arithmetic operators Under that rule, range(a, b+1) is unambiguously wrong and … Read more