pyflakes/0001-Remove-pychecker-from-README-639.patch
lb1107039128 38c7c6fe86 Remove pychecker from README
Signed-off-by: lb1107039128 <liubo1@xfusion.com>
2024-01-31 16:36:31 +08:00

36 lines
1.3 KiB
Diff

From 4cf21896576b734fd901b0dbf6efb0a15162b4af Mon Sep 17 00:00:00 2001
From: Adam Johnson <me@adamj.eu>
Date: Fri, 28 May 2021 18:28:29 +0100
Subject: [PATCH] Remove pychecker from README (#639)
Its last release was nearly 10 years ago: https://sourceforge.net/projects/pychecker/files/ , so it seems pretty dead.
---
README.rst | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/README.rst b/README.rst
index c456d25..47ea7ed 100644
--- a/README.rst
+++ b/README.rst
@@ -39,8 +39,7 @@ Design Principles
Pyflakes makes a simple promise: it will never complain about style,
and it will try very, very hard to never emit false positives.
-Pyflakes is also faster than Pylint_
-or Pychecker_. This is
+Pyflakes is also faster than Pylint_. This is
largely because Pyflakes only examines the syntax tree of each file
individually. As a consequence, Pyflakes is more limited in the
types of things it can check.
@@ -79,7 +78,6 @@ All changes should include tests and pass flake8_.
.. _Pylint: https://www.pylint.org/
.. _flake8: https://pypi.org/project/flake8/
.. _`PEP 8`: https://www.python.org/dev/peps/pep-0008/
-.. _Pychecker: http://pychecker.sourceforge.net/
.. _`rebase your changes`: https://git-scm.com/book/en/v2/Git-Branching-Rebasing
.. _`GitHub pull request`: https://github.com/PyCQA/pyflakes/pulls
--
2.42.0.windows.2