Hello,
while updating Basemap package in Debian, I noticed that
lib/mpl_toolkits/basemap/pyproj.py could use the same BASEMAPDATA
variable handling as of lib/mpl_toolkits/basemap/__init__.py , so I'm
applying a patch like this:
Index: basemap-1.0.5+dfsg/lib/mpl_toolkits/basemap/pyproj.py
=
On Fri, Aug 10, 2012 at 1:00 PM, Michael Droettboom wrote:
> That is the end goal. I'm talking simply about the static webpage hosting
> here. If I recall correctly, I think the space limitations on github used
> to be a problem for us, which is why we haven't used it as the canonical web
> host
On 08/10/2012 03:45 PM, Fernando Perez wrote:
> On Fri, Aug 10, 2012 at 7:26 AM, Michael Droettboom wrote:
>> Supporting existing links to matplotlib.sourceforge.net is of course
>> very important, and I would put whatever redirects we need to keep those
>> working in any event.
> Actually, why no
On Fri, Aug 10, 2012 at 7:26 AM, Michael Droettboom wrote:
> Supporting existing links to matplotlib.sourceforge.net is of course
> very important, and I would put whatever redirects we need to keep those
> working in any event.
Actually, why not move all the official domain machinery to
matplotl
- Forwarded message from Damon McDougall -
> Date: Fri, 10 Aug 2012 12:47:22 +0100
> From: Damon McDougall
> To: satish maurya
> Cc: matplotlib-us...@lists.sourceforge.net
> Subject: Re: [Matplotlib-users] help me Velocity depth plot in matplotlib
>
> On Fri, Aug 10, 2012 at 02:09:39PM
On 08/10/2012 10:49 AM, Phil Elson wrote:
> Great! Are we going to be able to move away from using the sourceforge
> mailing list too?
I haven't given that much thought. Are there much better free
alternatives to justify the disruption?
>
> Presumably these infrastructure costs get covered via
> As far as I can see the github docs are as up-to-date as the
> souceforge ones.
Scrub that statement. My browser cache needed clearing.
On 10 August 2012 15:44, Phil Elson wrote:
> I wasn't involved at the time, but was it because
> matplotlib.github.com is slower?
>
> As far as I can see
Great! Are we going to be able to move away from using the sourceforge
mailing list too?
Presumably these infrastructure costs get covered via the donations
that mpl receives rather than coming out of your pocket Michael?
I think getting hold of matplotlib.org is a really good idea. Thanks
for do
I wasn't involved at the time, but was it because
matplotlib.github.com is slower?
As far as I can see the github docs are as up-to-date as the
souceforge ones. (although reading the commit log on the docs repo
doesn't seem to agree with that statement)
All in all, sounds promising.
On 10 August
I have registered matplotlib.org. It currently just points to
matplotlib.sourceforge.net, but it will allow us to have a consistent
URL that isn't dependent on any particular host going forward.
Mike
--
Live Security V
I know we had experimented with moving the main documentation website to
matplotlib.github.com a while ago (and in fact there's still an old
version of the docs sitting there). I can't remember the reason we
chose to remain at matplotlib.sourceforge.net and searching the mailing
list archive i
Hi Ludwig,
You are right, it didn't work on the MacOSX backend either. I didn't notice
since the backend doesn't support blitting, so I never tried it.
In any case, it is exactly the same problem as in Qt4Agg, with exactly the
same fix: In lib/matplotlib/backends/backend_macosx.py, add the last l
Hi,
I noticed that when using tight_layout, the figure padding changes for
different figure.dpi settings. This is caused by an error in when converting
from points to inches. A point is always 1/72 inch and does not depend on
the dots per inches. This is the patch for fixing the conversion:
Diff
13 matches
Mail list logo
