[pycrypto] Pycrypto working with python 3.0 or 3.1
christoph.tapler at gmx.net
Mon Jun 21 12:56:12 CST 2010
I did a few adaptations in the test suite during the last days.
Dwayne is about to incorporate them. However, still, pycrypto is not
(yet) usable in combination with Python 3.1.
What I have experienced so far, is that there are still major issues in
the library and not only in the test suite.
I would also highly appreciate a repository for pycrypto-py3k. I would
be way easier for me to contribute (instead of generating the patches
and sending the forth and back). Is there any possibility to set up such
On 21.06.2010 13:19, Lorenz Quack wrote:
> Hi there,
> has there been further development on py3k porting?
> How about setting up a publicly accessible repository for a pycrypto-py3k branch?
> This would make it easier for others to contribute and track the porting progress.
> Dwayne, where do you stand on this? What are your plans for py3k support?
> On 04/11/2010 08:46 PM, Christoph Tapler wrote:
>> Short update - a missing string/byte conversion in the test suite caused
>> the high FAIL rate. With the conversion, the PASS/FAIL ratio looks way
>> better (>70% PASS). I assume that the rest of the FAILs have a similar
>> reason. Just tell me if some of you wants the patch.
>> -------- Original Message --------
>> Subject: Re: [pycrypto] Pycrypto working with python 3.0 or 3.1
>> Date: Sun, 11 Apr 2010 12:32:58 +0200
>> From: Christoph Tapler<christoph.tapler at gmx.net>
>> To: PyCrypto discussion list<pycrypto at lists.dlitz.net>
>> Fyi, I have adapted the test suite and now I am at least able to execute
>> it on Python 3.1. However, around 99% of all tests are fail. Moreover,
>> at the end of the test suite execution, Python crashes.
>> Hope to find some time to look into the issues. Anyway, if somebody
>> wants to have the patch, please let me know.
>> On 18.03.2010 02:57, Grail Dane wrote:
>>> Hi Christoph
>>> So I tried the suggestion below but still received the error about
>>> import from non-package :(
>>> I changed it to read:
>>> from Crypto.SelfTest.Cipher import common
>>> return common.make_block_tests(AES, "AES", test_data)
>>> and it does not error on that but now presents me with a segfault :(
>>> So I seem to have gone from bad to worse. So I am hoping someone on this
>>> list might be able to suggest how I can track the fault to find out what
>>> is wrong now??
> pycrypto mailing list
> pycrypto at lists.dlitz.net
E-Mail: christoph.tapler at gmail.com
Adresse: Langwattstrasse 36, CH - 8125 Zollikerberg
Telefon: +41 (0) 79 695 24 89
More information about the pycrypto