> As it looks like the problem is with the wxPython SlackBuild which
> installs version 2.8.x while newer versions of matplotlib require (if
> one wishes to have wxagg) at least 2.9.x. This is something I
> unfortunately overlooked while preparing the matplotlib upgrade. Many
> thanks go to
On 12/6/18 9:49 AM, Serban Udrea wrote:
On 12/4/18 5:10 PM, Fellype wrote:
Hi Benjamin,
Are you using a 32-bit system? This silent fail occurred only on the machine I
run Slackware 32-bits, and only for the 2.x matplotlib (1.x build fine). But I
haven't had time to investigate the reason(s)
On 12/4/18 5:10 PM, Fellype wrote:
Hi Benjamin,
Are you using a 32-bit system? This silent fail occurred only on the machine I run
Slackware 32-bits, and only for the 2.x matplotlib (1.x build fine). But I haven't
had time to investigate the reason(s) of the fail.
...
Hi Fellype,
I
On 2018-12-04 8:10 a.m., Fellype wrote:
Hi Benjamin,
Are you using a 32-bit system? This silent fail occurred only on the
machine I run Slackware 32-bits, and only for the 2.x matplotlib (1.x
build fine). But I haven't had time to investigate the reason(s) of the
fail.
Hi Fellype, all my
On 2018-12-04 3:02 a.m., Serban Udrea wrote:
And thank you for investigating the issue, reporting it and preparing
the patch. I'm not sure that disabling wxagg is always ok. I would put
its disabling as an option for now and try to find out more about this
issue.
Yeah I'm not sure if there
Hi Benjamin,
Are you using a 32-bit system? This silent fail occurred only on the
machine I run Slackware 32-bits, and only for the 2.x matplotlib (1.x build
fine). But I haven't had time to investigate the reason(s) of the fail.
Fellype
Em seg, 3 de dez de 2018 às 23:09, Benjamin
On 12/4/18 2:09 AM, Benjamin Trigona-Harany wrote:
Hi Serban,
I wonder if this small patch would make sense for libraries/matplotlib? I've been
having an issue where the script fails silently shortly after setup.py is run.
The following error is in SETUP.OUTPUT:
Unable to access the X
