Bug#876681: RFH: rst2pdf -- ReportLab-based reStructuredText to PDF renderer
On Mon, 8 Jan 2018 09:56:41 +0100 Elena ``of Valhalla''
<valhalla-d@trueelena.org> wrote:
> On 2018-01-07 at 16:31:58 +0100, Andrew Shadura wrote:
> > On 7 January 2018 at 16:13, Elena ``of Valhalla''
> > <valhalla-d@trueelena.org> wrote:
> > > On 2017-09-25 at 07:31:29 +0200, Andrew Shadura wrote:
> > >> I think I can have a look at it :) I'll let you know later today if
> > >> I'm really interested.
> > >
> > > Can I assume that you're not interested?
> > >
> > > rst2pdf is going to be autoremoved from testing because of #866477, and
> > > right now I'm more likely to just let it be removed rather than working
> > > on it only to have the package removed a little later because of a lack
> > > of py3 support (unless somebody else is interested in the package, of
> > > course).
> >
> > Sorry, I completely forgot about this. I will *indeed* jave a look later today.
> Update 1: thanks to Andrew I realized that #866477 wasn't rightfully
> release critical and brought it back to normal (so the package shouldn't
> get autoremoved.
>
> Update 2: upstream is currently working, apparently on tests
> https://github.com/rst2pdf/rst2pdf/commits/master and they seem to have
> a release planned https://github.com/rst2pdf/rst2pdf/milestones
> so maybe the only thing that is needed is to ping them a bit on python3
> support https://github.com/rst2pdf/rst2pdf/issues/537 where activity
> seems stalled (and it's not in any release milestone).
>
> I believe that having working automated tests is considered necessary
> for the port, but I don't know what's the current status of them.
Right. So now, having seen the code and the state of the project, I can
confirm this is too large a task for me, and I'm probably not that much
interested to work on it upstream. I'm not sure about Debian packaging
either, as it heavily depends on upstream's decisions on how to proceed
with Python 3 migration.
--
Cheers,
Andrew
Reply to: