django · adamchainz · Sep 30, 2019
diff --git a/accepted/0008-black.rst b/accepted/0008-black.rst
@@ -9,7 +9,6 @@ DEP 0008: Formatting Code with Black
 :Status: Accepted
 :Type: Process
 :Created: 2019-04-27
-:Last-Modified: 2019-05-10
 
 .. contents:: Table of Contents
    :depth: 3
@@ -378,7 +377,7 @@ Implementing this change requires:
      Since the change will be fully automated, there won't be anything to
      review, so it's easier to make just one commit. That commit will be easy
      to identify as non-significant in the future.
-   
+
    * Add the whole-repo-refactor commit SHA to a file in the root of the repo,
      ``.gitblameskip`` or similar, for use with ``git blame`` 's
      ``--ignore-revs-file`` flag

diff --git a/accepted/0009-async.rst b/accepted/0009-async.rst
@@ -9,7 +9,6 @@ DEP 0009: Async-capable Django
 :Status: Accepted
 :Type: Feature
 :Created: 2019-05-06
-:Last-Modified: 2019-05-06
 
 .. contents:: Table of Contents
    :depth: 3

diff --git a/draft/0002-experimental-apis.rst b/draft/0002-experimental-apis.rst
@@ -9,7 +9,6 @@ DEP 2: Experimental APIs
 :Status: Draft
 :Type: Process
 :Created: 2014-12-05
-:Last-Modified: 2014-12-05
 
 .. contents:: Table of Contents
    :depth: 3

diff --git a/draft/0007-dependency-policy.rst b/draft/0007-dependency-policy.rst
@@ -9,7 +9,6 @@ DEP 7: Dependency Policy
 :Status: Draft
 :Type: Process
 :Created: 2016-06-06
-:Last-Modified: 2016-11-05
 
 .. contents:: Table of Contents
    :depth: 3
@@ -56,7 +55,7 @@ as Django itself. We define "maturity" as:
   issues that wouldn't make it into Django shouldn't be accepted as a dependency,
   either.
 
-- **Maintained** - if we discover bugs in a dependency, we need to be fairly 
+- **Maintained** - if we discover bugs in a dependency, we need to be fairly
   confident that they'll be fixed quickly.
 
 - **Takes security seriously** - we should be confident that if we or our users
@@ -65,15 +64,15 @@ as Django itself. We define "maturity" as:
   should have a vulnerability disclosure policy, security-specific contacts,
   and a history of taking vulnerabilities seriously.
 
-- **Works on all the same platforms as Django does** - Linux, Mac, Windows, 
-  and all supported Python versions (including PyPy). This probably means that 
-  dependencies that require C extensions are probably not acceptable [1]_. 
+- **Works on all the same platforms as Django does** - Linux, Mac, Windows,
+  and all supported Python versions (including PyPy). This probably means that
+  dependencies that require C extensions are probably not acceptable [1]_.
 
 - **Backwards compatible** in minor releases. We should be able to specify as
   wide a range of required versions as possible so that releases of Django
   are de-coupled (as much as possible) from dependencies. Generally, we'll
   want to specify dependencies as ``foo>=1.0,<2.0``, and be confident that
-  point-releases of ``foo`` won't break Django. 
+  point-releases of ``foo`` won't break Django.
 
 Again, these are guidelines. At the end of the day, the criteria comes down to
 "would we include this code in Django?" The Tech Board has the final call.
@@ -103,8 +102,8 @@ answers a few questions:
 - What's the dependency? Why should we use it over re-inventing this
   particular wheel [2]_?
 
-- Does the package meet the maturity bar laid out above? If there are 
-  any maturity risks -- for example, if the project only has a single 
+- Does the package meet the maturity bar laid out above? If there are
+  any maturity risks -- for example, if the project only has a single
   maintainer -- that should be identified so we can do a cost/benefit
   analysis.
 
