diff options
Diffstat (limited to 'pipermail/pycrypto/attachments/20131030/fecad754/attachment.html')
-rw-r--r-- | pipermail/pycrypto/attachments/20131030/fecad754/attachment.html | 63 |
1 files changed, 63 insertions, 0 deletions
diff --git a/pipermail/pycrypto/attachments/20131030/fecad754/attachment.html b/pipermail/pycrypto/attachments/20131030/fecad754/attachment.html new file mode 100644 index 0000000..81088df --- /dev/null +++ b/pipermail/pycrypto/attachments/20131030/fecad754/attachment.html @@ -0,0 +1,63 @@ +<tt> +<div dir="ltr">I think you're going to get mostly anecdotal answers to this, fairly personal to whoever is answering it, but here's what I consider important:<div><ul style><li style>Clean, modern, easy-to-use API (that limits your ability to accidentally misuse stuff)</li><br> +<li style>Modularity</li><li style>Rapid development/developer-friendly codebase</li><li style>Nice documentation (willing to contribute to this personally)</li><li style>Elliptic curve cryptography (ECC)</li><li style>Ability to install via pip, even on machines that don't already have libsomething installed.</li><br> +</ul><div style>Conversely, I don't care about the following (although some/many probably will):</div></div><div style><ul style><li style>Backwards compatibility. As long as there's documentation, I'd rather deal with the byproducts of progress than a crippled interface.</li><br> +<li style>Distro packaging.</li><li style>Internal details of how PyCrypto works, as long as it fulfills the above wishlist.</li><li style>Legacy Python versions (your definition matches mine).</li><li style>License, so long as I can use it from an LGPL package (which seems compatible with Apache2)</li><br> +</ul><div style><br></div><div style>Hopefully this feedback helps!</div><div style><br></div><div style>Philip Horger</div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Oct 29, 2013 at 11:58 PM, Dave Pawson <span dir="ltr"><<a href="mailto:dave.pawson@gmail.com" target="_blank">dave.pawson@gmail.com</a>></span> wrote:<br><br> +<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 30 October 2013 06:09, Dwayne Litzenberger <<a href="mailto:dlitz@dlitz.net">dlitz@dlitz.net</a>> wrote:<br><br> +<br> +<br><br> +> 1. How many of you would really care if PyCrypto 2.6 was that last<br><br> +> version to support legacy versions of Python? By "legacy", I mean all<br><br> +> versions of Python that are NOT one of these:<br><br> +><br><br> +> - Python 2.6.x<br><br> +> - Python 2.7.x<br><br> +> - Python 3.3 and above.<br><br> +><br><br> +> I'd continue to make bugfix releases of PyCrypto 2.6.x, but add no<br><br> +> more substantial new features.<br><br> +<br><br> +</div>For some reason, Fedora is still pushing Python 2.7, so I'd be happy<br><br> +with this position.<br><br> +<div class="im"><br><br> +<br><br> +<br><br> +<br><br> +> 4. What if Crypto.* became a wrapper around some other crypto library?<br><br> +<br><br> +</div>What logic please?<br><br> +<div class="im"><br><br> +<br><br> +<br><br> +> Of particular concern is FOSS distributors packaging PyCrypto (e.g. Linux<br><br> +> distros, *BSD ports trees, MacPorts/HomeBrew, etc.), and anything else that<br><br> +> might impact a large number of downstream end-users.<br><br> +<br><br> +</div>Fedora seems a long way behind with the Python versions.<br><br> +<div class="im"><br><br> +<br><br> +><br><br> +> I'm beginning to wonder how the risk of downstream forks compares to the<br><br> +> risks that users face when developers still don't have a highly-visible,<br><br> +> easy-to-use Python crypto API. It might be better to merge PyCrypto with<br><br> +> one or more other Python crypto libraries...<br><br> +<br><br> +</div>I'll leave that to the more knowledgable.<br><br> +My position is I'm grateful for the code - meets my needs.<br><br> +<br><br> +regards<br><br> +<span class="HOEnZb"><font color="#888888"><br><br> +<br><br> +--<br><br> +Dave Pawson<br><br> +XSLT XSL-FO FAQ.<br><br> +Docbook FAQ.<br><br> +<a href="http://www.dpawson.co.uk" target="_blank">http://www.dpawson.co.uk</a><br><br> +</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br><br> +pycrypto mailing list<br><br> +<a href="mailto:pycrypto@lists.dlitz.net">pycrypto@lists.dlitz.net</a><br><br> +<a href="http://lists.dlitz.net/cgi-bin/mailman/listinfo/pycrypto" target="_blank">http://lists.dlitz.net/cgi-bin/mailman/listinfo/pycrypto</a><br><br> +</div></div></blockquote></div><br></div><br> + +</tt> |