Skip to content

Commit 0214593

Browse files
committed
Advertize the pep8-naming extension
1 parent a53c569 commit 0214593

1 file changed

Lines changed: 4 additions & 8 deletions

File tree

docs/intro.rst

Lines changed: 4 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -42,14 +42,10 @@ Always remember this statement from `PEP 8`_:
4242
Among other things, these features are currently not in the scope of
4343
the ``pep8`` library:
4444

45-
* **naming conventions**: there's `a feature request
46-
<https://github.com/jcrocholl/pep8/issues/44>`_ with `a patch
47-
<https://github.com/jcrocholl/pep8/pull/121>`_, but it might
48-
be too disruptive to include it in the library: currently it's easy to make
49-
an existing project clean regarding ``pep8`` checks; it can be done without
50-
changing the API or the behaviour of the existing code. It's not the same
51-
for naming conventions: if you change the name of a class or a method, it
52-
will break more code which depends on the library.
45+
* **naming conventions**: this kind of feature is supported through plugins.
46+
Install `flake8 <https://pypi.python.org/pypi/flake8>`_ and the
47+
`pep8-naming extension <https://pypi.python.org/pypi/pep8-naming>`_ to use
48+
this feature.
5349
* **docstring conventions**: they are not in the scope of this library;
5450
see the `pep257 project <https://github.com/GreenSteam/pep257>`_.
5551
* **automatic fixing**: see the section *PEP8 Fixers* in the

0 commit comments

Comments
 (0)