Excuse my abscence. I'm a little busy and cannot find the time to track
the list daily.
Small summary of zope.generic:
it's a not-yet-fully-implemented, experimental prototype trying to find
a high-level-usage pattern or framework for zope 3.
During the easter-sprint I decided to put the code
Hi Philipp, Dominik
Dominik, can you give a short overview what zope.generic
can do?
[...]
> > If you take a closer look at this package and you will see
> that each
> > subpackage is well documented.
>
> Right. But that information isn't easily accessible. You have
> to go to zope.generic/t
[EMAIL PROTECTED] wrote:
>> I see a few packages lurking in svn.zope.org that I can't
>> make much sense of:
>>
>> * For example, what is zope.generic? I can't find a
>> README.txt anywhere in the top-level directories. What I
>> *can* see is that it seems to be another big bag for
>> subpackag
Hi Philipp
good idea, just some update what allready happen when
you where in China ;-)
[...]
> I see a few packages lurking in svn.zope.org that I can't
> make much sense of:
>
> * For example, what is zope.generic? I can't find a
> README.txt anywhere in the top-level directories. What I
>
Fred Drake wrote:
> On 7/6/06, Philipp von Weitershausen <[EMAIL PROTECTED]> wrote:
>> - Do other people also think it'd be a good idea to come up with some
>> repository guidelines? Stephan had a proposal about specifying package
>> metadata and code maturity/quality, I think it's worth working to
On 7/6/06, Philipp von Weitershausen <[EMAIL PROTECTED]> wrote:
- Do other people also think it'd be a good idea to come up with some
repository guidelines? Stephan had a proposal about specifying package
metadata and code maturity/quality, I think it's worth working towards
easily accessible inf
