Contents |
CorePy 1.0 was released on November 18, 2008. Tarballs are available here:
http://www.osl.iu.edu/~afriedle/corepy/corepy-1.0.tar.gz
http://www.osl.iu.edu/~afriedle/corepy/corepy-1.0.tar.bz2
The latest CorePy source code is available via subversion. Developers attempt to keep the code in a useable/stable state, but that may not always be the case. The main development trunk is here:
https://svn.osl.iu.edu/svn/corepy/trunk
Use subversion to obtain a checkout of the code, like this:
$ svn checkout https://svn.osl.iu.edu/svn/corepy/trunk corepy-trunk
CorePy contains several OS- and CPU-specific SWIG (C language) Python modules that need to be compiled for CorePy to function properly. A setup.py script is provided at the top level of the source tree that will automatically compile the correct modules.
After downloading CorePy, change to the root CorePy directory ($PWD/corepy-trunk if you use a subversion checkout) and execute the setup.py script:
$ cd $COREPY $ python setup.py build_ext -i -f
$COREPY is the path to the root of the CorePy source tree. The -i parameter is a must -- this instructs setup.py to compile the modules 'in-place' in the source tree. Omitting this flag causes the compiled modules to be placed at the top of the source tree; CorePy won't be able to find the modules unless they are compiled 'in-place'.
If setup.py does not recognize the OS and CPU it is running on as a supported architecture, it will abort with the following error message:
Unsupported Python platform! Aborting.
If you see this and believe the OS/CPU you are running on should be supported (see the OS and CPU Architecture Support Matrix), report the 'Python platform' line from the setup.py output along with relevant information about your OS and CPU architecture to the corepy-devel Mailing Lists.
With the modules compiled, CorePy may be used by adding the source tree to your PYTHONPATH:
export PYTHONPATH=$COREPY:$PYTHONPATH
CorePy works on several 64-bit CPU architectures. To use CorePy on these platforms, a 64-bit Python binary is needed. On linux this is not a problem; most distributions provide 64-bit Python binaries by default. OS X, however, only provides 32-bit Python binaries. A separate page, How To Build a 64-bit Python and use Corepy/x86_64 on OSX, gives directions for compiling 64-bit Python binaries.