On Tue, Apr 20, 2010 at 15:23, Lennart Regebro wrote:
> On Tue, Apr 20, 2010 at 13:44, Wichert Akkerman wrote:
>> You may want to move it outside the zope.* namespace to encourage that :)
>
> We could certainly do that.
But the support for that idea seems very small, so let's stay with
zope.test
On Wed, Apr 21, 2010 at 07:10:38AM +0200, Lennart Regebro wrote:
> > Let zope.testing.doctest wither and die
>
> It hasn't been merged from python trunk since 2004, and the amount of
> bugfixes on that Python trunk since then is astounding. So I'd argue
> that is *is* withered. The monkey-patching
* Jim Fulton [2010-04-20 20:35]:
> On Tue, Apr 20, 2010 at 4:46 AM, Lennart Regebro wrote:
>> And here is another interesting experiment:
>> svn+ssh://rege...@svn.zope.org/repos/main/zope.testing/branches/regebro-doctest-patching
>> It replaces the custom doctest.py with monkey-patches.
>>
>> Ben
On Tue, Apr 20, 2010 at 20:35, Jim Fulton wrote:
> Monkey patching should be used as a last resort. Monkey
> patching the standard library is likely to make us look like
> jack asses.
Possibly. But having a doctest module with loads of bugs that doesn't
even behave exactly the same maybe doesn't
On Tue, Apr 20, 2010 at 4:46 AM, Lennart Regebro wrote:
> And here is another interesting experiment:
>
> svn+ssh://rege...@svn.zope.org/repos/main/zope.testing/branches/regebro-doctest-patching
>
> It replaces the custom doctest.py with monkey-patches.
> I will report these to the Python bugtrack
On 04/20/2010 03:59 PM, Martin Aspeli wrote:
> On 20 April 2010 21:23, Lennart Regebro wrote:
>> On Tue, Apr 20, 2010 at 13:44, Wichert Akkerman wrote:
>>> You may want to move it outside the zope.* namespace to encourage that :)
>
> -1
>
> I think zope.testrunner is just fine, and acknowledges t
On 20 April 2010 21:23, Lennart Regebro wrote:
> On Tue, Apr 20, 2010 at 13:44, Wichert Akkerman wrote:
>> You may want to move it outside the zope.* namespace to encourage that :)
-1
I think zope.testrunner is just fine, and acknowledges the heritage.
Namespaces should be about which community
On Tuesday 20 April 2010, Lennart Regebro wrote:
> (zope.testrunner of course also being one perfectly good idea).
I like zope.testrunner. If it gets its own Web site (eventually), we have a
good place to guide people there.
Regards.
Stephan
--
Entrepreneur and Software Geek
Google me. "Zope St
On Tue, Apr 20, 2010 at 15:23, Lennart Regebro wrote:
> On Tue, Apr 20, 2010 at 13:44, Wichert Akkerman wrote:
>> You may want to move it outside the zope.* namespace to encourage that :)
>
> We could certainly do that.
>
>
> Jarrett - After Arthur Jarrett, convicted of the crime of making of
>
On Tue, Apr 20, 2010 at 13:44, Wichert Akkerman wrote:
> You may want to move it outside the zope.* namespace to encourage that :)
We could certainly do that.
Jarrett - After Arthur Jarrett, convicted of the crime of making of
gratuitous sexist jokes in a moving picture.
Or maybe not. :) Othe
On Tue, Apr 20, 2010 at 7:44 AM, Wichert Akkerman wrote:
> You may want to move it outside the zope.* namespace to encourage that :)
People interested in interfaces or component architectures don't seem
to mind using zope.interface or zope.component; those get selected on
their own merits with so
On 4/20/10 13:37 , Stephan Richter wrote:
> On Tuesday 20 April 2010, Lennart Regebro wrote:
>> It replaces the custom doctest.py with monkey-patches.
>> I will report these to the Python bugtracker as well, although I have
>> no hope of getting them into Python 2.7. But that doesn't matter much.
>
On Tuesday 20 April 2010, Lennart Regebro wrote:
> It replaces the custom doctest.py with monkey-patches.
> I will report these to the Python bugtracker as well, although I have
> no hope of getting them into Python 2.7. But that doesn't matter much.
>
> :)
Fantastic. I really hate the improper c
13 matches
Mail list logo