[Grok-dev] libraries to use with Grok
steveschmechel at yahoo.com
Thu Dec 17 18:50:15 EST 2009
Are we possibly talking about two different things?
There was an idea about a list of particular "Useful Libraries"
and an idea about an "Overview of Namespaces".
Unfortunately, both discussions evolved in the same thread.
The spreadsheet I wish people to review has to do with "useful libraries".
The useful libraries document was not meant to be an index to all
possible code that could be used with Grok. Quite the opposite; a
manageable list of libraries that have proven useful to those with
much experience building Grok apps, so that the rest of us can
benefit from that experience.
For most people using the libraries, the key information would be the
PyPI project homepage and package name so that they can add it to
their project's build out. Most probably do not want to link to the
latest trunk code of a library. If they want to see the source code,
they can peek in the downloaded eggs.
That said, a link to a repository would be nice, but you have to deal
with upkeep when projects switch VCS or hosts. At least PyPI is fairly
There is a namespace overview document at:
I don't believe this is intended to be an index of all code using a
particular namespace either. That would be very hard to keep up to date.
Generally, the type of code and the people contributing it remain fairly
constant within a namespace. This document is an overview of those facts.
While for Dolman.* all of the packages in the namespace probably could
be associated with one project homepage, that would not be the case
many others. The links would end up being either trivial associations
that could be easily found with a search engine, or deep links into
large sites like zope.org which would be hard to maintain.
It just comes down to the fact that finding something by namespace
is by nature a hit-or-miss endeavor.
You might find a particular library or package that leads you to a
project website which lists some other related packages.
I think the namespace overview document is meant more for going in the
opposite direction; you encounter a package being referenced in some
code you are examining, and the namespace gives you some general context
of its origin and purpose.
It's more of a "tuck this away in your memory to improve future comprehension" type of document, than a exhaustive reference document.
Anyway, I don't mean to sound dismissive or discouraging.
Maybe others feel an exhaustive list with links would be useful also, so
feel free to gather support and make it happen.
For now, I am pretty satisfied with the context and experience I can
tap into using the current overview documents.
--- On Thu, 12/17/09, Kent Tenney <ktenney at gmail.com> wrote:
> From: Kent Tenney <ktenney at gmail.com>
> Subject: Re: [Grok-dev] libraries to use with Grok
> To: grok-dev at zope.org
> Date: Thursday, December 17, 2009, 1:57 PM
> On Thu, Dec 17, 2009 at 9:51 AM,
> Steve Schmechel
> <steveschmechel at yahoo.com>
> > I've received no feedback on this expanded library
> list yet.
> > I would like to wrap it up and get it published on the
> Grok site soon.
> > If the temporary formatting as a spreadsheet is the
> problem, I can go
> > ahead and transform it back into ReST. I just
> thought it would be
> > easier to collaboratively categorize and sort for now.
> (Probably more
> > people use Google Apps than have manager rights to
> edit other's work
> > on the Grok Documentation site.)
> > I can make it "world editable" for a period of time if
> that helps
> > people get involved. Otherwise, just drop me a email
> and I will send
> > you an invite.
> > Any feedback or edits are appreciated.
> OK, here goes again.
> I would welcome access to information along the lines of:
> in reference to grokcore.*:
> - a list of the inhabitants of the namespace
> - URL for the egg and the repository
> svn co
> I like to look at both the public face and the code when
> Just now, to find the location of the repository took me
> ~10 minutes of
> searching, I suspect others might spend the same 10 minutes
> if they want
> to look at the source. I would find it helpful if the link
> was near
> the description
> of the namespace, since a couple weeks from now I'll spend
> another 10 minutes
> searching ...
> I would like to see near the dolmen.* description:
> > Thank you,
> > Steve
> > --- On Thu, 12/3/09, Steve Schmechel <steveschmechel at yahoo.com>
> >> From: Steve Schmechel <steveschmechel at yahoo.com>
> >> Subject: Re: [Grok-dev] libraries to use with
> >> To: grok-dev at zope.org,
> "Martijn Faassen" <faassen at startifact.com>
> >> Date: Thursday, December 3, 2009, 4:20 PM
> >> I finally compiled the lists of
> >> libraries into one document. For now,
> >> it is a Google Docs spreadsheet, as that makes it
> easier to
> >> recategorize
> >> and sort the content.
> >> When the list becomes stable, I will write a
> script to
> >> transform it into
> >> whatever target format we desire (ReST, HTML,
> >> If you want to modify the content or add some
> >> items, send me
> >> an email and I will share the spreadsheet with
> >> Feel free to
> >> recategorize or modify anything as you see fit.
> >> https://spreadsheets.google.com/ccc?key=0Ag50MhE4pOa0dFl6VlBSZkpGSDlBTHNFd1pMVS1PS2c
> >> I learned a lot about the available libraries just
> >> going through
> >> this exercise. That was really helpful. I
> >> wait to try some of
> >> them out.
> >> Martijn had some "less interesting" libraries
> >> I'm not sure if I
> >> want to list them here, but I think this knowledge
> >> still be
> >> beneficial. Maybe, if a better package which
> >> the same purpose
> >> exists in the "useful libraries" list, we could
> add to that
> >> item some
> >> comments on how it is "superior" or easier to use
> than one
> >> that may rank
> >> higher in a Google search result.
> >> Also, is someone working on that "namespace
> >> document? If
> >> not, I am willing to format and publish that on
> the Grok
> >> site.
> >> Regards,
> >> Steve
> >> --- On Fri, 11/20/09, Martijn Faassen <faassen at startifact.com>
> >> wrote:
> >> > From: Martijn Faassen <faassen at startifact.com>
> >> > Subject: Re: [Grok-dev] libraries to use with
> >> > To: grok-dev at zope.org
> >> > Date: Friday, November 20, 2009, 2:30 PM
> >> > Steve Schmechel wrote:
> >> > > I will be out of town for a few days,
> back for a
> >> day,
> >> > and then gone
> >> > > for the rest of next week.
> >> > >
> >> > > Please don't stop adding library
> suggestions to
> >> the
> >> > list because you
> >> > > don't see the page on the Grok site
> >> updated.
> >> > >
> >> > > I will go through the list and find all
> >> > suggestions and compile
> >> > > them for review when I return.
> >> >
> >> > Thanks for the heads up, and have a good set
> >> trips!
> >> >
> >> > Regards,
> >> >
> >> > Martijn
> >> >
> >> >
> >> >
> >> > Grok-dev mailing list
> >> > Grok-dev at zope.org
> >> > https://mail.zope.org/mailman/listinfo/grok-dev
> >> >
> > _______________________________________________
> > Grok-dev mailing list
> > Grok-dev at zope.org
> > https://mail.zope.org/mailman/listinfo/grok-dev
> Grok-dev mailing list
> Grok-dev at zope.org
More information about the Grok-dev