Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
Close
From: mame louk <mamelouk@gm...>  20060318 20:16:25
Attachments:
Message as HTML

SGkgZXZlcnlvbmUsCgpJIHRyaWVkIHRvIGluc3RhbGwgbWF0cGxvdGxpYiBmb3IgdXNlIHdpdGgg TmV0d29ya1gsIGJ1dCBJIGdvdCB0aGlzIGVycm9yCgppbXBvcnQgcHlsYWIgLT4KClRyYWNlYmFj ayAobW9zdCByZWNlbnQgY2FsbCBsYXN0KToKPC4uLj4KICBGaWxlICJDOlxQcm9ncmFtCkZpbGVz XFB5dGhvbjI0XExpYlxzaXRlLXBhY2thZ2VzXG1hdHBsb3RsaWJcbnVtZXJpeFxfX2luaXRfXy5w eSIsIGxpbmUgNjAsCmluID8KICAgIGZyb20gTnVtZXJpYyBpbXBvcnQgKgpJbXBvcnRFcnJvcjog Tm8gbW9kdWxlIG5hbWVkIE51bWVyaWMKCgpJJ3ZlIHNlZW4gdGhhdCBOdW1lcmljIHdhcyByZWNl bnRseSBjaGFuZ2VkIHRvIE51bXB5LCBJJ3ZlIHRyaWVkIHRvIGluc3RhbGwKYSBsb3Qgb2YgcGFj a2FnZXMgYnV0IGl0IHN0aWxsIGRvbid0IHdvcmsuCgpEb2VzIGFueW9uZSBhbHJlYWR5IGhhdmUg dGhpcyBwcm9ibGVtID8KClRoYW5rcywK 
From: marc desmarais <mdesm2005@ya...>  20090811 02:04:35
Attachments:
Message as HTML

Are there still two pylabs? Are the following two web pages referring to the same pylab? http://www.scipy.org/PyLab http://matplotlib.sourceforge.net/ I'm a bit confused (trying to get the Scipy, Numpy, Pylab, Matplolib story straight, before I plunge in) Marc Desmarais Long Beach, CA, 90814 
From: Eric Firing <efiring@ha...>  20090811 02:22:31

marc desmarais wrote: > Are there still two pylabs? Are the following two web pages referring > to the same pylab? Not exactly: > This one is a vision or proposal, open for discussion: > http://www.scipy.org/PyLab This one is real: > http://matplotlib.sourceforge.net/ > The pylab interface to the matplotlib plotting library has some of the characteristics the author of the first link is talking about, but the trend has been away from some aspects of that vision, not towards it. For more about the real pylab, see http://matplotlib.sourceforge.net/faq/usage_faq.html#matplotlibpylabandpyplothowaretheyrelated > I'm a bit confused (trying to get the Scipy, Numpy, Pylab, Matplolib > story straight, before I plunge in) Numpy is the common core, providing Ndimensional arrays and math; matplotlib is a plotting library, using numpy; scipy is a collection of math/science functionality, also using numpy. But don't forget ipython, which provides a nice interactive shell: http://ipython.scipy.org/moin/ Eric > > Marc Desmarais > Long Beach, CA, 90814 
From: Sebastian Haase <seb.haase@gm...>  20090811 08:11:31

