stonebig
stonebig
a workaround on windows is to open the 'broken' pdf and print it "as pdf" per windows. the new 're-printed' pdf works correctly. I have the same pattern of error...
anyway, maybe it's a "strange" pdf generated, but it's not broken as windows can open it... a better handling shall be possible
if I open the "bad original" per notepad++ on Windows and the "reprinted per windows", the beginning is interesting: old bad: ```` %PDF-1.3 1 0 obj stream ÿØÿà ```` new...
The "bad" version seems to use `` as the carriage return on main partes, while "normal" pdf use apparently `` ==> a Mac thing ?  old bad;  new...
well, I'm creating a window each time there is a dataset return. like if executing in sql server front-end. big fan of sqlserver simplicity, or visadata application of last century
hi another small question. Is the "Step1"(adaptive, specializing interpreter): - helping, neutral, or delaying the multiple-interpreter approach ? https://www.python.org/dev/peps/pep-0554/ - helping, neutral or delaying the compatibility work between cpython and...
I see no movement on the project since a few months. Does it mean there is no realistic gilectomy on Cpython, and our only hope is an up-to-date pypy ?
You may look at what spider-ide folks are doing
(today) yes.
Yes. I had an issue with bqplot, now resolved.