Mailman 3 December 2001 - SciPy-Dev

RE: new compiler
by Rob Dec. 30, 2001

Dec. 30, 2001

Its a very simple mesh generator. It you follow the links on my web page to the EMAP code, there is a new link there that takes you right to the EMAP5 code and docs. I'm trying to come up with a total python port package. So far the mesh generator, sift works with pure MOM or pure FEM, but not with hybrids. I had real trouble converting linked C structures to python classes, since some of the structure members are arrays. There is no simple way of doing this. Paul Dubois is helping me, but i bit the bullet, and removed those array classes with the result of having to add about 20 additional numpy arrays in one of my program versions. Here is an example of what I am trying to do. It doesn't work: from Numeric import * class CellUnit: def __init__(self): self.start=0 self.stop=0 self.end=0 self.arr=zeros((20)) self.cellu=map(lambda dummy: CellUnit, self.arr) def CellU(self): return self.cellu u=CellUnit().CellU() v=CellUnit().CellU() u[0].start=3 u[0].step=5 v[0].start=8 v[0].step=18 print 3,5,8,18 print u[0].start print u[0].step print v[0].start print u[0].step -------------------------------------------------------- Hey Rob, > I see a new compiler in CVS! Rob. Yep, its there. There is quite a bit more functionality such as inlining C/C++ within Python, but I haven't done much testing on Unix at all. Also, the documentation isn't finished. I'm hoping to finish in early January. As far as changes to stuff you do in your FDTD code, the compiled_exec() function has been renamed to blitz(), and you don't have to pass in the locals() anymore if you don't want to. So, scipy.compiled_exec(expr,locals()) can now be called with: scipy.blitz(expr) So far, I think your the only one besides me that uses this thing, so the change shouldn't cause many people problems. > > ps. I'm now working on my FEM-MOM simulator stuff. I'm porting into > Python the mesh generator called "sift". Its a bear. What kind of mesh generator is it? Is there a web link? eric -- The Numeric Python EM Project www.pythonemproject.com

1 0

compiler
by Rob Dec. 28, 2001

Dec. 28, 2001

I see a new compiler in CVS! Rob. ps. I'm now working on my FEM-MOM simulator stuff. I'm porting into Python the mesh generator called "sift". Its a bear. -- The Numeric Python EM Project www.pythonemproject.com

2 1

Re: Scipy-dev digest, Vol 1 #47 - 1 msg
by Travis Oliphant Dec. 25, 2001

Dec. 25, 2001

On Monday 24 December 2001 11:00 am, you wrote: > Send Scipy-dev mailing list submissions to > scipy-dev(a)scipy.net > > To subscribe or unsubscribe via the World Wide Web, visit > http://www.scipy.net/mailman/listinfo/scipy-dev > or, via email, send a message with subject or body 'help' to > scipy-dev-request(a)scipy.net > > You can reach the person managing the list at > scipy-dev-admin(a)scipy.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Scipy-dev digest..." > > > Today's Topics: > > 1. Re: Debian package for SciPy (Joe Reinhardt) > > --__--__-- > > Message: 1 > To: <scipy-dev(a)scipy.org> > Subject: Re: [SciPy-dev] Debian package for SciPy > From: jmr(a)engineering.uiowa.edu (Joe Reinhardt) > Date: Sun, 23 Dec 2001 17:11:30 -0600 > Reply-To: scipy-dev(a)scipy.net > > > I ran the scipy.test() unit tests for my debian package. I got four > errors (see below). Is this normal, or did I do something wrong? > > Thanks - > > Joe All is well. This is due to some rapid upgrading taking place. trapz was moved from basic.py to the integrate package. The name error in roots has been fixed. -Travis

1 0

[OT] MayaVi license issues.
by Prabhu Ramachandran Dec. 25, 2001

Dec. 25, 2001

