Thorsten Behrens added the comment:
I can test this for 3.1, as all I have is the Express version of VC++. If you
could point me towards a library that will work with 3.1 and has C components,
that'll make the testing a lot easier. pycrypto and setuptools, the two libs
mentioned in
Thorsten Behrens added the comment:
You are right, this is not a bug in Python. The diff provides a workaround for
a limitation in VC++ 2008 Express. This diff is a piece of user service.
An equally as workable workaround is for the user to copy VC\bin\vcvars64.bat
into VC\bin\amd64
Thorsten Behrens added the comment:
Thank you for that patch, Stefan. I am currently tinkering with bringing
pycrypto to 3.x and ran into this issue. initfunc2.patch resolves the issue on
Win7-64, python31-64.
I don't feel comfortable releasing code that requires the user to manually
New submission from Thorsten Behrens :
The documentation titled "Building C and C++ Extensions on Windows" at
http://docs.python.org/py3k/extending/windows.html shows a Python 2.x way of
handling static type object initializers, to whit:
>>
If your module creates a new ty
Thorsten Behrens added the comment:
Confirmed that this issue exists on Python 3.1 and 3.2b2. The exception thrown
presents as:
ValueError: ['path', 'include', 'lib']
--
___
Python tracker
<
New submission from Thorsten Behrens :
The documentation for hashlib.hash.digest() states that digest() will "[r]eturn
the digest of the data passed to the update() method so far. This is a bytes
array of size digest_size[...]".
The returned object is of class 'bytes&#
