wassname/catalyst
1
0
Fork 0
mirror of https://github.com/wassname/catalyst.git synced 2026-06-27 19:30:28 +08:00
Code Issues Packages Projects Releases Wiki Activity

Removes documentation references to pavement.

Browse Source 
The references to pavement were causing confusion on what libraries
are needed for installation.
This commit is contained in:
Eddie Hebert
2013-02-01 11:33:32 -05:00
parent 079d7b322e
commit 68327f5a10
2 changed files with 0 additions and 45 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/extensions.rst
-20
View File
@@ -54,26 +54,6 @@ Also make sure to code against Python 2.7 and numpy 1.6.1 header
files. If using Cython have it auto figure out the paths to ensurable
portability.
Building
========
In pavement.py ::
example = Extension(
"zipline/example", ["zipline/example.pyx"],
)
If you need Numpy::
example = Extension(
"zipline/example", ["zipline/example.pyx"],
include_dirs=[np.get_include()],
)
To build in development ::
$ paver build_ext --inplace
Pure C
======
docs/installation.rst
-25
View File
@@ -36,31 +36,6 @@ To run tests::
$ nosetests
To build documentation::
$ paver apidocs html
# outputs to docs/_build/html
For an interactive shell::
$ paver ishell
For coverage information::
$ paver coverage
# outputs to cover/index.html
For line count::
$ paver sloccount
For syntax checking::
$ paver pyflakes
For building distributable egg::
$ paver bdist_egg
Tooling hints
================
:mod:`zipline` relies heavily on scientific python components (numpy, scikit, pandas, matplotlib, ipython, etc). Tooling up can be a pain, and it often involves managing a configuration including your OS, c/c++/fortran compilers, python version, and versions of numerous modules. I've found the following tools absolutely indispensable: