On Thu, Oct 28, 2010 at 12:44 AM, Andrew Straw wrote:
> On 10/23/2010 04:59, John Hunter wrote:
> > I would be happy to do a release early next week. Is anyone aware of
> > any show stopper bugs that need to be fixed first?
>
> I think we should really get the build bot to all green again before
On Thu, Oct 28, 2010 at 9:05 AM, Benjamin Root wrote:
> Just as a quick question that I would like to throw out. It isn't a bug,
> but rather an aesthetics issue that I caused for the version 1.0 release.
>
> With allowing 3d plots to be made subplottable, the margins for the plot
> area became
On Thu, Oct 28, 2010 at 9:55 AM, John Hunter wrote:
> On Thu, Oct 28, 2010 at 9:05 AM, Benjamin Root wrote:
>
> > Just as a quick question that I would like to throw out. It isn't a bug,
> > but rather an aesthetics issue that I caused for the version 1.0 release.
> >
> > With allowing 3d plots
On Mon, Oct 25, 2010 at 9:40 AM, Michael Droettboom wrote:
> On 10/23/2010 06:05 PM, David Carmean wrote:
>> As I blurted on -users, I'm thinking lately about callbacks in the
>> non-GUI portions of the libraries--mostly Artist and subclasses.
>> I'm curious if anybody else has been thinking abou
On 10/25/10 1:41 PM, Daniel Hyams wrote:
> It doesn't really insist on it right? There are MATPLOTLIBDIR and
> MPLCONFIGDIR environment variables.
> You can set these env variables within your code, before import of
> matplotlib via os.environment.
I'm glad I've learned about this, and will star
On Thu, Oct 28, 2010 at 1:11 PM, Christopher Barker
wrote:
> On 10/25/10 1:41 PM, Daniel Hyams wrote:
>> It doesn't really insist on it right? There are MATPLOTLIBDIR and
>> MPLCONFIGDIR environment variables.
>
>> You can set these env variables within your code, before import of
>> matplotlib v
On Thu, Oct 28, 2010 at 1:50 PM, John Hunter wrote:
> On Thu, Oct 28, 2010 at 1:11 PM, Christopher Barker
> wrote:
> > On 10/25/10 1:41 PM, Daniel Hyams wrote:
> >> It doesn't really insist on it right? There are MATPLOTLIBDIR and
> >> MPLCONFIGDIR environment variables.
> >
> >> You can set th
In article <4cc9bcd8.60...@noaa.gov>,
Christopher Barker wrote:
> On 10/25/10 1:41 PM, Daniel Hyams wrote:
> > It doesn't really insist on it right? There are MATPLOTLIBDIR and
> > MPLCONFIGDIR environment variables.
>
> > You can set these env variables within your code, before import of
> >
On Thu, Oct 28, 2010 at 2:46 PM, Russell E. Owen wrote:
> It's an interesting question. You can't call a matplotlib function to do
> it because it has to happen before matplotlib is loaded. I suppose there
> could be a configuration package to perform the operation.
This is basically what we alr
On 10/28/10 11:50 AM, John Hunter wrote:
> On Thu, Oct 28, 2010 at 1:11 PM, Christopher Barker
>>> You can set these env variables within your code, before import of
>>> matplotlib via os.environment.
> The MPLCONFIGDIR tells mpl where to find the config file. It's hard
> to read the config, no m
In reference to the configuration package idea...
I (and the users that I support) use matplotlib both as a standalone plotter
for generating lots of plots, as an interactive plotter, and as an embedded
plot in an application environment. In all of these instances we have found
the '.matplotlibrc
This line:
ARCH_FLAGS="-arch i386-arch x86_64"
should actually be
ARCH_FLAGS="-arch i386 -arch x86_64"
(notice the extra space after i386. it wouldn't build for me without this
fix.)
Uri
...
Uri Laserson
Graduate
Hello,
recently I upgraded to matplotlib 1.0.0 which I mainly use for plotting in my
(python 2.6 based) application with Qt4 GUI. Overall it works fine, but there
are a few issues I experienced also with the previous version, especially with
the toolbar.
When building a standalone version usin
The Sage developers have found two issues with MPLCONFIGDIR:
- First, when upgrading from version 0.99.3 to 1.0.0, the contents of
that directory seem to cause compatibility problems. That is, once
you upgrade to a version of Sage using 1.0.0, it overwrites whatever
was in that directory, and th
14 matches
Mail list logo
