From: Tim Lyons <guy.linton@gm...> - 2010-04-22 10:29:36
> 2010/4/22 St?phane Charette <stephanecharette@...>
>> This is not good. I began working on the 3.2.1 release earlier
>> tonight as I happen to have an evening where I could break free from
>> work for a few hours. Didn't know things had just recently been
> Don't blame yourself. I should have mailed the list the release was
> imminent, Doug should have reverted when he saw it then mail Rob
> and the
> list, Rob should never have committed it, ... We can pass blame
> around for a
> long time.
>> I just sent the announcement out, and now I see this e-mail thread...
>> Let me know if we're going to need a quick fix. It is nearing 2am, I
>> need to get to bed. I'll look for e-mail updates tomorrow before
> Ok, and many thanks for the release!
> Yes, the commit of Rob is inside 3.2.1:
> You made the tag on 9:12, I reverted the change on 9:28. Close.
> Doug, as you started this thread, is a quick new release 3.2.2 needed
> without commit?
> What I know now:
> 1. in python 2.5, nar web will probably not even load, if it loads,
> then it
> will crash on run (with statement import from future is removed)
Oh dear. python2.6 does not work for me on Mac OS X, and also I think
there are problems with Windows about python 2.6 being much slower
than python 2.5. This was going to be resolved I think when there was
an update to bsddb for Windows, but I don't think that is there yet.
My vote would be for a swift 3.2.1_1 or something to get it working
as before again.
> 2. you mention a bug in image regions. Is it serious?
> For 1., not many people are still running python 2.5, and if they
> do, they
> probably can only upgrade if they do it manually, so obtaining last
> from repo and overwriting the install, should not be difficult for
> users (but annoying). So that can wait some.
Not so easy for me.