I'm a co-maintainer for the python-sphinx package. There's a bug [1] I'd
like to address, but I'd like some input on what I was thinking. There was
some discussion about this on FPC ticket [2], but nothing workable really
came out of that. I also attempted to get input [3] from the Sphinx
community
Dne 13.7.2016 v 21:15 Avram Lubkin napsal(a):
> Does anyone have any preferences, thoughts or alternative approaches?
I do not have the solution. But I want to point out similar case, which I
recently reported against pyp2rpm:
https://github.com/fedora-python/pyp2rpm/issues/63
--
Miroslav Suc
As someone pointed out somewhere on IRC - we should try to invent
"alternatives" to python packages like it was done in java packages in
Fedora.
On Thu, Jul 14, 2016 at 3:13 PM, Miroslav Suchý wrote:
> Dne 13.7.2016 v 21:15 Avram Lubkin napsal(a):
>> Does anyone have any preferences, thoughts or
Avram Lubkin wrote:
> Potentially there are some Sphinx
> extensions that are Python version dependent, but I am not aware of
> any.
It sounds like I should start trying to get sphinxcontrib-adadomain
ported to Python 3.
> It was suggested the makefile should be changed so the Python version
> th
On Sun, Jul 17, 2016 at 6:09 AM, Björn Persson wrote:
> It sounds like I should start trying to get sphinxcontrib-adadomain
> ported to Python 3.
>
Definitely!
> I have two possible fixes:
> >
> > The first would be to decouple the commands from the libraries. Since
> > the package name sphinx
Avram Lubkin wrote:
> The
> second option would work as long as you don't have python3-sphinx
> installed during the package build. That should be fine in a mock
> build, but if someone wanted to do a rebuild on their regular system
> and had python3-sphinx installed, they'd have to set the sphinx