Mailman 3 November 2002 - SciPy-User

Tkinter/OpenGL version of Chaco/Kiva status follow-up
by David C. Morrill Nov. 21, 2002

Nov. 21, 2002

I just wanted to update everyone on the results of my recent request for help... With the kind help of both Perry Greenfield and especially Greg Couch, I have been able to resolve all of the major performance bottlenecks in the Tkinter/OpenGL Chaco/Kiva code. Yeah! The net result is that the OpenGL version now performs comparably to the wxPython version. While neither version is as fast as we (and users) would like, we think we know how to go after the remaining performance issues. However, we will probably wait until the code has matured a little more before doing any further optimization work. I just wanted to thank Perry and Greg for helping me with some nuances of OpenGL that had eluded and baffled me previously. Thanks a lot guys!!! Dave Morrill

1 0

Re: [SciPy-user] Tkinter/OpenGL version of Chaco/Kiva status and request for help
by Greg Couch Nov. 20, 2002

Nov. 20, 2002

Just thought I'd clear up some of the OpenGL/Togl/Tk issues in your post. Togl's overlay buffers need to be supported by the graphics card. Most PC graphics cards do not support overlay planes. You need a "workstation" card, such as a NVidia Quadro, a 3dLabs Wildcat, or an ATI FireGL card. glReadPixels is slow because graphics cards vendors say there is no incentive to make it fast. Talk to your vendor. OpenGL rubberbanding is best done with glLogicOp(GL_XOR). Tcl/Tk is slow compared to WxWindows. If you want GUI speed, go back to WxPython. OpenGL is same speed whether you are using WxWindows' wxGLCanvas or Tk's Togl. Hope this helps, Greg Couch UCSF Computer Graphics Lab

1 0

[ANN] PyTables 0.2 is out
by Francesc Alted Nov. 20, 2002

Nov. 20, 2002

