Sorry for the late reply. I will definitely consider submitting a pull
request to numexpr if it's the direction I decide to go. Right now I'm
still evaluating all of the many options for my project.
I am implementing a machine learning algorithm as part of my thesis work.
I'm in the make it
On Mon, 27 Apr 2015 19:35:51 -0400
Neil Girdhar mistersh...@gmail.com wrote:
Also, FYI: http://numba.pydata.org/numba-doc/0.6/doc/modules/transforms.html
It appears that numba does get the ast similar to pyautodiff and only get
the ast from source code as a fallback?
That documentation is
2015-04-28 4:59 GMT+02:00 Neil Girdhar mistersh...@gmail.com:
I don't think I'm asking for so much. Somewhere inside numexpr it builds
an AST of its own, which it converts into the optimized code. It would be
more useful to me if that AST were in the same format as the one returned
by
I've always wondered why numexpr accepts strings rather than looking a
function's source code, using ast to parse it, and then transforming the
AST. I just looked at another project, pyautodiff, which does that. And I
think numba does that for llvm code generation. Wouldn't it be nicer to
just
On Mon, Apr 27, 2015 at 4:23 PM, Neil Girdhar mistersh...@gmail.com wrote:
I was told that numba did similar ast parsing, but maybe that's not true.
Regarding the ast, I don't know about reliability, but take a look at
get_ast in pyautodiff:
Also, FYI: http://numba.pydata.org/numba-doc/0.6/doc/modules/transforms.html
It appears that numba does get the ast similar to pyautodiff and only get
the ast from source code as a fallback?
On Mon, Apr 27, 2015 at 7:23 PM, Neil Girdhar mistersh...@gmail.com wrote:
I was told that numba did
On Mon, Apr 27, 2015 at 7:42 PM, Nathaniel Smith n...@pobox.com wrote:
On Mon, Apr 27, 2015 at 4:23 PM, Neil Girdhar mistersh...@gmail.com
wrote:
I was told that numba did similar ast parsing, but maybe that's not true.
Regarding the ast, I don't know about reliability, but take a look at
On Mon, Apr 27, 2015 at 7:14 PM, Nathaniel Smith n...@pobox.com wrote:
There's no way to access the ast reliably at runtime in python -- it gets
thrown away during compilation.
The meta package supports bytecode to ast translation. See
On Apr 27, 2015 1:44 PM, Neil Girdhar mistersh...@gmail.com wrote:
I've always wondered why numexpr accepts strings rather than looking a
function's source code, using ast to parse it, and then transforming the
AST. I just looked at another project, pyautodiff, which does that. And I
think
I was told that numba did similar ast parsing, but maybe that's not true.
Regarding the ast, I don't know about reliability, but take a look at
get_ast in pyautodiff:
https://github.com/LowinData/pyautodiff/blob/7973e26f1c233570ed4bb10d08634ec7378e2152/autodiff/context.py
It looks up the __file__
Wow, cool! Are there any users of this package?
On Mon, Apr 27, 2015 at 9:07 PM, Alexander Belopolsky ndar...@mac.com
wrote:
On Mon, Apr 27, 2015 at 7:14 PM, Nathaniel Smith n...@pobox.com wrote:
There's no way to access the ast reliably at runtime in python -- it gets
thrown away during
On Apr 27, 2015 5:30 PM, Neil Girdhar mistersh...@gmail.com wrote:
On Mon, Apr 27, 2015 at 7:42 PM, Nathaniel Smith n...@pobox.com wrote:
On Mon, Apr 27, 2015 at 4:23 PM, Neil Girdhar mistersh...@gmail.com
wrote:
I was told that numba did similar ast parsing, but maybe that's not
true.
I don't think I'm asking for so much. Somewhere inside numexpr it builds
an AST of its own, which it converts into the optimized code. It would be
more useful to me if that AST were in the same format as the one returned
by Python's ast module. This way, I could glue in the bits of numexpr
Announcing Numexpr 2.4.3
=
Numexpr is a fast numerical expression evaluator for NumPy. With it,
expressions that operate on arrays (like 3*a+4*b) are accelerated
and use less memory than doing the same calculation in Python.
It wears multi-threaded capabilities, as well
14 matches
Mail list logo
