Currently PEP 554 states, that the idea of channels acting like queues was rejected.

I'm a bit surprised about that as single-producer-single-consumer queues (e.g. a ring buffer) are basically the most efficient known structures to share data in small batches (potentially of varying sizes in runtime) between operating system threads running on different physical CPU cores.

My question has thus 2 parts:

a) Is it expected, that Python at some point in the future will "promote" the currently single-item send() and recv() to batch variants supporting buffering? Or will this be rejected as well in the future and not implemented thus leaving Python with the same issue as in Go (see some details):

"it turns out that nearly every single team that has tried to scale golang servers has come to the same position. Give up channels as your concurrency primitives and revert to the sync package if you need to really scale golang programs"

b) Will Python add support for polling interface (poll_send(), poll_recv()) on the channels additionally to the current send() and recv() interface? Note, this does not imply support for timeouts though admittedly it could be achieved also with them.