On Mar 1, 2:03 pm, Bill Janssen <[email protected]> wrote:
> outside that community if there were some dirt-simple examples, too.
I agree and I think there a good number of simple examples already
there, but there is a need for more. One of the problems is that the
package itself is fairly large so it is takes time to produce
documentation that covers all of its functionality.
> box on OS X. Use of bsddb has been a long-standing breakage issue
> with Python; that's why it was removed in 2.6. It's perceived as
> impossible to provide stable support for.
That is not quite correct. bsddb has not been removed from 2.6 (it has
been removed from 3.0), there are many reasons for removal, most
compelling being that it changes more often than python itself, and
that makes it impossible to properly patch it withouth making a new
python release.
It'll is still available as a standalone package, and probably will be
of better quality. Frankly when a package works on most platforms but
it is broken on one of them, the fault most likely lies with the
platform rather than the code. In any way, unless there is a better
alternative to bsddb it is not likely to go away.
> 2. the GraphQuery class is not in the pygr.mapping module, despite
> what the documentation says.
Yes, we should have an official API documentation for this purpose, I
have formatted one
here, but this contains a few of my own modules, but did not alter the
pygr ones:
http://pygr.atlas.bx.psu.edu/epydoc/index.html
best,
Istvan
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pygr-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/pygr-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
