[Slackbuilds-users] possible matplotlib patch

[Benjamin Trigona-Harany]

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 Display, is $DISPLAY set properly?

After some trial and error, I've found that disabling wxagg in setup.cfg
avoids the script needing access to X. I do have wxPython and wxGTK3
installed but this issue only crops up on one of my two Slackware
laptops. The patch simply ensures that wxagg is disabled and I don't
think there's any downside to doing this.

Incidentally, I don't think SETUP.OUTPUT was meant to be added to the
repo, although no harm from it being there.

Thanks!

[Serban Udrea]

Post by Benjamin Trigona-Harany
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.
Unable to access the X Display, is $DISPLAY set properly?
After some trial and error, I've found that disabling wxagg in setup.cfg avoids
the script needing access to X. I do have wxPython and wxGTK3 installed but this
issue only crops up on one of my two Slackware laptops. The patch simply ensures
that wxagg is disabled and I don't think there's any downside to doing this.
Incidentally, I don't think SETUP.OUTPUT was meant to be added to the repo,
although no harm from it being there.

Hi Benjamin,

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.

I'm puzzled! Why should there be any need for accessing X? Did you enable tests?

Yes, SETUP.OUTPUT was intended just for me. I'll correct this. However, could you
please send me a SETUP.OUTPUT containing the error.

Best regards,
Serban
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-***@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Benjamin Trigona-Harany]

Post by Serban Udrea
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 are any drawbacks! After removing wxagg,
matplotlib *seemed* to work just fine.

Post by Serban Udrea
I'm puzzled! Why should there be any need for accessing X? Did you enable tests?

I didn't make any other changes. I assume it has something to do with
other packages that I have installed. But wxPython and wxGTK3 are on
both my Slackware current installs and only one shows this issue. I just
realised that in my initial email, I forgot to say that this happened on
*current* not 14.2, so feel free to ignore this request on that basis!

Post by Serban Udrea
Yes, SETUP.OUTPUT was intended just for me. I'll correct this. However,
could you please send me a SETUP.OUTPUT containing the error.

Attached.

Thanks for looking at this!
Ben

[Fellype]

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 Trigona-Harany <

Post by Benjamin Trigona-Harany
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.
Unable to access the X Display, is $DISPLAY set properly?
After some trial and error, I've found that disabling wxagg in setup.cfg
avoids the script needing access to X. I do have wxPython and wxGTK3
installed but this issue only crops up on one of my two Slackware
laptops. The patch simply ensures that wxagg is disabled and I don't
think there's any downside to doing this.
Incidentally, I don't think SETUP.OUTPUT was meant to be added to the
repo, although no harm from it being there.
Thanks!
_______________________________________________
SlackBuilds-users mailing list
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Benjamin Trigona-Harany]

Post by Serban Udrea
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 Slackware installs are 64-bit. The matplotlib
SlackBuild worked and one didn't, so it must be something else that is
behind the problem I glad that I am not totally alone in running into
the problem though!

_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-***@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/