[PYTHON-CRYPTO] m2crypto version confusion

[Guido van Rossum]

Amen. I really wish somebody made the time to pack up a proper release
rather than pointing people to svn or snapshot tarballs. (FWIW, I've
used 0.15, and AFAICT it's of release quality, fixing many of the
issues with 0.13.)

Oh, BTW, 0.13.1 is a bogus patch. It introduces a bug that happens to
changes the behavior in such a way that a certain memory leak no
longer occurs -- but it breaks a feature that works in 0.13. 0.15
solves both IIRC.

ISTM that M2Crypto's original author has lost interest or at least has no time.

--Guido

On 2/5/06, Patrick Dreker <patrick at dreker.de> wrote:
> Hello...
>
> I am looking into packaging m2crypto and I am slightly confused about
> the current version. http://sandbox.rulemaker.net/ngps/m2/ which looks
> like the official homepage has version 0.13 and a patch for 0.13.1 and
> calls that the "latest release".
>
> http://wiki.osafoundation.org/bin/view/Projects/MeTooCrypto on the other
> hand has a 0.15 tarball, which is declared the current release...
>
> So just to clarify the situation: Which version is the latest released
> version? Is 0.15 a devel snapshot, or is it really a release?
>
> Thanks in advance,
> Patrick
>
>
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFD5qzQcERm2vzC96cRArYJAJ9ZeNHiKXieu115nXTfhXFWC0cYYACghRb0
> 7Whrbyn4O7YMU4gTYdI05k8=
> =x3NF
> -----END PGP SIGNATURE-----
>
>
>


--
--Guido van Rossum (home page: http://www.python.org/~guido/)