matplotlib-users Mailing List for matplotlib

Setting the matplotlib.use('Agg') seems to have made the problem go away.

Thanks for your patience.
Scott



Christoph Gohlke wrote:
> 
> Again, please post a complete script that can reproduce the problem. 
> Since you do not need a GUI did you try to use the Agg backend?
> 
> Christoph
> 
> 
> 
> On 8/11/2010 2:31 PM, stetrick wrote:
>>
>> I removed and reinstalled everything, and I'm still getting it.
>>
>> I am using the multiprocessing lib.  Each process then produces a graph
>> with
>> matplotlib, which is only done with Savefig (never interactively
>> displaced
>> during the creation process).   I have nothing special in the
>> configuration
>> - just using the 64-bit windows defaults.
>>
>> Probably some setup thing.
>>
>>
>> Christoph Gohlke wrote:
>>>
>>>
>>>
>>>
>>>>> Christoph
>>>>
>>>> I thought that was fixed:
>>>> http://sourceforge.net/tracker/?func=detail&aid=3015013&group_id=80706&atid=560720
>>>>
>>>> Eric
>>>>
>>>
>>> Yes the bug is fixed. If the program is terminated properly. However,
>>> you can still crash the Python interpreter if you close or kill the
>>> console window while the following script is running.
>>>
>>> python -c"from matplotlib import pyplot;pyplot.hot();input()"
>>>
>>> --
>>> Christoph
>>>
>>> ------------------------------------------------------------------------------
>>> This SF.net email is sponsored by
>>>
>>> Make an app they can't live without
>>> Enter the BlackBerry Developer Challenge
>>> http://p.sf.net/sfu/RIM-dev2dev
>>> _______________________________________________
>>> Matplotlib-users mailing list
>>> Mat...@li...
>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>>>
>>>
>>
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by 
> 
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev 
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 
> 

-- 
View this message in context: http://old.nabble.com/Fatal-Python-Error-with-64-bit-versions-tp29392620p29413496.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

Again, please post a complete script that can reproduce the problem. 
Since you do not need a GUI did you try to use the Agg backend?

Christoph



On 8/11/2010 2:31 PM, stetrick wrote:
>
> I removed and reinstalled everything, and I'm still getting it.
>
> I am using the multiprocessing lib.  Each process then produces a graph with
> matplotlib, which is only done with Savefig (never interactively displaced
> during the creation process).   I have nothing special in the configuration
> - just using the 64-bit windows defaults.
>
> Probably some setup thing.
>
>
> Christoph Gohlke wrote:
>>
>>
>>
>>
>>>> Christoph
>>>
>>> I thought that was fixed:
>>> http://sourceforge.net/tracker/?func=detail&aid=3015013&group_id=80706&atid=560720
>>>
>>> Eric
>>>
>>
>> Yes the bug is fixed. If the program is terminated properly. However,
>> you can still crash the Python interpreter if you close or kill the
>> console window while the following script is running.
>>
>> python -c"from matplotlib import pyplot;pyplot.hot();input()"
>>
>> --
>> Christoph
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by
>>
>> Make an app they can't live without
>> Enter the BlackBerry Developer Challenge
>> http://p.sf.net/sfu/RIM-dev2dev
>> _______________________________________________
>> Matplotlib-users mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>>
>>
>

Adding a close() at the end didn't do anything - still get the same message.


stetrick wrote:
> 
> I removed and reinstalled everything, and I'm still getting it.
> 
> I am using the multiprocessing lib.  Each process then produces a graph
> with matplotlib, which is only done with Savefig (never interactively
> displaced during the creation process).   I have nothing special in the
> configuration - just using the 64-bit windows defaults.
> 
> Probably some setup thing.
> 
> 
> Christoph Gohlke wrote:
>> 
>> 
>> 
>> 
>>>> Christoph
>>>
>>> I thought that was fixed:
>>> http://sourceforge.net/tracker/?func=detail&aid=3015013&group_id=80706&atid=560720
>>>
>>> Eric
>>>
>> 
>> Yes the bug is fixed. If the program is terminated properly. However, 
>> you can still crash the Python interpreter if you close or kill the 
>> console window while the following script is running.
>> 
>> python -c"from matplotlib import pyplot;pyplot.hot();input()"
>> 
>> --
>> Christoph
>> 
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by 
>> 
>> Make an app they can't live without
>> Enter the BlackBerry Developer Challenge
>> http://p.sf.net/sfu/RIM-dev2dev 
>> _______________________________________________
>> Matplotlib-users mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>> 
>> 
> 
> 

-- 
View this message in context: http://old.nabble.com/Fatal-Python-Error-with-64-bit-versions-tp29392620p29413159.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

I removed and reinstalled everything, and I'm still getting it.

I am using the multiprocessing lib.  Each process then produces a graph with
matplotlib, which is only done with Savefig (never interactively displaced
during the creation process).   I have nothing special in the configuration
- just using the 64-bit windows defaults.

Probably some setup thing.


Christoph Gohlke wrote:
> 
> 
> 
> 
>>> Christoph
>>
>> I thought that was fixed:
>> http://sourceforge.net/tracker/?func=detail&aid=3015013&group_id=80706&atid=560720
>>
>> Eric
>>
> 
> Yes the bug is fixed. If the program is terminated properly. However, 
> you can still crash the Python interpreter if you close or kill the 
> console window while the following script is running.
> 
> python -c"from matplotlib import pyplot;pyplot.hot();input()"
> 
> --
> Christoph
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by 
> 
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev 
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 
> 

-- 
View this message in context: http://old.nabble.com/Fatal-Python-Error-with-64-bit-versions-tp29392620p29413051.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

>
> Maybe the OP's problem is that the colors become indistinguishable in
> the relatively small intervals?  If so, the answer is to use a different
> norm, or to use a ListedColormap with a color for each interval.  The
> ListedColormap allows complete freedom to explicitly specify the color
> for each interval between contour boundaries.

See 
http://matplotlib.sourceforge.net/examples/pylab_examples/contourf_demo.html

