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 -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
