Depending on the exact use case you can get pretty good mileage out of
blitting (See http://matplotlib.org/api/animation_api.html#funcanimation for
an explanation or how it is used in the widgets module).
The best way to make things faster is to just do less work :)
Tom
On Thu, Sep 21, 2017 at 5
Folks,
Matthias as just helped us to install the meeseeks bot than ipython /
jupyter is using to help with their backporting onto matplotlib.
For details, see https://github.com/MeeseeksBox/MeeseeksDev .
The most important command is
@MeeseeksDev backport [to] {branch}
to automatically open a
That wording is unclear. Could you open a PR on github to fix that? For
small wording changes like this you can do it through the github web
interface.
Tom
On Mon, Jul 31, 2017 at 6:52 AM wrote:
> "*shrink* 1.0; fraction by which to shrink the colorbar"
>
>
> should be something like
>
>
> "*
Folks,
Sorry for the late notice. This weeks call have been moved to today at the
normal time (1500 EDT).
Tom
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://s
We have moved our mailing lists hosting to python.org, the source-forge
lists should no longer be used.
The new lists are
matplotlib-de...@python.org
https://mail.python.org/mailman/listinfo/matplotlib-devel
matplotlib-us...@python.org
https://mail.python.org/mailman/listinfo/matplotlib-users
mat
Did you mean 1.4.1 instead of 1.5.1 ?
Exactly which paths are you looking at and how are you generating then on
the mpl side? We have many ways to generate the paths and there maybe
inconsistence in how closed paths are handled.
Tom
On Wed, Aug 12, 2015, 1:57 PM Andrés Vargas wrote:
> Hello,
>
One of my co-workers brought this to my attention:
http://savvastjortjoglou.com/nba-shot-sharts.html
Tom
--
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.
Hey all,
Everyone should be aware of
https://github.com/matplotlib/matplotlib/pull/4787 which is both a very
simple, but very important change to the mpl API by providing a minimal API
to pass labeled data (that is anything that `foo[key]` return an array-like
object) into mpl plotting functions.
This should be fixed now, Thanks for reporting this!
Tom
On Fri, Jul 24, 2015 at 10:06 AM Thomas Caswell wrote:
> Sorry, i must have broken that when I updated the docs to have the banner,
> i will look into fixing it asap.
>
> Tom
>
> On Fri, Jul 24, 2015, 7:04 AM Pierr
Sorry, i must have broken that when I updated the docs to have the banner,
i will look into fixing it asap.
Tom
On Fri, Jul 24, 2015, 7:04 AM Pierre Haessig
wrote:
> Le 24/07/2015 15:10, Jens Nielsen a écrit :
> > In the mean time you can use the development version of the docs up
> > here: htt
There is a discussion over names happening in a scikit-image PR thread (
https://github.com/scikit-image/scikit-image/pull/1599)
There is a proposal for naming options A-C as {'ignis', 'ortus', 'fyrian'}
in some order.
Commenting here and copying the devel list so it gets some visibility.
On We
.
Tom
Note: I have trimmed the
On Mon, Jul 13, 2015 at 4:54 AM Philipp A. wrote:
> Thomas Caswell schrieb am So., 12. Juli 2015 um
> 18:21 Uhr:
>
>> The new default color map will be 'viridis' (aka option D).
>>
>
> hi,
>
> how did you get to that
he current default
values will be a single line of python (`mpl.style.use('classic')`).
Please distribute this as widely as possible. We only want to do this once
and want to get feedback from as many users as possible.
Thomas Caswell
PS jet is harmful to you and those around you
plt
> > import seaborn as sns
> >
> > N = 100
> > y1 = np.random.randn(N) + 3.0
> > y2 = np.random.randn(N) * 5.0 + 50
> > y3 = np.ones(N) * 100 # causing plt.violinplot problem
> > y4 = np.arange(0) # causing plt.violinplot problem
> >
> > #pl
The KDE computation code is a copy of the KDE code from scipy (
https://github.com/scipy/scipy/blob/master/scipy/stats/kde.py), I suggest
raising this issue on their mailing list/github.
I strongly suspect that violin plot should be doing data sanitation on the
way in or catching exceptions like
We would like to tag 1.5 around scipy and it would be nice to get the new
color maps out, even if they are not yet the default.
On Wed, Jul 1, 2015, 11:13 PM Nathaniel Smith wrote:
> On Jul 1, 2015 6:31 PM, "Eric Firing" wrote:
> >
> > On 2015/07/01 1:56 PM, Nathaniel Smith wrote:
> > > On Tue,
Hey all,
I just moved the stand alone cycler repo to be owned by the matplotlib org
in preparation for it (hopefully) be a required dep in the near future.
The plan is to get a v0.9 up on pypi ASAP and I will be pushing directly to
master for the time being. Once it is tagged and posted I would
Yes, the size related functions in collections were added in the 1.4 series.
See
http://matplotlib.org/users/whats_new.html#added-size-related-functions-to-specialized-collections
Tom
On Thu, Jun 25, 2015, 11:50 AM Benjamin Root wrote:
> Which version of matplotlib are you using. The set_sizes
Who will be around for the sprints? We should start to come up with a list
what we want to work on. There are a number of issues tagged as
'hack-a-thon' which are good candidates for novice contributors.
A few major projects that need attention are:
- sorting out how to reliably find freetype
I am not sure what you mean by cherry-picking/uncherry picking. I just
looked at what is on `color_overhaul` which is not in master and it is:
changes that should be discarded (changes to cxx / changes to _tri.* that
rely on cxx), one change related to mathtext layout (and conflicts due to
mathext
As a heads up, there is now a `pyplot` and a `pylab` packages on pypi.
I have created an issue with the pypi folks
https://sourceforge.net/p/pypi/support-requests/512/
and with both projects
https://github.com/javipalanca/pylab/issues/1
https://github.com/sirrice/pyplot/issues/2
I found both of t
Following up on the last email, I would like to aim for a 1.5 release at
the end of July, with the sprint at scipy being focused on finishing it
off. The 2.0 color/style release will happen (hopefully soon) after that.
Does this schedule seem ok to everyone?
I have started to triage the issues/
Hey all,
Today we had a phone call with myself, Eric Firing, Micheal
Droettboom, Stéfan van der Walt, and Nathaniel Smith to discuss the path
forward for the changes to the default color map / style. The notes are
below:
- re-order feature release/style change if needed
- can focus sprint ef
There is a proof-of-concept implementation of this by Matthias
http://carreau.github.io/posts/09-Matplotlib-And-IPython-Config.html
Tom
On Fri, May 15, 2015 at 4:40 PM Brian Granger wrote:
> OK i have the MEP for this on my todo list...
>
> On Thu, May 14, 2015 at 5:47 AM, Benjamin Root wrote
There is an on-going discussion over on the pandas issue tracker about how
to 'pipe' a dataframe into an arbitrary function. This is relevant to mpl
as one of the primary use-case for this is plotting.
https://github.com/pydata/pandas/issues/10129
It would be good if more mpl developers than jus
, and
FancyArrow (which I do not have a clear view of yet).
Tom
On Fri, May 15, 2015 at 11:04 AM Neil Girdhar wrote:
> On Fri, May 15, 2015 at 10:53 AM, Thomas Caswell
> wrote:
>
>> A few very quick comments (just skimmed the docstrings)
>>
>> We already have a mpl.path.Path
TurnedSquare
> TipCombination (accepts multiple tips and merges them)
> """
> def __init__(self, draw=None, fill=True, reversed_=False):
> pass
>
> def convex_hulls(self, line_width):
> """
> Returns
Diego,
Thank you for looking in to this.
What version of the source are you working off of? The location of those
headers was recently moved and they no longer exist on master.
I have opened a PR with this patch (
https://github.com/matplotlib/matplotlib/pull/4431) and it should go in for
the c
It is my understanding that most of this code pre-dates properties and
going through and updating all of the classes is a _huge_ amount of work.
It is more a matter of time than will.
There is also a slowly simmering discussion about implementing artists in a
managed property/attribute frame work
>>> On Wed, May 13, 2015 at 9:10 PM, Benjamin Reedlunn
>>> wrote:
>>>
>>>> Yes, I fully agree that we need to unify the many different ways to
>>>> draw arrows.
>>>>
>>>> Neil, in case an example would be helpful for you, I have
rue, else to
> right?
> - Why do you expect the second expression to work? Is ** supposed to have
> lower preference than "or"? (Which seems weird to me.)
>
> Thanks!
>
> Juan.
>
> On Thu, May 14, 2015 at 5
The other thing that should be done is to unify the (I think 7?!?) unique
ways to draw arrows in mpl.
On Wed, May 13, 2015 at 4:52 PM Neil Girdhar wrote:
> Yes, I just noticed that as well. That's how the tikz pgf code looks (a
> sequence of line_to and curve_to commands and so on) so it should
The failures on python nightly are currently due to a bug in python (
http://bugs.python.org/issue24176)
Tom
--
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring sup
I think that so long as you maintain the mapping of 'manager' to be 'gui
element holding the Figure' (rather than 'gui window holding figure')
numbering the managers should be ok. That is, the tabs are the managers
and the multi-figure windows are a layer above the managers.
The notion of 'figur
That sounds reasonable to me. My only concern is getting enough (any?)
bandwidth from enough of the core mpl developers.
IPython and scikit image both have gitter rooms running that seem to
working well for them as well, is there any reason to go with slack over
gitter?
Tom
-- Forwarded
1.4.x was always the latest release in the v1.4
> series.
>
> False alarm. Sorry.
>
> M
>
> On 4/25/15 4:26 PM, Thomas Caswell wrote:
> > The commit that fixes that
> >
> https://github.com/matplotlib/matplotlib/commit/40720ef9fb5de75d908d0ce433d5c3bb8902884f
>
not clear to me if
> the preferred medium for discussion is the mailing list or the PR comments).
>
>
> Nicolas
>
> > On 25 Apr 2015, at 23:04, Thomas Caswell wrote:
> >
> > The MEP tree has been moved into the main repo
> https://github.com/matplotlib/matplotlib/t
The MEP tree has been moved into the main repo
https://github.com/matplotlib/matplotlib/tree/master/doc/devel/MEP
I am pretty excited about this feature.
I don't remember if this got mentioned upthread, but this ties in with
https://github.com/matplotlib/matplotlib/issues/1109 as a nice way to se
Sorry this never got a response. I also have no idea where to start, but
mpl depends an numpy (which has significant c code) and a number of c
extensions internally (Agg for rasterization, freetype for font rendering).
I would suggest starting with figuring out how to compile numpy as it is
requi
The commit that fixes that
https://github.com/matplotlib/matplotlib/commit/40720ef9fb5de75d908d0ce433d5c3bb8902884f
should be in 1.4.1 an onward. Exactly which version are you using?
There will be no 1.4.4.
On Tue, Apr 21, 2015 at 11:00 AM Michael Kaufman wrote:
> Is there any possibility of b
Kelvin,
Thank you for your work. Would it be possible for you to open a pull
request on git hub with these changes (that is where we so almost all of
our code review recently and is hooked in to a continuous integration
service).
I have not looked at the diff yet (still on my phone), but from loo
up for teaching it.
> Cheers!
> -Joe
>
> On Sun, Mar 29, 2015 at 9:17 PM, Thomas Caswell
> wrote:
>
>> Ben,
>>
>> Have you sorted out if you can make scipy this year and does anyone want
>> to be back up on teaching the tutorial?
>>
>> It seems
15 at 5:06 PM Michael Droettboom wrote:
> This sounds great. Unfortunately, I can't attend Scipy this year due to
> a family commitment, but would be more than happy to help put together and
> review materials beforehand.
>
> Cheers,
> Mike
>
>
> On 03/26/2015 10:
I also think we should have a 'state of the library' talk.
We definitely have a few important things to announce/show off:
- FSA
- nbagg/notebook
- new default colors
- style module
and should have a couple more by July
- sane serialize/deserialize + interop with plotly/bokeh
- better
I am proposing to move the MEPs from the wiki into the main documentation.
https://github.com/matplotlib/matplotlib/pull/4249
The main benifits to this are to make preserve the MEPs long term, to keep
a better history of their development, and to improve the discussion around
them.
The motivatio
> places like plt.subplots and GridSpec and such.
> >
> > A thought... could this perhaps be extended somehow to specify colorbars
> in the layout? I am not sure how I would do that, but if we could come up
> with a way to do it, *that* would make this a killer feature. But eve
Cool. I think it make sense to put this in to `pyplot.py` next to
`subplots`
Tom
On Wed, Mar 18, 2015 at 1:14 PM Nicolas P. Rougier
wrote:
>
> Hi,
>
> I've been experimenting with a simple idea for specifying plot layout in a
> rather intuitive way.
> The idea is simply to "draw" your layout u
Also see https://github.com/matplotlib/matplotlib/issues/3889
On Wed, Mar 18, 2015 at 10:22 AM Benjamin Root wrote:
> Please update your install of setuptools.
>
> On Wed, Mar 18, 2015 at 10:01 AM, wrote:
>
>> kbriggs:~/Downloads/matplotlib-1.4.3> python3 setup.py build
>> =
I have opened a PR to document this discussion. It is meant to provide a
permanent record of the thought process leading up to color map and to
serve as a tool in making the finial decision.
https://github.com/matplotlib/matplotlib/pull/4238
On Mon, Mar 2, 2015 at 6:32 AM jni wrote:
> Hi Pierr
MEP 25 is working towards providing a way to serialize the contents of a
figure in a more controlled way. The main target of this is
saving/reopening figures and export to bokeh/plotly/d3, but I think this
would also work well for exporting everything off to an opengl backend.
Tom
On Fri, Mar 13
Right on no longer supporting 1.5, but this code never got updated.
This is a bit of a bigger job than I first anticipated as numpy has
deprecated the norm kwarg, so we probably should too.
On Tue, Mar 10, 2015, 07:19 OceanWolf wrote:
> Tom, ``When we drop numpy 1.5''? I thought we already had
Cool.
There is a lot of code there to digest so I don't have anything technically
sensible to say yet, but in principle/abstract this seems like a good idea.
This also ties back into the MEP25 (figure serialization) discussion and
the discussion I was having with Eric Firing in the comments of
ht
Paul,
Note that by zoom the op means they are changing the bins, not actual
zooming(by just changing the x axis).
I was going to say we deal with normalization by delegating to numpy, but
we actually handle it internally (with a note that when we drop np 1.5 to
make numpy do it).
I think the best
Achyut,
Thank your for your interest, mpl on touch devices sounds super cool!
The easiest course is probably to develop a backend modeled after the
{qt,wx,gtk}Agg backends which embed an Agg backend into the gui framework
of choice. In those cases we rely on Agg to handle the mpl specific
drawin
This should probably be changed to use the new and improved container class
(along with error bar), but I should read the code to be sure.
On Mon, Feb 23, 2015, 11:44 Benjamin Root wrote:
> Huh, how about that. ContourSet subclasses ScalarMappable, but not Artist.
> I don't know if that is inten
@Nathaniel I think developing the color-overhaul as a maintenance release
is a decent compromise. All non-color changes get directed at the master
branch and we can cherry-picked back bug-fixes as needed.
The next feature release is planned for July/August, I _really_ hope
sorting out the colors
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 pypi (via pip). Additionally the source is available
tarball is available from github [2] and mac-wheels from
http://wheels.sci
At risk of sounding defensive, all of the core developers are working mpl
on a mostly volunteer basis and only have so much bandwidth. This leads to
both thing falling through the cracks (we have close to 100 open PRs, that
is _way_ too many) and major re-factors (which every one agrees should be
d
Hey all,
I have tagged 1.4.3.
Once the binaries are built I will get everything pushed up to pypi and
make a wider announcement.
As discussed before, this will be the last planned release in the 1.4
series.
Tom
--
Downl
; /home/ben/Programs/matplotlib/result_images/test_collections/regularpolycollection_scale.png
>> vs.
>> /home/ben/Programs/matplotlib/result_images/test_collections/regularpolycollection_scale-expected.png
>> (RMS 120.828)
>>
>> --
:51 PM Todd wrote:
>
> On Feb 8, 2015 1:13 AM, "Thomas Caswell" wrote:
> >
> > Hey all,
> >
> > To start with, the 2.0 release is pending a choice of new default color
> map. I think that when we pick that we should cut 2.0 off of the last
> release
:
> Hi all!
>
> On Sun, Feb 8, 2015 at 12:13 AM, Thomas Caswell
> wrote:
> > Hey all,
> >
> > To start with, the 2.0 release is pending a choice of new default color
> map.
> > I think that when we pick that we should cut 2.0 off of the last release
> and
>
Hey all,
To start with, the 2.0 release is pending a choice of new default color
map. I think that when we pick that we should cut 2.0 off of the last
release and then the next minor release turns into 2.1. If we want to do
other breaking changes we will just do a 3.0 when that happens. It make
w how much of a hassle that would be
for you.
Tom
On Sat Feb 07 2015 at 4:14:36 PM Sandro Tosi wrote:
> On Sat, Feb 7, 2015 at 9:05 PM, Thomas Caswell wrote:
> > Sandro,
> >
> > Can you use the tarball from github
> > (https://github.com/matplotlib/matplotlib/archive/v1.
Sandro,
Can you use the tarball from github (
https://github.com/matplotlib/matplotlib/archive/v1.4.3rc1.tar.gz ?)
Tom
On Sat Feb 07 2015 at 4:01:01 PM Sandro Tosi wrote:
> Hi Thomas,
>
> On Mon, Feb 2, 2015 at 5:37 AM, Thomas Caswell wrote:
> > Evening all,
> >
> &
May be of interest:
http://www.nature.com/news/programming-pick-up-python-1.16833
We get mention down towards the bottom.
Tom
--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel an
Evening all,
I have tagged the first release candidate for v1.4.3 (
https://github.com/matplotlib/matplotlib/releases/tag/v1.4.3rc1).
Although this is a bug-fix release, a fair amount of work has gone into
making the nbagg (interactive figures in ipython notebooks) feature
complete compared to th
> >> Getting to it from the other side, is there a matplotlib widget in
> >> the works where I can type text or numbers in a box? Like
> >> the FloatTextWidget in IPython?
> >>
> >> Problem is I want to make a small GUI that i
Hey all,
If anyone is interested, there is a software position open at BNL in the
group I work with:
https://www.bnl.gov/hr/careers/jobs/?cpUrl=https://careers.peopleclick.com/careerscp/Client_BrookhavenLab/external/en_US/gateway.do?functionName=viewFromLink&localeCode=en-us&jobPostId=525
Please
nbagg is always running in the IPython event loop (as I understand it), so
I am not sure how to integrate that with the blocking.
On the 1.4.x/master branch we have support for (almost, one PR still
pending) all mouse and keyboard events so all of the mpl widgets should
work (big thanks to Steven
s important to consider.
> >
> > Mike
> >
> > On 01/18/2015 04:52 PM, R Hattersley wrote:
> >> You need an extra "matplotlib" ... https://waffle.io/matplotlib/
> matplotlib
> >>
> >> On 17 January 2015 at 19:29, Thomas Caswell >
Hey all,
We have set up waffle.io to try and help manage our issues:
https://waffle.io/matplotlib/
If you have commit rights, you should be able to move the cards around.
Any thoughts on this tool? I would like to use this to keep track of the
review state of PRs.
Tom
--
Hello all,
I would like to try to hit the Feb 1 target date for 1.4.3 and plan to do
an RC next Monday (Jan 19).
Any major protests from anyone on this timeline?
If people could take a look at the 1.4.3 and 1.4.x milestones on github and
either move stuff around (in terms of finding any blockers
current floating point
> format. Our custom classes are not public (and can't really be made
> public) but they aren't very complicated so we can certainly talk about the
> implementation if that helps.
>
>
> --
> *From:* Thomas Casw
One of the other driving factors to over-haul the default date handling is
that floats do not have enough precision to deal with nano-second
resolution data (which is what I think drove pandas to use datetime64).
It sounds like the correct solution
Is the unit framework documented anywhere and ar
We have a Twitter account?!?
On Fri, Dec 19, 2014, 20:05 Benjamin Root wrote:
> I just realized today that people have been posting questions to a
> matplotlib handle on twitter, but it hasn't posted any tweets since April.
>
> Same issue for numpy as well, it seems.
>
> Ben Root
> -
For reference, the IPython script is in tools/update_whatsnew.py
On Thu Nov 27 2014 at 11:58:40 AM Ian Thomas wrote:
> On 27 November 2014 at 16:16, Thomas Caswell wrote:
>
>> There should be an automatic process, but no one has written it yet. I
>> think IPython has co
There should be an automatic process, but no one has written it yet. I
think IPython has code we can adapt in their doc build process. I had
planned to deal with this when we cut the next minor/major release.
Tom
On Thu, Nov 27, 2014, 04:18 Ian Thomas wrote:
> Fellow developers,
>
> I know we a
That is super cool. I was thinking about doing something similar, glad it
has already been so well done.
The example figures at the bottom bring up another point, we should have a
canonical set of test figures, both for the color map and the defaults in
general, I think that will really help with
The contents of that talk are also in our documentation
http://matplotlib.org/users/colormaps.html
Tom
On Sat Nov 22 2014 at 9:33:11 AM gary ruben wrote:
> There was a talk by Kristen Thyng at scipy2014 that might be a good
> backgrounder for this:
> http://pyvideo.org/video/2769/perceptions-of
I am a bit wary of doing a 2.0 _just_ to change the color map, but when
every I try to write out why, they don't sound convincing. We may end up
with a 3.0 within a year or so due to the possible plotting API/pyplot work
that is (hopefully) coming.
If we are going to do this, I think we should do
Ah, never mind then, I just got out of sync.
On Wed, Nov 19, 2014, 04:04 Joel B. Mohler wrote:
> On 11/18/2014 08:29 PM, Thomas Caswell wrote:
>
> Is there an issue for this (and if not can you make one)?
>
>
> This is https://github.com/matplotlib/matplotlib/pull/3811 wh
Is there an issue for this (and if not can you make one)?
On Mon, Nov 17, 2014, 09:56 Joel B. Mohler wrote:
> On Mon, Nov 17, 2014 at 09:36:50AM -0500, Joel B. Mohler wrote:
> > I think I see a breakage of the scatter call that I think should work
> and did
> > work before
> > https://github.com
Have a look at the recipe in conda-rescipes for matplotlib, they might be
doing some funny patching.
On Mon, Nov 17, 2014, 22:48 Benjamin Root wrote:
> Ok, I am just really confused now. I have confirmed that using the
> matplotlib supplied by miniconda (v1.4.2) works just fine. Ripping that out
Stumbled across this today https://code.google.com/p/mplh5canvas/
It hasn't had a commit in 18mos and I have not tried it, but I am just
making sure the community is aware of it's existence.
Tom
--
Comprehensive Server Mo
Not sure what you mean about agg + py3k, it should work fine (as we test
it).
The issue is that the cairo backend is a vector backend, which does not
have a notion of blitting, which is something that span selector uses to
make it nice and snappy. Should be able to get it to work by passing the
k
IPython notebooks got a write up in Nature.
http://www.nature.com/news/interactive-notebooks-sharing-the-code-1.16261
All of the examples depend on mpl.
Tom
--
___
Matplotlib-d
fic prior written permission.
>
> ..."
>
> So Scipy Console shoud be ok ? Since Scipy does not seem to be forbidden
> by the licence text.
>
> Thanks for your help.
>
> Apps Embedded Team.
>
> 2014-11-07 15:03 GMT+01:00 Thomas Caswell :
>
>> I (personall
-devel mailing list
> Matplotlib-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
--
Thomas Caswell
tcasw...@gmail.com
--
___
ge log to separate them from the release candidates.
>
>
> Jens
>
> On Wed, Nov 5, 2014 at 4:15 PM, Benjamin Root wrote:
>
>> Same here. I like the old tags for historical research purposes. Now, if
>> there was a way for github to only display the N most recent tags
r removing tags for old release candidates? I know that
> IPython does this and it does clean up the tags quite a bit since
> approximately half the tags are for release candidates.
>
>
> Jens
>
> On Sat, Nov 1, 2014 at 7:56 PM, Thomas Caswell wrote:
>
>> This is done n
Please create a pull request.
This sounds reasonable to me, but I have never seen a plot with that scale
and don't really understand it from your description. Seeing the code
usually clarifies things.
Tom
On Mon, Nov 3, 2014, 05:58 Fabio Zanini
wrote:
> Dear all,
>
> I've been using matplotlib
runs a prune command on the
upstream repos we still have this information around.
I left rgb2lab_local because there is still an open PR against it, but will
go away when we close that PR.
Tom
On Sat Nov 01 2014 at 2:32:19 PM Eric Firing wrote:
> On 2014/11/01, 5:49 AM, Thomas Caswell wr
Todd,
The tags would not go anywhere, just the branches would be removed.
The tags are for releases, branches are for active work and there should be
no active work on anything but those three branches.
Tom
On Sat, Nov 1, 2014, 12:14 Todd wrote:
>
> On Nov 1, 2014 4:49 PM, "Tho
Does anyone protest to removing all of the branches from the main repo
except:
- master
- v1.4.x
- v1.4.2-doc
Having old branches around can lead to confusion (see
https://github.com/matplotlib/matplotlib/pull/3748#issuecomment-61372162).
Tom
--
We should ask the scikit-image devs how they managed it last summer as I
think they had at least one student.
On Wed Oct 22 2014 at 3:33:11 PM Chris Barker wrote:
> On Sat, Oct 18, 2014 at 8:50 AM, Thomas Caswell
> wrote:
>
>> We should be a mentoring organization for next summ
t!
>
> --
> Dr Andy Buckley, Royal Society University Research Fellow
> Particle Physics Expt Group, University of Glasgow / PH Dept, CERN
>
>
>
> --
>
> ___________
> Matplot
https://github.com/HamsterHuey/easyplot?utm_content=buffer48700&utm_medium=social&utm_source=twitter.com&utm_campaign=buffer
I have not looked at it carefully, but it is something we might want to be
aware of when thinking about API re-designs.
Tom
--
Thomas Caswell
tcasw.
Hot on the tails of v1.4.1, we have a v1.4.2 due to an error in the boxplot
api in pyplot.py
The only changes between 1.4.1 and 1.4.2 are:
- corrected boxplot in pyplot.py
- added extra paths to default search paths for freetype
Tom
--
Thomas Caswell
tcasw...@gmail.com
Yes, pyplot didn't get regenerated after one of the boxplot fixes.
On Thu, Oct 23, 2014 at 9:17 AM, Sandro Tosi wrote:
> I see a 1.4.2 already?
>
> On Sun, Oct 19, 2014 at 3:54 AM, Thomas Caswell wrote:
>> Hello,
>>
>> We are pleased to announce the release of m
1 - 100 of 155 matches
Mail list logo
