# Implementation of swapped marker order

**URL:** <https://discuss.python.org/t/implementation-of-swapped-marker-order/107060>\
**Category:** Standards\
**Created:** [April 22, 2026, 4:08pm UTC](https://discuss.python.org/t/implementation-of-swapped-marker-order/107060 "2026-04-22T16:08:57Z")\
**Posts on this page:** 1\
**Showing post:** 22

<div class="post-metadata">

**Author:** ![konstin](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/konstin/32/20207_2.png) [@konstin](https://discuss.python.org/u/konstin)\
**Post date:** [April 24, 2026, 5:13pm UTC](https://discuss.python.org/t/implementation-of-swapped-marker-order/107060/22 "2026-04-24T17:13:40Z")

</div>

From my perspective, writing a text clarification PR (such as [Attempt to clarify environment marker evaluation by ncoghlan · Pull Request #1988 · pypa/packaging.python.org · GitHub](https://github.com/pypa/packaging.python.org/pull/1988)) and writing a full PEP (with format, editing, core dev sponsor, submission, pre-merge iterations, approval, separate DPO thread, and then finally still the [packaging.python.org](http://packaging.python.org) PR, which may require clarifications different than the PEP) are a massive difference in burden, especially if the alternative is making an (undocumented) decision at tool level.

---

_[View the full topic](https://discuss.python.org/t/implementation-of-swapped-marker-order/107060)._