Summary of messages to the zope-tests list.
Period Fri Apr 3 12:00:00 2009 UTC to Sat Apr 4 12:00:00 2009 UTC.
There were 8 messages: 8 from Zope Tests.
Test failures
-
Subject: FAILED (failures=1) : Zope-trunk Python-2.6.1 : Linux
From: Zope Tests
Date: Fri Apr 3 20:53:14 EDT
Wichert Akkerman wrote:
Previously Marius Gedminas wrote:
BTW I've yet to see a firewall that blocks SSH. Am I lucky?
Yes. Blocking ssh is very common in larger companies in me experience.
An ssh server running on port 443 (HTTPS) can come in very handy. ssh -D
gives you a socks proxy,
Hey All,
http://pypi.python.org/pypi/zdaemon indicates that zdaemon is alpha.
I would have though it would be marked as stable, given how long its
been around?
Is there a reason for that? If not, I'll change it on trunk...
Chris
--
Simplistix - Content Management, Zope Python Consulting
My 2 cents:
I like svn over https. It works reliably, and is easy to use, and
externals work as expected, etcs.
So I'm +1 on allowing https access.
That said, svn+ssh tunnels svn over ssh, and if you are in a place
where ssh doesn't work, you need to find the network admit and punch
him in the
On Fri, Apr 3, 2009 at 7:21 PM, Wichert Akkerman wich...@wiggy.net wrote:
Previously Chris Rossi wrote:
I was wondering if the Zope collective had given any consideration to
allowing constants to be defined in interfaces. To be clear, these are
constant values that make up the protocol
Using an interface class for a constant container would often be handy but it
might be an inappropriate use of interface classes. FTR, I do often put
constants in an interfaces.py module at module scope (if there are more than
one related, sometimes in a dictionary or within a non-interface class
On Sat, Apr 4, 2009 at 6:04 PM, Chris McDonough chr...@plope.com wrote:
Using an interface class for a constant container would often be handy
but it
might be an inappropriate use of interface classes.
I would argue that it is appropriate, but that's probably related to my
experience with
Chris McDonough wrote:
FTR, I do often put
constants in an interfaces.py module at module scope (if there are more than
one related, sometimes in a dictionary or within a non-interface class
statement) in order to not feel I need to create some constants.py module.
Maybe we could just agree
Chris Rossi wrote:
from zope.interface import Constant
class IHttpResponse(Interface):
Models an HTTP 1.1 response.
HTTP_OK = Constant(200 Ok, An HTTP Ok response.)
HTTP_NOT_FOUND = Constant(404 Not Found, An HTTP Not Found response)
status = Attribute(HTTP status
