Re: sphinx-build conf.py circular dependency

On Fri, Feb 15, 2019 at 06:19:10PM +0100, Miro Hrončok wrote: > On 15. 02. 19 17:57, Gabriel L. Somlo wrote: >> I'm trying to package 'migen': >> >> http://www.contrib.andrew.cmu.edu/~somlo/python-migen-rpm/python-migen.spec >> >> The sources come with a ./doc directory that uses sphinx-build to >> generate documentation, and a ./doc/conf.py file which imports >> the package being built, in order to automatically paste various >> code and doc bits from the module into the resulting documentation >> ... >> make: Entering directory '/builddir/build/BUILD/migen-afe4405becdbc76539f0195c319367187012b05e/doc' >> sphinx-build -b man -d _build/doctrees . _build/man >> Running Sphinx v1.7.5 >> make: Leaving directory '/builddir/build/BUILD/migen-afe4405becdbc76539f0195c319367187012b05e/doc' >> >> Configuration error: >> There is a programable error in your configuration file: >> >> Traceback (most recent call last): >> ... >> pkg_resources.DistributionNotFound: The 'migen' distribution was not found and is required by the application > > > This is tricky. It doesn't import it (that is easily tricked with > PYTHONPATH), but uses pkg_resources to fetch data about installed > packages. > > I believe the easiest way is to sed conf.py to replace > > pkg_resources.require("migen")[0].version Argh, upstream is doing the typical overengineered crap. Do they realize that they are embedding the identifier of the _previously_ installed version in the docs?