[Python-ideas] TAPS Implementation
steve at pearwood.info
Mon Dec 10 17:31:36 EST 2018
Hi Max, and welcome!
On Mon, Dec 10, 2018 at 09:47:07PM +0000, Franke, Maximilian Julian Shawn wrote:
> We are currently looking into implementing TAPS, a novel way to offer
> transport layer services to the application layer.
> TAPS is currently being standardized ...
> Here you can find the proposed architecture ...
These are factors which strongly go against TAPS being implemented in
the standard library: it is novel and the usage of it is unproven, and
it hasn't been standardized yet.
Generally speaking, the Python standard library only provides proven,
standardized protocols. A few reasons for this:
- We don't have the resources of Apple, we can't support everything,
so we have to choose those which are most likely to be useful;
that means those with a proven track-record, not experimental or
- We take backwards-compatibility seriously, so with a few exceptions,
any API we offer would have to be stable. (There are ways around
this, but we don't use them lightly.)
- The Python release cycle is relatively sedate and slow, and
experimental libraries usually need a much faster release cycle.
This is not to absolutely rule out a std lib implementation. If the
networking experts among the core developers think this is a good idea,
it could happen, regardless of how novel it is.
But in the meantime, I recommend that you consider writing a library and
offering it on PyPI as a third-party library:
If you are still keen to push for a standard library implementation, you
will probably need to write a PEP:
At the very least, reading over some successful PEPs will suggest what
sort of arguments you should make in order to get TAPS approved.
More information about the Python-ideas