Commit e34e9886 authored by Pierre Augier's avatar Pierre Augier
Browse files

Improve doc

parent 01fa9ecc68c2
......@@ -6,6 +6,11 @@ Future
- Alternative syntax for blocks (see `issue #29
<https://bitbucket.org/fluiddyn/fluidpythran/issues/29>`_)
Next release
------------
- Environment variable :code:`FLUIDPYTHRAN_NO_REPLACE`
0.1.7 (2018-12-18)
------------------
......
......@@ -27,7 +27,7 @@ FluidPythran: easily speedup your Python code with Pythran
<https://bitbucket.org/fluiddyn/fluidfft>`_ (see examples for `blocks
<https://bitbucket.org/fluiddyn/fluidsim/src/default/fluidsim/base/time_stepping/pseudo_spect.py>`_,
`@boost
<https://bitbucket.org/fluiddyn/fluidsim/src/default/fluidsim/operators/operators3d.py>`_
<https://bitbucket.org/fluiddyn/fluidfft/src/default/fluidfft/fft3d/operators.py>`_
and `@cachedjit
<https://bitbucket.org/fluiddyn/fluidsim/src/default/fluidsim/solvers/plate2d/output/correlations_freq.py>`_).
......
Information for developers
==========================
For developers
==============
.. toctree::
:maxdepth: 1
......
......@@ -5,14 +5,15 @@ To do list
<https://bitbucket.org/fluiddyn/fluidpythran/issues/18/>`_ for a nicer user
API.
- pythran_def for methods (see `issue 3
<https://bitbucket.org/fluiddyn/fluidpythran/issues/3>`_ and `issue 8
<https://bitbucket.org/fluiddyn/fluidpythran/issues/8>`_)
- `Alternative syntax for blocks with decorator and context manager
<https://bitbucket.org/fluiddyn/fluidpythran/issues/29>`_
- Type hints:
- Type hints: `Shape <https://bitbucket.org/fluiddyn/fluidpythran/issues/12>`_
* Shape
* Union
.. toctree::
:maxdepth: 2
universal_booster
Inline to do items
------------------
......
Big long-term idea: a "universal" Numpy booster
===============================================
It would be very useful to have a pure-Python package similar to FluidPythran
but able to accelerate Numpy code with different tools (Pythran, Cython, Numba,
Numba with CuPy, PyTorch)...
The idea was first proposed in `issue #21
<https://bitbucket.org/fluiddyn/fluidpythran/issues/21>`_.
First step: refactor the code to split the analysis (FluidPythran "frontend")
and the production and compilations of Pythran files (a Pythran backend). This
backend should be written as an extension (`issue #32
<https://bitbucket.org/fluiddyn/fluidpythran/issues/32>`_).
Second step: write a Numba backend extension (it should not be too difficult
because we don't have to handle the compilation).
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment