Pypar 2.0alpha update - Simple and efficient MPI binding for Python.
pypar 2.0alpha released on sourceforge. Pypar is a simple and efficient MPI binding for Python Copyright (C) 2001-2007 Ole M. Nielsen --- This is to announce an upgrade of pypar, ver 2.0 alpha - a simple and efficient Python binding to MPI for parallel programming using Python. Version 1.0 was announced on this mailing list on 7th of February 2002 http://mail.python.org/pipermail/python-announce-list/2002-February/001228.html. Pypar has been used in many projects over the years but it became clear that relying on the Numeric was becoming a liability and many developers requested an upgrade to numpy. The update to version 2.0alpha signifies 1: Porting pypar to numpy instead of the discontinued Numeric module 2: Moving pypar to sourceforge: http://sourceforge.net/projects/pypar/ 3: Numerous improvements and optimisations added over the past years Version 2.0alpha has been tested on a few platforms, but I haven't been able to verify that it installs everywhere. The purpose of this post is to encourage existing and new users of pypar to try the new release and to get back to me with questions, feedback and patches that will allow pypar to run on as many platforms as possible. I am looking forward to hear from you Ole M. Nielsen Canberra, Australia [EMAIL PROTECTED] Background: --- The use of multi processor computers is becoming increasingly common and they appear in many forms: Desktop computers with more than one processor sharing memory, clusters of PC's connected with fast networks known as Beowulf clusters, and high-end super computers all make use of parallelism. Even playstations have been connected to form computational networks (http://arrakis.ncsa.uiuc.edu/ps2/cluster.php). To efficiently use these machines in a portable way one must be able to control communication among programs running in parallel. One such standard is the Message Passing Interface (MPI) for inter-processor communication. Python and MPI: --- There are a number of other Python bindings to MPI that are more comprehensive than pypar (PyMPI, Scientific Python). However, pypar stands out by not requiring the Python interpreter to be modified, by being very easy to install and by by shielding the user from many details involving data types and MPI parameters without sacrificing the full bandwidth provided by the underlying MPI implementation. Download: - Pypar can be downloaded from http://sourceforge.net/projects/pypar Credentials: Pypar was developed by Ole Nielsen at the Australian National University in 2001 for use in the APAC Data Mining Expertise Program and has been published under the GNU Public License (http://www.gnu.org/licenses/gpl.txt) Contact: [EMAIL PROTECTED] [EMAIL PROTECTED] PA HREF=http://sourceforge.net/projects/pypar; http://datamining.anu.edu.au/pyparPypar 2.0alpha/A - A simple and efficient MPI binding for Python. (07-July-07) -- http://mail.python.org/mailman/listinfo/python-announce-list Support the Python Software Foundation: http://www.python.org/psf/donations.html
bbfreeze 0.95.0
Hi all, I've just uploaded bbfreeze 0.95.0 to python's cheeseshop. bbfreeze creates standalone executables from python scripts. It's similar in functionality to py2exe or cx_Freeze. *NEW* support for egg files: bbfreeze scans zipped egg files and now includes whole egg files/directories in the distribution. Programs using setuptools' pkg_resources module will now work. It offers the following features: easy installation bbfreeze can be installed with setuptools' easy_install command. zip/egg file import tracking bbfreeze tracks imports from zip files. multiple script freezing bbfreeze can freeze multiple scripts at once. python interpreter included bbfreeze will create an extra executable named 'py', which might be used like the python executable itself. bbfreeze works on windows and UNIX-like operating systems. It currently does not work on OS X. bbfreeze has been tested with python 2.4 and 2.5. bbfreeze will not work with python versions prior to 2.3 as it uses the zipimport feature introduced with python 2.3. Links cheese shop entry: http://cheeseshop.python.org/pypi/ bbfreeze/http://cheeseshop.python.org/pypi/bbfreeze/ homepage: http://systemexit.de/bbfreeze/ mercurial repository: http://systemexit.de/repo/bbfreeze Regards, - Ralf -- http://mail.python.org/mailman/listinfo/python-announce-list Support the Python Software Foundation: http://www.python.org/psf/donations.html
ANN: Ophelia 0.3 - Create web sites from TAL templates
Ophelia 0.3 has just been released. Ophelia creates XHTML pages from templates written in TAL, the Zope Tag Attribute Language. It is designed to reduce code repetition to zero. The package contains both a WSGI application running Ophelia as well as a request handler for mod_python, the Python module for the Apache2 web server. Additionally, a script is included that renders a page and dumps it to stdout, and another one that runs a wsgiref based HTTP server hosting Ophelia's WSGI application. Ophelia is released under the Zope Public License, version 2.1. To use Ophelia 0.3, you need Python 2.4. The mod_python request handler requires mod_python 3.3 or better. The package is available from the Python package index as a source distribution and a Python 2.4 egg: http://cheeseshop.python.org/pypi/ophelia The source code contains a zc.buildout configuration for an environment including Apache and mod_python. You can access the source code repository at https://svn.thomas-lotze.de/repos/public/Ophelia/, browse it using ViewCVS at http://svn.thomas-lotze.de/svn-public/Ophelia/, or visit Ophelia's web page, containing a commented live usage example, at http://www.thomas-lotze.de/en/software/ophelia/. From the documentation: What kind of sites is Ophelia good for? === Static content -- Consider Ophelia as SSI on drugs. It's not fundamentally different, just a lot friendlier and more capable. Use Ophelia for sites where you basically write your HTML yourself, except that you need write the recurring stuff only once. Reducing repetition to zero comes at a price: your site must follow a pattern for Ophelia to combine your templates the right way. Consider your site's layout to be hierarchical: there's a common look to all your pages, sections have certain characteristics, and each page has unique content. It's crucial to Ophelia that this hierarchy reflect in the file system organization of your documents; how templates combine is deduced from their places in the hierarchy of directories. Dynamic content --- Ophelia makes the Python language available for including dynamic content. Each template file may include a Python script. Python scripts and templates contributing to a page share a common set of variables to modify and use. Ophelia's content model is very simple and works best if each content object you publish is its own view: the page it is represented on. If you get content from external resources anyway (e.g. a database or a version control repository), it's still OK to use Ophelia even with multiple views per content object as long as an object's views don't depend on the object's type or even the object itself. Trying to use Ophelia on a more complex site will lead to an ugly entanglement of logic and presentation. Don't use Ophelia for sites that are actually web interfaces to applications, content management systems and the like. -- Viele Grüße, Thomas -- http://mail.python.org/mailman/listinfo/python-announce-list Support the Python Software Foundation: http://www.python.org/psf/donations.html