Hi, PyTables 0.2 is out. I think it would be interesting for people on this list. Also, if this is considered interesting (and think so), I'm ready to work for its inclusion in scipy. What's new ----------- - Numerical Python arrays supported! - Much improved documentation - Programming API almost stable - Improved navegability across the object tree - Added more unit tests (there are almost 50) - Dropped HDF5_HL dependency (a tailored version is included in sources now) - License changed from LGPL to BSD What is ------- The goal of PyTables is to enable the end user to manipulate easily scientific data tables and Numerical Python objects (new in 0.2!) in a persistent hierarchical structure. The foundation of the underlying hierachical data organization is the excellent HDF5 library (http://hdf.ncsa.uiuc.edu/HDF5). Right now, PyTables provides limited support of all the HDF5 functions, but I hope to add the more interesting ones (for PyTables needs) in the near future. Nonetheless, this package is not intended to serve as a complete wrapper for the entire HDF5 API. A table is defined as a collection of records whose values are stored in fixed-length fields. All records have the same structure and all values in each field have the same data type. The terms "fixed-length" and strict "data types" seems to be quite a strange requirement for an interpreted language like Python, but they serve a useful function if the goal is to save very large quantities of data (such as is generated by many scientifc applications, for example) in an efficient manner that reduces demand on CPU time and I/O. In order to emulate records (C structs in HDF5) in Python, PyTables implements a special metaclass that detects errors in field assignments as well as range overflows. PyTables also provides a powerful interface to process table data. Quite a bit effort has been invested to make browsing the hierarchical data structure a pleasant experience. PyTables implements just three (orthogonal) easy-to-use methods for browsing. What is HDF5? ------------- For those people who know nothing about HDF5, it is is a general purpose library and file format for storing scientific data made at NCSA. HDF5 can store two primary objects: datasets and groups. A dataset is essentially a multidimensional array of data elements, and a group is a structure for organizing objects in an HDF5 file. Using these two basic constructs, one can create and store almost any kind of scientific data structure, such as images, arrays of vectors, and structured and unstructured grids. You can also mix and match them in HDF5 files according to your needs. How fast is it? --------------- Despite to be an alpha version and that there is lot of room for improvements (it's still CPU bounded!), PyTables can read and write tables quite fast. But, if you want some (very preliminary) figures (just to know orders of magnitude), in a AMD Athlon@900 it can currently read from 40000 up to 60000 records/s and write from 5000 up to 13000 records/s. Raw data speed in read mode ranges from 1 MB/s up to 2 MB/s, and it drops to the 200 KB/s - 600 KB/s range for writes. Go to http://pytables.sf.net/bench.html for a somewhat more detailed description of this small (and synthetic) benchmark. Anyway, this is only the beginning (premature optimization is the root of all evils, you know ;-). Platforms --------- I'm using Linux as the main development platform, but PyTables should be easy to compile/install on other UNIX machines. Thanks to Scott Prater, this package has passed all the tests on a UltraSparc platform with Solaris 7. It also compiles and passes all the tests on a SGI Origin2000 with MIPS R12000 processors and running IRIX 6.5. If you are using Windows and you get the library to work, please let me know. An example? ----------- At the bottom of this message there is some code (less that 100 lines and only less than half being real code) that shows basic capabilities of PyTables. Web site -------- Go to the PyTables web site for more details: http://pytables.sf.net/ Final note ---------- This is second alpha release, and probably last alpha, so it is still time if you want to suggest some API addition/change or addition/change of any useful missing capability. Let me know of any bugs, suggestions, gripes, kudos, etc. you may have. -- Francesc Alted falted(a)openlc.org *-*-*-**-*-*-**-*-*-**-*-*- Small code example *-*-*-**-*-*-**-*-*-**-*-*-* """Small but almost complete example showing the PyTables mode of use. As a result of execution, a 'tutorial1.h5' file is created. You can look at it with whatever HDF5 generic utility, like h5ls, h5dump or h5view. """ import sys from Numeric import * from tables import * #'-**-**-**-**-**-**- user record definition -**-**-**-**-**-**-**-' # Define a user record to characterize some kind of particles class Particle(IsRecord): name = '16s' # 16-character String idnumber = 'Q' # unsigned long long (i.e. 64-bit integer) TDCcount = 'B' # unsigned byte ADCcount = 'H' # unsigned short integer grid_i = 'i' # integer grid_j = 'i' # integer pressure = 'f' # float (single-precision) energy = 'd' # double (double-precision) print print '-**-**-**-**-**-**- file creation -**-**-**-**-**-**-**-' # The name of our HDF5 filename filename = "tutorial1.h5" print "Creating file:", filename # Open a file in "w"rite mode h5file = openFile(filename, mode = "w", title = "Test file") print print '-**-**-**-**-**-**- group an table creation -**-**-**-**-**-**-**-' # Create a new group under "/" (root) group = h5file.createGroup("/", 'detector', 'Detector information') print "Group '/detector' created" # Create one table on it table = h5file.createTable(group, 'readout', Particle(), "Readout example") print "Table '/detector/readout' created" # Get a shortcut to the record object in table particle = table.record # Fill the table with 10 particles for i in xrange(10): # First, assign the values to the Particle record particle.name = 'Particle: %6d' % (i) particle.TDCcount = i % 256 particle.ADCcount = (i * 256) % (1 << 16) particle.grid_i = i particle.grid_j = 10 - i particle.pressure = float(i*i) particle.energy = float(particle.pressure ** 4) particle.idnumber = i * (2 ** 34) # This exceeds long integer range # Insert a new particle record table.appendAsRecord(particle) # Flush the buffers for table table.flush() print print '-**-**-**-**-**-**- table data reading & selection -**-**-**-**-**-' # Read actual data from table. We are interested in collecting pressure values # on entries where TDCcount field is greater than 3 and pressure less than 50 pressure = [ x.pressure for x in table.readAsRecords() if x.TDCcount > 3 and x.pressure < 50 ] print "Last record read:" print x print "Field pressure elements satisfying the cuts ==>", pressure # Read also the names with the same cuts names = [ x.name for x in table.readAsRecords() if x.TDCcount > 3 and x.pressure < 50 ] print print '-**-**-**-**-**-**- array object creation -**-**-**-**-**-**-**-' print "Creating a new group called '/columns' to hold new arrays" gcolumns = h5file.createGroup(h5file.root, "columns", "Pressure and Name") print "Creating a Numeric array called 'pressure' under '/columns' group" h5file.createArray(gcolumns, 'pressure', array(pressure), "Pressure column selection") print "Creating another Numeric array called 'name' under '/columns' group" h5file.createArray('/columns', 'name', array(names), "Name column selection") # Close the file h5file.close() print "File '"+filename+"' created" -- Francesc Alted PGP KeyID: 0x61C8C11F Scientific aplications developer Public PGP key available: http://www.openlc.org/falted_at_openlc.asc Key fingerprint = 1518 38FE 3A3D 8BE8 24A0 3E5B 1328 32CC 61C8 C11F

2 2

Problem with plt on debian sid box
by Douglas Eck Nov. 20, 2002

Nov. 20, 2002

I am running a debian sid box. I downloaded from CVS today and did a build and generated no errors, but plt doesn't work. >>> from scipy import plt >>> plt.plot([1,2,3,4,5]) <C wxFrame instance at _8988178_wxFrame_p> It imports without error and even gives me a wxFrame object. But nothing ever appears on the screen. It doesn't seem to be a window manager permissions problem. I can quit python and run a windowed program. Maybe a problem linking against wxpython? Any hints on how to troubleshoot this? A more broad question. Is anyone using plt, or doing upkeep on it? If not, I'll just bag it and use wxPlotCanvas directly. Regards, Doug Eck

2 2

Tkinter/OpenGL version of Chaco/Kiva status and request for help
by David C. Morrill Nov. 19, 2002

Nov. 19, 2002

First the good news: The Tkinter/OpenGL based version of Chaco/Kiva is very near completion. The major remaining work items are: 1) Convert Eric's wxPython based FreeType Kiva code to work with the OpenGL based version of Kiva. 2) Improve overall performance dramatically. Some people voiced a concern that the wxPython based version of Chaco seems a little slow. Well, compared to the current OpenGL version, it hums like a well oiled machine :-( Hence the request for help... Most of the performance issues with the OpenGL version of Chaco have to do with interactive operations, like drawing the cursor crosshair lines or the graph and axis selection regions. In the wxPython version, we maintain an off-screen bitmap of the PlotWindow contents and either xor the cursor or selection regions into the screen or blit the off-screen bitmap onto the screen (e.g. to refresh the window when a region of the PlotWindow is exposed). Being fairly inexperienced with OpenGL I have not been able to find a way to do something equivalent in OpenGL: - The OpenGL 'overlay' buffers do not appear to be supported by the version of 'togl' supplied with the current PyOpenGL package. - Trying to do a glReadPixels(...) call to read the contents of the OpenGL buffer seems to take about a second on a >1 GHz processor (hardly useful for interactive work). So the question is: Does anyone know how to efficiently 'rubberband' things in OpenGL? If the asnwer is to use the overlay buffer, does anyone know how to get it to work with a Tkinter based OpenGL widget? Thanks in advance for any help... Dave Morrill

