The example works fine with matplotlib 1.4.0, python 3.4.0 (not from Anaconda)
with Mac OS X Maverick.
Best,
-Michiel.
On Wed, 9/17/14, Christophe Bal wrote:
Subject: [Matplotlib-users] Anaconda Mac or matplolib bug ?
To: anaco...@continuum.io, ma
many thanks - was struggling to find out where's the document!
On 16 September 2014 17:20, Scott Lasley wrote:
>
> On Sep 16, 2014, at 11:31 AM, Xiaobo Yang wrote:
>
> > Hi,
> >
> > My X axis represents dates. When I used get_xlim(), I got something like
> 735461.0 and 735490.5. What are these
Hello.
I do not know the guilty people in this story. The following code works
with Anaconda Python 3 on Lubuntu 14 but it does not with Anaconda Python 3
Mac OS Maverick. Why ?
This message has been posted on both the list of Anaconda and the one of
matplotlib.
Christophe
=== Code ===
# Sourc
On Sep 16, 2014, at 11:31 AM, Xiaobo Yang wrote:
> Hi,
>
> My X axis represents dates. When I used get_xlim(), I got something like
> 735461.0 and 735490.5. What are these values? How can I convert to python
> date objects?
>
> Many thanks,
> Tom
See the matplotlib dates documentation at
h
Le 16/09/2014 17:31, Xiaobo Yang a écrit :
> My X axis represents dates. When I used get_xlim(), I got something
> like 735461.0 and 735490.5. What are these values? How can I convert
> to python date objects?
Please, read the documentation of datetime.
Your data are *ordinals*, numbers which
Hi,
My X axis represents dates. When I used get_xlim(), I got something like
735461.0 and 735490.5. What are these values? How can I convert to python
date objects?
Many thanks,
Tom
--
Want excitement?
Manually upgrade yo
Just posted some small code under
https://github.com/matplotlib/matplotlib/issues/3522
I guess the formatting is not up to standards, but I did not find
another way to attach the code...
Cheers, Gerd
On 16.09.2014 15:29, Benjamin Root wrote:
Perhaps something is odd with the date values you
Perhaps something is odd with the date values you have? Can you make an
SSCCE (sscce.org)that demonstrates the problem? There is definitely some
sort of bug at play here.
Cheers!
Ben Root
On Tue, Sep 16, 2014 at 9:20 AM, Gerd Wellenreuther <
gerd.wellenreut...@xfel.eu> wrote:
> Tried this befor
Tried this before, I think, here is the traceback (it is kind of
different) - maybe it tells some of you where to look at IF this should
really be a bug:
Traceback (most recent call last):
File "C:\Users\gwellenr\Desktop\Test_Sabine\Plot_csv.py", line 187,
in
matplotlib.pyplot.savefig
I would still consider this to be a bug, though. Gerd, could you please
file a bug report?
Cheers!
Ben Root
On Tue, Sep 16, 2014 at 7:45 AM, Joe Kington wrote:
> A quick way to do this is ``ax.invert_yaxis()`` (and invert_xaxis() for
> the x-axis). That way you preserve auto-scaling and don't
A quick way to do this is ``ax.invert_yaxis()`` (and invert_xaxis() for
the x-axis). That way you preserve auto-scaling and don't wind up with
manually set axis limits.
What you did should have worked, but ``ymin`` and ``ymax`` are probably
datetime objects. ``ylim`` isn't smart enough to conve
Dear all,
I hope some of you could help me out. I am currently trying to generate
some timetables using matplotlib.pyplot.plot_date, having the time-axis
on the y-axis. Typically, one would like to read these plots from top to
bottom, from older to newer items (future on the bottom). Unfortunat
12 matches
Mail list logo
