Author jkloth
Recipients brett.cannon, jkloth, ncoghlan, serhiy.storchaka, vstinner
Date 2018-11-23.03:04:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1542942269.35.0.788709270274.issue35134@psf.upfronthosting.co.za>
In-reply-to
Content
As a heavy user of the non-limited Python C API, I would like to offer my suggestions for consideration.  (I'm not allowed to post in discourse)

First off, to me, 'unstable' comes off quite negative, i.e. risky or erratic.  Brett's suggestion of 'broad' is, well, seemingly too "broad" :)

In no particular order, some ideas:

- 'extended' or 'extra'; as opposed to limited (from the macro)

- 'volatile'; synonym for 'unstable' but with the benefit of being a C concept.  I like this one as the APIs covered by this include would have access to the "volatile" object details.  Things like borrowed references, direct array access or even the structure fields of the objects themselves.

- 'crunchy'; Monty Python reference, "If we took the bones out, it wouldn't be crunchy, would it?"
  https://en.wikipedia.org/wiki/Crunchy_Frog
History
Date User Action Args
2018-11-23 03:04:29jklothsetrecipients: + jkloth, brett.cannon, ncoghlan, vstinner, serhiy.storchaka
2018-11-23 03:04:29jklothsetmessageid: <1542942269.35.0.788709270274.issue35134@psf.upfronthosting.co.za>
2018-11-23 03:04:29jklothlinkissue35134 messages
2018-11-23 03:04:28jklothcreate