1 0

TypeError: compile() argument 1 must be string without null bytes, not string
by Nils Wagner Nov. 19, 2002

Nov. 19, 2002

Hi, I have some trouble with installing scipy on SuSE 8.1. Traceback (most recent call last): File "setup.py", line 127, in ? install_package() File "setup.py", line 117, in install_package url = "http://www.scipy.org", File "scipy_distutils/core.py", line 42, in setup return old_setup(**new_attr) File "/usr/lib/python2.1/distutils/core.py", line 138, in setup dist.run_commands() File "/usr/lib/python2.1/distutils/dist.py", line 899, in run_commands self.run_command(cmd) File "/usr/lib/python2.1/distutils/dist.py", line 919, in run_command cmd_obj.run() File "/usr/lib/python2.1/distutils/command/install.py", line 484, in run self.run_command(cmd_name) File "/usr/lib/python2.1/distutils/cmd.py", line 328, in run_command self.distribution.run_command(command) File "/usr/lib/python2.1/distutils/dist.py", line 919, in run_command cmd_obj.run() File "/usr/lib/python2.1/distutils/command/install_lib.py", line 93, in run self.byte_compile(outfiles) File "/usr/lib/python2.1/distutils/command/install_lib.py", line 130, in byte_ compile verbose=self.verbose, dry_run=self.dry_run) File "/var/tmp/python21-2.1.3-build/usr/lib/python2.1/distutils/util.py", line 439, in byte_compile File "/usr/lib/python2.1/py_compile.py", line 62, in compile codeobject = __builtin__.compile(codestring, dfile or file, 'exec') TypeError: compile() argument 1 must be string without null bytes, not string Any idea ? Nils

