Sorry about the venting, but it is kind of frustrating to spend months
working on something with no feedback just to be told that it all was
for nothing.  But that's how it is.  I'll just keep updating my path
every now and then since I need it anyway and don't want my application
to fall too far behind compared to mainstream Python.

My point is mostly that that export_keying_material is starting to be
used in more IETF RFCs.  The most recent one was accepted just a few
weeks ago.  I think that is a bit of a shame that Python doesn't have
support for that functionality out of the box.  If enough people say
it's useful for them maybe that would influence your decision.

As for the rest of my mail.  Since I am trying to keep my patch sort of
up date, I might as well point to it and explain how to use it. 
Hopefully that will reduce your support burden since it will allow
those who need that functionality to build a Python interpreter on
their own.