[pycrypto] Pycrypto working with python 3.0 or 3.1

[Lorenz Quack]

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?

cheers,
//Lorenz



On 04/11/2010 08:46 PM, Christoph Tapler wrote:
> Hi,
>
> 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.
>
> Cheers,
> Christoph
>
> -------- 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>
>
> Hi,
>
> 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.
>
> Cheers,
> Christoph
>
> 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??
>>
>> Cheers
>> Grail
>