Hello,
I'm wondering if it would be possible to drop the dependency between
zope.location and zope.copy. It makes sense to me because zope.location
depends on zope.copy only because it registers a LocationCopyHook, not
because it is really using anything from that package.
Attached to this messag
Chris McDonough wrote:
> Thomas Lotze wrote:
>> Because then, if you use third-party code that uses
>> zope.interface.Interface and other code (third-party or your own) that
>> uses the subclassed interfaces, you'll have to deal with both types at
>> the same time in your client code. You could us
On Mon, Dec 21, 2009 at 22:23, Marius Gedminas wrote:
> On Mon, Dec 21, 2009 at 07:41:24PM +0100, Lennart Regebro wrote:
>> On Mon, Dec 21, 2009 at 13:20, Marius Gedminas wrote:
>> > Can you please make it a PendingDeprecationWarning first?
>>
>> Yeah, I guess, but why?
>
> Because I hate it when
On Mon, Dec 21, 2009 at 07:41:24PM +0100, Lennart Regebro wrote:
> On Mon, Dec 21, 2009 at 13:20, Marius Gedminas wrote:
> > Can you please make it a PendingDeprecationWarning first?
>
> Yeah, I guess, but why?
Because I hate it when my code emits DeprecationWarnings, and I wasn't
sure I could t
Hi.
On Mon, Dec 21, 2009 at 9:34 PM, Fabio Tranchitella wrote:
> I've just committed a simple patch to allow extras in the eggs option of a
> z3c.recipe.depgraph-based recipe.
Cool. I properly released 0.5 including your fix :)
Hanno
___
Zope-Dev mail
Hello,
I've just committed a simple patch to allow extras in the eggs option of a
z3c.recipe.depgraph-based recipe. While doing it, I just realized that the
0.4 release has not been uploaded to PyPI, where the most recent version is
0.3.
Package index owners for the package are hannosch, faassen.
On Mon, Dec 21, 2009 at 13:20, Marius Gedminas wrote:
> Can you please make it a PendingDeprecationWarning first?
Yeah, I guess, but why? Yes, it had bugfixes, and I have
monkey-patches of doctest in the branch to fix them. But it's not like
they are going to get fixed in 2.4 because we wait with
On Mon, Dec 21, 2009 at 02:20:54PM +0200, Marius Gedminas wrote:
> On Mon, Dec 21, 2009 at 10:32:42AM +0100, Lennart Regebro wrote:
> > On Sun, Dec 20, 2009 at 23:55, Marius Gedminas wrote:
> > > I don't know if 'doctestunit' was ever a part of the official
> > > zope.testing API, I just know that
On Mon, Dec 21, 2009 at 10:32:42AM +0100, Lennart Regebro wrote:
> On Sun, Dec 20, 2009 at 23:55, Marius Gedminas wrote:
> > I don't know if 'doctestunit' was ever a part of the official
> > zope.testing API, I just know that I've learned to use
So, Monday! I take a deeper look at the codebase,
Summary of messages to the zope-tests list.
Period Sun Dec 20 12:00:00 2009 UTC to Mon Dec 21 12:00:00 2009 UTC.
There were 6 messages: 6 from Zope Tests.
Tests passed OK
---
Subject: OK : Zope-2.10 Python-2.4.6 : Linux
From: Zope Tests
Date: Sun Dec 20 20:37:19 EST 2009
URL: http://
Thomas Lotze wrote:
> Chris McDonough wrote:
>
>> I'll throw out the obvious...
>>
>> Why not subclass Interface in zope.component and make the required API
>> additions there? If it were anybody but us thinking about doing this,
>> they'd probably just subclass.
>
> Because then, if you use thi
Hi,
Jean-Francois and I made a few improvements to zope.schema.
Would it be possible to get a new release ?
Or to give us access on Pypi so that we can make it ourselves ?
Thanks
--
Godefroid Chapelle (aka __gotcha) http://bubblenet.be
___
Zope-Dev m
Hi,
this is a long message with a lot of replies to things that I don't agree
with. Since I realize that making those points over and over again doesn't
get us anywhere, I'd like to point out first that I'm going to implement
Martijn's suggestions anyway on one of my branches, hoping that seeing
m
On Sun, Dec 20, 2009 at 23:55, Marius Gedminas wrote:
> I don't know if 'doctestunit' was ever a part of the official
> zope.testing API, I just know that I've learned to use
I've looked through the history of doctestunit, and it seems like it
once was. This was changed 5 years ago, and doctestun
14 matches
Mail list logo
