On Jul 10, 2006, at 11:44 PM, Benji York wrote:
...
I'd like to merge the branch to zope.testing in the next few days.
Thoughts/questions?
Sounds great. My main concern is the continued forking of doctest. :(
I had intended to sync it up with Python 2.5, but I never did. I have
no
On 7/7/06, Julien Anguenot [EMAIL PROTECTED] wrote:
Jim Fulton wrote:
On Jul 7, 2006, at 9:45 AM, Julien Anguenot wrote:
Hi there,
Jim Fulton wrote:
On Jul 5, 2006, at 5:46 AM, Christian Theune wrote:
I'm sitting at EuroPython right now, and a small discussion came up,
trying to find
Jim Fulton wrote:
[snip]
I would say that there are two bugs in the case you are describing: the
one you meant to fix and the one which is the lack of any tests for the
module / class / whatever. I would bet that spending your thirty
minutes adding minimal tests to such a module is a *higher*
Jim Fulton wrote:
On Jul 11, 2006, at 8:05 AM, Patrick Gerken wrote:
...
As a non committer I would like to note that it was easy for me to
search if somebody already submitted a bug I found, and submit a new
patch, it was also trivial to add the for the bugfix and the test. The
only thing
Martijn Faassen wrote:
The other suggestion I made elsewhere is the ability for developers to
add breaking tests to the codebase (explicitly marked as such, and not
normally run).
+1
--
Benji York
Senior Software Engineer
Zope Corporation
___
As an update...
Hanno Schlichting wrote:
- configurable language negotiation based on a set of registered extractors
- extractors: browser language, cookie and URL segment
All good... :-)
(lemme know when it's ready ;-) )
(maybe member
property but this is probably impossible in pure Zope3
Benji York wrote:
Gary Poster had a really good idea a couple weeks ago: teach doctest
about ReST-style footnotes.
After some promising discussion on python-dev and Gary's endless begging
:) I've merged my branch into zope.testing, I still have some TODO
items to finish up in the near
Hi all,
I recently had reason to check out and use the soap product for Zope3.
I needed it to work with the 3.2 HTTPRequest/Response api (setResult
instead of self._body or setBody), so I made the changes I saw . I
also wanted/needed it to work with the ZSI 2.0rc2 that's out now, so I
updated
Hi.
As far as I understand there is really a bug. The code should deal with
the situation where msgid is a Message object. What it does right now is
to look up a translation for that Message object in the translation
domain of the current TranslationDomain (self). The line you mention is
part of
On 7/11/06, Chris Withers [EMAIL PROTECTED] wrote:
Puzzling as to what this chunk of code:
if msgid.domain != self.domain:
util = getUtility(ITranslationDomain, msgid.domain)
I don't see it being used either. I suspect those two lines can be
removed. :-)
Folks,
I have what seems to be an odd problem with persistence of information
in simultaneous sessions.
I keep track of an iterator in an object that is persistent (one
instance per-session). The iterator is updated as the user navigates a
sequence of objects. The iteration seems to work fine
11 matches
Mail list logo
