# Choice of complex buffer protocol format intentional break with PEP?

**URL:** <https://discuss.python.org/t/choice-of-complex-buffer-protocol-format-intentional-break-with-pep/106949>\
**Category:** Core Development\
**Created:** [April 13, 2026, 6:54am UTC](https://discuss.python.org/t/choice-of-complex-buffer-protocol-format-intentional-break-with-pep/106949 "2026-04-13T06:54:42Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![pitrou](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/pitrou/32/28_2.png) [@pitrou](https://discuss.python.org/u/pitrou)\
**Post date:** [April 13, 2026, 5:10pm UTC](https://discuss.python.org/t/choice-of-complex-buffer-protocol-format-intentional-break-with-pep/106949/10 "2026-04-13T17:10:53Z")

</div>

> [@skirpichev](#):
>
> > [@pitrou](#):
> >
> > This is obviously incompatible with PEP 3118
> 
> That seems to be not true, per SC decision.

Which SC decision are you talking about?

> [@](#):
>
> > [@pitrou](#):
> >
> > This PEP is implemented by many third-party packages
> 
> I asked above where it was implemented the part of this proposal, related to long doubles. I suspect — nowhere. But maybe you know.

I have no idea about long doubles, but how is that related to complex floats and doubles (which _are_ implemented)?

> [@skirpichev](#):
>
> Should we then apply same policy to the struct module? Its type codes used by the memoryview. To ctypes?

That’s a lot of whataboutism, isn’t it?

In any case: PEP 3118 specifies the semantics of the _buffer protocol_. Any type implementing the buffer protocol should follow the conventions specified by PEP 3118. That is the case of the `memoryview` object and of the `array.array` object as well.

Whether or not the `struct` module should use the same conventions as the buffer protocol is a separate decision.

---

_[View the full topic](https://discuss.python.org/t/choice-of-complex-buffer-protocol-format-intentional-break-with-pep/106949)._
