Remove Python 2.7 from the documentation

sebastinas · sebastinas · commit 07f4fe34438e · 2020-10-13T22:00:32.000+02:00
diff --git a/README.rst b/README.rst
@@ -100,23 +100,10 @@ Dependencies
 * curtsies >= 0.3.0
 * greenlet
 * Sphinx != 1.1.2 (optional, for the documentation)
-* mock (optional, for the testsuite)
 * babel (optional, for internationalization)
 * watchdog (optional, for monitoring imported modules for changes)
 * jedi (optional, for experimental multiline completion)
 
-Python 2 before 2.7.7
----------------------
-If you are using Python 2 before 2.7.7, the following dependency is also
-required:
-
-* requests[security]
-
-cffi
-----
-If you have problems installing cffi, which is needed by OpenSSL, please take a
-look at `cffi docs`_.
-
 bpython-urwid
 -------------
 ``bpython-urwid`` requires the following additional packages:
@@ -188,7 +175,6 @@ may be interested to try.
 .. _ipython: https://ipython.org/
 .. _homepage: http://www.bpython-interpreter.org
 .. _full documentation: http://docs.bpython-interpreter.org/
-.. _cffi docs: https://cffi.readthedocs.org/en/release-0.8/#macos-x
 .. _issues tracker: http://github.com/bpython/bpython/issues/
 .. _pip: https://pip.pypa.io/en/latest/index.html
 .. _project homepage: http://bpython-interpreter.org
diff --git a/doc/sphinx/source/contributing.rst b/doc/sphinx/source/contributing.rst
@@ -17,8 +17,8 @@ the time of day.
 Getting your development environment set up
 -------------------------------------------
 
-bpython supports Python 2.7, 3.6 and newer. The code is compatible with all
-supported versions without the need to run post processing like `2to3`.
+bpython supports Python 3.6 and newer. The code is compatible with all
+supported versions.
 
 Using a virtual environment is probably a good idea. Create a virtual
 environment with
@@ -47,7 +47,7 @@ Next install your development copy of bpython and its dependencies:
     # install optional dependencies
     $ pip install watchdog urwid
     # development dependencies
-    $ pip install sphinx mock nose
+    $ pip install sphinx nose
     <modify a file in some way>
     # this runs your modified copy of bpython!
     $ bpython
@@ -60,14 +60,12 @@ Next install your development copy of bpython and its dependencies:
 
     .. code-block:: bash
 
-        $ sudp apt-get install python-greenlet python-pygments python-requests
-        $ sudo apt-get install python-watchdog python-urwid
-        $ sudo apt-get install python-sphinx python-mock python-nose
+        $ sudp apt install python3-greenlet python3-pygments python3-requests
+        $ sudo apt install python3-watchdog python3-urwid
+        $ sudo apt install python3-sphinx python3-nose
 
-    Remember to replace ``python`` with ``python3`` in every package name if
-    you intend to develop with Python 3. You also need to run `virtualenv` with
-    `--system-site-packages` packages, if you want to use the packages provided
-    by your distribution.
+    You also need to run `virtualenv` with `--system-site-packages` packages, if
+    you want to use the packages provided by your distribution.
 
 .. note::
 
@@ -76,7 +74,7 @@ Next install your development copy of bpython and its dependencies:
 
     .. code-block:: bash
 
-        $ sudo apt-get install gcc python-dev
+        $ sudo apt install gcc python3-dev
 
 As a first dev task, I recommend getting `bpython` to print your name every
 time you hit a specific key.
diff --git a/doc/sphinx/source/releases.rst b/doc/sphinx/source/releases.rst
@@ -45,7 +45,7 @@ A checklist to perform some manual tests before a release:
 
 Check that all of the following work before a release:
 
-* Runs under Python 2.7, 3.4, 3.5 and 3.6.
+* Runs under Python 3.6 - 3.9
 * Save
 * Rewind
 * Pastebin
@@ -59,4 +59,3 @@ Check that all of the following work before a release:
 * Command line arguments correctly passed to scripts
 * Delegate to standard Python appropriately
 * Update CHANGELOG
-* Update __version__
diff --git a/doc/sphinx/source/tips.rst b/doc/sphinx/source/tips.rst
@@ -21,8 +21,7 @@ equivalent file.
 Where the `~/python/bpython`-path is the path to where your bpython source code
 resides.
 
-You can of course add multiple aliases, so you can run bpython with 2.7 and the
-3 series.
+You can of course add multiple aliases.
 
 .. note::
 
