matplotlib-devel Mailing List for matplotlib

On Sat, Jul 11, 2009 at 08:18:25AM -1000, Eric Firing wrote:
> Thank you for the testing and reporting. I don't normally use wx and I 
> am not willing to fiddle with multiple versions of it, so I am working 
> almost blind on this.
I use wx a lot, and with MPL embedded in other programs, so I am a good
test bed, and will hopefully catch major problems. However, I of course
cover only the configurations I have installed on the various boxes I
work on.
One of the really nice things with MPL, is that there is a significant
user base working from SVN, and thus catching problems early.
Gaël

On Sat, Jul 11, 2009 at 1:18 PM, Eric Firing<ef...@ha...> wrote:
>> These things are hard problems, thanks for your work.
>
> Thank you for the testing and reporting. I don't normally use wx and I am
> not willing to fiddle with multiple versions of it, so I am working almost
> blind on this.
This is working for me, and by working I mean not displaying the warning...
Thanks Eric
JDH

Gael Varoquaux wrote:
> On Sat, Jul 11, 2009 at 08:10:23AM -1000, Eric Firing wrote:
>> OK, I tried again in svn 7256. I think this is a little cleaner. More 
>> diagnostic information could still be added to the exception messages if 
>> this is going to be a continuing problem.
> 
> It seems to work for me in all the configurations I can think of (and
> does raises the error when 2.6 is imported instead of 2.8.). I could be
> forgetting configurations, as the combinatory is high.
> 
> These things are hard problems, thanks for your work.
Thank you for the testing and reporting. I don't normally use wx and I 
am not willing to fiddle with multiple versions of it, so I am working 
almost blind on this.
Eric

On Sat, Jul 11, 2009 at 08:10:23AM -1000, Eric Firing wrote:
> OK, I tried again in svn 7256. I think this is a little cleaner. More 
> diagnostic information could still be added to the exception messages if 
> this is going to be a continuing problem.
It seems to work for me in all the configurations I can think of (and
does raises the error when 2.6 is imported instead of 2.8.). I could be
forgetting configurations, as the combinatory is high.
These things are hard problems, thanks for your work.
Gaël

Gael Varoquaux wrote:
> On Sat, Jul 11, 2009 at 12:49:03PM -0500, John Hunter wrote:
>>> Can you do an 'import wxversion; print wxversion.__file__', so that we
>>> understand better why you are getting these warnings.
> 
>> In [1]: import wxversion
> 
>> In [2]: print wxversion.__file__
>> /Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/wxversion.pyc
> 
> Hell, sorry, I don't understand why you are getting the warning.
> 
> Gaël
OK, I tried again in svn 7256. I think this is a little cleaner. More 
diagnostic information could still be added to the exception messages if 
this is going to be a continuing problem.
Eric

On Sat, Jul 11, 2009 at 12:49:03PM -0500, John Hunter wrote:
> > Can you do an 'import wxversion; print wxversion.__file__', so that we
> > understand better why you are getting these warnings.
> In [1]: import wxversion
> In [2]: print wxversion.__file__
> /Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/wxversion.pyc
Hell, sorry, I don't understand why you are getting the warning.
Gaël

On Sat, Jul 11, 2009 at 12:43 PM, Gael
Varoquaux<gae...@no...> wrote:
> On Sat, Jul 11, 2009 at 12:38:13PM -0500, John Hunter wrote:
>> If I can speak for the typical user, these kinds of warnings are
>> usually annoying and not that helpful. I am a naive wx user -- I
>> installed it many moons ago from a binary when I installed python and
>> haven't thought about it since. I don't know what wxversion is or how
>> to upgrade it. All I know is mpl was working fine, still works fine,
>> and now generates an annoying warning.  So I am not sure this is
>> progress, but may help someone who has a complicated wx setup avoid
>> difficult to trackdown bug.  So I would prefer to silence this, but
>> am not sure what the right solution is. Here is my wx installation
>
> I am a bit like you. I believe these warning are not terribly helpful.
>
> Can you do an 'import wxversion; print wxversion.__file__', so that we
> understand better why you are getting these warnings.
In [1]: import wxversion
In [2]: print wxversion.__file__
/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/wxversion.pyc
In [3]: import wx
In [4]: print wx.__version__
2.8.3.0
In [5]: print wx.__file__
/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/wx-2.8-mac-unicode/wx/__init__.pyc
In [6]: wxversion.
wxversion.UPDATE_URL wxversion.__setattr__
wxversion.VersionError wxversion.__str__
wxversion._EM_DEBUG wxversion._find_default
wxversion.__builtins__ wxversion._find_installed
wxversion.__class__ wxversion._get_best_match
wxversion.__delattr__ wxversion._pattern
wxversion.__dict__ wxversion._selected
wxversion.__doc__ wxversion._wxPackageInfo
wxversion.__file__ wxversion.checkInstalled
wxversion.__getattribute__ wxversion.ensureMinimal
wxversion.__hash__ wxversion.fnmatch
wxversion.__init__ wxversion.getInstalled
wxversion.__name__ wxversion.glob
wxversion.__new__ wxversion.os
wxversion.__reduce__ wxversion.re
wxversion.__reduce_ex__ wxversion.select
wxversion.__repr__ wxversion.sys
In [6]: wxversion.getInstalled?
Type:		function
Base Class:	<type 'function'>
String Form:	<function getInstalled at 0xe62e30>
Namespace:	Interactive
File:		/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/wxversion.py
Definition:	wxversion.getInstalled()
Docstring:
 Returns a list of strings representing the installed wxPython
 versions that are found on the system.
