dulwich-users team mailing list archive

[David Blewett <david@xxxxxxxxxxxxxxxx>]

On Sat, Mar 19, 2011 at 9:12 PM, Jelmer Vernooij <jelmer@xxxxxxxxx> wrote:
> I'm getting two test failures now:

Both errors are due to pkg_resources not being able to load the
entry_points successfully. I usually work in a virtualenv, using
`python setup.py develop` to link the cwd into the virtualenv. Doing
this step allows the tests to succeed. I think they are of some value,
as they provide a sanity check to make sure the definitions in
setup.py actually work. I can re-work the logic though to see if there
are any entry_points for this package defined at all before running
the test.

I should probably also update the tests to use the version from
dulwich/__init__.py when trying to load the entry_points.

We talked on IRC about the `make doc` failures. I can try to look into
that, but it will probably be until next week before I could fix that.
The dependencies for setting up the doc toolchain should be added to
HACKING in my opinion. I'd never heard of pydoctor, and wasn't
expecting to have to install nevow, twisted, epydoc and docutils to
get it up and working.

-- 
Thanks,

David Blewett