matplotlib-devel Mailing List for matplotlib

On 16 Mar 2011, at 09:48, Georges Arsouze wrote:
> I'am working with Python3.1 under Mac Os Snow Leopard
> I download matplotlib with http://www.cgl.ucsf.edu/Outreach/pc204/matplotlib.html
>
> It doesn't work
> Can you help me ?
>
That package, as the site states (though maybe not clearly enough),
has been built for Snow Leopard's system Python 2.6.2, so it cannot
work with Python3.1. If you call python2.6 or /usr/bin/python, you 
should
be able to use matplotlib. But if you need Python3.1, I am afraid you
are stuck for the moment, since the latest release does not support
Python3 yet. I think support is in the works, and may be partly 
available
in the development version, but unless you have considerable experience
in building your own installation, I would not recommend that road.
HTH,
						Derek

Georges Arsouze, on 2011年03月16日 09:48, wrote:
> Hello
> I'am working with Python3.1 under Mac Os Snow Leopard
> I download matplotlib with
> http://www.cgl.ucsf.edu/Outreach/pc204/matplotlib.html
> 
> It doesn't work
> Can you help me ?
Hi Georges,
What version of matplotlib are you trying to run? At the moment,
there isn't a "stable" release which is compatible with Python 3,
and you have to grab it from:
https://github.com/matplotlib/matplotlib-py3
Not all of the backends work in -py3, mostly because the underlying toolkits
have not been ported to Python 3. You can notes about the work in
progress, what's been completed, and what's left to do here:
https://github.com/matplotlib/matplotlib-py3/wiki
(Also, this is more of a matplotlib-users question, so I'm replying
to that list)
best,
-- 
Paul Ivanov
314 address only used for lists, off-list direct email at:
http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 