1 0

RE: [SciPy-user] Weave on W2K problems -- more clues
by Christopher Fonnesbeck Nov. 18, 2002

Nov. 18, 2002

Thanks this is helping. I have loaded MinGW, and it now seems to find g++, but the problem it has is with dllwrap. Even though dllwrap is in the MinGW bin directory, I get the following: ====================================================================== ERROR: result[1:-1,1:-1] = (b[1:-1,1:-1] + b[2:,1:-1] + b[:-2,1:-1] ---------------------------------------------------------------------- Traceback (most recent call last): File "T:\Python22\Lib\site-packages\weave\tests\test_blitz_tools.py", line 150, in check_5point_avg_2d self.generic_2d(expr) File "T:\Python22\Lib\site-packages\weave\tests\test_blitz_tools.py", line 124, in generic_2d mod_location) File "T:\Python22\Lib\site-packages\weave\tests\test_blitz_tools.py", line 80, in generic_test blitz_tools.blitz(expr,arg_dict,{},verbose=0) #, File "T:\Python22\Lib\site-packages\weave\blitz_tools.py", line 72, in blitz type_converters = converters.blitz, File "T:\Python22\Lib\site-packages\weave\inline_tools.py", line 439, in compile_function verbose=verbose, **kw) File "T:\Python22\Lib\site-packages\weave\ext_tools.py", line 332, in compile verbose = verbose, **kw) File "T:\Python22\Lib\site-packages\weave\build_tools.py", line 221, in build_extension setup(name = module_name, ext_modules = [ext],verbose=verb) File "T:\Python22\lib\distutils\core.py", line 157, in setup raise SystemExit, "error: " + str(msg) CompileError: error: command 'dllwrap' failed with exit status 1 and os.system('dllwrap') confirms that dllwrap is there and functioning. Thanks. ChrisF ----- Original Message ----- From: "eric jones" <eric(a)enthought.com> Date: Mon, 18 Nov 2002 13:57:37 -0600 To: <scipy-user(a)scipy.net> Subject: RE: [SciPy-user] Weave on W2K problems -- more clues > > > > I also get the following in the test output: > > > > WARNING: failed to build import library for gcc. Linking will fail. > > Looking at build_tools.py, I think this is associated with the use of > cygwin instead of mingw. Mingw has a tool called "dlltool" that is used > in converting the python22.lib to a libpython22.a file. It doesn't look > like cygwin has the same tools. > > Can you use mingw instead of cygwin and see if it solves your problems? > You'll need to use the version based on 2.95.3 (mingw1.1 I believe), as > weave doesn't work with the latest version. > > > E > > warning: specified build_dir '_bad_path_' does not exist or is not > > writable. Trying default locations > > This warning is supposed to happen -- it is part of a unit test. > > > > > Not sure if that helps with respect to the g++ problems > > Hopefully moving to mingw fixes your problems. > > Good luck, > Eric > > > > > > > > > ----- Original Message ----- > > From: "eric jones" <eric(a)enthought.com> > > Date: Fri, 15 Nov 2002 16:31:29 -0600 > > To: <scipy-user(a)scipy.net> > > Subject: RE: [SciPy-user] Weave on W2K problems > > > > > > > Hey Chris, > > > > > > > I am trying to set up weave/scipy on a very fast machine, > > > unfortunately > > > > running W2K, rather than *NIX, and am having a couple of problems > with > > > > weave. First, although the scipy binary puts its weave components > in > > > > $PYTHONHOME\Lib\site-packages as I would expect, the full weave > binary > > > > puts its stuff in $PYTHONHOME. > > > > > > This may be because the standalone version was built with 2.1.3 and > I > > > believe it defaulted to putting things in $PYTHONHOME on windows > > > distributions. This was corrected in Python2.2 (which is used to > build > > > SciPy). > > > > > > > Second, though I have the cygwin gcc > > > > compiler (with g++ also) installed and listed first on my user > path, I > > > get > > > > the following error claiming g++ cannot be found. > > > > > > > > > ====================================================================== > > > > ERROR: result[1:-1,1:-1] = (b[1:-1,1:-1] + b[2:,1:-1] + > b[:-2,1:-1] > > > > > ---------------------------------------------------------------------- > > > > Traceback (most recent call last): > > > > File > > > "T:\Python22\Lib\site-packages\weave\tests\test_blitz_tools.py", > > > > line 150, in check_5point_avg_2d > > > > self.generic_2d(expr) > > > > File > > > "T:\Python22\Lib\site-packages\weave\tests\test_blitz_tools.py", > > > > line 124, in generic_2d > > > > mod_location) > > > > File > > > "T:\Python22\Lib\site-packages\weave\tests\test_blitz_tools.py", > > > > line 80, in generic_test > > > > blitz_tools.blitz(expr,arg_dict,{},verbose=0) #, > > > > File "T:\Python22\Lib\site-packages\weave\blitz_tools.py", line > 72, > > > in > > > > blitz > > > > type_converters = converters.blitz, > > > > File "T:\Python22\Lib\site-packages\weave\inline_tools.py", line > > > 439, in > > > > compile_function > > > > verbose=verbose, **kw) > > > > File "T:\Python22\Lib\site-packages\weave\ext_tools.py", line > 332, > > > in > > > > compile > > > > verbose = verbose, **kw) > > > > File "T:\Python22\Lib\site-packages\weave\build_tools.py", line > 221, > > > in > > > > build_extension > > > > setup(name = module_name, ext_modules = [ext],verbose=verb) > > > > File "T:\Python22\lib\distutils\core.py", line 157, in setup > > > > raise SystemExit, "error: " + str(msg) > > > > CompileError: error: command 'g++' failed: No such file or > directory > > > > > > > > > ---------------------------------------------------------------------- > > > > Ran 184 tests in 250.797s > > > > > > > > FAILED (errors=1) > > > > <unittest.TextTestRunner instance at 0x00D90AD0> > > > > > > > > I need this stuff to work in order to make my dynamic > optimizations > > > run > > > > faster, so any assistance is most welcome. > > > > > > It looks like all the weave tests passed accept for the one blitz > test. > > > If your not planning on using blitz, then I think you may be OK. > > > > > > I just tried running weave with my cygwin installation with: > > > > > > > ---------------------------------------------------------------------- > > > Ran 184 tests in 74.055s > > > > > > FAILED (failures=1, errors=22) > > > > > > The blitz() test failed but not like yours. I actually got > incorrect > > > results. The 22 errors were all of the MSC++ tests failing because > they > > > couldn't find the C++ file they were asked to compile: > > > > > > sc_abccabed66f253b594f63a36ae4b0cdb0.cpp > > > fatal error C1083: Cannot open source file: > > > '/cygdrive/c/DOCUME~1/eric/LOCALS~1/ > > > Temp/(a)1336.2/sc_abccabed66f253b594f63a36ae4b0cdb0.cpp': No such file > or > > > directory > > > E > > > > > > I'll have to explore these. > > > > > > As for the error of not finding g++, I don't know why it is > happening. > > > If it is in the path and you can execute the following: > > > > > > eric@ERICDESKTOP ~/wrk > > > $ python > > > Python 2.2.1 (#1, Jun 25 2002, 10:55:46) > > > [GCC 2.95.3-5 (cygwin special)] on cygwin > > > Type "help", "copyright", "credits" or "license" for more > information. > > > >>> import os > > > >>> os.system('g++') > > > g++: No input files > > > 256 > > > > > > weave shouldn't complain -- especially since it appears to be > finding it > > > in many of the other 184 tests. > > > > > > Hope something here helps, > > > eric > > > > > > > > > > > > > > > > > > > > Thanks, > > > > Chris Fonnesbeck > > > > -- > > > > ______________________________________________ > > > > http://www.linuxmail.org/ > > > > Now with POP3/IMAP access for only US$19.95/yr > > > > > > > > Powered by Outblaze > > > > _______________________________________________ > > > > SciPy-user mailing list > > > > SciPy-user(a)scipy.net > > > > http://www.scipy.net/mailman/listinfo/scipy-user > > > > > > > > > > > > _______________________________________________ > > > SciPy-user mailing list > > > SciPy-user(a)scipy.net > > > http://www.scipy.net/mailman/listinfo/scipy-user > > > > > > > -- > > ______________________________________________ > > http://www.linuxmail.org/ > > Now with POP3/IMAP access for only US$19.95/yr > > > > Powered by Outblaze > > _______________________________________________ > > SciPy-user mailing list > > SciPy-user(a)scipy.net > > http://www.scipy.net/mailman/listinfo/scipy-user > > > > _______________________________________________ > SciPy-user mailing list > SciPy-user(a)scipy.net > http://www.scipy.net/mailman/listinfo/scipy-user > -- ______________________________________________ http://www.linuxmail.org/ Now with POP3/IMAP access for only US$19.95/yr Powered by Outblaze

