[pycrypto] FW: python crypto with python 3.0 or 3.1

Grail Dane grail69 at hotmail.com
Tue Mar 2 03:28:40 CST 2010

Hi Christoph

I did a quick search and found this:


diff is what is used to create the patch file. You then simply need to run patch to execute it on the necessary files.

Hope that helps.

If you still need help on fixing the issues let me know and I will see what I can do :)


Date: Mon, 1 Mar 2010 21:37:42 +0100
From: christoph.tapler at gmx.net
To: pycrypto at lists.dlitz.net
Subject: Re: [pycrypto] FW: python crypto with python 3.0 or 3.1


Hi Grail!

I think in you need to return the pointer from the newly created
module. Currently the return value seems to be a dangling pointer.

A "return m" at the end of the generic init function in
block_template.c may help.

Btw, in Windows, there are still a few issues which prevent successful

Should I generate a patch? If yes, could you probably give me a hint
how to generate this patch?

Btw, there seems to be a test suite included (python setup.py test).
However, at that stage it is not too much of 

help, because the test suite itself needs to be adapted as well. In
Python 2 the test suite works perfectly fine.



On 01.03.2010 01:02, Grail Dane wrote:


  I have made more head way since that one (and made a lot more
  I found that the module creation required a few more steps and I
have come up 
  with two solutions (in attached patches):

  1. First patch follows most of the online info I could find
related to PyModuleDef and the related PyTypeObject.
     This required that all tp_getattr functions be removed and
set to 0 (zero) in the PyTypeObject definition.

  2. The second patch retained the already created tp_getattr

  With either applied I am able to compile but when running a test
program with the following lines only:

  #!/usr/bin/env python

  from Crypto.Cipher import AES
  import base64
  import os


  When run I receive the following error:

  Traceback (most recent call last):
    File "./cypher.py", line 3, in <module>
      from Crypto.Cipher import AES
  SystemError: NULL result without error in PyObject_Call

  So apply patches (and make necessary changes for Windows) and we
will see if I can help further :)

  Cheers Grail


  Get straight to the Point Find a great
deal on your next car. 

   Browse profiles for free! View
photos of singles in your area.
pycrypto mailing list
pycrypto at lists.dlitz.net

Looking for a new home? With all the latest places, searching has never been easier.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.dlitz.net/pipermail/pycrypto/attachments/20100302/6f5ea7a8/attachment.htm 

More information about the pycrypto mailing list