Christoph Zwerschke wrote:
Ian Bicking wrote:
To me, Webware's lack of a conventional Python installation process
has always been a serious problem. There's no reason to use Webware's
distribution mechanism (which clearly is slow and error prone, which has
a lot to do with the many-year
Actually it was not only DBUtils why I asked to postpone, but I still
hadn't tested the last beta with my main application and had only time
to do it this week. So I thought it would be a better timing to have the
next beta cut one week later.
Also, before the 0.9 release, CVS reminescensces
On Sep 8, 2005, at 4:01 AM, Christoph Zwerschke wrote:
Mark, how about doing this one week earlier on September 13th? This
would give me enough time and not cause such a delay. The actual
release could follow very quickly.
Done. I will make a cut on the 13th.
I have added time on September
Christoph Zwerschke wrote:
Is there any reason that should be part of the main Webware release?
The DBUtils package is actually completely independent from Webware.
It could be used as well by other application servers or other
multi-threading environments.
But since nearly all Webware
Ian Bicking wrote:
To me, Webware's lack of a conventional Python installation process
has always been a serious problem. There's no reason to use Webware's
distribution mechanism (which clearly is slow and error prone, which has
a lot to do with the many-year delay of 0.9) when you have a
Christoph Zwerschke has new work he would like to check-in, and get
feedback from the community.
Per his request, I have postponed the next beta cut until September 20.
Mark Phillips
---
SF.Net email is Sponsored by the Better Software
Christoph's work looks very interesting, but I don't think it should
be tied to 0.9 at all. We've always faced this same situation with
past Webware releases where there are some enhancements some of us
would like to include--therefore, let's postpone the release.
One problem with this is that
Mark Phillips wrote:
Christoph Zwerschke has new work he would like to check-in, and get
feedback from the community.
Is there any reason that should be part of the main Webware release? It
seems like it should just be an independent package -- Chris can move it
to the top level of the