feat: add uv and pyproject.toml to OEP-67, archive OEP-18

Add pyproject.toml (PEP 621/735) and uv as backend technology standards
in OEP-67, with a new backend ADR documenting the decision to replace
pip-tools. Archive OEP-18 (Python Dependency Management) as Replaced,
following the same pattern used when OEP-11 was superseded by OEP-67.

References:
- PEP 621: https://peps.python.org/pep-0621/
- PEP 735: https://peps.python.org/pep-0735/
- uv docs: https://docs.astral.sh/uv/
- Jazzband sunsetting: https://jazzband.co/news/2026/03/14/sunsetting-jazzband

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: feanil

…ices/oep-0018-bp-python-dependencies.rst …ived/oep-0018-bp-python-dependencies.rstoeps/best-practices/oep-0018-bp-python-dependencies.rst renamed to oeps/archived/oep-0018-bp-python-dependencies.rst oeps/best-practices/oep-0018-bp-python-dependencies.rst renamed to oeps/archived/oep-0018-bp-python-dependencies.rst

@@ -8,13 +8,13 @@ OEP-18: Python Dependency Management
 +-----------------+--------------------------------------------------------+
 | Title           | Python Dependencies Management                         |
 +-----------------+--------------------------------------------------------+
-| Last Modified   | 2023-03-06                                             |
+| Last Modified   | 2026-04-24                                             |
 +-----------------+--------------------------------------------------------+
 | Authors         | Jeremy Bowman <jbowman@edx.org>                        |
 +-----------------+--------------------------------------------------------+
 | Arbiter         | Calen Pennington <cale@edx.org>                        |
 +-----------------+--------------------------------------------------------+
-| Status          | Approved                                               |
+| Status          | Replaced                                               |
 +-----------------+--------------------------------------------------------+
 | Type            | Best Practice                                          |
 +-----------------+--------------------------------------------------------+
@@ -27,6 +27,11 @@ OEP-18: Python Dependency Management
 
 .. _open-edx-proposals#56 resolution: https://github.com/openedx/openedx-proposals/pull/56#pullrequestreview-116976355
 
+.. warning::
+
+   This OEP has been replaced and may be out of date.  For the most up-to-date
+   information see :ref:`OEP-67 Standard Tools and Technologies`.
+
 .. contents::
    :local:
    :depth: 2

oeps/best-practices/oep-0067-bp-tools-and-technology.rst

@@ -11,7 +11,7 @@ OEP-67: Standard Tools and Technologies
    * - Title
      - Tools and Technology Standards
    * - Last Modified
-     - 2025-02-10
+     - 2026-04-24
    * - Authors
      - Feanil Patel <feanil@axim.org>
    * - Arbiter
@@ -27,7 +27,8 @@ OEP-67: Standard Tools and Technologies
    * - Resolution
      - * https://github.com/openedx/openedx-proposals/pull/518
    * - References
-     - :ref:`OEP-11 Front End Technology Standards`
+     - * Replaces :ref:`OEP-11 Front End Technology Standards`
+       * Replaces :ref:`OEP-18 Python Dependency Management`
 
 Abstract
 ********
@@ -327,6 +328,32 @@ they do not require disruptive migrations that would break existing MySQL
 installations. Support for these other database backends is not guaranteed and
 may require plugins or lag behind the official releases.
 
+#. **pyproject.toml should be used to declare project metadata and dependencies**
+
+   **Rationale**: `PEP 621`_ standardized project metadata in ``pyproject.toml``,
+   and `PEP 735`_ added dependency groups — a standard way to declare
+   context-specific dependencies (test, docs, CI, dev, etc.). Using
+   ``pyproject.toml`` as the single source of truth replaces the older pattern
+   of ``requirements/*.in`` files and ``setup.py`` / ``setup.cfg``, simplifies
+   tooling, and aligns with the broader Python ecosystem.
+
+#. **uv should be used for Python dependency locking and virtual environment management**
+
+   **Rationale**: `uv`_ consolidates dependency resolution, locking, virtual
+   environment creation, and tool execution into a single fast tool. It replaces
+   `pip-tools`_ (``pip-compile`` / ``pip-sync``) and produces a single
+   ``uv.lock`` file from ``pyproject.toml`` dependency groups. The existing
+   ``make upgrade`` pattern is preserved — the target now runs
+   ``uv lock --upgrade`` instead of ``pip-compile --upgrade``.
+
+   **Decision Record**: For details, see
+   :ref:`Use uv for Python dependency management`.
+
+.. _PEP 621: https://peps.python.org/pep-0621/
+.. _PEP 735: https://peps.python.org/pep-0735/
+.. _uv: https://docs.astral.sh/uv/
+.. _pip-tools: https://github.com/jazzband/pip-tools
+
 
 Decisions
 *********
@@ -357,7 +384,7 @@ considered.
    :maxdepth: 1
    :glob:
 
-..   oep-0067/decisions/backend/*
+   oep-0067/decisions/backend/*
 
 
 
@@ -368,11 +395,22 @@ Consequences
 
 * All ADRs under OEP-11 will be moved to be under this OEP instead.
 
+* :ref:`OEP-18 Python Dependency Management` will be superseded by the backend
+  technology recommendations in this OEP.
+
 * Future decisions for technology changes will require an ADR and an update to this OEP
 
 Change History
 **************
 
+2026-04-24
+==========
+
+* Add ``pyproject.toml`` and ``uv`` to Backend Technology Selection
+* Add backend ADR for adopting uv (replacing pip-tools)
+* Mark :ref:`OEP-18 Python Dependency Management` as superseded
+* `Pull request #784 <https://github.com/openedx/openedx-proposals/pull/784>`_
+
 2025-02-10
 ==========