# Not using structseq in sys?

**URL:** <https://discuss.python.org/t/not-using-structseq-in-sys/109328>\
**Category:** Committers\
**Created:** [October 2, 2026, 10:30pm UTC](https://discuss.python.org/t/not-using-structseq-in-sys/109328 "2026-10-02T22:30:10Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![brettcannon](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/brettcannon/32/34895_2.png) [@brettcannon](https://discuss.python.org/u/brettcannon)\
**Post date:** [October 2, 2026, 10:30pm UTC](https://discuss.python.org/t/not-using-structseq-in-sys/109328/1 "2026-10-02T22:30:10Z")

</div>

I want to add `sys._wasi_info`, but I noticed that everything in sys which stores any structured data uses structseq. But since `sys._wasi_info` will be new there’s no need to support an index API. And yet it almost feels weird not using structseq since everything else in that module does it that way.

Are there any objections to **not** using structseq?

---

<div class="post-metadata">

**Author:** ![guido](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/guido/32/21_2.png) [@guido](https://discuss.python.org/u/guido)\
**Post date:** [October 3, 2026, 12:04am UTC](https://discuss.python.org/t/not-using-structseq-in-sys/109328/2 "2026-10-03T00:04:01Z")

</div>

Don’t you worry that _someday_, _someone_ will file a bug saying they’d like to use the index API on this object, but, unlike every other struct in sys, it doesn’t support it?

---

<div class="post-metadata">

**Author:** ![stoneleaf](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/stoneleaf/32/88_2.png) [@stoneleaf](https://discuss.python.org/u/stoneleaf)\
**Post date:** [October 3, 2026, 6:22pm UTC](https://discuss.python.org/t/not-using-structseq-in-sys/109328/3 "2026-10-03T18:22:49Z")

</div>

> [@guido](#):
>
> Don’t you worry that …

😆

---

<div class="post-metadata">

**Author:** ![vstinner](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/vstinner/32/15130_2.png) [@vstinner](https://discuss.python.org/u/vstinner)\
**Post date:** [October 3, 2026, 11:08pm UTC](https://discuss.python.org/t/not-using-structseq-in-sys/109328/4 "2026-10-03T23:08:49Z")

</div>

IMO it’s a good thing to add the tuple API to new `sys` members (so not use structseq). We can add it later, if someone comes with a good use case for it.

I proposed to deprecate the tuple API of existing sys objects, but multiple users asked to keep it: [Deprecate the tuple API (object[index]) of structseq objects like os.stat\_result](https://discuss.python.org/t/deprecate-the-tuple-api-object-index-of-structseq-objects-like-os-stat-result/108464).