Thanks for the info  very informative  maybe this post could be somehow added or linked to from http://www.scipy.org/PyLab  Sebastian Haase On Tue, Aug 11, 2009 at 4:22 AM, Eric Firing<efiring@...> wrote: > marc desmarais wrote: >> Are there still two pylabs? Are the following two web pages referring >> to the same pylab? > > Not exactly: >> > This one is a vision or proposal, open for discussion: >> http://www.scipy.org/PyLab > > This one is real: >> http://matplotlib.sourceforge.net/ >> > > The pylab interface to the matplotlib plotting library has some of the > characteristics the author of the first link is talking about, but the > trend has been away from some aspects of that vision, not towards it. > > For more about the real pylab, see > http://matplotlib.sourceforge.net/faq/usage_faq.html#matplotlibpylabandpyplothowaretheyrelated > > >> I'm a bit confused (trying to get the Scipy, Numpy, Pylab, Matplolib >> story straight, before I plunge in) > > Numpy is the common core, providing Ndimensional arrays and math; > matplotlib is a plotting library, using numpy; scipy is a collection of > math/science functionality, also using numpy. > > But don't forget ipython, which provides a nice interactive shell: > http://ipython.scipy.org/moin/ > > Eric > >> >> Marc Desmarais >> Long Beach, CA, 90814 > >  > Let Crystal Reports handle the reporting  Free Crystal Reports 2008 30Day > trial. Simplify your report design, integration and deployment  and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobjjuly > _______________________________________________ > Matplotlibusers mailing list > Matplotlibusers@... > https://lists.sourceforge.net/lists/listinfo/matplotlibusers > 
From: Tom K. <tpk@kr...>  20090811 09:28:31

Sebastian Haase3 wrote: > > Thanks for the info  very informative  maybe this post could be > somehow added or linked to from http://www.scipy.org/PyLab > >  Sebastian Haase > Sebastian  I've done as you suggest... I added a link to this post on nabble  do you think there is a better URL for it than http://www.nabble.com/pylabtd24910613.html ?  View this message in context: http://www.nabble.com/pylabtp24910613p24914380.html Sent from the matplotlib  users mailing list archive at Nabble.com. 
From: John [H2O] <washakie@gm...>  20090811 17:28:38

Just an thought regarding the whole PyLab concept... >>> import this The Zen of Python, by Tim Peters Beautiful is better than ugly. Explicit is better than implicit. [snip]... If the implementation is hard to explain, it's a bad idea. If the implementation is easy to explain, it may be a good idea. Namespaces are one honking great idea  let's do more of those! >>> I have to agree... When I started to work with Python, I used "from pylab import *" all too often, eventually I realized I didn't know where things were coming from. Documentation has recently improved greatly, but still, it's nice to know what's driving the functions/classes you are working with. Python is a great tool for <your application here>. The modules matplotlib, numpy, scipy, etc.. will also undoubtedly find their place in more than just a 'pylab' environment. Having taught others a little about python, I can say the use of "from pylab import *" definitely resulted in confusion down the road... For the Original Poster, I would offer this advice. Use Ipython with your own profile. Make sure you maintain namespaces, such that you call: import numpy as np import matplotlib as mpl import scipy as sp etc... See here for creating profiles: http://ipython.scipy.org/doc/manual/html/config/customization.html Using the namespaces results in significantly more clarity at the cost of a few extra keystrokes. (People will have opinions on this) Then, once working in Ipython... I always keep (at least) these pages handy: http://docs.scipy.org/doc/numpy/reference/index.html http://docs.scipy.org/doc/scipy/reference/index.html http://matplotlib.sourceforge.net/api/index.html Good luck!  View this message in context: http://www.nabble.com/pylabtp24910613p24922147.html Sent from the matplotlib  users mailing list archive at Nabble.com. 
From: John Hunter <jdh2358@gm...>  20090811 17:47:01

On Tue, Aug 11, 2009 at 12:28 PM, John [H2O]<washakie@...> wrote: > > Just an thought regarding the whole PyLab concept... If you would like to frame this as a FAQ "Should I import * from pylab?" and post it as a rest svn diff against doc/faq/howto_faq.rst, I would be happy to include this on the website http://matplotlib.sourceforge.net/faq/howto_faq.html#contributinghowto JDH 
From: robert fujii <robertf111@gm...>  20101125 13:24:19
Attachments:
Message as HTML

