You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
(12) |
Sep
(12) |
Oct
(56) |
Nov
(65) |
Dec
(37) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(59) |
Feb
(78) |
Mar
(153) |
Apr
(205) |
May
(184) |
Jun
(123) |
Jul
(171) |
Aug
(156) |
Sep
(190) |
Oct
(120) |
Nov
(154) |
Dec
(223) |
| 2005 |
Jan
(184) |
Feb
(267) |
Mar
(214) |
Apr
(286) |
May
(320) |
Jun
(299) |
Jul
(348) |
Aug
(283) |
Sep
(355) |
Oct
(293) |
Nov
(232) |
Dec
(203) |
| 2006 |
Jan
(352) |
Feb
(358) |
Mar
(403) |
Apr
(313) |
May
(165) |
Jun
(281) |
Jul
(316) |
Aug
(228) |
Sep
(279) |
Oct
(243) |
Nov
(315) |
Dec
(345) |
| 2007 |
Jan
(260) |
Feb
(323) |
Mar
(340) |
Apr
(319) |
May
(290) |
Jun
(296) |
Jul
(221) |
Aug
(292) |
Sep
(242) |
Oct
(248) |
Nov
(242) |
Dec
(332) |
| 2008 |
Jan
(312) |
Feb
(359) |
Mar
(454) |
Apr
(287) |
May
(340) |
Jun
(450) |
Jul
(403) |
Aug
(324) |
Sep
(349) |
Oct
(385) |
Nov
(363) |
Dec
(437) |
| 2009 |
Jan
(500) |
Feb
(301) |
Mar
(409) |
Apr
(486) |
May
(545) |
Jun
(391) |
Jul
(518) |
Aug
(497) |
Sep
(492) |
Oct
(429) |
Nov
(357) |
Dec
(310) |
| 2010 |
Jan
(371) |
Feb
(657) |
Mar
(519) |
Apr
(432) |
May
(312) |
Jun
(416) |
Jul
(477) |
Aug
(386) |
Sep
(419) |
Oct
(435) |
Nov
(320) |
Dec
(202) |
| 2011 |
Jan
(321) |
Feb
(413) |
Mar
(299) |
Apr
(215) |
May
(284) |
Jun
(203) |
Jul
(207) |
Aug
(314) |
Sep
(321) |
Oct
(259) |
Nov
(347) |
Dec
(209) |
| 2012 |
Jan
(322) |
Feb
(414) |
Mar
(377) |
Apr
(179) |
May
(173) |
Jun
(234) |
Jul
(295) |
Aug
(239) |
Sep
(276) |
Oct
(355) |
Nov
(144) |
Dec
(108) |
| 2013 |
Jan
(170) |
Feb
(89) |
Mar
(204) |
Apr
(133) |
May
(142) |
Jun
(89) |
Jul
(160) |
Aug
(180) |
Sep
(69) |
Oct
(136) |
Nov
(83) |
Dec
(32) |
| 2014 |
Jan
(71) |
Feb
(90) |
Mar
(161) |
Apr
(117) |
May
(78) |
Jun
(94) |
Jul
(60) |
Aug
(83) |
Sep
(102) |
Oct
(132) |
Nov
(154) |
Dec
(96) |
| 2015 |
Jan
(45) |
Feb
(138) |
Mar
(176) |
Apr
(132) |
May
(119) |
Jun
(124) |
Jul
(77) |
Aug
(31) |
Sep
(34) |
Oct
(22) |
Nov
(23) |
Dec
(9) |
| 2016 |
Jan
(26) |
Feb
(17) |
Mar
(10) |
Apr
(8) |
May
(4) |
Jun
(8) |
Jul
(6) |
Aug
(5) |
Sep
(9) |
Oct
(4) |
Nov
|
Dec
|
| 2017 |
Jan
(5) |
Feb
(7) |
Mar
(1) |
Apr
(5) |
May
|
Jun
(3) |
Jul
(6) |
Aug
(1) |
Sep
|
Oct
(2) |
Nov
(1) |
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2025 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
|
|
1
(9) |
2
(11) |
3
(2) |
|
4
|
5
(6) |
6
(1) |
7
(6) |
8
(7) |
9
(16) |
10
(6) |
|
11
(2) |
12
(13) |
13
(3) |
14
(6) |
15
(6) |
16
(19) |
17
(2) |
|
18
(1) |
19
(1) |
20
(11) |
21
(5) |
22
(4) |
23
(7) |
24
(14) |
|
25
(15) |
26
(27) |
27
(26) |
28
(7) |
29
(2) |
30
(7) |
|
|
From: Matthieu B. <mat...@gm...> - 2007-11-10 22:22:07
|
Hi, mpl does not build the wxagg bridge starting from wxPython 2.8, thanks to an upgraded system. So you can use wx directly without (much ?) loss of speed. Matthieu 2007/11/10, Jeff Peery <jef...@ya...>: > > Hello, > I've been using wxpython 2.6 unicode version and I recently upgraded > to 2.8 unicode version. I'm using matplotlib 0.90.1 wxAgg in my wx app > and when I fire it up it gives me a message that it cannot find > 'wxmsw26uh_vc.dll'. I've had this problem before and the solution was to > install the unicode version of wxpython. But it doesn't seem to solve the > problem with wxpython 2.8. > > how do I get rid of this error? > thanks! > > Jeff > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users > > -- French PhD student Website : http://miles.developpez.com/ Blogs : http://matt.eifelle.com and http://blog.developpez.com/?blog=92 LinkedIn : http://www.linkedin.com/in/matthieubrucher |
|
From: Darren D. <dar...@co...> - 2007-11-10 22:15:40
|
On Saturday 10 November 2007 04:52:31 pm Michael McNeil Forbes wrote:
> On 10 Nov 2007, at 7:51 AM, Michael V. DePalatis wrote:
> ...
>
> > I recently discovered that if I import
> > pylab after importing numpy, I get tons of warnings:
> >
> > Warning: divide by zero encountered in divide
> > Warning: invalid value encountered in multiply
> > Warning: overflow encountered in long_scalars
> >
> > with the last occurring far most often (interestingly, I do not get
> > these warnings if pylab is imported before numpy). My question then is
> > two fold:
> >
> > (1) Why do I only get these warnings depending on when I import pylab?
>
> I am not sure: with the latest svn builds I get the message both
> ways. Maybe the default error handling is different between the
> version of numpy and matplotlib you have installed.
>
> > (2) (a more general python question) How can I get these warning
> > messages to give me *useful* information, such as where the
> > problems
> > are happening?
>
> In numpy you can cause these to be exceptions by setting
>
> numpy.seterr("raise")
>
> Now you can see exactly where the exception happens.
>
> If you don't want to stop execution at this point, you use a
> callback. This will pop-open the debugger at the point of error, but
> allow you to continue.
>
> def f(err,flag):
> import pdb; pdb.set_trace()
>
> numpy.seterr("call")
> numpy.seterrcall(f)
>
> In general, with python warnings you can change them to exceptions by
> using warnings.simplefilter('error',Warning) (see http://
> docs.python.org/lib/module-warnings.html for details), however numpy
> does not seem to issue warnings, instead opting to directly print a
> message. (Anyone know why the warnings library is not used? Is this
> a bug that should be fixed?)
It would be better to discuss this on the numpy mailing list.
Darren
|
|
From: Jeff P. <jef...@ya...> - 2007-11-10 21:59:40
|
Hello, I've been using wxpython 2.6 unicode version and I recently upgraded to 2.8 unicode version. I'm using matplotlib 0.90.1 wxAgg in my wx app and when I fire it up it gives me a message that it cannot find 'wxmsw26uh_vc.dll'. I've had this problem before and the solution was to install the unicode version of wxpython. But it doesn't seem to solve the problem with wxpython 2.8. how do I get rid of this error? thanks! Jeff __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
|
From: Michael M. F. <mf...@ph...> - 2007-11-10 21:52:41
|
On 10 Nov 2007, at 7:51 AM, Michael V. DePalatis wrote:
...
> I recently discovered that if I import
> pylab after importing numpy, I get tons of warnings:
>
> Warning: divide by zero encountered in divide
> Warning: invalid value encountered in multiply
> Warning: overflow encountered in long_scalars
>
> with the last occurring far most often (interestingly, I do not get
> these warnings if pylab is imported before numpy). My question then is
> two fold:
>
> (1) Why do I only get these warnings depending on when I import pylab?
>
I am not sure: with the latest svn builds I get the message both
ways. Maybe the default error handling is different between the
version of numpy and matplotlib you have installed.
> (2) (a more general python question) How can I get these warning
> messages to give me *useful* information, such as where the
> problems
> are happening?
>
In numpy you can cause these to be exceptions by setting
numpy.seterr("raise")
Now you can see exactly where the exception happens.
If you don't want to stop execution at this point, you use a
callback. This will pop-open the debugger at the point of error, but
allow you to continue.
def f(err,flag):
import pdb; pdb.set_trace()
numpy.seterr("call")
numpy.seterrcall(f)
In general, with python warnings you can change them to exceptions by
using warnings.simplefilter('error',Warning) (see http://
docs.python.org/lib/module-warnings.html for details), however numpy
does not seem to issue warnings, instead opting to directly print a
message. (Anyone know why the warnings library is not used? Is this
a bug that should be fixed?)
Michael.
|
|
From: John H. <jd...@gm...> - 2007-11-10 20:09:54
|
On Nov 9, 2007 1:08 PM, Don Peterson <do...@gd...> wrote: > Note: I had been using the Enthought edition of python (2.4.3 version of > python) and matplotlib and everything worked great. I then tried to > install the map addition to matplotlib and the installation failed. After > that, I started getting the import error on gobject, which I assume is > something from GTK. > > Does anyone have any suggestions on how to fix this? I'm pretty helpless > right now without matplotlib, as I use it to generate graphs for a > technical document I'm writing. For some reason, your backend is being set to GTKAgg, though this should not be the default on windows. If you want to use GTK, you can install pygtk which has a win32 installer. But more likely, you don't want this, so you need to find your matplotlib rc file and change the backend bariable o TkAgg (i you ant to use TkInter) or WXAgg (if you want to use wxpython). If you are usin the enthought tools, you may want to consider WxAgg since many of their tools work with wx. The easiest way to find your matplotlib rc file is to run a simple script that imports pylab with the --verbose-helpful flag, eg > python myscript.py --verbose-helpful and it will print a line telling you the path to the matplotlib rc file. Change the backend line from GTKAgg to the desired backend. JDH |
|
From: Michael V. D. <mv...@ga...> - 2007-11-10 15:53:04
|
Hello,
I am attempting to write a small simulation to reproduce something
from a paper. However, I'm having a whale of a time getting it to
work (as far as I have been able to tell, the calculations from the
paper at least are identical to what I am trying to do, which makes
this all the more frustrating). I recently discovered that if I import
pylab after importing numpy, I get tons of warnings:
Warning: divide by zero encountered in divide
Warning: invalid value encountered in multiply
Warning: overflow encountered in long_scalars
with the last occurring far most often (interestingly, I do not get
these warnings if pylab is imported before numpy). My question then is
two fold:
(1) Why do I only get these warnings depending on when I import pylab?
(2) (a more general python question) How can I get these warning
messages to give me *useful* information, such as where the problems
are happening?
Thanks,
--
Michael V. DePalatis
Georgia Institute of Technology
School of Physics
837 State Street
Atlanta, GA 30332-0430
em vee dee at gatech dot edu
http://mike.depalatis.net
|