Commit c786fee80e5 by Pierre Augier

Bitbucket to Heptapod

parent d3cda49511b
......@@ -57,7 +57,7 @@ See the `ROADMAP.rst file
------------------
- Support source in multiple files (`#14
<https://bitbucket.org/fluiddyn/transonic/issues/14>`_ and #21)
<https://foss.heptapod.net/fluiddyn/transonic/issues/14>`_ and #21)
- Fix issues #8 (Recursion for boosted method), #17 (Bad formating for Pythran
error), #18 (Improve logging jit), #19 (Change default arguments of jit
decorator) and #20 (No Pythran signature generated for boosted functions
......
.. warning ::
Our repository in Bitbucket.org will soon be deleted! Our new home:
https://foss.heptapod.net/fluiddyn/transonic (`more details
<https://fluiddyn.readthedocs.io/en/latest/advice_developers.html>`_).
Make your Python code fly at *transonic* speeds!
================================================
......@@ -11,8 +17,8 @@ Make your Python code fly at *transonic* speeds!
:target: http://transonic.readthedocs.org
:alt: Documentation status
.. |coverage| image:: https://codecov.io/bb/fluiddyn/transonic/branch/default/graph/badge.svg
:target: https://codecov.io/bb/fluiddyn/transonic/branch/default/
.. |coverage| image:: https://codecov.io/gh/fluiddyn/transonic/branch/master/graph/badge.svg
:target: https://codecov.io/gh/fluiddyn/transonic/branch/master/
:alt: Code coverage
.. |travis| image:: https://travis-ci.org/fluiddyn/transonic.svg?branch=master
......@@ -56,13 +62,13 @@ You can try Transonic online by clicking this button: |mybinder|.
suggestions are very welcome.
However, Transonic is now really usable, useful and used "in production" in
`FluidSim <https://bitbucket.org/fluiddyn/fluidsim>`_ and `FluidFFT
<https://bitbucket.org/fluiddyn/fluidfft>`_ (see examples for `blocks
<https://bitbucket.org/fluiddyn/fluidsim/src/default/fluidsim/base/time_stepping/pseudo_spect.py>`_,
`FluidSim <https://foss.heptapod.net/fluiddyn/fluidsim>`_ and `FluidFFT
<https://foss.heptapod.net/fluiddyn/fluidfft>`_ (see examples for `blocks
<https://foss.heptapod.net/fluiddyn/fluidsim/src/default/fluidsim/base/time_stepping/pseudo_spect.py>`_,
`@boost
<https://bitbucket.org/fluiddyn/fluidfft/src/default/fluidfft/fft3d/operators.py>`_
<https://foss.heptapod.net/fluiddyn/fluidfft/src/default/fluidfft/fft3d/operators.py>`_
and `@jit
<https://bitbucket.org/fluiddyn/fluidsim/src/default/fluidsim/solvers/plate2d/output/correlations_freq.py>`_).
<https://foss.heptapod.net/fluiddyn/fluidsim/src/default/fluidsim/solvers/plate2d/output/correlations_freq.py>`_).
The long-term project
......@@ -147,7 +153,7 @@ also (more experimental) backends for Cython and Numba.
.. note ::
Transonic can be used in libraries and applications using MPI (as
`FluidSim <https://bitbucket.org/fluiddyn/fluidsim>`_).
`FluidSim <https://foss.heptapod.net/fluiddyn/fluidsim>`_).
.. _compile-at-import :
......@@ -363,8 +369,8 @@ pythran export`.
.. warning ::
I'm not satisfied by the syntax for blocks so I (PA) proposed an
alternative syntax in `issue #29
<https://bitbucket.org/fluiddyn/fluidpythran/issues/29>`_.
alternative syntax in `issue #6
<https://foss.heptapod.net/fluiddyn/transonic/issues/6>`_.
Python classes: :code:`@boost` and :code:`@jit` for methods
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
......@@ -436,9 +442,9 @@ setup.py like this:
Note that :code:`make_backend_files` does not compile the backend files. The
compilation has to be done after the call of this function (see for example how
it is done in the `example packages
<https://bitbucket.org/fluiddyn/transonic/src/default/doc/examples/packages/>`_
<https://foss.heptapod.net/fluiddyn/transonic/src/default/doc/examples/packages/>`_
or in `fluidsim's setup.py
<https://bitbucket.org/fluiddyn/fluidsim/src/default/setup.py>`_).
<https://foss.heptapod.net/fluiddyn/fluidsim/src/default/setup.py>`_).
License
-------
......
......@@ -82,7 +82,7 @@ We can try that with `pyccel <https://github.com/pyccel/pyccel>`_.
Alternative syntax for blocks
-----------------------------
See `issue #6 <https://bitbucket.org/fluiddyn/transonic/issues/6>`_
See `issue #6 <https://foss.heptapod.net/fluiddyn/transonic/issues/6>`_
Alternative implementations for specified backends
......
......@@ -4,8 +4,8 @@ Define accelerated blocks
.. warning ::
I'm not satisfied by the syntax for Pythran blocks so I (PA) proposed an
alternative syntax in `issue #29
<https://bitbucket.org/fluiddyn/fluidpythran/issues/29>`_.
alternative syntax in `issue #6
<https://foss.heptapod.net/fluiddyn/transonic/issues/6>`_.
Transonic blocks can be used with classes and more generally in functions
......@@ -47,8 +47,8 @@ export`.
.. note ::
The Pythran keyword :code:`or` cannot be used in block annotations (not yet
implemented, see `issue #2
<https://bitbucket.org/fluiddyn/fluidpythran/issues/2/implement-keyword-or-in-block-annotation>`_).
implemented, see `issue #11
<https://foss.heptapod.net/fluiddyn/transonic/issues/11>`_).
Blocks can now also be defined with type hints!
......
# Enhancements related to static code analysis
See also [Issue 18](https://bitbucket.org/fluiddyn/fluidpythran/issues/18/)
- 1st step: issues 6 and 7
- issue 29 is more difficult
- it's also interesting to take into account [issue 32 (Refactoring frontend /
backends as extensions)](https://bitbucket.org/fluiddyn/fluidpythran/issues/32)
"""
See https://bitbucket.org/fluiddyn/fluidpythran/issues/29/
See https://foss.heptapod.net/fluiddyn/transonic/issues/6
"""
from transonic import boost, with_blocks, block
......
"""
See https://bitbucket.org/fluiddyn/fluidpythran/issues/29/
See https://foss.heptapod.net/fluiddyn/transonic/issues/6
"""
from transonic import with_blocks, block
......
......@@ -4,6 +4,7 @@ For developers
.. toctree::
:maxdepth: 1
Advice for FluidDyn developers <http://fluiddyn.readthedocs.io/en/latest/advice_developers.html>
for_dev/todo
for_dev/pypy
for_dev/typing
......@@ -67,7 +67,7 @@ Pieces of code to create realistic input parameters for all boosted functions
## Next tasks
- [x] Fix <https://bitbucket.org/fluiddyn/transonic/issues/29/default-parameters>
- [x] Fix <https://foss.heptapod.net/fluiddyn/transonic/issues/29>
- Good solution to easily benchmark the different backends on these examples
with nice representation of the results
......
......@@ -2,9 +2,9 @@ To do list
==========
- `Alternative syntax for blocks with decorator and context manager
<https://bitbucket.org/fluiddyn/fluidpythran/issues/29>`_
<https://foss.heptapod.net/fluiddyn/transonic/issues/6>`_
- Type hints: `Shape <https://bitbucket.org/fluiddyn/fluidpythran/issues/12>`_
- Type hints: `Shape <https://foss.heptapod.net/fluiddyn/transonic/issues/9>`_
Inline to do items
------------------
......
......@@ -55,11 +55,12 @@ More
.. toctree::
:maxdepth: 1
Transonic forge on Bitbucket <https://bitbucket.org/fluiddyn/transonic>
Transonic forge on Heptapod <https://foss.heptapod.net/fluiddyn/transonic>
Transonic in PyPI <https://pypi.python.org/pypi/transonic/>
changes
roadmap
thanks
Advice for FluidDyn developers <http://fluiddyn.readthedocs.io/en/latest/advice_developers.html>
for_dev
......
"""
See https://bitbucket.org/fluiddyn/fluidpythran/issues/29/
See https://foss.heptapod.net/fluiddyn/transonic/issues/6
"""
from transonic import with_blocks, block
......
"""
See https://bitbucket.org/fluiddyn/fluidpythran/issues/29/
See https://foss.heptapod.net/fluiddyn/transonic/issues/6
"""
from transonic import boost, with_blocks, block
......
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