Drew Perttula wrote:
>>You may be aware that Phillip Eby's PEAK package has a
>>sub-package called 'dispatch', which unfortunately (and,
>>IMO, rather arrogantly ;) PEAK installs into the
>>top-level site-packages namespace. So, since I already
>
> Possibly this is related to [1], where PJE goes into some detail about the
> "important" differences between PyDispatcher and his (second?) rewrite.
>
> I don't know exactly what his needs are, but if even if they do need a
> variation on PyDispatcher, I would certainly have asked this group first
> about offering that feature on the real thing, myself.
>
> [1] http://cvs.osafoundation.org/viewcvs.cgi/internal/Spike/src/spike/events.txt?rev=1.6&content-type=text/vnd.viewcvs-markup
No, I don't think the two are related. The problem with PEAK began
before Philip was aware of this project, and is unrelated to his OSAF
Spike. It's only his Spike dispatcher that is similar to this one. The
PEAK dispatcher is a different beast altogether, iirc. (And let's face
it, dispatch is a pretty generic term. I wasn't the first and only
person to create something with that name.)
We are actually using pydispatcher and parts of PEAK in Schevo. To
solve the conflict we had to do some local renaming tricks in our
Subversion repository. When Matthew Scott has some free time he'll
provide more details.
For now, let's give Mr. Eby the benefit of the doubt and assume that we
can work out an amicable solution. If that fails, Mike can feed him to
the lions at PyCon while I sit ringside cheering on the lions. ;-)
In all seriousness, perhaps a nice, polite message to PJE would be a
good way to start. I'd do it myself except I'm dog-tired right now.
--
Patrick K. O'Brien
Orbtech http://www.orbtech.com
Schevo http://www.schevo.org
Pypersyst http://www.pypersyst.org
|