hi, I'm resuming part of the c.l.py thread on Scientific libraries on Python over here. Sorry about the cross posting and off topic nature of the post. MayaVi (http://mayavi.sf.net) is currently distributed under the GPL. I wrote mayavi for the community and intend that it stays that way. Although the GPL tries to ensure that software remain free, its a little too restrictive at times. SciPy is distributed under a BSD like(?) license. That may be fine for SciPy but I think the BSD license is too non-restrictive. I would very much like that all future enhancements to MayaVi stay free. If some company decides to put 5 folks on MayaVi and make it much nicer, I'd *like* that the new version remain free. However, forcing the person who links to or uses MayaVi as an application or even component to also release their software under the GPL is a little too restrictive. It also prevents the scipy folks from possibly bundling mayavi along with their package even though their code is "free". IIRC, several folks on c.l.py expressed their desire that mayavi (and other things) should be bundled along with scipy. One possiblity suggested by Travis Oliphant was to release mayavi under the LGPL. This makes MayaVi itself distributed under a more restrictive license and yet allows SciPy to bundle it with their code. However, I still dont really understand the LGPL license. What does it allow and what doesn't it allow? Specifically I have a few questions. (1) Can someone subclass a MayaVi class and distribute the new code and yet keep the source closed? Is it worth protecting mayavi from such attempts? (2) What does the LGPL protect actually? What type of changes are allowed and what are not? (3) What are the advantages/disadvantages of LGPL versus the GPL/BSD. Is there anything to worry about? Thanks, prabhu

1 0

RPMs and source distribution
by Travis Oliphant Dec. 23, 2001

Dec. 23, 2001

I've been playing for hours and finally have it so that python setup.py sdist python setup.by bdist_rpm work as expected. I have distributions and RPM's that I need to put somewhere. Thanks, -Travis

6 14

A few gui_thread improvements.
by Prabhu Ramachandran Dec. 22, 2001

Dec. 22, 2001

hi, I just committed some code to gui_thread that adds a __setattr__ method to the proxy classes. Without these changes the following example will not work. import gui_thread from scipy import plt p = plt.plot([1,2,3]) # so far so good. plt.xaxis([1,2]) at this point you should see the xaxes bounds change but nothing will happen. With the newly added __setattr__ this should behave correctly. This should also make the behaviour of proxied objects nicer. I've also added a simple unit test for the new method. You can view the changes here: http://scipy.net/cgi-bin/viewcvs.cgi/scipy/gui_thread/ Cheers, prabhu

1 0

Re: [Numpy-discussion] converting IDL to python
by eric Dec. 20, 2001

Dec. 20, 2001

