[pycrypto] Wanted: Additional unit tests for Python 3.x porting effort

[Thorsten Behrens]

Crypto.Random.random has unit tests now. A few notes on that:
     - random.shuffle() was broken, it had a TypeError and an 
IndexError. Not my doing, that's always been the case. That's been fixed.
     - random.sample() does not work on 2.1. Not my doing, that's always 
been the case. I will not fix this. Others are welcome to.
     - random does not implement the full compliment of functions that 
Python offers, it is a much smaller subset
     - I somehow doubt anyone ever actually used this interface. We may 
declare it "static for backwards compatibility" and leave well enough alone.

I will not write unit tests for qNEW, though others are welcome to.

We still need unit tests for ElGamal and AllOrNothing. Anyone?

Thorsten

On 12/29/2010 4:28 PM, Thorsten Behrens wrote:
> Now that we have a working pycrypto on Python 3.x, it's time to see what
> we don't have unit tests for. See
> https://bugs.launchpad.net/pycrypto/+bug/335995 for results.
>
> Currently, the following are not included in unit testing at all:
>
> Protocol/AllOrNothing
> PublicKey/ElGamal
> PublicKey/qNEW
> random/random
>
> I'd love some unit tests for those. With public test vectors, please,
> not test vectors derived from pycrypto.
>
> Volunteers?
>
> Thorsten
>
> _______________________________________________
> pycrypto mailing list
> pycrypto at lists.dlitz.net
> http://lists.dlitz.net/cgi-bin/mailman/listinfo/pycrypto
>