All,
This is due to the fact that you have nothing to plot and the axes range
defaults to 0->1. Unfortunately 0 cannot map to a valid datetime. I
thought that I had fixed this so that using datetimes would cause the axes
to initialize to a valid datetime value. Once I get up to speed with the
whole 'git' thing and figure out how to make submissions again, etc. 
A quick work-around is to manually set the bounds for our datetime axis and
turn off autoscaling until you have some data to display.
I can probably take another look at it, but I am pretty busy and learning
the git model of doing things is only slowing things down. :(
--James
> -----Original Message-----
> From: Benjamin Root [mailto:ben...@ou...]
> Sent: Friday, March 25, 2011 6:34 AM
> To: Gerrit Kuhlmann
> Cc: mat...@li...
> Subject: Re: [matplotlib-devel] Bug: plot numpy.nans vs. datetime objects
> 
> On Friday, March 25, 2011, Gerrit Kuhlmann
> <ger...@st...> wrote:
> > On Fri, 2011年03月25日 at 01:08 -0700, Paul Ivanov wrote:
> >> Gerrit Kuhlmann, on 2011年03月25日 14:26, wrote:
> >> > Hi all,
> >> >
> >> > I get a ValueError, if I try to plot a list of numpy.nans against
> >> > datetime objects. I'm using Python 2.6.5 and Matplotlib 1.0.1 on
> >> > Ubuntu Linux 10.04. Code and traceback are below.
> >> >
> >> > Best regards,
> >> > Gerrit
> >> >
> >> >
> >> >
> >> > Code
> >> > """"
> >> > import matplotlib.pyplot as plt
> >> > import numpy as np
> >> > from datetime import datetime as DateTime
> >> >
> >> > t = [DateTime(2011,1,day) for day in xrange(1,20)] x = [np.nan for
> >> > i in xrange(1,20)]
> >> >
> >> > plt.plot(t,x)
> >> > plt.show()
> >>
> >> Hi Gerrit,
> >>
> >> Thanks for the report, though I'm not sure what you expect to happen
> >> here?
> >>
> >> Changing at least one of the elements of x to be something other than
> >> nan does not cause the error.
> >>
> >> There is an inconsistency, though, in that plt.plot(x,x) when x is
> >> full of nans does not cause any errors.
> >>
> >> best,
> >
> > Hi Paul,
> >
> > thanks for your answer. I would expect similar behaviour as for
> > "plot([0,1,2], [nan,nan,nan])", which creates an empty plot. A passed
> > through exceptions from the datetime module seems a bit odd.
> >
> > Regards,
> > Gerrit
> >
> 
> Agreed, I just came across this yesterday while working on my general exam
> project. I have no clue why the behavior would be different because we
are
> using datetime objects.
> 
> Ben Root
> 
> 
> >
> > ----------------------------------------------------------------------
> > -------- Enable your software for Intel(R) Active Management
> > Technology to meet the growing manageability and security demands of
> > your customers. Businesses are taking advantage of Intel(R) vPro (TM)
> > technology - will your software be a part of the solution? Download
> > the Intel(R) Manageability Checker today!
> > http://p.sf.net/sfu/intel-dev2devmar
> > _______________________________________________
> > Matplotlib-devel mailing list
> > Mat...@li...
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> >
> 
>
----------------------------------------------------------------------------
--
> Enable your software for Intel(R) Active Management Technology to meet
> the growing manageability and security demands of your customers.
> Businesses are taking advantage of Intel(R) vPro (TM) technology - will
your
> software be a part of the solution? Download the Intel(R) Manageability
> Checker today! http://p.sf.net/sfu/intel-dev2devmar
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

On Friday, March 25, 2011, Gerrit Kuhlmann
<ger...@st...> wrote:
> On Fri, 2011年03月25日 at 01:08 -0700, Paul Ivanov wrote:
>> Gerrit Kuhlmann, on 2011年03月25日 14:26, wrote:
>> > Hi all,
>> >
>> > I get a ValueError, if I try to plot a list of numpy.nans against
>> > datetime objects. I'm using Python 2.6.5 and Matplotlib 1.0.1 on Ubuntu
>> > Linux 10.04. Code and traceback are below.
>> >
>> > Best regards,
>> > Gerrit
>> >
>> >
>> >
>> > Code
>> > """"
>> > import matplotlib.pyplot as plt
>> > import numpy as np
>> > from datetime import datetime as DateTime
>> >
>> > t = [DateTime(2011,1,day) for day in xrange(1,20)]
>> > x = [np.nan for i in xrange(1,20)]
>> >
>> > plt.plot(t,x)
>> > plt.show()
>>
>> Hi Gerrit,
>>
>> Thanks for the report, though I'm not sure what you expect to
>> happen here?
>>
>> Changing at least one of the elements of x to be something other
>> than nan does not cause the error.
>>
>> There is an inconsistency, though, in that plt.plot(x,x) when x
>> is full of nans does not cause any errors.
>>
>> best,
>
> Hi Paul,
>
> thanks for your answer. I would expect similar behaviour as for
> "plot([0,1,2], [nan,nan,nan])", which creates an empty plot. A passed
> through exceptions from the datetime module seems a bit odd.
>
> Regards,
> Gerrit
>
Agreed, I just came across this yesterday while working on my general
exam project. I have no clue why the behavior would be different
because we are using datetime objects.
Ben Root
>
> ------------------------------------------------------------------------------
> Enable your software for Intel(R) Active Management Technology to meet the
> growing manageability and security demands of your customers. Businesses
> are taking advantage of Intel(R) vPro (TM) technology - will your software
> be a part of the solution? Download the Intel(R) Manageability Checker
> today! http://p.sf.net/sfu/intel-dev2devmar
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

On Fri, 2011年03月25日 at 01:08 -0700, Paul Ivanov wrote: 
> Gerrit Kuhlmann, on 2011年03月25日 14:26, wrote:
> > Hi all,
> > 
> > I get a ValueError, if I try to plot a list of numpy.nans against
> > datetime objects. I'm using Python 2.6.5 and Matplotlib 1.0.1 on Ubuntu
> > Linux 10.04. Code and traceback are below.
> > 
> > Best regards,
> > Gerrit
> > 
> > 
> > 
> > Code
> > """"
> > import matplotlib.pyplot as plt
> > import numpy as np
> > from datetime import datetime as DateTime
> > 
> > t = [DateTime(2011,1,day) for day in xrange(1,20)]
> > x = [np.nan for i in xrange(1,20)]
> > 
> > plt.plot(t,x)
> > plt.show()
> 
> Hi Gerrit,
> 
> Thanks for the report, though I'm not sure what you expect to
> happen here?
> 
> Changing at least one of the elements of x to be something other
> than nan does not cause the error.
> 
> There is an inconsistency, though, in that plt.plot(x,x) when x
> is full of nans does not cause any errors.
> 
> best,
Hi Paul,
thanks for your answer. I would expect similar behaviour as for
"plot([0,1,2], [nan,nan,nan])", which creates an empty plot. A passed
through exceptions from the datetime module seems a bit odd. 
Regards,
Gerrit

Gerrit Kuhlmann, on 2011年03月25日 14:26, wrote:
> Hi all,
> 
> I get a ValueError, if I try to plot a list of numpy.nans against
> datetime objects. I'm using Python 2.6.5 and Matplotlib 1.0.1 on Ubuntu
> Linux 10.04. Code and traceback are below.
> 
> Best regards,
> Gerrit
> 
> 
> 
> Code
> """"
> import matplotlib.pyplot as plt
> import numpy as np
> from datetime import datetime as DateTime
> 
> t = [DateTime(2011,1,day) for day in xrange(1,20)]
> x = [np.nan for i in xrange(1,20)]
> 
> plt.plot(t,x)
> plt.show()
Hi Gerrit,
Thanks for the report, though I'm not sure what you expect to
happen here?
Changing at least one of the elements of x to be something other
than nan does not cause the error.
There is an inconsistency, though, in that plt.plot(x,x) when x
is full of nans does not cause any errors.
best,
-- 
Paul Ivanov
314 address only used for lists, off-list direct email at:
http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 

Hi all,
I get a ValueError, if I try to plot a list of numpy.nans against
datetime objects. I'm using Python 2.6.5 and Matplotlib 1.0.1 on Ubuntu
Linux 10.04. Code and traceback are below.
Best regards,
Gerrit
Code
""""
import matplotlib.pyplot as plt
import numpy as np
from datetime import datetime as DateTime
t = [DateTime(2011,1,day) for day in xrange(1,20)]
x = [np.nan for i in xrange(1,20)]
plt.plot(t,x)
plt.show()
Traceback
"""""""""
Exception in Tkinter callback
Traceback (most recent call last):
 File "/usr/lib/python2.6/lib-tk/Tkinter.py", line 1413, in __call__
 return self.func(*args)
 File
"/usr/local/lib/python2.6/dist-packages/matplotlib/backends/backend_tkagg.py", line 245, in resize
 self.show()
 File
"/usr/local/lib/python2.6/dist-packages/matplotlib/backends/backend_tkagg.py", line 248, in draw
 FigureCanvasAgg.draw(self)
 File
"/usr/local/lib/python2.6/dist-packages/matplotlib/backends/backend_agg.py", line 394, in draw
 self.figure.draw(self.renderer)
 File "/usr/local/lib/python2.6/dist-packages/matplotlib/artist.py",
line 55, in draw_wrapper
 draw(artist, renderer, *args, **kwargs)
 File "/usr/local/lib/python2.6/dist-packages/matplotlib/figure.py",
line 798, in draw
 func(*args)
 File "/usr/local/lib/python2.6/dist-packages/matplotlib/artist.py",
line 55, in draw_wrapper
 draw(artist, renderer, *args, **kwargs)
 File "/usr/local/lib/python2.6/dist-packages/matplotlib/axes.py", line
1946, in draw
 a.draw(renderer)
 File "/usr/local/lib/python2.6/dist-packages/matplotlib/artist.py",
line 55, in draw_wrapper
 draw(artist, renderer, *args, **kwargs)
 File "/usr/local/lib/python2.6/dist-packages/matplotlib/axis.py", line
971, in draw
 tick_tups = [ t for t in self.iter_ticks()]
 File "/usr/local/lib/python2.6/dist-packages/matplotlib/axis.py", line
904, in iter_ticks
 majorLocs = self.major.locator()
 File "/usr/local/lib/python2.6/dist-packages/matplotlib/dates.py",
line 743, in __call__
 self.refresh()
 File "/usr/local/lib/python2.6/dist-packages/matplotlib/dates.py",
line 752, in refresh
 dmin, dmax = self.viewlim_to_dt()
 File "/usr/local/lib/python2.6/dist-packages/matplotlib/dates.py",
line 524, in viewlim_to_dt
 return num2date(vmin, self.tz), num2date(vmax, self.tz)
 File "/usr/local/lib/python2.6/dist-packages/matplotlib/dates.py",
line 289, in num2date
 if not cbook.iterable(x): return _from_ordinalf(x, tz)
 File "/usr/local/lib/python2.6/dist-packages/matplotlib/dates.py",
line 203, in _from_ordinalf
 dt = datetime.datetime.fromordinal(ix)
ValueError: ordinal must be >= 1

Matthew Brett, on 2011年03月24日 16:37, wrote:
> Welcome to the wonderful world of git and DVCS!
Thanks, I wish I could claim that I only started using git
recently, but I've just sort of been uncomfortably trying my best
to not cause too much trouble for the past year and a half...
> 
> I think you could have solved this one by:
> 
> git reset --hard 8506c33c811e970c6aa73a446d3ed223ac48f989
> 
> and pushing that. Assuming you had that commit, which I guess you would have.
This actually wasn't the case - I hadn't pulled from
matplotlib/master for a few days, hence the stale commit become a
head after my push.
 
> The way I try and avoid doing that very easy thing is
> 
> 1) Having a moderately frightening name for the upstream remote like
> 'upstream-rw'.
> 2) Having a moderately frightening name for the tracking branch like:
> 
> git co -b main-master --track upstream-rw/master
good tips, thanks.
> 
> 3) Making sure I've got the git-completion bash command line
> completion tools working, so I can always see my branch name
This was actually the case for me - I wasn't working on master,
but a seperate branch called 'one-figure' which didn't have a
remote branch affiliated with it (or a wrong one). I had
previously pushed it using 'git push ivanov one-figure', and
*wrongly* assumed that this state was preserved somewhere
16:46@matplotlib(one-figure)$ 
> 4) Never working on main-master, always branching, and merging when I'm sure.
> 5) Deleting my own master branch to avoid confusion. This involves:
> 
> Going to your github fork, choosing Admin, set default branch to be
> something other than 'master'
> 
> git co that-other-branch
> git branch -D master # delete locally
> git push origin :master # delete on github
> 
> Every error, is a jewel.
Wise words, but if that were true, De Beers and Tiffany's
couldn't hope to compete with me.
best,
-- 
Paul Ivanov
314 address only used for lists, off-list direct email at:
http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7