pep257 complains that setters (and mabye deleters) have no docstring.
Here is an example
return self._proxy.getBoolean(self._section_name, 'enabled')
def enabled(self, value):
self._section_name, 'enabled', value)
Documentation tools should ignore setters and deletes docstring when creating api docs.
Also, setters and deleters are pretty standard and they will only have a boilerplate text which will not say anything new.
Updated the parser to keep a record for decorators.
In Method.is_private i check the list of decorators and if decorators start with same name then it is marked private.
I have removed unused / broken tests from test_pep257 as this is just hoarding of junk. http://blog.8thlight.com/uncle-bob/2014/04/03/Code-Hoarders.html
Added test for new code.
Check that changed make sense
py.test test_pep257.py -v
Let me know if you find this useful.
Initial code to mark setters as private.
Your tests are failing https://travis-ci.org/GreenSteam/pep257/builds/22946274
Master is also failing and is not my fault :( : https://travis-ci.org/GreenSteam/pep257/builds/22006902
Please see command used for running my tests.
I now see that pep8 is failing. I will udpate my code ... is ugly to work with a master branch which is not clean.
@adiroiban the master branch is now clean. Can you pull and merge it with your code so I can see if your tests are failing or not?
Hi. I don't have time right now to continue working on this but feel free to fork the branch.
Update PyCQA/pydocstyle#69 to latest code
This can probably be closed now that #107 is merged.