Hi,
As a Theano developer, I like the idea of sharing this part of logic.
If you don't make it into a separate project, can you try to keep the
code in a few files that we could copy? I'm fine with doing sharing
code by copy is dependency is a problem. It was in my wish list to
make Theano reuse
Please observe. The durand-kerner module is my own home-built version
based on some C++ code I saw on the net.
In [1]: from durandkerner_1 import durandkerner
...: from sympy import solve
...: from sympy . abc import x
...: from mpmath import polyroots, nprint
...:
In [2]: solve ( x *
Yes i should be more familiar with Python and Sympy to continue this.
Thanks for your details Aaron, i will check and study the issues page. I
will post here if i face problems.
Thank you..!
On Wednesday, January 9, 2013 8:23:00 AM UTC+5:30, Aaron Meurer wrote:
>
> Each issue falls into one
On Jan 9, 2013, at 10:23 AM, Shriramana Sharma wrote:
> Please observe. The durand-kerner module is my own home-built version
> based on some C++ code I saw on the net.
>
> In [1]: from durandkerner_1 import durandkerner
> ...: from sympy import solve
> ...: from sympy . abc import x
> ...:
Pure python until it's clear that more performance is needed. I'm not
certain how far out a C or Cython core could extend though. It's
advantageous to allow programmers to express logical goals in standard
Python code.
My schedule is now busier than expected. I do not plan to work on this
immed
GItHub has a pretty neat new feature. See
https://github.com/blog/1375-task-lists-in-gfm-issues-pulls-comments
You can now add check lists as comments to pull requests. The syntax is like
- [ ] Item 1
- [ ] Item 2
- [x] Checked item
So this is a great way to summarize the TODOs for pull request