1 0

RE: [SciPy-user] Weave on W2K problems -- more clues
by Christopher Fonnesbeck Nov. 18, 2002

Nov. 18, 2002

I also get the following in the test output: WARNING: failed to build import library for gcc. Linking will fail. Ewarning: specified build_dir '_bad_path_' does not exist or is not writable. Trying default locations Not sure if that helps with respect to the g++ problems ----- Original Message ----- From: "eric jones" <eric(a)enthought.com> Date: Fri, 15 Nov 2002 16:31:29 -0600 To: <scipy-user(a)scipy.net> Subject: RE: [SciPy-user] Weave on W2K problems > Hey Chris, > > > I am trying to set up weave/scipy on a very fast machine, > unfortunately > > running W2K, rather than *NIX, and am having a couple of problems with > > weave. First, although the scipy binary puts its weave components in > > $PYTHONHOME\Lib\site-packages as I would expect, the full weave binary > > puts its stuff in $PYTHONHOME. > > This may be because the standalone version was built with 2.1.3 and I > believe it defaulted to putting things in $PYTHONHOME on windows > distributions. This was corrected in Python2.2 (which is used to build > SciPy). > > > Second, though I have the cygwin gcc > > compiler (with g++ also) installed and listed first on my user path, I > get > > the following error claiming g++ cannot be found. > > > > ====================================================================== > > ERROR: result[1:-1,1:-1] = (b[1:-1,1:-1] + b[2:,1:-1] + b[:-2,1:-1] > > ---------------------------------------------------------------------- > > Traceback (most recent call last): > > File > "T:\Python22\Lib\site-packages\weave\tests\test_blitz_tools.py", > > line 150, in check_5point_avg_2d > > self.generic_2d(expr) > > File > "T:\Python22\Lib\site-packages\weave\tests\test_blitz_tools.py", > > line 124, in generic_2d > > mod_location) > > File > "T:\Python22\Lib\site-packages\weave\tests\test_blitz_tools.py", > > line 80, in generic_test > > blitz_tools.blitz(expr,arg_dict,{},verbose=0) #, > > File "T:\Python22\Lib\site-packages\weave\blitz_tools.py", line 72, > in > > blitz > > type_converters = converters.blitz, > > File "T:\Python22\Lib\site-packages\weave\inline_tools.py", line > 439, in > > compile_function > > verbose=verbose, **kw) > > File "T:\Python22\Lib\site-packages\weave\ext_tools.py", line 332, > in > > compile > > verbose = verbose, **kw) > > File "T:\Python22\Lib\site-packages\weave\build_tools.py", line 221, > in > > build_extension > > setup(name = module_name, ext_modules = [ext],verbose=verb) > > File "T:\Python22\lib\distutils\core.py", line 157, in setup > > raise SystemExit, "error: " + str(msg) > > CompileError: error: command 'g++' failed: No such file or directory > > > > ---------------------------------------------------------------------- > > Ran 184 tests in 250.797s > > > > FAILED (errors=1) > > <unittest.TextTestRunner instance at 0x00D90AD0> > > > > I need this stuff to work in order to make my dynamic optimizations > run > > faster, so any assistance is most welcome. > > It looks like all the weave tests passed accept for the one blitz test. > If your not planning on using blitz, then I think you may be OK. > > I just tried running weave with my cygwin installation with: > > ---------------------------------------------------------------------- > Ran 184 tests in 74.055s > > FAILED (failures=1, errors=22) > > The blitz() test failed but not like yours. I actually got incorrect > results. The 22 errors were all of the MSC++ tests failing because they > couldn't find the C++ file they were asked to compile: > > sc_abccabed66f253b594f63a36ae4b0cdb0.cpp > fatal error C1083: Cannot open source file: > '/cygdrive/c/DOCUME~1/eric/LOCALS~1/ > Temp/(a)1336.2/sc_abccabed66f253b594f63a36ae4b0cdb0.cpp': No such file or > directory > E > > I'll have to explore these. > > As for the error of not finding g++, I don't know why it is happening. > If it is in the path and you can execute the following: > > eric@ERICDESKTOP ~/wrk > $ python > Python 2.2.1 (#1, Jun 25 2002, 10:55:46) > [GCC 2.95.3-5 (cygwin special)] on cygwin > Type "help", "copyright", "credits" or "license" for more information. > >>> import os > >>> os.system('g++') > g++: No input files > 256 > > weave shouldn't complain -- especially since it appears to be finding it > in many of the other 184 tests. > > Hope something here helps, > eric > > > > > > > > Thanks, > > Chris Fonnesbeck > > -- > > ______________________________________________ > > http://www.linuxmail.org/ > > Now with POP3/IMAP access for only US$19.95/yr > > > > Powered by Outblaze > > _______________________________________________ > > SciPy-user mailing list > > SciPy-user(a)scipy.net > > http://www.scipy.net/mailman/listinfo/scipy-user > > > > _______________________________________________ > SciPy-user mailing list > SciPy-user(a)scipy.net > http://www.scipy.net/mailman/listinfo/scipy-user > -- ______________________________________________ http://www.linuxmail.org/ Now with POP3/IMAP access for only US$19.95/yr Powered by Outblaze

