path: root/pipermail/pycrypto/attachments/20131031/8f35bc3d/attachment-0001.html

<tt>
&lt;div&nbsp;dir=&quot;ltr&quot;&gt;&lt;div&nbsp;class=&quot;gmail_quote&quot;&gt;&lt;div&nbsp;dir=&quot;ltr&quot;&gt;Hi&nbsp;Dwayne&nbsp;and&nbsp;everyone,&nbsp;&lt;br&gt;&lt;br&gt;<br>
&gt;1.&nbsp;How&nbsp;many&nbsp;of&nbsp;you&nbsp;would&nbsp;really&nbsp;care&nbsp;if&nbsp;PyCrypto&nbsp;2.6&nbsp;was&nbsp;that&nbsp;last&lt;br&gt;<br>
&gt; &nbsp; &nbsp;version&nbsp;to&nbsp;support&nbsp;legacy&nbsp;versions&nbsp;of&nbsp;Python?&nbsp; By&nbsp;&quot;legacy&quot;,&nbsp;I&nbsp;mean&lt;br&gt;&gt;&nbsp; &nbsp;all&nbsp;versions&nbsp;of&nbsp;Python&nbsp;that&nbsp;are&nbsp;NOT&nbsp;one&nbsp;of&nbsp;these:&lt;br&gt;<br>
&lt;br&gt;<br>
&gt; &nbsp;  &nbsp;-&nbsp;Python&nbsp;2.6.x&lt;br&gt;<br>
&gt; &nbsp;  &nbsp;-&nbsp;Python&nbsp;2.7.x&lt;br&gt;&gt;&nbsp;  &nbsp;-&nbsp;Python&nbsp;3.3&nbsp;and&nbsp;above.&lt;br&gt;<br>
&lt;br&gt;<br>
&gt; &nbsp; &nbsp;I&#39;d&nbsp;continue&nbsp;to&nbsp;make&nbsp;bugfix&nbsp;releases&nbsp;of&nbsp;PyCrypto&nbsp;2.6.x,&nbsp;but&nbsp;add&nbsp;no&lt;br&gt;<br>
&gt; &nbsp; &nbsp;more&nbsp;substantial&nbsp;new&nbsp;features.&lt;br&gt;<br>
&lt;br&gt;+1&nbsp;for&nbsp;that,&nbsp;assuming&nbsp;it&nbsp;will&nbsp;make&nbsp;other&nbsp;efforts&nbsp;in&nbsp;PyCrypto&nbsp;easier.&nbsp;&lt;br&gt;&lt;br&gt;<br>
&gt;2.&nbsp;I&#39;m&nbsp;thinking&nbsp;of&nbsp;pulling&nbsp;in&nbsp;additional&nbsp;dependencies&nbsp;(e.g.&nbsp;cffi),&lt;br&gt;<br>
&gt; &nbsp; &nbsp;requiring&nbsp;setuptools,&nbsp;and&nbsp;basically&nbsp;joining&nbsp;what&nbsp;the&nbsp;rest&nbsp;of&nbsp;the&lt;br&gt;&gt;&nbsp; &nbsp;Python&nbsp;community&nbsp;is&nbsp;doing&nbsp;in&nbsp;2013.&lt;br&gt;<br>
&lt;br&gt;Like&nbsp;people&nbsp;said&nbsp;before&nbsp;me,&nbsp;it&nbsp;seems&nbsp;very&nbsp;immature,&nbsp;and&nbsp;Cython&nbsp;is&nbsp;not&nbsp;a&nbsp;bad&nbsp;alternative&nbsp;at&nbsp;all.&nbsp;&lt;br&gt;There&nbsp;is&nbsp;a&nbsp;lot&nbsp;of&nbsp;know&nbsp;how&nbsp;out&nbsp;there&nbsp;with&nbsp;Cython.&nbsp;I&nbsp;would&nbsp;be&nbsp;willing&nbsp;to&nbsp;help&nbsp;with&nbsp;the&nbsp;efforts.&nbsp;&lt;br&gt;&lt;br&gt;&lt;br&gt;<br>
&gt;3.&nbsp;What&nbsp;if&nbsp;src/*.c&nbsp;were&nbsp;removed,&nbsp;and&nbsp;any&nbsp;relevant&nbsp;C&nbsp;code&nbsp;moved&nbsp;into&nbsp;an&lt;br&gt;<br>
&gt; &nbsp; &nbsp;independent&nbsp;library,&nbsp;which&nbsp;could&nbsp;be&nbsp;loaded&nbsp;using&nbsp;cffi?&nbsp; (This&nbsp;is&lt;br&gt;&gt;&nbsp; &nbsp;basically&nbsp;what&nbsp;we&nbsp;need&nbsp;to&nbsp;do&nbsp;to&nbsp;support&nbsp;PyPy&nbsp;properly.)&lt;br&gt;<br>
&lt;br&gt;An&nbsp;independent&nbsp;library,&nbsp;sounds&nbsp;good.&nbsp;But&nbsp;it&nbsp;seems&nbsp;that&nbsp;Cython&nbsp;supports&nbsp;pypy&nbsp;too.&nbsp;&lt;br&gt;&lt;br&gt;<br>
&gt;4.&nbsp;What&nbsp;if&nbsp;Crypto.*&nbsp;became&nbsp;a&nbsp;wrapper&nbsp;around&nbsp;some&nbsp;other&nbsp;crypto&nbsp;library?&lt;br&gt;<br>
&lt;br&gt;Why&nbsp;?&nbsp;what&nbsp;is&nbsp;the&nbsp;benefit&nbsp;here?&lt;br&gt;&lt;br&gt;<br>
&gt;5.&nbsp;The&nbsp;Apache&nbsp;License&nbsp;2.0.&nbsp; What&nbsp;if&nbsp;PyCrypto&nbsp;were&nbsp;licensed&nbsp;under&nbsp;it,&nbsp;or&lt;br&gt;<br>
&gt; &nbsp; &nbsp;included&nbsp;dependencies&nbsp;that&nbsp;are&nbsp;licensed&nbsp;under&nbsp;it?&lt;br&gt;<br>
&lt;br&gt;As&nbsp;the&nbsp;maintainer&nbsp;of&nbsp;a&nbsp;small&nbsp;project&nbsp;and&nbsp;humble&nbsp;project&nbsp;(pwman3)&nbsp;that&nbsp;uses&nbsp;pycrypto,&nbsp;and&nbsp;it&nbsp;is&lt;br&gt;licensed&nbsp;unde&nbsp;GPL&nbsp;I&nbsp;would&nbsp;have&nbsp;a&nbsp;problem&nbsp;with&nbsp;it.&nbsp;I&nbsp;think&nbsp;the&nbsp;better&nbsp;choice&nbsp;would&nbsp;be&nbsp;LGPL,&nbsp;as&nbsp;said&lt;br&gt;also&nbsp;before&nbsp;me.&nbsp;&lt;br&gt;<br>
<br>
<br>
 &nbsp;&lt;br&gt;<br>
I&nbsp;would&nbsp;love&nbsp;to&nbsp;have&nbsp;support&nbsp;for&nbsp;pypi,&nbsp;pip&nbsp;and&nbsp;setuptools,&nbsp;until&nbsp;now&nbsp;installing&nbsp;pycrypto&nbsp;&lt;br&gt;was&nbsp;always&nbsp;a&nbsp;pain.&nbsp;&lt;br&gt;&lt;br&gt;Best&nbsp;Regards,&nbsp;&lt;br&gt;Oz&lt;br&gt;&lt;/div&gt;<br>
&lt;/div&gt;&lt;br&gt;&lt;/div&gt;<br>

</tt>