On 08/11/2010 08:54 AM, Friedrich Romstedt wrote:
> 2010/8/11 tgabriel<tra...@gm...>:
>> I would like to have the colorbar displaying the same color scaling
>> regardless of the data input.
>
> This /should/ be feasible with .contourf(.., vmin=VMIN, vmax=VMAX),
> but from the doc this isn't clear at least.  If it doesn't work, we
> have to work out how to use the norm=... argument properly to hand
> over a Norm instance.  Please give vmin/max a try, we can look that up
> if it fails.

No, contour* do not use vmin, vmax kwargs. Setting the levels should be 
enough for what I thought the OP wanted to do, so I don't understand the 
problem--hence I requested a standalone script to illustrate it.

vmin, vmax can still be set by using the plt.clim function.

Maybe the OP's problem is that the colors become indistinguishable in 
the relatively small intervals?  If so, the answer is to use a different 
norm, or to use a ListedColormap with a color for each interval.  The 
ListedColormap allows complete freedom to explicitly specify the color 
for each interval between contour boundaries.

>
>> Problem 2: If I have a colorbar scale which goes from -10 to 5, and I use
>> one of the standard colormaps which has white in the center of it. How do I
>> keep the zero point at the white color instead of the colorbar automatically
>> picking the midpoint for zero?
>
> So you want to set the color-MAP's range with the solution to problem
> 1, and display in the color-BAR only a subset of the value range used
> by the Norm?  This has been solved already in a former task, if it
> suits you I can send the sources for that.

This sounds like a job for a custom norm, but maybe you found a better way?

Eric

>
> Friedrich
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

