# OEP-67 Update: Add uv and pyproject.toml as backend Python standards

**URL:** <https://discuss.openedx.org/t/oep-67-update-add-uv-and-pyproject-toml-as-backend-python-standards/18857>\
**Category:** Architecture\
**Created:** [April 24, 2026, 2:43pm UTC](https://discuss.openedx.org/t/oep-67-update-add-uv-and-pyproject-toml-as-backend-python-standards/18857 "2026-04-24T14:43:22Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![feanil](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/feanil/32/37_2.png) [@feanil](https://discuss.openedx.org/u/feanil)\
**Post date:** [April 24, 2026, 2:43pm UTC](https://discuss.openedx.org/t/oep-67-update-add-uv-and-pyproject-toml-as-backend-python-standards/18857/1 "2026-04-24T14:43:22Z")

</div>

I’ve opened a PR to update OEP-67 (Standard Tools and Technologies) with two new backend technology entries:

- **pyproject.toml** (PEP 621/735) as the standard way to declare project metadata and dependencies
- **uv** as the standard tool for Python dependency locking and virtual environment management

This would replace the pip-tools workflow described in OEP-18, which would be archived as “Replaced.”

The PR includes a backend ADR with full context, rejected alternatives, and examples: [OEP-67: Add uv and pyproject.toml as backend standards, archive OEP-18 by feanil · Pull Request #784 · openedx/openedx-proposals · GitHub](https://github.com/openedx/openedx-proposals/pull/784)

I’d appreciate any feedback or concerns — please comment on the PR.