# PEP 780: ABI features as environment markers

**URL:** <https://discuss.python.org/t/pep-780-abi-features-as-environment-markers/86013>\
**Category:** Standards\
**Created:** [March 26, 2025, 10:34am UTC](https://discuss.python.org/t/pep-780-abi-features-as-environment-markers/86013 "2025-03-26T10:34:40Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![steve.dower](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/steve.dower/32/56_2.png) [@steve.dower](https://discuss.python.org/u/steve.dower)\
**Post date:** [March 26, 2025, 1:13pm UTC](https://discuss.python.org/t/pep-780-abi-features-as-environment-markers/86013/7 "2025-03-26T13:13:31Z")

</div>

> [@rgommers](#):
>
> I think this post should have had `Packaging` and `Standards` tags, rather than `PEPs`.

The PEP contains a section “Adding `sys.abi_features` to the Python Standard Library”, which requires a core PEP.

You may need to split into two PEPs to enable the packaging side of it. Though it’s possible that a PEP could be skipped if it’s literally just going to be to enable `x in sys_abi_features` on versions of the runtime where the `sys` attribute exists.

(And just to be 100% clear, I think the post was and the PEP is correctly classified, it just has to talk less about environment markers as _specification_ and move them to examples of how the new `sys.abi_features` attribute might be used.)

---

_[View the full topic](https://discuss.python.org/t/pep-780-abi-features-as-environment-markers/86013)._