Hi,
Am Samstag, den 07.05.2005, 12:56 -0400 schrieb Tim Peters:
Both appear to be due to that Zope 2.7.6 on Windows shipped with a
wrong (too old) version of pywin32, and continued to repackage pywin32
in the old (certifiably insane 0.7 wink) flat way.
Mark Hammond submitted patches to
Philipp von Weitershausen wrote:
Martijn Faassen wrote:
yuppie wrote:
By the way, I've just merged in Five 1.0 into Zope 2.8 (which was a
significant amount of work, due to all kinds of copyright headers
being different).
Can't we use the same headers for Five 1.0 and Zope 2.8? Both
releases
Andreas Jung wrote:
in agreement with Jim Fulton and Brian Lloyd we decided to put the
Zope 2.8 release on hold for now. There are several open issues
related to running Zope on Windows (building, startup problems).
Since we need to have a stable source code release and a stable
windows release
--On Montag, 9. Mai 2005 14:59 Uhr +0200 Martijn Faassen
[EMAIL PROTECTED] wrote:
Andreas Jung wrote:
in agreement with Jim Fulton and Brian Lloyd we decided to put the
Zope 2.8 release on hold for now. There are several open issues
related to running Zope on Windows (building, startup
Derrick Hudson wrote:
On Sun, May 08, 2005 at 02:28:55PM +0200, yuppie wrote:
| Hi!
|
| On Windows, this 15 months old change in ZConfig sets the default
| hostname for inet_address to 'localhost':
|
| http://svn.zope.org/ZConfig/?rev=376view=rev
|
| I have no idea why this was changed, the
On 5/9/05, yuppie [EMAIL PROTECTED] wrote:
But I still believe it was wrong to change the 'inet_address' datatype
in ZConfig.
I spoke with Tim about this briefly today, and I can't remember the
reasons for some of the relevant changes. I suspect at this point
that putting less magic in the
