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, dmalcolm, eric.araujo, exarkun, georg.brandl, giampaolo.rodola, gregory.p.smith, heikki, jsamuel, lemburg, loewis, lorph, mcrute, pitrou, vstinner
Date 2010-10-14.11:33:40
SpamBayes Score 3.4305838e-06
Marked as misclassified No
Message-id <1287056015.3343.3.camel@localhost.localdomain>
In-reply-to <1287055360.18.0.806196401183.issue8998@psf.upfronthosting.co.za>
Content
> I've been in touch with the copyright holders of pyOpenSSL and they
> all were positive about contributing the code to the PSF under a
> contributor agreement.
> So how should we go about this ? Open a new ticket ?

I would like to see public discussion about this, especially in the
light of the ssl module improvements in Python 3.2. It is not obvious
that duplicate APIs in the stdlib are a good idea, especially when they
are not compatible with each other. It also means that the current
pyOpenSSL maintainer (Jean-Paul) should agree to do maintenance directly
in the stdlib rather than in a separate repo.

> The idea would then be to add the crypto routines to pyOpenSSL and
> have that added to the stdlib as say openssl package.

This sounds a bit ridiculous. Why not add the crypto routines directly
to the stdlib?
History
Date User Action Args
2010-10-14 11:33:43pitrousetrecipients: + pitrou, lemburg, loewis, georg.brandl, gregory.p.smith, exarkun, vstinner, giampaolo.rodola, lorph, heikki, eric.araujo, debatem1, dmalcolm, daniel.urban, mcrute, jsamuel
2010-10-14 11:33:40pitroulinkissue8998 messages
2010-10-14 11:33:40pitroucreate