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-19.11:52:31
SpamBayes Score 0.0001556643
Marked as misclassified No
Message-id <1276948348.3371.0.camel@localhost.localdomain>
In-reply-to <AANLkTila7wm_4BPir7ffUqe9p0G9OZCz2hYGnMV_qOOt@mail.gmail.com>
Content
Le samedi 19 juin 2010 à 00:55 +0000, geremy condra a écrit :
> geremy condra <debatem1@gmail.com> added the comment:
> 
> On Fri, Jun 18, 2010 at 6:05 AM, Antoine Pitrou <report@bugs.python.org> wrote:
> >
> > Antoine Pitrou <pitrou@free.fr> added the comment:
> >
> >> Great, I'm thinking more-or-less the API proposed in PEP 272- the
> >> exception I'm thinking of is that 'strings' should be substituted for
> >> 'bytes'- for AES and DES. It gets trickier when talking about public
> >> key crypto, though. Perhaps something along the lines of
> >> RSA.new(public_key=None, private_key=None,...), with the resulting
> >> object supporting encrypt/decrypt/sign/verify operations?
> >
> > I don't have any opinion right now. I think a concrete proposal should
> > be initiated and we can iterate from that.
> > (that's assuming other people agree on the principle, of course)
> 
> I assume that by "a concrete proposal" you're talking about code? Or
> API docs? Also, what more needs to be done to ensure that other people
> agree on the principle?

I was thinking about a PEP. Of course, you are free to reuse existing
PEP content for that :)
History
Date User Action Args
2010-06-19 11:52:34pitrousetrecipients: + pitrou, loewis, gregory.p.smith, exarkun, giampaolo.rodola, gdamjan, heikki, eric.araujo, debatem1, daniel.urban, mcrute, jsamuel
2010-06-19 11:52:32pitroulinkissue8998 messages
2010-06-19 11:52:31pitroucreate