On Wed, Jun 30, 2010 at 02:09:10PM +0200, Andreas Ostermann wrote:
> I wanted to try be, however in the bugs-everwhere package comming with
> Ubuntu 10.04 the be init command could not be found.

Yes, that package is fairly ancient.

> so I wanted to get the sources directly from the git repository, but
> after make and make install:
> 
> a...@farnsworth:~/workspace/be$ make install
> ...
> make -C doc html
> make[1]: Entering directory `/home/ao/workspace/be/doc'
> python generate-libbe-txt.py
> sphinx-build -b html -d .build/doctrees   . .build/html
> Running Sphinx v0.6.4

You don't actually need to build the docs to use BE.  If you comment
out the doc dependency in the Makefile:
  -install: build doc
  +install: build # doc
installation should work fine.  The install target doesn't actually
install the docs anyway, and they're online at
  http://docs.bugseverywhere.org/
That said, you should be able to build them if you want.

> Extension error:
> Could not import extension numpydoc (exception: No module named numpydoc)
> ...
> However, looking into the /usr/share/doc/python-chaco/source/sphinxext/
> directory:
> 
> a...@farnsworth:~/workspace/be$ ll
> /usr/share/doc/python-chaco/source/sphinxext/
> ...
> -rw-r--r-- 1 root root 15855 2009-07-16 18:26 numpydoc.py

I imagine that Chaco does some sys.path manipulation to find that module.
We do this too, in doc/conf.py so Sphinx can find libbe:
  sys.path.insert(0, os.path.abspath('..'))
If you want access to chaco's numpydoc.py and the other sphinxext
modules, add that directory to your PYTHONPATH.  If you're not
currently using PYTHONPATH, that would look like
  export PYTHONPATH=/usr/share/doc/python-chaco/source/sphinxext/
If you don't want general access and only want BE to find those
modules, edit doc/conf.py:
   sys.path.insert(0, os.path.abspath('..'))
  +sys.path.insert(0, '/usr/share/doc/python-chaco/source/sphinxext/')
Or you could put a symlink to numpydoc.py somewhere else in the
standard sys.path, etc., etc.

-- 
This email may be signed or encrypted with GPG (http://www.gnupg.org).
The GPG signature (if present) will be attached as 'signature.asc'.
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy

My public key is at http://www.physics.drexel.edu/~wking/pubkey.txt

Attachment: pgpRejucem3AT.pgp
Description: PGP signature

_______________________________________________
Be-devel mailing list
[email protected]
http://void.printf.net/cgi-bin/mailman/listinfo/be-devel

Reply via email to