In [7]: wxversion.getInstalled()
Out[7]: ['2.8-mac-unicode']

On Sat, Jul 11, 2009 at 12:38:13PM -0500, John Hunter wrote:
> If I can speak for the typical user, these kinds of warnings are
> usually annoying and not that helpful. I am a naive wx user -- I
> installed it many moons ago from a binary when I installed python and
> haven't thought about it since. I don't know what wxversion is or how
> to upgrade it. All I know is mpl was working fine, still works fine,
> and now generates an annoying warning. So I am not sure this is
> progress, but may help someone who has a complicated wx setup avoid
> difficult to trackdown bug. So I would prefer to silence this, but
> am not sure what the right solution is. Here is my wx installation
I am a bit like you. I believe these warning are not terribly helpful.
Can you do an 'import wxversion; print wxversion.__file__', so that we
understand better why you are getting these warnings.
Cheers,
Gaël

On Fri, Jul 10, 2009 at 4:33 PM, Eric Firing<ef...@ha...> wrote:
> Gael Varoquaux wrote:
>> On Fri, Jul 10, 2009 at 11:05:24PM +0200, Gael Varoquaux wrote:
>>>> Committed to svn. Please check it.
>>
>>> Certainly does work betters.
>>
>> Actually, I beg your pardon, but it does not really work: if you have
>> 2.6 and 2.8 installed, it will still import 2.6, which is not what you
>> want.
>>
>> Here is a patch that works a bit better: it does import 2.8 even when 2.6
>> is installed:
>
> Committed, thank you.
I just updated mpl from svn and now get
y:126: UserWarning: Update your wxversion.py to one including
AlreadyImportedError
 "Update your wxversion.py to one including AlreadyImportedError")
backend WXAgg version 2.8.3.0
If I can speak for the typical user, these kinds of warnings are
usually annoying and not that helpful. I am a naive wx user -- I
installed it many moons ago from a binary when I installed python and
haven't thought about it since. I don't know what wxversion is or how
to upgrade it. All I know is mpl was working fine, still works fine,
and now generates an annoying warning. So I am not sure this is
progress, but may help someone who has a complicated wx setup avoid
difficult to trackdown bug. So I would prefer to silence this, but
am not sure what the right solution is. Here is my wx installation
In [6]: wx.__version__
Out[6]: '2.8.3.0'
In [7]: !ls -ld
/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/wx*
drwxrwxr-x 5 root admin 170 Mar 22 2007
/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/wx-2.8-mac-unicode
-rw-r--r-- 1 root admin 18 Mar 22 2007
/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/wx.pth
-rw-r--r-- 1 root admin 1266 Mar 22 2007
/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/wxPython_common-2.8.3.0-py2.5.egg-info
drwxr-xr-x 5 root admin 170 Mar 22 2007
/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/wxaddons
-rw-r--r-- 1 root admin 1259 Mar 22 2007
/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/wxaddons-2.8.3.0-py2.5.egg-info
-rw-r--r-- 1 root admin 17809 Mar 16 2006
/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/wxversion.py
-rw-r--r-- 1 jdhunter admin 15750 Mar 23 20:28
/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/wxversion.pyc
JDH

The early registration deadline for SciPy 2009 has been extended
for one week to July 17, 2009. Please register (
http://conference.scipy.org/to_register )
by this date to take advantage of the reduced early registration rate.
About the conference
--------------------
SciPy 2009, the 8th Python in Science conference, will be held from
August 18-23, 2009 at Caltech in Pasadena, CA, USA. The conference
starts with two days of tutorials to the scientific Python tools.
There will be two tracks, one for introduction of the basic tools to
beginners, and one for more advanced tools. The tutorials will be
followed by two days of talks. Both days of talks will begin with a
keynote address. The first day’s keynote will be given by Peter
Norvig, the Director of Research at Google; while, the second keynote
will be delivered by Jon Guyer, a Materials Scientist in the
Thermodynamics and Kinetics Group at NIST. The program committee will
select the remaining talks from submissions to our call for papers.
All selected talks will be included in our conference proceedings
edited by the program committee. After the talks each day we will
provide several rooms for impromptu birds of a feather discussions.
Finally, the last two days of the conference will be used for a number
of coding sprints on the major software projects in our community.
For the 8th consecutive year, the conference will bring together the
developers and users of the open source software stack for scientific
computing with Python. Attendees have the opportunity to review the
available tools and how they apply to specific problems. By providing
a forum for developers to share their Python expertise with the wider
commercial, academic, and research communities, this conference
fosters collaboration and facilitates the sharing of software
components, techniques, and a vision for high level language use in
scientific computing.
For further information, please visit the conference homepage:
http://conference.scipy.org.
Important Dates
---------------
* Friday, July 3: Abstracts Due
* Wednesday, July 15: Announce accepted talks, post schedule
* Friday, July 17: Early Registration ends
* Tuesday-Wednesday, August 18-19: Tutorials
* Thursday-Friday, August 20-21: Conference
* Saturday-Sunday, August 22-23: Sprints
* Friday, September 4: Papers for proceedings due
Executive Committee
-------------------
* Jarrod Millman, UC Berkeley, USA (Conference Chair)
* Gaël Varoquaux, INRIA Saclay, France (Program Co-Chair)
* Stéfan van der Walt, University of Stellenbosch, South Africa
(Program Co-Chair)
* Fernando Pérez, UC Berkeley, USA (Tutorial Chair)