Hi, as suggested in #zope3-dev I'll post my experiences with interface
invariants and formlib here.
I have an interface with two password fields which should be equal:
class IUser(Interface):
password=zope.schema.Password(title=u"password")
password2=zope.schema.Password(title=u"password
On Monday 30 January 2006 02:23, Andrew Bennetts wrote:
> On Sat, Jan 28, 2006 at 09:44:44PM +, Michael Kerrin wrote:
> > Hi All,
> >
> > I have just fixed issue #533 and it just reminded me that I have some
> > test for the twisted ftp server written using the Twisted trial testing
> > frame
On Mon, Jan 30, 2006 at 11:07:50AM +, Michael Kerrin wrote:
> On Monday 30 January 2006 02:23, Andrew Bennetts wrote:
[...]
> > With sufficiently recent Twisted (possibly 2.1, but definitely SVN), it
> > should be possible to run these tests with the standard zope testing
> > framework. Trial
Hi Jim,
If you are happy to wait a few days more, before including these into
buildbot, I will create a branch to get these tests back into the same zope
testing framework. From what Andrew Bennetts said in his response, this is
very possible but will probable require a update of Twisted to
Michael Kerrin wrote:
Hi Jim,
If you are happy to wait a few days more, before including these into
buildbot, I will create a branch to get these tests back into the same zope
testing framework. From what Andrew Bennetts said in his response, this is
very possible but will probable require
On Sun, Jan 29, 2006 at 12:19:24PM +0100, Balazs Ree wrote:
> So this is where I see the importance of this: allow access to a
> method/template via RPC only, and disallow the method to be called
> directly from the browser.
I'm curious.
How do you distinguish between a jsonrpc request and a direc
On Jan 30, 2006, at 3:21 AM, Michael Howitz wrote:
Hi, as suggested in #zope3-dev I'll post my experiences with interface
invariants and formlib here.
I have an interface with two password fields which should be equal:
class IUser(Interface):
password=zope.schema.Password(title=u"password
Fred Drake wrote:
On 1/30/06, Michael Howitz <[EMAIL PROTECTED]> wrote:
I have an interface with two password fields which should be equal:
class IUser(Interface):
password=zope.schema.Password(title=u"password")
password2=zope.schema.Password(title=u"password again")
Gary outlined on
On Jan 30, 2006, at 12:11 PM, Jim Fulton wrote:
Fred Drake wrote:
On 1/30/06, Michael Howitz <[EMAIL PROTECTED]> wrote:
I have an interface with two password fields which should be equal:
class IUser(Interface):
password=zope.schema.Password(title=u"password")
password2=zope.schema.Pas
Paul Winkler wrote:
On Sun, Jan 29, 2006 at 12:19:24PM +0100, Balazs Ree wrote:
So this is where I see the importance of this: allow access to a
method/template via RPC only, and disallow the method to be called
directly from the browser.
I'm curious.
How do you distinguish between a j
On 1/30/06, Michael Howitz <[EMAIL PROTECTED]> wrote:
> I have an interface with two password fields which should be equal:
>
> class IUser(Interface):
> password=zope.schema.Password(title=u"password")
> password2=zope.schema.Password(title=u"password again")
Gary outlined one approach, b
Stephan Richter wrote:
On Wednesday 25 January 2006 05:40, Christian Theune wrote:
I'm quite sure that part b) isn't written yet, but I'm not sure what the
state of part a) is.
(a) is done. It is indeed the default Zope behavior.
I'd love for this to be configurable somehow... The "pop up an
Jim Fulton wrote:
Every change I've ever been involved with has been extremely painful.
I can't even explain well what made it painful because I didn't really
understand what was going on and needed help from Fred. Maybe someone
would make the same comment about ZCML, although I've had a lot of
Sidnei da Silva wrote:
What I think is that the Zope ZConfig schema should have something
just like 'package-includes' is for ZCML. A place where you can drop a
snippet of ZConfig schema and it will get picked up at boot time.
Try having a play with MailingLogger in Zope 2.
Both the .conf and s
Tres Seaver wrote:
+1 to that. I think Chris doesn't really believe in the Second Law of
Python (according to the prophet Peters).
Urm, can you refresh for someone with hazy knowledge of PSU epistles?
Shane Hathaway wrote:
No, Chris just doesn't like XML namespaces. You can still have
expli
Ah, a man after my own heart :-)
(and I never thought I'd say that abotu Dieter!)
*grinz*
Chris
Dieter Maurer wrote:
Martijn Faassen wrote at 2006-1-27 13:21 +0100:
...
Five actually adds a 'five' namespace, which I think is very useful --
it clearly marks which directives are only there f
>> I remember that Jim once presented two XML samples and asked which one
>> was more readable. I preferred many elements over many attributes. He
>> preferred the opposite. I thought he was crazy, and as I recall, he
>> thought I was crazy, too. :-)
Elements vs Attributes is an age old debate
Tres Seaver wrote:
Thought so! I'm just not sure whether this is intended behaviour. What's
the current policy about displaying tracebacks to the "end-user" in Zope
3?
The policy seems to be that the end user should *never* see the
traceback, unless she selects the '++skin++Debug' skin *and* t
On Mon, Jan 30, 2006 at 09:36:12PM +, Chris Withers wrote:
> >Tres Seaver wrote:
> >>+1 to that. I think Chris doesn't really believe in the Second Law of
> >>Python (according to the prophet Peters).
>
> Urm, can you refresh for someone with hazy knowledge of PSU epistles?
[EMAIL PROTECTED]
Ok, getUtility() doesn't work, but:
def bootStrapSubscriberDatabase(event):
[...]
db, connection, root, root_folder = getInformationFromEvent(event)
if ( ensureUtility(root_folder, IIkAdminUtility, 'IkAdminUtility',
IkAdminUtility, '') ) :
logger.info("Ensure unnamed IkAdminUtilit
Chris Withers wrote:
Tres Seaver wrote:
Thought so! I'm just not sure whether this is intended behaviour. What's
the current policy about displaying tracebacks to the "end-user" in Zope
3?
The policy seems to be that the end user should *never* see the
traceback, unless she selects the '++s
21 matches
Mail list logo