Thanks Ghislain and Simon for your responses.
It turns out mkdocs need python-markdown not for tests, but rather for
building its own docs.
So probably the correct way to go is to make sure both packages take the
nodoc build profile into account.
On Thu, Jan 11, 2018 at 11:29:34AM +, Simon
On Thu, 11 Jan 2018 at 13:35:13 +0300, Dmitry Shachnev wrote:
> The new release of python-markdown has switched docs building from its own
> custom build system to mkdocs. However python-mkdocs itself build-depends on
> python3-markdown for tests, which results in a circular build-dependency.
It
2018-01-11 10:35 GMT+00:00 Dmitry Shachnev :
> Hi Brian and list,
>
> The new release of python-markdown has switched docs building from its own
> custom build system to mkdocs. However python-mkdocs itself build-depends on
> python3-markdown for tests, which results in a
Hi Brian and list,
The new release of python-markdown has switched docs building from its own
custom build system to mkdocs. However python-mkdocs itself build-depends on
python3-markdown for tests, which results in a circular build-dependency.
Will it be fine if I just mark the build-dependency
4 matches
Mail list logo