[pycrypto] Once again: Python3 with PyCrypto
sbehrens at gmx.li
Thu Dec 23 19:04:23 CST 2010
This is most vexing.
Using VC++ 2008, I can build, but not test - wrong version of VC++ for
Using gcc in cygwin, I cannot build - issue with LONG_BIT definition.
Although it's a 32-bit gcc, LONG_BIT is defined as 64, and that makes
python21 most unhappy.
Suggestions welcome. Push comes to shove, if you have a working build
environment for 2.1, maybe you can test changes. Or if you can suggest a
Linux distribution that has a working 2.1 tool-chain, I could run that
in a VM and test from there.
On 12/23/2010 6:59 PM, Thorsten Behrens wrote:
> On 12/23/2010 6:36 PM, Dwayne C. Litzenberger wrote:
>> One thing I want to be clear about is that Python 2.x compatibility
>> should go back as far as 2.1, or 2.2 at the latest. It's not
>> acceptable to tell people running 2.2 to "just upgrade to 2.6".
> Sure, I get that. I am having a hard time testing 2.1, because VC++
> 2008 doesn't seem to play well with it. Suggestions? -c cygwin?
More information about the pycrypto