dropping python 2.4 support for pyramid 1.1

[Chris McDonough]

Hi all,

I'm leaning towards dropping support for Python 2.4 in Pyramid 1.1.

Here are some reasons:

- Chameleon 2 is Python 2.5 and better, meaning that
unless you pin Chameleon version 1 in your Pyramid
application's setup.py, you *have* to use Python 2.5+.

- Maintenance and support for 2.4 is becoming burdensome
when attempting to add newer features. For example, 2.4
doesn't allow exceptions to be new-style classes, making
it impossible to have an exception class which is also a
Webob Response object (this pattern has become desirable
lately for exception views).

Work towards Python 3 compatibility is happening now as part of the
Google Summer of Code project. It's expected that the outcome of that
will feed into what will eventually become Pyramid 2. It's going to be
true that Pyramid 2.X *definitely* won't be compatible with Python 2.4
(and maybe not even with Python 2.5, depending on how hard it is to
achieve). I had hoped to keep Pyramid 1.X 2.4 compatible in the
meantime if I could help it, but it's becoming more of a burden than I
expected.

If anyone is truly passionate about having a Pyramid 1.1 that supports
Python 2.4, I'd like to hear your reasoning (non-theoretical,
directly-hurts-me-to-not-have-2.4-spport reasoning, preferably).

- C

[Sebastien Douche]

On Sun, May 29, 2011 at 06:50, Chris McDonough <chr...@plope.com> wrote:
> It's going to be
> true that Pyramid 2.X *definitely* won't be compatible with Python 2.4
> (and maybe not even with Python 2.5, depending on how hard it is to
> achieve).  I had hoped to keep Pyramid 1.X 2.4 compatible in the
> meantime if I could help it, but it's becoming more of a burden than I
> expected.

+1000. Python2 4 is not maintained anymore (will be the case with
Python 2.5 at the end of the year).

--
Sebastien Douche <sdo...@gmail.com>
Twitter: @sdouche (agile, lean, python, git, open source)

[Rocky Burt]

Python 2.4 not getting any future patches/releases?  Yeah I would say any Python version not being officially maintained by the Python community shouldn't be supported by Pyramid.

[Sebastien Douche]

On Sun, May 29, 2011 at 16:36, Rocky Burt <rocky...@gmail.com> wrote:
> Python 2.4 not getting any future patches/releases?

Ya, the branche is closed:

[~/src/cpython]$ hg branches -c
default 70502:76e9c3e876d4
2.7 70480:6e4be7a0cda5
3.2 70496:f290cba000ec (inactive)
3.1 70494:dba9d9dea06c (inactive)
2.6 70460:23340842e920 (inactive)
2.5 70459:0072a98566c7 (inactive)
3.0 68249:4cd9f5e89061 (closed)
legacy-trunk 68241:b77918288f7d (closed)
2.4 68239:ceec209b26d4 (closed)
2.3 68237:364638d6434d (closed)
2.2 68235:61b0263d6881 (closed)
2.1 68233:e849d484029f (closed)
2.0 68231:5fd74354d73b (closed)

2.5 is closed in few months.