On 07/23/2013 03:33 PM, Benjamin Root wrote:
Just checked out rc5 from git and did an install, and ran into a
pyparsing version check issue.
What was the issue? Is it that you had 2.0.1 which rc5 still considers
to be incompatible with Python 2? I'd like to know specifically what
happened
Thanks. I will address these issues before final.
None of this is new -- we've gone through 5 release candidates over many
weeks. Why is this just coming to light now?
Mike
On 07/23/2013 11:16 PM, Michiel de Hoon wrote:
I noticed that this release candidate will always skip the Mac OS X
Would you mind testing https://github.com/matplotlib/matplotlib/pull/2250
On 07/23/2013 11:16 PM, Michiel de Hoon wrote:
I noticed that this release candidate will always skip the Mac OS X
backend,
as the .check() method of BackendMacOSX in setupext.py returns None.
Adding
return darwin
On Wed, Jul 24, 2013 at 9:39 AM, Michael Droettboom md...@stsci.edu wrote:
On 07/23/2013 03:33 PM, Benjamin Root wrote:
Just checked out rc5 from git and did an install, and ran into a
pyparsing version check issue.
What was the issue? Is it that you had 2.0.1 which rc5 still considers
Same with me. I had a stale pyparsing.pyc file in the MPL source directory
(presumably from an old MPL version) whose version # was too old. When mpl
tried to 'import pyparsing', it found that version, and raised an error. Of
course, if I tried import pyparsing; print pyparsing.__version__ from my
We could update the makefile so that make clean really cleans up the
installation junk before installing a new version. I personnally would
find it very useful, but the makefile needs a bit of love. Typically make
would run make clean and make install.
I can work on that if people agree that
.
From: Michael Droettboom md...@stsci.edu
To: Michiel de Hoon mjldeh...@yahoo.com
Cc: Benjamin Root ben.r...@ou.edu; matplotlib-devel@lists.sourceforge.net
matplotlib-devel@lists.sourceforge.net
Sent: Wednesday, July 24, 2013 10:36 PM
Subject: Re: [matplotlib-devel] 1.3.0rc5 tagged
...@stsci.edu
*To:* Michiel de Hoon mjldeh...@yahoo.com
*Cc:* Benjamin Root ben.r...@ou.edu;
matplotlib-devel@lists.sourceforge.net
matplotlib-devel@lists.sourceforge.net
*Sent:* Wednesday, July 24, 2013 10:36 PM
*Subject:* Re: [matplotlib-devel] 1.3.0rc5 tagged
Thanks. I will address these issues
In article 51edb794.9010...@stsci.edu,
Michael Droettboom md...@stsci.edu
wrote:
On 07/22/2013 05:59 PM, Russell E. Owen wrote:
In article 51e9681b.3010...@stsci.edu,
Michael Droettboom md...@stsci.edu
wrote:
At long last, I have a 1.3.0rc5 tagged. I really hope to the software
Just checked out rc5 from git and did an install, and ran into a pyparsing
version check issue. Turns out I completely forgot to do a git clean
-fxd. Doing that fixed the problem. When we officially announce this,
perhaps it would be best to mention that command? In addition, it would
probably
I noticed that this release candidate will always skip the Mac OS X backend,
as the .check() method of BackendMacOSX in setupext.py returns None. Adding
return darwin
or some other string solves the issue.
Also, if I am not mistaken, the files under
lib/matplotlib/backends/Matplotlib.nib (as
On 07/22/2013 05:59 PM, Russell E. Owen wrote:
In article 51e9681b.3010...@stsci.edu,
Michael Droettboom md...@stsci.edu
wrote:
At long last, I have a 1.3.0rc5 tagged. I really hope to the software
deities that this is the last rc before final.
If you wouldn't mind creating and
At long last, I have a 1.3.0rc5 tagged. I really hope to the software
deities that this is the last rc before final.
If you wouldn't mind creating and posting the binaries, I'll make an
announcment on matplotlib-users, give this a week and then put final out.
Cheers,
Mike
13 matches
Mail list logo