On 08/11/2010 06:13 AM, tgabriel wrote:
>
>
> Problem 1: I have a dataset which has more values on one side of the scale
> than the other in a contour map. Matplotlib will see that I have more values
> towards one side of the scale, and put all of the colors in that color map
> to that side of the scale.
>
> For example, lets say I would like my colorbar to show values from -10^6 all
> the way to 10^6.
> But, most of my values are in the -10^6 to -10^5 range. How do I get my
> colorbar not to automatically send all of the colors to that portion of the
> colorbar and leave everything greater than -10^5 to have one color.
>
> I would like to have the colorbar displaying the same color scaling
> regardless of the data input.
>
> Here is a copy of my code:
> v2 =
> [-1000000,-100000,-10000,-1000,-100,-10,0,10,100,1000,10000,100000,1000000]
> 	plt.subplot(6,1,2)
> 	cset4 = plt.contourf(x2,z2,k2,v2,cmap=cm.get_cmap('jet', len(v2)-1))
> 	cset5 = plt.contour(x2,z2,k2,v2,colors = 'k',linewidths = .22,hold='on')
> 	#set axes values
> 	plt.axis([xmin2,xmax2, zmin,zmax])
> 	#set y axes label
> 	plt.ylabel('Z, [km]')
> 	#display title
> 	plt.title('v3 Plot              Max:'+str("%.2f" %k2.max())+'		   Min:
> '+str("%.2f" %k2.min()),size='small')
> 	#colorbar manipulation
> 	cbar = plt.colorbar(cset4,spacing="uniform", shrink =
> 0.95,ticks=[-1000000,-100000,-10000,-1000,-100,-10,0,10,100,1000,10000,100000,1000000])
>
> cbar.ax.set_yticklabels(['-10^5','-10^4','-10^3','-10^2','-10^1',0,'10^1','10^2','10^3','10^4','10^5'])
> 	#close file
> 	f2.close()

I don't understand the problem based on your description and code. 
Please make a stand-alone example script, runnable by anyone, generating 
fake data as needed in the script.  It should require only a little 
reworking of the fragment that you included above.  Please include the 
script as an attachment, so it does not get mangled by the mail sending 
or reading software.

Also, please specify what mpl version you are using.

Eric
>
> Problem 2: If I have a colorbar scale which goes from -10 to 5, and I use
> one of the standard colormaps which has white in the center of it. How do I
> keep the zero point at the white color instead of the colorbar automatically
> picking the midpoint for zero?
>
> Problem 1 is much more of a pressing issue right now than problem 2.
>
> Thank you
>

On Sun, Jul 18, 2010 at 1:17 PM, Benjamin Root <ben...@ou...> wrote:

>
>
> On Thu, Jul 15, 2010 at 9:13 PM, Jeff Berry <jj...@em...>wrote:
>
>> Hi,
>>
>> I'm using the new mixed axes feature in matplotlib 1.0.0 to combine 3D and
>> 2D plots in a single figure. The problem is that the 3D axes have a lot of
>> extra white space around them that prevents the plot to line up flush with
>> the 2D plot. Here is an example image of this:
>>
>> using matplotlib: http://www.u.arizona.edu/~jjberry/matplotlib.png<http://www.u.arizona.edu/%7Ejjberry/matplotlib.png>
>>
>> vs. matlab of the same thing:
>> http://www.u.arizona.edu/~jjberry/matlab.png<http://www.u.arizona.edu/%7Ejjberry/matlab.png>
>>
>> Is there any way of changing the space on the 3D axis to look more like
>> the matlab figure?
>>
>> Thanks,
>> Jeff Berry
>>
>>
>>
> Jeff, thanks for pointing this out.  An inadvertant side-effect of using
> add_subplot() for 3d axes seems to be that the creation process greatly
> restricts the available space for the 3d figure to be plotted.  Whereas
> doing the old Axes3D() approach (albeit for non-subplots) would allow the 3D
> figure to use all the available space.
>
> I am currently examining this issue right now and might be tied to another
> bug that has been reported recently.
>
> Ben Root
>

Jeff,

Sorry for taking so long to get back to you.  I have found a sort of
workaround that should help you out.

You can use subplots_adjust(left=0.0, bottom=0.0, right=1.0, top=1.0),
before creating the axes to specify that the axes objects should use all the
space available to them.  Note, this will still allow for a buffer between
the graphs, which can be adjusted using wspace and hspace keywords.

http://matplotlib.sourceforge.net/api/pyplot_api.html#matplotlib.pyplot.subplots_adjust

I hope that helps,
Ben Root

2010/8/11 tgabriel <tra...@gm...>:
> I would like to have the colorbar displaying the same color scaling
> regardless of the data input.

This /should/ be feasible with .contourf(.., vmin=VMIN, vmax=VMAX),
but from the doc this isn't clear at least.  If it doesn't work, we
have to work out how to use the norm=... argument properly to hand
over a Norm instance.  Please give vmin/max a try, we can look that up
if it fails.

> Problem 2: If I have a colorbar scale which goes from -10 to 5, and I use
> one of the standard colormaps which has white in the center of it. How do I
> keep the zero point at the white color instead of the colorbar automatically
> picking the midpoint for zero?

So you want to set the color-MAP's range with the solution to problem
1, and display in the color-BAR only a subset of the value range used
by the Norm?  This has been solved already in a former task, if it
suits you I can send the sources for that.

Friedrich

This worked perfectly.  Thanks Christoph.

Ryan

On Wed, Aug 11, 2010 at 11:35 AM, Christoph Gohlke <cg...@uc...> wrote:
> Ryan: you could try matplotlib-1.0.0.svn.win32-py2.6.exe from
> http://www.lfd.uci.edu/~gohlke/pythonlibs/#matplotlib .It was built this
> morning from svn.
>
> Christoph
>
> On 8/11/2010 7:26 AM, Ryan Krauss wrote:
>> 0.99.3 is more or less fine, but there is an annoying exception window
>> that pops up if you close IPython with a plot window open (using the
>> TkAgg backend).  But in my mind this is less bothersome than having to
>> close all the plot windows every time I run a script (I tend to write
>> scripts that generate 5-10 plots at a minimum).
>>
>> If I could easily build an installer from svn, I would try it.  I
>> don't have any microsoft compilers installed on my windows computers.
>>
>> Thanks again,
>>
>> Ryan
>>
>> On Wed, Aug 11, 2010 at 9:09 AM, Ryan Krauss<rya...@gm...>  wrote:
>>> Thanks.
>>>
>>> I need to role out a python install for my students.  Classes start in
>>> a week and a half.  What should I do?  The installation for most of
>>> them needs to be fairly simple.
>>>
>>> Thanks,
>>>
>>> Ryan
>>>
>>> On Wed, Aug 11, 2010 at 2:25 AM, Eric Firing<ef...@ha...>  wrote:
>>>> On 08/10/2010 05:43 PM, Ryan Krauss wrote:
>>>>> I just upgraded my windows machine to matplotlib 1.0.0 and a simple
>>>>> script such as
>>>>>
>>>>> from pylab import *
>>>>> from scipy import *
>>>>>
>>>>> t = arange(0,1,0.01)
>>>>> y = sin(2*pi*t)
>>>>>
>>>>> figure(1)
>>>>> clf()
>>>>> plot(t,y)
>>>>>
>>>>> show()
>>>>>
>>>>> Now halts execution when run from the ipython -pylab prompt.  The same
>>>>> commands typed at the commandline do not lead to show() halting
>>>>> execution.
>>>>>
>>>>> Is this expected behavior?
>>>>
>>>> This was fixed three weeks ago in svn, both the maintenance branch and
>>>> the trunk.  I made some changes in show() shortly before 1.0, trying to
>>>> get uniform and reasonable behavior in all backends, and I didn't quite
>>>> succeed.  I think I got it all straightened out--but only after the
>>>> release, unfortunately.  I hope it won't be too long before a 1.0.1
>>>> bugfix release can be made, but I am aware of no schedule.
>>>>
>>>> Eric
>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Ryan
>>>>>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

Ryan: you could try matplotlib-1.0.0.svn.win32-py2.6.exe from 
http://www.lfd.uci.edu/~gohlke/pythonlibs/#matplotlib .It was built this 
morning from svn.

Christoph

On 8/11/2010 7:26 AM, Ryan Krauss wrote:
> 0.99.3 is more or less fine, but there is an annoying exception window
> that pops up if you close IPython with a plot window open (using the
> TkAgg backend).  But in my mind this is less bothersome than having to
> close all the plot windows every time I run a script (I tend to write
> scripts that generate 5-10 plots at a minimum).
>
> If I could easily build an installer from svn, I would try it.  I
> don't have any microsoft compilers installed on my windows computers.
>
> Thanks again,
>
> Ryan
>
> On Wed, Aug 11, 2010 at 9:09 AM, Ryan Krauss<rya...@gm...>  wrote:
>> Thanks.
>>
>> I need to role out a python install for my students.  Classes start in
>> a week and a half.  What should I do?  The installation for most of
>> them needs to be fairly simple.
>>
>> Thanks,
>>
>> Ryan
>>
>> On Wed, Aug 11, 2010 at 2:25 AM, Eric Firing<ef...@ha...>  wrote:
>>> On 08/10/2010 05:43 PM, Ryan Krauss wrote:
>>>> I just upgraded my windows machine to matplotlib 1.0.0 and a simple
>>>> script such as
>>>>
>>>> from pylab import *
>>>> from scipy import *
>>>>
>>>> t = arange(0,1,0.01)
>>>> y = sin(2*pi*t)
>>>>
>>>> figure(1)
>>>> clf()
>>>> plot(t,y)
>>>>
>>>> show()
>>>>
>>>> Now halts execution when run from the ipython -pylab prompt.  The same
>>>> commands typed at the commandline do not lead to show() halting
>>>> execution.
>>>>
>>>> Is this expected behavior?
>>>
>>> This was fixed three weeks ago in svn, both the maintenance branch and
>>> the trunk.  I made some changes in show() shortly before 1.0, trying to
>>> get uniform and reasonable behavior in all backends, and I didn't quite
>>> succeed.  I think I got it all straightened out--but only after the
>>> release, unfortunately.  I hope it won't be too long before a 1.0.1
>>> bugfix release can be made, but I am aware of no schedule.
>>>
>>> Eric
>>>
>>>>
>>>> Thanks,
>>>>
>>>> Ryan
>>>>

Problem 1: I have a dataset which has more values on one side of the scale
than the other in a contour map. Matplotlib will see that I have more values
towards one side of the scale, and put all of the colors in that color map
to that side of the scale.

For example, lets say I would like my colorbar to show values from -10^6 all
the way to 10^6.
But, most of my values are in the -10^6 to -10^5 range. How do I get my
colorbar not to automatically send all of the colors to that portion of the
colorbar and leave everything greater than -10^5 to have one color.

I would like to have the colorbar displaying the same color scaling
regardless of the data input.

Here is a copy of my code:
v2 =
[-1000000,-100000,-10000,-1000,-100,-10,0,10,100,1000,10000,100000,1000000]
	plt.subplot(6,1,2)
	cset4 = plt.contourf(x2,z2,k2,v2,cmap=cm.get_cmap('jet', len(v2)-1))
	cset5 = plt.contour(x2,z2,k2,v2,colors = 'k',linewidths = .22,hold='on')
	#set axes values
	plt.axis([xmin2,xmax2, zmin,zmax])
	#set y axes label
	plt.ylabel('Z, [km]')
	#display title
	plt.title('v3 Plot              Max:'+str("%.2f" %k2.max())+'		   Min:
'+str("%.2f" %k2.min()),size='small')
	#colorbar manipulation
	cbar = plt.colorbar(cset4,spacing="uniform", shrink =
0.95,ticks=[-1000000,-100000,-10000,-1000,-100,-10,0,10,100,1000,10000,100000,1000000])

cbar.ax.set_yticklabels(['-10^5','-10^4','-10^3','-10^2','-10^1',0,'10^1','10^2','10^3','10^4','10^5'])
	#close file
	f2.close()

Problem 2: If I have a colorbar scale which goes from -10 to 5, and I use
one of the standard colormaps which has white in the center of it. How do I
keep the zero point at the white color instead of the colorbar automatically
picking the midpoint for zero?

Problem 1 is much more of a pressing issue right now than problem 2.

Thank you 

-- 
View this message in context: http://old.nabble.com/Disable-Colorbar-Scaling-In-Contour-Plot-tp29409978p29409978.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

On Wed, Aug 11, 2010 at 8:43 AM, Tony S Yu <ts...@gm...> wrote:
>
> On Aug 11, 2010, at 6:56 AM, Rob Schneider wrote:
>
>>
>> I extract data out of a database (via Django and Python).  I'm drawing two bar charts.  One is a stacked bar, and one is a simple bar.
>> The code for each graph is in their own function.  I call the function to draw the graph sequencially (in function "CreateAllWebSite() below).
>>
>> Problem is that when I do this, the graph called second comes out all jumbled.  See attached copies of png files.  If I swap the function calls, always first is ok and the the second one is jumbled.  If I call them one at a time, they both work just fine (which is how i developed the second).  once put together, the second is wrong.  For example, the legend from the first graph gets put on the second graph . The x-axis for the second is all jumbled at the bottom left corner of the graph instead of along the x-axis properly.
>>
>> I'm using Matplotlib 0.98.5.3 on OS X.  I will upgrade to 1.0 of Matplot lib soon.
>>
>> I suspect some sort of memory issue; perhaps caused by how I import matplotlib in the global section of the python program; but far as I can tell this is correct, or is it?  I suspect memory as how else would legend from the first graph get put on the second graph? Is there some sort of reset function to call to clear out the old graph? I sort of thought that calling a completely different function would cover that.
>>
>> Here's the code extract with portions I think no relevant snipped out. From debugging I'm confident the number arrays holding the data is ok.  As I said, when producing the graphs one at a time, it work fine.  So that code snipped out below.
>>
>> #!/usr/bin/env python
>> # -*- coding: UTF-8 -*-
>>
>> import matplotlib
>> matplotlib.use('Agg') # before importing pyplot per docs
>> import matplotlib.pyplot as plt
>> import numpy as np
>>
>> [snipped the import of Python and Django libraries]
>>
>> ###########################################################
>> def CreateAllWebSite():
>>  # here is the one function that calls the two graphing functions sequentially.
>>  # whichever of these is called first is done fine.  Second flawed.  calling one at at time, each works ok
>>  CreateMemberStatFigure()
>>  CreateMemberStatCategoryFigure()
>> ###############################################
>> def CreateMemberStatFigure():
>> # this function creates a stacked bar chart
>> [snipped out portions where arrays created]
>
> Hi Rob,
>
> It would be helpful if you could provide a runnable example. I know it's a pain, but you should simplify your example so that it's runnable with only matplotlib and numpy You should create some fake data to replace these portions that you've cut out. Plus there are some (Django?) classes/functions/globals that are undefined.
>

Agreed. The only thing I can think of is that the second figure is
reusing the first. You can try calling plt.figure() at the beginning
of the functions to create a new figure, or call plt.figure() in
between the calls to CreateMemberStatCategoryFigure() and
CreateMemberStatFigure(). I can't be sure since you didn't include the
code that actually calls these functions.

Ryan


-- 
Ryan May
Graduate Research Assistant
School of Meteorology
University of Oklahoma

On Wed, Aug 11, 2010 at 9:27 AM, John Hunter <jd...@gm...> wrote:

> On Wed, Aug 11, 2010 at 7:10 AM, c.jeang
> <chr...@un...> wrote:
> > Hie john,
> > and thank you for your prompt answer.
> > my version is currently
> > the
> > 0.99.1.1
> > I am going to install the
> > 1.0.0
> > Thank again
> > Best regards
>
> If you are on 0.99.1, then this is not the source of your problems
> since that version shipped with mpl_toolkits.mplot3d.  Can you
> describe the environment in which you are running, ie, exactly what
> you are doing to load mpl, what python interpreter, what OS, where you
> got matplotlib from?  For more info on how to provide us the
> information we need, see
>
>
> http://matplotlib.sourceforge.net/faq/troubleshooting_faq.html#report-a-problem
>
> PS: please keep all responses on list by replying to matplotlib-users
>
>
John,

The problem wasn't the mplot3d was missing (because it wasn't missing).  The
problem was that he was running the v1.0 examples with has the new syntax
for 3d plots that was not available in previous versions.  The change was
due to a commit I made just prior to the v1.0 release (which allowed for
subplotting of figures).

Maybe I should add a note to the documentation for the correct syntax for
mpl version prior to v1.0?

Ben Root

On Wed, Aug 11, 2010 at 7:10 AM, c.jeang
<chr...@un...> wrote:
> Hie john,
> and thank you for your prompt answer.
> my version is currently
> the
> 0.99.1.1
> I am going to install the
> 1.0.0
> Thank again
> Best regards

If you are on 0.99.1, then this is not the source of your problems
since that version shipped with mpl_toolkits.mplot3d.  Can you
describe the environment in which you are running, ie, exactly what
you are doing to load mpl, what python interpreter, what OS, where you
got matplotlib from?  For more info on how to provide us the
information we need, see

  http://matplotlib.sourceforge.net/faq/troubleshooting_faq.html#report-a-problem

PS: please keep all responses on list by replying to matplotlib-users

0.99.3 is more or less fine, but there is an annoying exception window
that pops up if you close IPython with a plot window open (using the
TkAgg backend).  But in my mind this is less bothersome than having to
close all the plot windows every time I run a script (I tend to write
scripts that generate 5-10 plots at a minimum).

If I could easily build an installer from svn, I would try it.  I
don't have any microsoft compilers installed on my windows computers.

Thanks again,

Ryan

On Wed, Aug 11, 2010 at 9:09 AM, Ryan Krauss <rya...@gm...> wrote:
> Thanks.
>
> I need to role out a python install for my students.  Classes start in
> a week and a half.  What should I do?  The installation for most of
> them needs to be fairly simple.
>
> Thanks,
>
> Ryan
>
> On Wed, Aug 11, 2010 at 2:25 AM, Eric Firing <ef...@ha...> wrote:
>> On 08/10/2010 05:43 PM, Ryan Krauss wrote:
>>> I just upgraded my windows machine to matplotlib 1.0.0 and a simple
>>> script such as
>>>
>>> from pylab import *
>>> from scipy import *
>>>
>>> t = arange(0,1,0.01)
>>> y = sin(2*pi*t)
>>>
>>> figure(1)
>>> clf()
>>> plot(t,y)
>>>
>>> show()
>>>
>>> Now halts execution when run from the ipython -pylab prompt.  The same
>>> commands typed at the commandline do not lead to show() halting
>>> execution.
>>>
>>> Is this expected behavior?
>>
>> This was fixed three weeks ago in svn, both the maintenance branch and
>> the trunk.  I made some changes in show() shortly before 1.0, trying to
>> get uniform and reasonable behavior in all backends, and I didn't quite
>> succeed.  I think I got it all straightened out--but only after the
>> release, unfortunately.  I hope it won't be too long before a 1.0.1
>> bugfix release can be made, but I am aware of no schedule.
>>
>> Eric
>>
>>>
>>> Thanks,
>>>
>>> Ryan
>>>
>>> ------------------------------------------------------------------------------
>>> This SF.net email is sponsored by
>>>
>>> Make an app they can't live without
>>> Enter the BlackBerry Developer Challenge
>>> http://p.sf.net/sfu/RIM-dev2dev
>>> _______________________________________________
>>> Matplotlib-users mailing list
>>> Mat...@li...
>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by
>>
>> Make an app they can't live without
>> Enter the BlackBerry Developer Challenge
>> http://p.sf.net/sfu/RIM-dev2dev
>> _______________________________________________
>> Matplotlib-users mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>>
>

Thanks.

I need to role out a python install for my students.  Classes start in
a week and a half.  What should I do?  The installation for most of
them needs to be fairly simple.

Thanks,

Ryan

On Wed, Aug 11, 2010 at 2:25 AM, Eric Firing <ef...@ha...> wrote:
> On 08/10/2010 05:43 PM, Ryan Krauss wrote:
>> I just upgraded my windows machine to matplotlib 1.0.0 and a simple
>> script such as
>>
>> from pylab import *
>> from scipy import *
>>
>> t = arange(0,1,0.01)
>> y = sin(2*pi*t)
>>
>> figure(1)
>> clf()
>> plot(t,y)
>>
>> show()
>>
>> Now halts execution when run from the ipython -pylab prompt.  The same
>> commands typed at the commandline do not lead to show() halting
>> execution.
>>
>> Is this expected behavior?
>
> This was fixed three weeks ago in svn, both the maintenance branch and
> the trunk.  I made some changes in show() shortly before 1.0, trying to
> get uniform and reasonable behavior in all backends, and I didn't quite
> succeed.  I think I got it all straightened out--but only after the
> release, unfortunately.  I hope it won't be too long before a 1.0.1
> bugfix release can be made, but I am aware of no schedule.
>
> Eric
>
>>
>> Thanks,
>>
>> Ryan
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by
>>
>> Make an app they can't live without
>> Enter the BlackBerry Developer Challenge
>> http://p.sf.net/sfu/RIM-dev2dev
>> _______________________________________________
>> Matplotlib-users mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

On Aug 11, 2010, at 6:56 AM, Rob Schneider wrote:

> 
> I extract data out of a database (via Django and Python).  I'm drawing two bar charts.  One is a stacked bar, and one is a simple bar.
> The code for each graph is in their own function.  I call the function to draw the graph sequencially (in function "CreateAllWebSite() below).
> 
> Problem is that when I do this, the graph called second comes out all jumbled.  See attached copies of png files.  If I swap the function calls, always first is ok and the the second one is jumbled.  If I call them one at a time, they both work just fine (which is how i developed the second).  once put together, the second is wrong.  For example, the legend from the first graph gets put on the second graph . The x-axis for the second is all jumbled at the bottom left corner of the graph instead of along the x-axis properly.  
> 
> I'm using Matplotlib 0.98.5.3 on OS X.  I will upgrade to 1.0 of Matplot lib soon.
> 
> I suspect some sort of memory issue; perhaps caused by how I import matplotlib in the global section of the python program; but far as I can tell this is correct, or is it?  I suspect memory as how else would legend from the first graph get put on the second graph? Is there some sort of reset function to call to clear out the old graph? I sort of thought that calling a completely different function would cover that.
> 
> Here's the code extract with portions I think no relevant snipped out. From debugging I'm confident the number arrays holding the data is ok.  As I said, when producing the graphs one at a time, it work fine.  So that code snipped out below.
> 
> #!/usr/bin/env python
> # −*− coding: UTF−8 −*−
> 
> import matplotlib
> matplotlib.use('Agg') # before importing pyplot per docs
> import matplotlib.pyplot as plt
> import numpy as np
> 
> [snipped the import of Python and Django libraries]
> 
> ###########################################################
> def CreateAllWebSite():
>  # here is the one function that calls the two graphing functions sequentially.
>  # whichever of these is called first is done fine.  Second flawed.  calling one at at time, each works ok
>  CreateMemberStatFigure()
>  CreateMemberStatCategoryFigure()
> ###############################################
> def CreateMemberStatFigure():
> # this function creates a stacked bar chart
> [snipped out portions where arrays created]

Hi Rob,

It would be helpful if you could provide a runnable example. I know it's a pain, but you should simplify your example so that it's runnable with only matplotlib and numpy You should create some fake data to replace these portions that you've cut out. Plus there are some (Django?) classes/functions/globals that are undefined.

Best,
-Tony

I extract data out of a database (via Django and Python).  I'm drawing two bar charts.  One is a stacked bar, and one is a simple bar.
The code for each graph is in their own function.  I call the function to draw the graph sequencially (in function "CreateAllWebSite() below).

Problem is that when I do this, the graph called second comes out all jumbled.  See attached copies of png files.  If I swap the function calls, always first is ok and the the second one is jumbled.  If I call them one at a time, they both work just fine (which is how i developed the second).  once put together, the second is wrong.  For example, the legend from the first graph gets put on the second graph . The x-axis for the second is all jumbled at the bottom left corner of the graph instead of along the x-axis properly.  

I'm using Matplotlib 0.98.5.3 on OS X.  I will upgrade to 1.0 of Matplot lib soon.

I suspect some sort of memory issue; perhaps caused by how I import matplotlib in the global section of the python program; but far as I can tell this is correct, or is it?  I suspect memory as how else would legend from the first graph get put on the second graph? Is there some sort of reset function to call to clear out the old graph? I sort of thought that calling a completely different function would cover that.

Here's the code extract with portions I think no relevant snipped out. From debugging I'm confident the number arrays holding the data is ok.  As I said, when producing the graphs one at a time, it work fine.  So that code snipped out below.

#!/usr/bin/env python
# −*− coding: UTF−8 −*−

import matplotlib
matplotlib.use('Agg') # before importing pyplot per docs
import matplotlib.pyplot as plt
import numpy as np

[snipped the import of Python and Django libraries]

###########################################################
def CreateAllWebSite():
  # here is the one function that calls the two graphing functions sequentially.
  # whichever of these is called first is done fine.  Second flawed.  calling one at at time, each works ok
  CreateMemberStatFigure()
  CreateMemberStatCategoryFigure()
###############################################
def CreateMemberStatFigure():
# this function creates a stacked bar chart
[snipped out portions where arrays created]
  corp1=[]
  corp2=[]
  corp3=[]
  ordm=[]
  ordr=[]
  ordh=[]
  month=[]
  for i in memberstatsp:
      month.append(None2Zero(i['month']))   # None2Zero simply converts any "None" data to a number zero.
      corp1.append(None2Zero(i['CORP1']))
      corp2.append(None2Zero(i['CORP2']))
      corp3.append(None2Zero(i['CORP3']))
      ordm.append(None2Zero(i['ORM']))
      ordr.append(None2Zero(i['ORMR']))
      ordh.append(None2Zero(i['HON']))
  N=len(month)
  corp1=np.array(corp1)
  corp2=np.array(corp2)
  corp3=np.array(corp3)
  ordm=np.array(ordm)
  ordr=np.array(ordr)
  ordh=np.array(ordh)

  # create new bases for each bar
  base=np.zeros(N,int)
  base1=base+ordh
  base2=base1+corp3
  base3=base2+corp2
  base4=base3+corp1
  base5=base4+ordm

  width = 24        # the width of the bars: can also be len(x) sequence

  p1 = plt.bar(month, ordh, width, color=barchartcolor[0],linewidth=0)
  p2 = plt.bar(month, corp3, width, color=barchartcolor[1],bottom=base1,linewidth=0)
  p3 = plt.bar(month, corp2, width, color=barchartcolor[2],bottom=base2,linewidth=0)
  p4 = plt.bar(month, corp1, width, color=barchartcolor[3],bottom=base3,linewidth=0)
  p5 = plt.bar(month, ordm, width, color=barchartcolor[4],bottom=base4,linewidth=0)
  p6 = plt.bar(month, ordr, width, color=barchartcolor[5],bottom=base5,linewidth=0)

  plt.yticks(np.arange(0,200,20))
  plt.title(ORG_NAME+' Membership by Month')
  plt.ylabel('Count')
  plt.legend( (p1[0], p2[0], p3[0], p4[0], p5[0], p6[0]),mtypes,loc='best') 
  plt.show()

  matplotlib.rcParams['figure.figsize']=(3,2)

  fn=TEMP_DIR+SOC_MEMBER_STAT_BARCHART_FIGURE
  plt.savefig(fn)

  return

###############################################
def CreateMemberStatCategoryFigure():
  membercategories=Membercategory.objects.all()  # gets the categories out of the database
  mcats=[]
  cnt=[]
  for i in membercategories:
      mcats.append(i.category)
      cnt.append(Member.Active_objects.filter(membercategory__category=i.category).count())    
  xlocations = np.array(range(len(mcats)))+0.5
  p1 = plt.bar(xlocations,cnt)
  plt.figtext(0.15,0.85,dt)
  plt.xticks(xlocations+0.4, mcats,rotation=17)
  plt.title(ORG_NAME+' Membership by Member Category')
  plt.ylabel('Count')
  plt.show()

  matplotlib.rcParams['figure.figsize']=(3,2)

  fn=TEMP_DIR+SOC_MEMBER_STAT_BARCHART_CAT_FIGURE
  plt.savefig(fn)

  return

################################################

2010/8/11 Markus Baden <mar...@gm...>:
> I'm running Mac OS X 10.5.8.

Ok, that explains why it works to flawlessly.  When you would be on
10.6, you would probably run into the problem I mentioned, because the
software is compiled /also/ for 10.5, and hence with gcc-4.0.  Lucky
one ;-)  - I'm a bit annoyed by this, but it seems, one can load with
gcc-4.2 compiled software gcc-4.0 compiled libraries, but not vice
versa (i.e. load with a gcc-4.0 compiled program like python from EPD
a shared lib compiled with gcc-4.2).

Is the EPD you're using both for 10.5 and 10.6?

Well,
Friedrich

On 08/10/2010 05:43 PM, Ryan Krauss wrote:
> I just upgraded my windows machine to matplotlib 1.0.0 and a simple
> script such as
>
> from pylab import *
> from scipy import *
>
> t = arange(0,1,0.01)
> y = sin(2*pi*t)
>
> figure(1)
> clf()
> plot(t,y)
>
> show()
>
> Now halts execution when run from the ipython -pylab prompt.  The same
> commands typed at the commandline do not lead to show() halting
> execution.
>
> Is this expected behavior?

This was fixed three weeks ago in svn, both the maintenance branch and 
the trunk.  I made some changes in show() shortly before 1.0, trying to 
get uniform and reasonable behavior in all backends, and I didn't quite 
succeed.  I think I got it all straightened out--but only after the 
release, unfortunately.  I hope it won't be too long before a 1.0.1 
bugfix release can be made, but I am aware of no schedule.

Eric

>
> Thanks,
>
> Ryan
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

On Tuesday August 10 2010 20:31:02 Michael Waters wrote:
> Hi, I am making a simple pie chart that needs to be small ~3x3 inches.
> The problem I am having is that the text labels get pushed out side the
> figure. Is there anyway to make the plot smaller relative to the figure
> size? Here is my code and the resulting plot:

Hi Michael,

If you reduce the axes in size the pie chart will be reduced as well, so maybe 
something like
ax = axes([0.25, 0.25, 0.5, 0.5])
is all you need to do. I attached the resulting picture for your interest.

Kind regards,
Matthias

In case this is helpful:

E:\>C:\Python26\python.exe ipython_show_test.py --verbose-debug
$HOME=D:\
CONFIGDIR=D:\.matplotlib
matplotlib data path C:\Python26\lib\site-packages\matplotlib\mpl-data
loaded rc file D:\.matplotlib\matplotlibrc
matplotlib version 1.0.0
verbose.level debug
interactive is False
units is False
platform is win32
loaded modules: ['numpy.lib._iotools', 'xml.sax.urlparse', 'distutils', 'numpy.l
ib.npyio', 'functools', 'pylab', '_bisect', 'subprocess', 'gc', 'matplotlib.temp
file', 'distutils.sysconfig', 'ctypes._endian', 'encodings.encodings', 'matplotl
ib.colors', 'msvcrt', 'numpy.testing.sys', 'numpy.core.info', 'xml', 'numpy.fft.
types', 'numpy.ma.cPickle', 'matplotlib.copy', 'numpy.matrixlib.defmatrix', 'num
py.random.info', 'tempfile', 'numpy.compat.types', 'base64', 'numpy.linalg', 'ma
tplotlib.threading', 'numpy.core.machar', 'numpy.testing.types', 'numpy.testing'
, 'bisect', 'collections', 'numpy.polynomial.sys', 'numpy.core.umath', '_struct'
, 'distutils.types', 'numpy.testing.operator', 'numpy.lib.numpy', 'numpy.core.sc
alarmath', 'numpy.ma.sys', 'matplotlib.matplotlib', 'string', 'matplotlib.subpro
cess', 'numpy.testing.os', 'matplotlib.locale', 'numpy.lib.arraysetops', 'numpy.
testing.unittest', 'numpy.lib.math', 'textwrap', 'matplotlib.__future__', 'ssl',
 'numpy.testing.re', 'itertools', 'numpy.version', 'numpy.lib.re', 'distutils.re
', 'numpy.matrixlib.sys', 'ctypes.os', 'numpy.core.os', 'numpy.lib.type_check',
'numpy.compat.sys', 'numpy.lib.__builtin__', 'signal', 'numpy.lib.types', 'numpy
.lib._datasource', 'random', 'threading', 'numpy.fft.fftpack_lite', 'matplotlib.
cbook', 'ctypes.ctypes', 'xml.sax.xmlreader', 'numpy.polynomial.string', 'distut
ils.version', 'cStringIO', 'numpy.polynomial', 'numpy.numpy', 'matplotlib.String
IO', 'numpy.ma.extras', 'locale', 'numpy.add_newdocs', 'numpy.core.getlimits', '
xml.sax.saxutils', 'numpy.lib.sys', 'encodings', 'numpy.ma.itertools', 'array',
'StringIO', 'abc', 'numpy.matrixlib', 'numpy.ctypes', 'numpy.testing.decorators'
, 'matplotlib.warnings', 'rfc822', 'matplotlib.string', '_subprocess', 'urllib',
 'matplotlib.sys', 're', 'numpy.lib._compiled_base', 'ntpath', 'new', 'numpy.ran
dom.mtrand', 'urllib2', 'matplotlib.cPickle', 'math', 'numpy.fft.helper', 'numpy
.ma.warnings', 'matplotlib.numpy', 'UserDict', 'numpy.lib.function_base', 'distu
tils.os', 'matplotlib', 'numpy.fft.numpy', 'xml.sax.codecs', 'exceptions', 'nump
y.lib.info', 'numpy.core.numerictypes', 'ctypes', 'numpy.lib.warnings', 'ctypes.
struct', 'codecs', 'numpy.core._sort', 'numpy.os', 'struct', '_functools', '_loc
ale', 'numpy.__builtin__', 'matplotlib.sre_constants', 'matplotlib.os', 'thread'
, 'numpy.lib.ufunclike', 'numpy.core.memmap', 'traceback', 'numpy.testing.warnin
gs', 'weakref', 'numpy.core._internal', 'numpy.fft.fftpack', 'numpy.linalg.lapac
k_lite', 'numpy.ma', 'distutils.sys', 'os', 'numpy.matrixlib.numpy', 'httplib',
'numpy.lib.itertools', '__future__', '_collections', 'xml.sax.types', 'matplotli
b.traceback', '_sre', 'unittest', 'numpy.core.sys', 'numpy.random', 'numpy.linal
g.numpy', '__builtin__', 'numpy.lib.twodim_base', 'numpy.ma.core', 'matplotlib.r
e', 'numpy.core.cPickle', 'operator', 'numpy.polynomial.polytemplate', 'numpy.co
re.arrayprint', 'distutils.string', 'numpy.lib.arrayterator', 'ctypes._ctypes',
'ctypes.sys', 'matplotlib.errno', 'numpy.testing.nosetester', 'posixpath', 'nump
y.lib.financial', 'numpy.core.multiarray', 'errno', '_socket', 'binascii', 'sre_
constants', 'datetime', 'numpy.core.shape_base', 'xml.sax.handler', 'os.path', '
numpy.core.function_base', 'numpy.compat.py3k', '_ctypes', 'numpy.lib.stride_tri
cks', 'numpy.core.numpy', 'numpy', '_warnings', 'numpy.polynomial.chebyshev', 'm
atplotlib.types', 'xml.sax.os', 'cPickle', 'encodings.__builtin__', 'numpy.polyn
omial.warnings', 'matplotlib.xml', 'matplotlib.new', '_codecs', 'numpy.lib.opera
tor', 'numpy.polynomial.polynomial', 'encodings.cp1252', 'matplotlib.pyparsing',
 'nturl2path', 'numpy.ma.numpy', 'copy', 'numpy.core.re', 'socket', 'numpy.core.
fromnumeric', 'hashlib', 'numpy.ctypeslib', 'keyword', 'numpy.lib.scimath', 'num
py.fft', 'numpy.lib', 'numpy.random.numpy', 'matplotlib.urllib2', 'matplotlib.ra
ndom', 'numpy.polynomial.__future__', 'encodings.aliases', 'matplotlib.distutils
', 'fnmatch', 'sre_parse', 'numpy.core.ctypes', 'mimetools', 'distutils.distutil
s', 'copy_reg', 'sre_compile', 'xml.sax', '_hashlib', '_random', 'numpy.lib.__fu
ture__', 'site', 'numpy.lib.polynomial', 'numpy.compat', 'numpy._import_tools',
'zipimport', '__main__', 'numpy.fft.info', 'numpy.core.records', 'shutil', 'nump
y.lib.cPickle', 'numpy.sys', 'matplotlib.weakref', 'xml.sax.urllib', 'numpy.core
._dotblas', 'numpy.testing.traceback', 'strop', 'numpy.testing.numpytest', 'nump
y.polynomial.numpy', 'numpy.core.numeric', 'numpy.linalg.info', 'encodings.codec
s', '_abcoll', 'numpy.core', 'matplotlib.rcsetup', 'matplotlib.time', 'nt', 'xml
.sax._exceptions', 'genericpath', 'stat', '_ssl', 'numpy.lib.index_tricks', 'num
py.testing.utils', 'warnings', 'numpy.lib.utils', 'numpy.core.defchararray', 'nu
mpy.polynomial.polyutils', 'numpy.lib.shape_base', 'numpy.core.types', 'sys', 'n
umpy.core.warnings', 'numpy.compat._inspect', 'numpy.core.__builtin__', 'xml.sax
.sys', 'numpy.lib.format', 'numpy.lib.os', 'numpy.__config__', 'types', 'numpy.l
ib.shutil', 'matplotlib.datetime', 'matplotlib.fontconfig_pattern', '_weakref',
'distutils.errors', 'urlparse', 'linecache', 'matplotlib.shutil', 'numpy.lib.cSt
ringIO', 'time', 'numpy.linalg.linalg', 'numpy.testing.numpy']
Using fontManager instance from D:\.matplotlib\fontList.cache
backend TkAgg version 8.5
findfont: Matching :family=serif:style=normal:variant=normal:weight=normal:stret
ch=normal:size=medium to Bitstream Vera Serif (C:\Python26\lib\site-packages\mat
plotlib\mpl-data\fonts\ttf\VeraSe.ttf) with score of 0.166667



IPython 0.10

In [4]: scipy.__version__
Out[4]: '0.8.0'

In [5]: import numpy

In [6]: numpy.__version__
Out[6]: '1.5.0b1'



On Tue, Aug 10, 2010 at 10:43 PM, Ryan Krauss <rya...@gm...> wrote:
> I just upgraded my windows machine to matplotlib 1.0.0 and a simple
> script such as
>
> from pylab import *
> from scipy import *
>
> t = arange(0,1,0.01)
> y = sin(2*pi*t)
>
> figure(1)
> clf()
> plot(t,y)
>
> show()
>
> Now halts execution when run from the ipython -pylab prompt.  The same
> commands typed at the commandline do not lead to show() halting
> execution.
>
> Is this expected behavior?
>
> Thanks,
>
> Ryan
>

I just upgraded my windows machine to matplotlib 1.0.0 and a simple
script such as

from pylab import *
from scipy import *

t = arange(0,1,0.01)
y = sin(2*pi*t)

figure(1)
clf()
plot(t,y)

show()

Now halts execution when run from the ipython -pylab prompt.  The same
commands typed at the commandline do not lead to show() halting
execution.

Is this expected behavior?

Thanks,

Ryan

On Aug 11, 2010, at 6:09 AM, Friedrich Romstedt wrote:

> Are you on OSX 10.5 or 10.6?  I'm asking because it's important for
> others when you're on 10.5 because you're using gcc-4.0 then, while
> 10.6 users have at least for non-Python (distutils) compilations
> gcc-4.2 as default.

I'm running Mac OS X 10.5.8.

Markus