This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients daniel.urban, debatem1, eric.araujo, exarkun, gdamjan, giampaolo.rodola, gregory.p.smith, heikki, jsamuel, loewis, mcrute, pitrou
Date 2010-06-18.09:37:30
SpamBayes Score 0.034424197
Marked as misclassified No
Message-id <1276853848.3338.22.camel@localhost.localdomain>
In-reply-to <AANLkTikDzsT12AbUb7zaQilonFofzqNqYQEsDQr8MtBO@mail.gmail.com>
Content
> I would suggest that we focus on defining and building a
> lower-level interface along the lines of the PEP noted earlier,
> integrating that with evpy, and getting it in shape to go into the
> stdlib.

That sounds reasonable to me.
(although I would be also content with the lower-level interface
alone :-))

> If somebody does, then perhaps a four-tiered
> model makes more sense, with the bottom one being the raw wrappers
> around the various libs, the second from the bottom being
> compatibility shims, and the top two matching the other proposal.

That sounds much too complicated.
History
Date User Action Args
2010-06-18 09:37:32pitrousetrecipients: + pitrou, loewis, gregory.p.smith, exarkun, giampaolo.rodola, gdamjan, heikki, eric.araujo, debatem1, daniel.urban, mcrute, jsamuel
2010-06-18 09:37:30pitroulinkissue8998 messages
2010-06-18 09:37:30pitroucreate