@@ -126,7 +125,7 @@ During each minor release cycle -- and especially before LTS releases -- the
 core team should re-evaluate all existing dependencies. If some dependency is
 starting regress on the maturity front (particularly if it has become
 unmaintained), we want to identify it early and start looking for backup plans.
-This might mean removing the dependency, taking over maintenance ourselves, 
+This might mean removing the dependency, taking over maintenance ourselves,
 looking for funding to pay new maintainers, etc.
 
 Background and Motivation

diff --git a/draft/0010-dissolve-core.rst b/draft/0010-dissolve-core.rst
@@ -9,7 +9,6 @@ DEP 0010: Dissolving Django Core
 :Status: Draft
 :Type: Process
 :Created: 2018-09-22
-:Last-Modified: 2019-06-10
 
 .. contents:: Table of Contents
    :depth: 3
@@ -581,4 +580,4 @@ Copyright
 This document has been placed in the public domain per the Creative Commons
 CC0 1.0 Universal license (http://creativecommons.org/publicdomain/zero/1.0/deed).
 
-(All DEPs must include this exact copyright statement.)
+(All DEPs must include this exact copyright statement.)
diff --git a/draft/0191-composite-fields.rst b/draft/0191-composite-fields.rst
@@ -9,7 +9,6 @@ DEP 191: Composite Fields
 :Status: Draft
 :Type: Feature
 :Created: 2015-03-12
-:Last-Modified: 2015-03-12
 
 .. contents:: Table of Contents
    :depth: 3

diff --git a/draft/0192-standalone-composite-fields.rst b/draft/0192-standalone-composite-fields.rst
@@ -9,7 +9,6 @@ DEP 192: Standalone Composite Fields
 :Status: Draft
 :Type: Feature
 :Created: 2015-03-18
-:Last-Modified: 2015-03-18
 
 .. contents:: Table of Contents
    :depth: 3

diff --git a/final/0003-javascript-tests.rst b/final/0003-javascript-tests.rst
@@ -9,7 +9,6 @@ JavaScript Tests & Linting
 :Status: Final
 :Type: Process
 :Created: 2014-05-04
-:Last-Modified: 2015-07-24
 
 .. contents:: Table of Contents
    :depth: 3

diff --git a/final/0005-improved-middleware.rst b/final/0005-improved-middleware.rst
@@ -9,7 +9,6 @@ DEP 0005: Improved middleware
 :Status: Final
 :Type: Feature
 :Created: 2016-01-07
-:Last-Modified: 2016-06-17
 
 .. contents:: Table of Contents
    :depth: 3

diff --git a/final/0007-official-projects.rst b/final/0007-official-projects.rst
@@ -9,7 +9,6 @@ DEP 0007: Official Django Projects
 :Status: Final
 :Type: Process
 :Created: 2016-06-01
-:Last-Modified: 2016-07-12
 
 .. contents:: Table of Contents
    :depth: 3

diff --git a/final/0182-multiple-template-engines.rst b/final/0182-multiple-template-engines.rst
@@ -6,7 +6,6 @@ DEP 182: Multiple Template Engines
 :Type: Feature
 :Status: Final
 :Created: 2014-09-14
-:Last-Modified: 2015-10-02
 :Author: Aymeric Augustin
 :Implementation-Team: Aymeric Augustin
 :Shepherd: Carl Meyer

diff --git a/final/0201-simplified-routing-syntax.rst b/final/0201-simplified-routing-syntax.rst
@@ -9,7 +9,6 @@ DEP 0201: Simplified routing syntax
 :Status: Final
 :Type: Feature
 :Created: 2016-10-19
-:Last-Modified: 2017-09-30
 
 .. contents:: Table of Contents
    :depth: 3

diff --git a/withdrawn/0006-channels.rst b/withdrawn/0006-channels.rst
@@ -9,7 +9,6 @@ DEP 0006: Channels
 :Status: Withdrawn
 :Type: Feature
 :Created: 2016-05-08
-:Last-Modified: 2016-05-08
 
 .. contents:: Table of Contents
    :depth: 3