FS#43392 - [python-matplotlib] does not display data points

Attached to Project: Community Packages
Opened by Alex (Dekalog) - Friday, 09 January 2015, 22:30 GMT
Last edited by Jelle van der Waa (jelly) - Saturday, 08 April 2017, 15:17 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Felix Yan (felixonmars)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
When plotting scattered data with the "," marker, the data points do not show up either on screen (Qt4Agg backend) or in saved bitmap images (tested with png); they do show up if the plot is exported as pdf.

Additional info:
* package version(s)
community/python-matplotlib 1.4.2-3
community/ipython 2.3.1-1
community/python-scipy 0.14.1-1

* config and/or log files etc.
The only thing set in ~/.config/matplotlib/matplotlibrc is
backend : Qt4Agg
interactive : True

Steps to reproduce:
Start python:
$ ipython --pylab
In ipython: Create data and plot (500 randomly scattered points)

import numpy as np
a = np.random.standard_normal(500)
b = np.random.standard_normal(500)
plot(a,b,',')
savefig("testplot.png")
savefig("testplot.pdf")

Expected result: Scatter plot of random data points, both on screen and in saved files.

Actual result: Empty-looking plot both on screen and in png, but plot as expected in pdf.
This task depends upon

Closed by  Jelle van der Waa (jelly)
Saturday, 08 April 2017, 15:17 GMT
Reason for closing:  No response
Additional comments about closing:  No response for a year
Comment by Felix Yan (felixonmars) - Saturday, 10 January 2015, 15:23 GMT
Did you report this upstream? This looks like an upstream issue to me.
Comment by Alex (Dekalog) - Saturday, 10 January 2015, 17:46 GMT
I didn't report it upstream yet. Are the arch-packages unmodified enough for me to go straight to upstream, or will they send me straight back?
Also, can you reproduce the bug?
Comment by Alex (Dekalog) - Monday, 09 February 2015, 22:39 GMT
Upstream says (and I can confirm) that it's fixed in 1.4.3rc1.
For reference, check the matplotlib mailinglist...
Comment by Felix Yan (felixonmars) - Friday, 27 February 2015, 15:57 GMT
matplotlib 1.4.3 released to [community], does it fix your problem too?

Loading...