3 2

RPMs for Mandrake 9.0
by RA Nov. 18, 2002

Nov. 18, 2002

If you want to test: http://www.scipy.org/Members/RalfA/packages/Mandrake-9.0-RPM/python-f2py-2.… http://www.scipy.org/Members/RalfA/packages/Mandrake-9.0-RPM/python-scipy-c… http://www.scipy.org/Members/RalfA/packages/Mandrake-9.0-RPM/python-scipy-0… To build a custom atlas (semiautomaticaly): http://www.scipy.org/Members/RalfA/packages/Mandrake-9.0-RPM/atlas.spec http://www.scipy.org/Members/RalfA/packages/Mandrake-9.0-RPM/atlas3.3.15-co… You need the source package from math-atlas.sourceforge.net

1 0

Debian package(s)? -- and RPM
by RA Nov. 18, 2002

Nov. 18, 2002

Hi! I've just read the ml archive, because I want to contribute some packages (scipy and f2py), both RPM (Mdk 9.0) and DEB (woody). I've got some experience with RPM and I'll also submit these packages to cooker (just updated yesterday, with custom atlas ). For debian, well, the debs evolved from joe r. packages. They were updated a few weeks ago (build with atlas-base). I hope, that they can be at least a starting point. So, how could I upload the stuff? Ralf.

4 10