[reportlab-users] Reportlab issue list

Claude Paroz claude at 2xlibre.net
Sat Jan 16 16:27:24 EST 2021

Le 16.01.21 à 22:16, Robin Becker a écrit :
> On 16/01/2021 20:15, Claude Paroz wrote:
>> Maybe it's not too late to ask bitbucket for a backup of those ticket 
>> data?
>> Typically, I'd like to read reportlab issue #185 mentioned in this 
>> thread:
>> https://github.com/deeplook/svglib/issues/193
> no offence was taken, I oroginally thought they (Atlassian) would just 
> freeze everything; they gave us a while and then removed everything. I 
> missed it and probably wouldn't know how to copy the issues/bugs anyway.

I'll see if I can ask Atlassian to get an archive of those.

>> ............
>> Mmmmh, this sounds again a bit awkward :-) You know that 99% of open 
>> source projects have issue lists, on which anyone can also discuss and 
>> contribute if they wish. For example, with a mailing list, how can you 
>> keep track of the status of reported issues? Browsing each mailing 
>> list thread one by one to know if the discussed issue is resolved or not?
> .......
> Let 100 flowers bloom :)

Ha, ha, ha, indeed!!

> Anyhow from your issue 193 I think you just want to allow the graphics 
> strings to have stroke properties (at least in PDF).
> I think that's doable with a small change in renderPDF.py; whether it is 
> feasable in renderPS / renderPM I don't know.

It would be a step forward, even if it's only for PDF rendering.


More information about the reportlab-users mailing list