The docstring of sympify() explains this issue in more detail and how to
work around it.
http://docs.sympy.org/latest/modules/core.html#sympy.core.sympify.sympify
Aaron Meurer
On Tue, Jul 21, 2015 at 10:33 PM, Jason Moore moorepa...@gmail.com wrote:
N is a function in SymPy, so is S. So
FYI, this database is building up:
http://www.moorepants.info/misc/sympy-asv/ (I'm running this with the sympy
cache set to 1).
For the integration benchmarks it has every single functioning commit and
maybe half the commits for the other benchmarks.
The repository to submit benchmarks to is
We will work on the documentation. But essentially I'm a running:
SYMPY_CACHE_SIZE=1 asv run ALL --parallel -k -e
You can use -s num to do a sparser mesh and then replace ALL with a git
commit range to narrow down to commits in specific areas. Note that `asv
find` is useful for bisecting to
On Wed, Jul 22, 2015 at 6:26 PM, Jason Moore moorepa...@gmail.com wrote:
We will work on the documentation. But essentially I'm a running:
SYMPY_CACHE_SIZE=1 asv run ALL --parallel -k -e
You can use -s num to do a sparser mesh and then replace ALL with a git
commit range to narrow down
On Wed, Jul 22, 2015 at 4:16 PM, Jason Moore moorepa...@gmail.com wrote:
FYI, this database is building up:
http://www.moorepants.info/misc/sympy-asv/ (I'm running this with the sympy
cache set to 1).
For the integration benchmarks it has every single functioning commit and
maybe half
Yes, but it is likely to fail on many of the commits (probably more than
half depending on the functionality being tested and how backwards
compatible the benchmark is written).
There is also setup overhead time for each commit, so it will take longer
than your calc.
Jason
moorepants.info
+01
