On Tue, Oct 15, 2013 at 3:04 PM, Jakub Wilk <jw...@debian.org> wrote:
> True for docutils; however, sphinx doesn't use alternatives, and it doesn't
> do so for good reasons.
>
> The alternatives mechanisms is only suitable if both commands are
> compatible, i.e. their behavior doesn't vary with Python version. This is
> the case for rst2html and friends, but no so much for sphinx-build. The
> problem is that sphinx-build can import 3rd-party Python code, which is not
> necessarily compatible with both Python 2 and 3.
Right, I shouldn't have mentioned Sphinx here, as it is a very specific case.
> As I understand it, python{2,3}-coverage are NOT compatible, and therefore
> they should NOT use alternatives.
Can you please explain why they are incompatible for people who never
used them (like me)?
--
Dmitry Shachnev
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CAKimPHXN3NUYm9bSHOaSZHf=zdsnujt6h9gwt+ei3quk4e6...@mail.gmail.com
