On Thu, Sep 17, 2009 at 8:48 AM, Mike Orr <sluggos...@gmail.com> wrote: > > And how to you arrange for Sphinx to import the package it's > documenting if it's in a sibling directory or parent directory of the > docs directory? Righit now I think it's documenting the webhelpers in > my virtualenv, but what I really want it to do is to document the > package in the source. >
I use buildout. Add a buildout.cfg at the root of your package: [buildout] newest = false parts = eggs develop = . [eggs] recipe = zc.recipe.egg eggs = WebHelpers Sphinx nose Run buildout. Then you are able to use buildout's binaries to run nose/sphinx. You just need to change Sphinx's Makefile so he use ../bin/sphinx-build Have a look at this package as a full example (with bootstrap.py / .hgignore): http://bitbucket.org/gawel/configobject/src/ -- Gael > -- > Mike Orr <sluggos...@gmail.com> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-devel@googlegroups.com To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en -~----------~----~----~----~------~----~------~--~---
