On Thu, 2003-04-24 at 16:09, Brett Cannon wrote: > > IMO there are more important batteries to include before we deal with > > the hassle of registering for crypto stuff. Even if it's harmless, > > the inclusion of any crypto at all causes some people to have to go > > through a lot of corporate red tape. > <snip> > > Good point. I admit I think it would be cool to have an AES > implementation in the stdlib, but I don't see it as crucial. > > I think does make sense, though, to have a package that is maintained > separately that python-dev pseudo endorses (like PyXML and win32all) that > contains all of this crypto stuff. Where do we draw the line? Do we delete the ssl stuff? What about the crypto hashes? hmac? md5? mpz? All of Chapter 15 in the library reference manual? -Barry
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4