mirror of
https://github.com/PyCQA/flake8.git
synced 2026-04-04 20:26:53 +00:00
remove flake8 setuptools command
This commit is contained in:
parent
00f92087da
commit
83fc824ca1
5 changed files with 0 additions and 167 deletions
|
|
@ -47,21 +47,6 @@ both cases, however, you end up in :func:`flake8.main.cli.main`. This is the
|
|||
primary way that users will end up starting Flake8. This function creates an
|
||||
instance of |Application|.
|
||||
|
||||
via Setuptools
|
||||
--------------
|
||||
|
||||
If you're invoking |Flake8| from your ``setup.py`` then you actually end up in
|
||||
:meth:`flake8.main.setuptools_command.Flake8.run`. This then collects the
|
||||
files that are included in the package information and creates an instance of
|
||||
|Application|.
|
||||
|
||||
via Git or Mercurial
|
||||
--------------------
|
||||
|
||||
In both cases, they call their respective ``hook`` functions which create
|
||||
instances of |Application|.
|
||||
|
||||
|
||||
Application Logic
|
||||
=================
|
||||
|
||||
|
|
|
|||
|
|
@ -8,8 +8,6 @@
|
|||
|
||||
- invoked via Python
|
||||
|
||||
- called by Git or Mercurial on or around committing
|
||||
|
||||
This guide will cover all of these and the nuances for using |Flake8|.
|
||||
|
||||
.. note::
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue