Re: Anyone depending on M2Crypto and Python < 2.3?

Heikki,

I think the most prudent way to decide whether to make Python 2.3 or
greater a requirement is to check which platforms have not yet
upgraded. I don't see a reason why M2Crypto should maintain support
for a release that is not being similarly supported by its vendor.

I know that the last SUSE Linux release to ship with Python 2.2 was
release 8.2, which has been discontinued and is unsupported. I think
that at least FreeBSD and Red Hat's supported releases also have at
least Python 2.3; not sure about others, but seeing as Python 2.3 was
released almost 2 years ago, I think it is safe to assume that anyone
with reason enough to stay with an old release also has reason enough
to either patch M2Crypto or build a recent Python release. :)

Cheers,
-- 
Scott Moynes
"The purpose of computing is insight, not numbers." - Richard W. Hamming

On 5/27/05, Heikki Toivonen <[email protected]> wrote:
> I could make an isolated change to just the callbacks functions, and
> ifdef things so that callbacks would be just as broken as they are now
> for Python < 2.3, and make them work for later Python versions.
> 
> Or I could do a complete overhaul which would make M2Crypto depend on
> Python >= 2.3. I actually prefer this solution so hoping nobody is
> depending on old Python. Here's how: