Hi team,
We've been discussing at several occasions of cleaning up our GitHub
labels, and merging some. In order to guide the discussion of which
labels to keep and to move, I've analysed a bit what where the labels
we were using. Attached is a plot of the number of issues (including
PRs) open
Hello everyone,
Nathan just proposed names for the new vega colors:
https://github.com/matplotlib/matplotlib/issues/7248
As Antony mentioned, getting the names right is quite important as
this is probably going to be the default for the next 10 years.
Cheers,
N
Congrats on the new position!
On 30 September 2015 at 14:18, Michael Droettboom wrote:
> Just a heads up to the matplotlib developer team:
>
> I'm leaving Space Telescope for a new position at Continuum Analytics
> starting next week. This position will be primarily to work on
of opportunity for someone else to submit a tutorial for more
advanced users!
Cheers!
Ben Root
On Thu, Mar 12, 2015 at 6:46 PM, Nelle Varoquaux
nelle.varoqu...@gmail.com wrote:
Hi everyone,
Is someone submitting a tutorial on matplotlib? The call for
tutorial is open, and I think
Hello everyone,
(I apologize for the cross posting).
This is a quick reminder that the call for submission for Scipy 2015
is open but due April 1st! There is only 7 days left to submit a
proposal.
Thanks,
Nelle
-- Forwarded message --
From: Courtenay Godshall
Hi everyone,
Is someone submitting a tutorial on matplotlib? The call for tutorial is
open, and I think it would be nice to have one on matplotlib.
Cheers,
N
-- Forwarded message --
From: SciPy 2015 Organizers scipy-organiz...@scipy.org
Date: 11 March 2015 at 01:02
Subject:
Thanks again Thomas for the release !
Cheers,
N
On 17 February 2015 at 06:09, Thomas Caswell tcasw...@gmail.com wrote:
Hello all,
We are pleased to announce the release of matplotlib v1.4.3!
Wheels, windows binaries and the source tarball are available through both
source-forge [1] and
On 16 February 2015 at 19:36, Eric Firing efir...@hawaii.edu wrote:
On 2015/02/16 8:23 AM, Nelle Varoquaux wrote:
IMO, never.
Rationale, please?
Consistency: it is never capitalized in matplotlib's documentation.
Eric
IMO, never.
Rationale, please?
Consistency: it is never capitalized in matplotlib's documentation.
True, and a valid point--but we could easily change that. Wouldn't it make
it bit more readable if sentences always started with a capital letter?
Starting with lower case just looks
IMO, never.
On 16 February 2015 at 19:16, Benjamin Root ben.r...@ou.edu wrote:
I am in the final rounds of edits for my book and a question has come up
between me and the editors. When should the matplotlib be capitalized?
1) never
2) mostly never (even in the beginning of a sentence),
On 14 July 2014 00:10, Damon McDougall damon.mcdoug...@gmail.com wrote:
On Sun, Jul 13, 2014 at 12:27 AM, Eric Firing efir...@hawaii.edu wrote:
On 2014/07/12, 7:20 PM, Thomas Caswell wrote:
Hey all,
After a very productive sprint at scipy (according to pluse, we merged
35 PRs in the
Hi everyone!
I'm currently reviewing PR critical for 1.4: can people make sure to tag
those as release_critical? There is only two open right now.
Cheers,
N
--
___
Our standard test has gotten out of control. The most serious problem is
that running a full test suite now fails on a linux VM with 4 GB--it's out
of memory. Half-way through the set, it is already using more than 2 GB.
That's ridiculous. Running nosetests separately on each test module
Hello everyone,
Just a quick reminder that the EuroScipy call for abstracts closes on the
14th: don't forget to submit your talk proposal! It is in four days only!
In short, EuroScipy is a cross-disciplinary gathering focused on the use
and development of the Python language in scientific
Does anyone know why we are seeing a huge number of PEP 8 failures now?
It looks to me like it is a change in which modules are subject to the
test, or in which tests are grounds for failure. I don't know how all
this is set up, though.
If it started very recently, it could be linked to
Hello,
I've not been very active in the development of matplotlib these past
few months, but I'll answer anyways.
I'll be at Scipy this year, but I won't be able to stay after the
sprints. I have another conference right after.
Cheers,
N
On 2 March 2014 04:37, Thomas Caswell tcasw...@gmail.com
On 6 March 2014 21:47, Skip Montanaro s...@pobox.com wrote:
On Thu, Mar 6, 2014 at 2:38 PM, Ryan May rma...@gmail.com wrote:
I don't think a leading _ is the way to go, because that's a common
convention for internal class variables--property variables that you don't
intend to be part of any
On 6 March 2014 21:53, Federico Ariza ariza.feder...@gmail.com wrote:
Nelle
Is that written somewhere?
I think the convention originated from google's python style guide.
Pylint should warn you if you don't use this convention.
On Thu, Mar 6, 2014 at 3:51 PM, Nelle Varoquaux
nelle.varoqu
On 6 March 2014 22:03, Skip Montanaro s...@pobox.com wrote:
On Thu, Mar 6, 2014 at 2:51 PM, Nelle Varoquaux
nelle.varoqu...@gmail.com wrote:
The convention is to use a simple _.
mode, _, dev, nlink, uid, gid, size, _, _, _ = os.stat(/etc/hosts)
Which is pylint-compliant, but removes any
Hi,
For the CI stuff, I think it would be worth discussing this with the
Enthought guys, specifically Didrik Pinte and David Cournapeau.
From what I understood, they are developping some stuff to
automatically build canopy from projects hosted on github. Hence, they
have to run all the tests, on
that soon.
I fixed the copyright (Github takes a while to update the pages, hence it
might not be up yet).
On Thu, Aug 8, 2013 at 10:48 AM, Nelle Varoquaux
nelle.varoqu...@gmail.comwrote:
Hi everyone,
Here is my attempt at making the website:
http://nellev.github.io/tmp/jhepc/index.html
Hello,
At Scipy, we briefly discussed the possibility of having the nicest plots
of the John Hunter Excellence in Plotting Contest on matplotlib's website,
with the code available.
I personnally would love to be able to see those plots again, and the code
used to generate them. It would also be
On 31 July 2013 15:11, Michael Droettboom md...@stsci.edu wrote:
(I've Cc'd the scipy organizers list who should probably be able to
address your questions).
On 07/31/2013 06:09 AM, Nelle Varoquaux wrote:
Hello,
At Scipy, we briefly discussed the possibility of having the nicest
plots
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
It was me :-)
Only a day to day user who follow matplotlib (and other famous libs)
development. I clicked on the survey thinking it was public. Anyway it was
only curiosity so if you prefer keep it secret, it's cool for me !
Keep the good work guys !!!
You could provide the summary view
On 18 July 2013 15:27, Michael Droettboom md...@stsci.edu wrote:
On 07/17/2013 04:57 PM, Eric Firing wrote:
On 2013/07/17 3:14 AM, Michael Droettboom wrote:
Yes. This is great work!
Just to chime in (after having been away for most of this conversation)
--
I think we can do this
FYI, I have started the refactoring we discussed at scipy. I think
what tony is suggesting is the same thing.
I've created a work in progress pull request:
https://github.com/matplotlib/matplotlib/pull/2213
In the refactoring we discussed at Scipy, we did not mention the
pyplots wrapper at all.
Hello pythonistas,
We've just finished refactoring the axes module at the scipy sprint, and
before merging we would like to inform developers of the changes. The axes
module contained more than 9k loc, and a few classes. It used to be a file.
Now, it became a folder called axes. This module
No, there was no such message. That is all that was displayed to my
screen.
I've seen this error before, and I think cleaning up all sphinx caching and
temporary files fixed it.
Try running a python make.py clean before building the documention.
Cheers,
N
I'm hoping to host a matplotlib sprint during the final two days of Scipy
2013 this year, and I hope to see as many as possible of you there. I
think it's also really important to bring new developers into sprints,
because it's such an efficient way to get people familiar with the code
On 22 March 2013 18:06, Michael Droettboom md...@stsci.edu wrote:
On 03/22/2013 12:45 PM, Nelle Varoquaux wrote:
I'm hoping to host a matplotlib sprint during the final two days of
Scipy 2013 this year, and I hope to see as many as possible of you there.
I think it's also really
Hello,
Since I've updated my master branch, I have a new error when installing
matplotlib. It seems it doesn't find a header file from numpy:
I've reinstalled numpy (development version), and I tried to reinstall
everything (on python 2.6) but I still get the error. Am I the only one
having
That's weird. Did you try installing a stable numpy version instead?
I tried compiling mpl against numpy 1.6.2 and everything worked out
fine.
I'm reinstalled everything, and it works fine. I still have problems when I
switch from an old branch (before the merge of the packaging changes)
Hi all,
Recently, it has become more and more common that the travis builds
fail. They fail not because the test suite fails but because of some
inherent issues with travis itself. Usually, either the git clone
fails or some other simple shell command fails. I consider these
'failures'
.
Cheers,
Mike
Thanks,
N
Mike
On 01/07/2013 10:24 AM, Nelle Varoquaux wrote:
Hello everyone,
I was recently looking at the cbook module, and I was wondering
whether this module was public or not. I think there are several
unused method
Hi all,
A while back, Mike drafted a MEP to modernize the documentation:
https://github.com/matplotlib/matplotlib/wiki/Mep10
The main idea behind this MEP is to use the full potential of new tools and
conventions available for sphinx, to make the documentation more readable,
maintainable and
a PR.
Cheers,
Mike
Thanks,
N
Mike
On 01/07/2013 10:24 AM, Nelle Varoquaux wrote:
Hello everyone,
I was recently looking at the cbook module, and I was wondering
whether this module was public or not. I think there are several
unused method in it, such as ``unmasked_index_ranges
Hello everyone,
I was recently looking at the cbook module, and I was wondering
whether this module was public or not. I think there are several
unused method in it, such as ``unmasked_index_ranges``. If this isn't
public, it may be worth cleaning the module a bit and removing the
unused method.
useful to anyone.
Thanks,
N
Mike
On 01/07/2013 10:24 AM, Nelle Varoquaux wrote:
Hello everyone,
I was recently looking at the cbook module, and I was wondering
whether this module was public or not. I think there are several
unused method in it, such as ``unmasked_index_ranges
Any thoughts? Do we go back to Sourceforge for our download hosting? Is
anyone familiar with any other services? Do we try to piggy-back on what
other scipy projects are doing?
Scikit-learn uses sourceforge.
Scikits-image doesn't provide download links on the website (except
for windows
One package (Pysam) that I use a lot relies on Cython, and requires
users to install Cython before they can install Pysam itself. With Cython,
is that always the case? Will all users need to install Cython? Or is it
sufficient if only matplotlib developers install Cython?
You can set
On 15 October 2012 06:10, Eric Firing efir...@hawaii.edu wrote:
On 2012/10/14 12:44 PM, Damon McDougall wrote:
On Sun, Oct 14, 2012 at 9:22 PM, Eric Firing efir...@hawaii.edu wrote:
All,
I think we are in a messy situation, and we need to reach some agreement
as to how to proceed.
On 15 October 2012 04:49, Jae-Joon Lee lee.j.j...@gmail.com wrote:
I'd agree with Eric on most of his points.
On Mon, Oct 15, 2012 at 5:22 AM, Eric Firing efir...@hawaii.edu wrote:
If some of the PEP8 commits include genuine bug-fixes that need to be in
v1.2.x, then these fixes should be
Hi Ben,
Seems like github is down at the moment, and I wanted to relay something I
have noticed in some of the PEP8 changes:
I'm guessing it's on one of my PR
The preferred place to break around a binary operator is *after* the
operator, not before it.
I am seeing some proposed changes
Hello,
Do you still accept pep8 cleaning up ? I've got a couple of important
deadlines coming up soon, but I might be able to clean up the whole code.
Thanks,
N
On 10 September 2012 18:00, Michael Droettboom md...@stsci.edu wrote:
Today is the scheduled day for release candidate 1.2rc1.
We
Hello,
I've just checked out the source code from github, and I ran the
tests. Unfortunately, I get loads of errors (more than 1k), most of
them such as the following:
==
ERROR: matplotlib.tests.test_text.test_multiline.test
On 28 August 2012 16:01, Benjamin Root ben.r...@ou.edu wrote:
On Tue, Aug 28, 2012 at 9:58 AM, Benjamin Root ben.r...@ou.edu wrote:
On Tue, Aug 28, 2012 at 9:47 AM, Nelle Varoquaux
nelle.varoqu...@gmail.com wrote:
Hello,
I've just checked out the source code from github, and I ran
47 matches
Mail list logo