Rick and Joe, I'm not familiar with these erosion and dialation functions. Are they something that should be in SciPy? We could start an "idl" package that houses functions familiar to this community. Or maybe they should live in another place like "signal" or maybe an image processing package. Thoughts? I've crossed posted this to the scipy-dev(a)scipy.org list as this is probably the best place to continue such a discussion. eric ----- Original Message ----- From: "Joe Reinhardt" <jmr(a)engineering.uiowa.edu> To: <numpy-discussion(a)lists.sourceforge.net> Sent: Wednesday, December 19, 2001 11:12 PM Subject: [Numpy-discussion] converting IDL to python > > Rick White writes: > > The hardest part (as you mention) is that IDL has a really large > > collection of built-in functions which probably will not be readily > > available in Python. Until someone writes things like the morphological > > dilation and erosion operations, it won't be possible to translate IDL > > programs that use them. > > By the way, I do have binary erosion and dilation, along with > connected components analysis, flood fill region grow, and several > other common 2D/3D image processing functions working in NumPy. > > I would be glad to share them. I don't know how similar the > interface is to IDL, since I have never used IDL. > > - Joe Reinhardt > > > > -- > Joseph M. Reinhardt, Ph.D. Department of Biomedical Engineering > joe-reinhardt(a)uiowa.edu University of Iowa, Iowa City, IA 52242 > Telephone: 319-335-5634 FAX: 319-335-5631 > > _______________________________________________ > Numpy-discussion mailing list > Numpy-discussion(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/numpy-discussion >

2 1

Broken link on your website
by adam.brett＠mail.internetseer.com Dec. 12, 2001

Dec. 12, 2001

I noticed that your page: http://www.scipy.org/site_content/FAQ/document_view contains a link to: http://www.scipy.org/site_content/FAQ/tutorials\testing_guidelines. The page at http://www.scipy.org/site_content/FAQ/tutorials\testing_guidelines cannot currently be accessed because of the following error: 404 File not found. No one likes broken links on their website so we thought youd like to be the first to know. WHO ARE WE? Were Internetseer.com, the worlds largest FREE website monitoring service. One recent subscriber wrote the following; You did an awesome job identifying to me that our site went down and tracking it until it came back up again. HOW CAN OUR SERVICE BE FREE? Our service is supported by advertisers and subscribers who purchase additional services, but our basic service is FREE. WHAT DO YOU GET FOR FREE? Well monitor your site once every hour, 24 hours a day, seven days a week for free. You can even have multiple people notified when we detect an error. In addition, youll receive a website performance report every week showing uptime percentages, average connect times, helpful links to others sites and of course promotions from our advertisers. You can cancel your free subscription at any time. This message is not spam because we are not trying to sell you a service. We are simply advising you that a link on your website is currently broken due to the error listed above. If you would like to subscribe to our free website monitoring service, please click on the following link: http://scclick.internetseer.com/sitecheck/clickthrough.jsp?I5s57l5f5h5h5g5o… If you do not wish to receive any further email messages from us, please respond to this message with the word cancel in the subject line. You must leave the entire body of this message in your reply so we can accurately determine whom we originally notified about the broken link. We sincerely hope that youll become one of InternetSeer's 850,000 satisfied subscribers. Adam Brett Web Site Analyst cs-adam.brett(a)mail.internetseer.com InternetSeer.com "Free Website Monitoring" http://www.internetseer.com ##scipy-dev(a)scipy.org##

1 0

ANN: F2PY - Fortran to Python Interface Generator
by Pearu Peterson Dec. 4, 2001

Dec. 4, 2001

F2PY - Fortran to Python Interface Generator I am pleased to announce the third public release of f2py (2nd Edition) (version 2.3.328): http://cens.ioc.ee/projects/f2py2e/ f2py is a command line tool for binding Python and Fortran codes. It scans Fortran 77/90/95 codes and generates a Python C/API module that makes it possible to call Fortran subroutines from Python. No Fortran or C expertise is required for using this tool. Features include: *** All basic Fortran types are supported: integer[ | *1 | *2 | *4 | *8 ], logical[ | *1 | *2 | *4 | *8 ], character[ | *(*) | *1 | *2 | *3 | ... ] real[ | *4 | *8 | *16 ], double precision, complex[ | *8 | *16 | *32 ] *** Multi-dimensional arrays of (almost) all basic types. Dimension specifications: <dim> | <start>:<end> | * | : *** Supported attributes and statements: intent([ in | inout | out | hide | in,out | inout,out ]) dimension(<dimspec>) depend([<names>]) check([<C-booleanexpr>]) note(<LaTeX text>) optional, required, external NEW: intent(c), threadsafe, fortranname *** Calling Fortran 77/90/95 subroutines and functions. Also Fortran 90/95 module subroutines are supported. Internal initialization of optional arguments. *** Accessing COMMON blocks from Python. NEW: Accessing Fortran 90/95 module data. *** Call-back functions: calling Python functions from Fortran with very flexible hooks. *** In Python, arguments of the interfaced functions may be of different type - necessary type conversations are done internally in C level. *** Automatically generates documentation (__doc__,LaTeX) for interfaced functions. *** Automatically generates signature files --- user has full control over the interface constructions. Automatically detects the signatures of call-back functions, solves argument dependencies, etc. NEW: * Automatically generates setup_<modulename>.py for building extension modules using tools from distutils and fortran_support module (from SciPy). *** Automatically generates Makefile for compiling Fortran and C codes and linking them to a shared module. Many compilers are supported: gcc, Compaq Fortran, VAST/f90 Fortran, Absoft F77/F90, MIPSpro 7 Compilers, etc. Platforms: Intel/Alpha Linux, HP-UX, IRIX64. *** Complete User's Guide in various formats (html,ps,pdf,dvi). *** f2py users list is available for support, feedback, etc. NEW: * Installation with distutils. *** And finally, many bugs were fixed. More information about f2py, see http://cens.ioc.ee/projects/f2py2e/ LICENSE: f2py is released under the LGPL. Sincerely, Pearu Peterson <pearu(a)cens.ioc.ee> December 4, 2001 <P><A HREF="http://cens.ioc.ee/projects/f2py2e/">f2py 2.3.328</A> - The Fortran to Python Interface Generator (04-Dec-01)

1 0