Re: Future Formencode releases

Am 14.09.2012 18:00, schrieb Chris Lambacher:
> RHEL6 looks like it supports 2.5 and 2.6 would you then need 2.5 support or
> your app would work with the latest version available on the system OS?

RHEL 6 provides only Python 2.6.

MediaCore works on Python 2.4-2.7 (whatever the user chooses). The main
difficulty is that it's software installed by random users on their various
environments. And it turns out a number of hosts still only provide 2.4
(usually on RHEL/CentOS 5).

> I'll do a maintenance branch for 1.2 before we start on 1.3 and we can
> continue to do bugfix releases but maybe people using older versions Python
> should start pinning their versions or FormEncode to < 1.3 so that you don't
> get version that don't work for you on PyPI.

Version pinning is no problem for MediaCore, that was done by the old
maintainers anyway (we host all dependencies on the project server so also
Pypi downtime does not affect users).

A stable 1.2 branch with security fixes only would be actually great solution
to us!

> I want to have a mixed 2.x 3.x code base and not have to deal with 2to3 and
> some of the things you need to do to make it work with older versions of
> Python (like
> <http://docs.pythonsprints.com/python3_porting/py-porting.html#handling-exceptions>)
> are not pretty. Making 2.6 be the lowest supporte version make things much
> simpler.

I didn't have any troubles using 2to3 on a code base and thus supporting
Python 2.3 - 3.2. The only real PITA is doctests which are (IMHO) not
portable. Heck, I even had troubles for different versions of Python 2.x when
the repr output for a class changed (Decimal in 2.4 vs. 2.5+).


fs


------------------------------------------------------------------------------
Got visibility?
Most devs has no idea what their production app looks like.
Find out how fast your code is with AppDynamics Lite.
http://ad.doubleclick.net/clk;262219671;13503038;y?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html