Hello  I am using python 2.6, numpy1.3.0win32 superpackpython2.6, scipy0.7.1win32superpackpython2.6, sympy0.6.7.win32, matplotlib1.0.0.win32py2.6, and brian1.2.1.win32. I would like to "import pylab" , however I get the following messages shown below. Any assistnce would be highly appreciated. Thank you. Robert ********************************************************************************* import pylab File "F:\Python26\lib\sitepackages\pylab.py", line 1, in <module> from matplotlib.pylab import * File "F:\Python26\lib\sitepackages\matplotlib\pylab.py", line 206, in <module> from matplotlib import mpl # pulls in most modules File "F:\Python26\lib\sitepackages\matplotlib\mpl.py", line 2, in <module> from matplotlib import axis File "F:\Python26\lib\sitepackages\matplotlib\axis.py", line 10, in <module> import matplotlib.font_manager as font_manager File "F:\Python26\lib\sitepackages\matplotlib\font_manager.py", line 1301, in <module> _rebuild() File "F:\Python26\lib\sitepackages\matplotlib\font_manager.py", line 1292, in _rebuild fontManager = FontManager() File "F:\Python26\lib\sitepackages\matplotlib\font_manager.py", line 984, in __init__ self.ttffiles = findSystemFonts(paths) + findSystemFonts() File "F:\Python26\lib\sitepackages\matplotlib\font_manager.py", line 330, in findSystemFonts for f in win32InstalledFonts(fontdir): File "F:\Python26\lib\sitepackages\matplotlib\font_manager.py", line 213, in win32InstalledFonts key, direc, any = _winreg.EnumValue( local, j) MemoryError 
From: Benjamin Root <ben.root@ou...>  20101126 21:40:14

On Thursday, November 25, 2010, robert fujii <robertf111@...> wrote: > Hello  I am using python 2.6, numpy1.3.0win32 > > superpackpython2.6, > scipy0.7.1win32superpackpython2.6, sympy0.6.7.win32, > > matplotlib1.0.0.win32py2.6, > and brian1.2.1.win32. > I would like to "import pylab" , however I get the following messages > shown below. Any assistnce would be highly appreciated. > Thank you. > Robert > ********************************************************************************* > import pylab > File "F:\Python26\lib\sitepackages\pylab.py", line 1, in <module> > from matplotlib.pylab import * > File "F:\Python26\lib\sitepackages\matplotlib\pylab.py", line 206, in > <module> > from matplotlib import mpl # pulls in most modules > File "F:\Python26\lib\sitepackages\matplotlib\mpl.py", line 2, in > <module> > from matplotlib import axis > File "F:\Python26\lib\sitepackages\matplotlib\axis.py", line 10, in > <module> > import matplotlib.font_manager as font_manager > File "F:\Python26\lib\sitepackages\matplotlib\font_manager.py", line > 1301, in <module> > _rebuild() > File "F:\Python26\lib\sitepackages\matplotlib\font_manager.py", line > 1292, in _rebuild > fontManager = FontManager() > File "F:\Python26\lib\sitepackages\matplotlib\font_manager.py", line 984, > in __init__ > self.ttffiles = findSystemFonts(paths) + findSystemFonts() > File "F:\Python26\lib\sitepackages\matplotlib\font_manager.py", line 330, > in findSystemFonts > for f in win32InstalledFonts(fontdir): > File "F:\Python26\lib\sitepackages\matplotlib\font_manager.py", line 213, > in win32InstalledFonts > key, direc, any = _winreg.EnumValue( local, j) > MemoryError > > Did you have a previous version of matplotlib? Did you ever have difficulties with that version on this computer? Ben Root 
From: Darren Dale <dd55@co...>  20060318 20:30:34

On Saturday 18 March 2006 3:16 pm, mame louk wrote: > Hi everyone, > > I tried to install matplotlib for use with NetworkX, but I got this error > > import pylab > > > Traceback (most recent call last): > <...> > File "C:\Program > Files\Python24\Lib\sitepackages\matplotlib\numerix\__init__.py", line 60, > in ? > from Numeric import * > ImportError: No module named Numeric > > > I've seen that Numeric was recently changed to Numpy, I've tried to install > a lot of packages but it still don't work. If you have not installed Numeric, but you have installed numpy, you have two options: 1) Install Numeric 2) Change your numerix rc setting to numpy (see http://matplotlib.sourceforge.net/matplotlibrc for more information) Hope this helps, Darren 