I'm not quite back to normality here after getting back from over a month
out of the office (Scipy'13 taking a chunk of that time) and didn't manage
to fill in the questionnaire. I guess it doesn't matter too much that I
didn't manage to fill it in (I know my own users, all 250+ of them, pretty
wel
Hi,
Just wanted to say that I am currently at the IPython developers' meeting
in case, so I can act as a conduit in case anybody has any suggestions /
comments / bugs related to the matplotlib--IPython interaction.
David.
--
Dr. David P. Sanders
Profesor Titular "A" / Associate Professor
Depar
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 i
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
ba
Thanks, David. I'll let you know. I am also planning on coming in by
Google Hangout on Thursday and possibly parts of Friday.
Mike
On 07/24/2013 09:10 AM, David P. Sanders wrote:
Hi,
Just wanted to say that I am currently at the IPython developers'
meeting in case, so I can act as a condui
Sorry. We could have handled that better. I think we will probably do
this again in the future, so we'll have an opportunity to be more
explicit about these things.
Mike
On 07/24/2013 08:37 AM, Phil Elson wrote:
I'm not quite back to normality here after getting back from over a
month out o
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"
First, I should say out loud that I'm personally embarrassed by how long
it's taken to go from release candidate to a final release in the 1.3.0
cycle. For those that haven't been following along the hold ups have
all been along the lines of showstoppers like "won't install on platform
X", so
On Wed, Jul 24, 2013 at 9:39 AM, Michael Droettboom 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 to
> be i
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 m
On Jul 24, 2013, at 7:23 AM, Michael Droettboom wrote:
Part of this is due to the change to setuptools/distribute,
Even though I was the one who spearheaded the move
to setuptools, I'm wondering whether we shouldn't examine backtracking
on some of this for the 1.4.x release.
I don't think s
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 ha
Hi Michael,
> Thanks. I will address these issues before final.
Thanks.
> None of this is new -- we've gone through 5 release candidates over many
> weeks. Why is this just coming to light now?
The output of running "python setup.py build" passes by quickly, and people
(including myself)
On 07/24/2013 11:36 AM, Michiel de Hoon wrote:
Hi Michael,
> Thanks. I will address these issues before final.
Thanks.
>None of this is new -- we've gone through 5 release candidates over
many weeks. Why is this just coming to light now?
The output of running "python setup.py build" passe
Hi David, everyone,
David P. Sanders, on 2013-07-24 08:10, wrote:
> Just wanted to say that I am currently at the IPython
> developers' meeting in case, so I can act as a conduit in case
> anybody has any suggestions / comments / bugs related to the
> matplotlib--IPython interaction.
I've been a
Great, thanks Paul -- much better conduit solution :)
On Wed, Jul 24, 2013 at 12:44 PM, Paul Ivanov wrote:
> Hi David, everyone,
>
> David P. Sanders, on 2013-07-24 08:10, wrote:
> > Just wanted to say that I am currently at the IPython
> > developers' meeting in case, so I can act as a condui
https://github.com/matplotlib/matplotlib/issues/2243
The above issue raises the question of whether the default for aspect
ratio handling should be "datalim" instead of "box". The big advantage
is that this completely avoids the problem described in the issue, where
setting aspect='equal' can
In article <51edb794.9010...@stsci.edu>,
Michael Droettboom
wrote:
> On 07/22/2013 05:59 PM, Russell E. Owen wrote:
> > In article <51e9681b.3010...@stsci.edu>,
> > Michael Droettboom
> > wrote:
> >
> >> At long last, I have a 1.3.0rc5 tagged. I really hope to the software
> >> deities t
18 matches
Mail list logo
