Marc 'HE' Brockschmidt wrote: > Piotr Ozarowski <firstname.lastname@example.org> writes: > > Marc 'HE' Brockschmidt wrote: > >> Piotr Ozarowski <email@example.com> writes: > >>> 0.3.2 and 0.3.3 upstream releases were mainly a bug fix releases (one > >>> very important MySQL related bug was fixed) - they're available in > >>> experimental since few weeks and no bugs were reported (except one about > >>> new upstream version being available). > >> I feel the diff is too big. Is there a bug in the version currently in > >> etch that needs to be fixed urgently? > > reported? No, but python-turbogears users who are using SQLAlchemy > > (SQLObject is default) and MySQL will need it. > > So this will only affect users of a special, non-default flavour? SQLAlchemy is getting more popular every day. It's more powerful than SQLObject and Python frameworks/app. are using it as default or are adding support for it (Django, Pylons, TurboGears - these are most popular Python web frameworks and all can use SA, only TurboGears will be in Etch though). I will also backport Griffith 0.9 (when we will release final version) after Etch release and thus I'm interested in having SA in more stable/faster version than 0.3.1. GNU Mailman's author is moving to SQLAlchemy as well. > > Please note that there is new documentation.html file in 0.3.2 (1 225 > > 964 bytes!) > > Yes, but that's not the only change. A big diff is, for a freeze > exception, everything with more than 100 lines of code that were > changed. As I said before, debdiff is large (2 new upstreams) but these versions are well tested. 0.3.4 will be released in the near future, but it doesn't contain critical fixes, see changelog   http://www.sqlalchemy.org/trac/browser/sqlalchemy/trunk/CHANGES -- :wq!
Description: PGP signature