congrats to all, again :)
--
You received this message because you are subscribed to the Google Groups
"sympy" group.
To post to this group, send email to sympy@googlegroups.com.
To unsubscribe from this group, send email to
sympy+unsubscr...@googlegroups.com.
For more options, visit this group
Hi,
What is the current status of the initiatives like cythonize sympy.core or
write it in some other fast statically typed language?, I have seen various
info internet, however it is unclear what is the present status.
best.
Pallab
--
You received this message because you are subscribed to t
atoms searches for instances of a class. So when given an instance,
it apparently just uses the class of that instance:
In [23]: sin(y).atoms(sin(x))
Out[23]: set([sin(y)])
In [24]: (2**x).atoms(x**2)
Out[24]:
⎛⎡ x⎤⎞
set⎝⎣2 ⎦⎠
Since it's unclear what it should do with an instance, this could
It's present status is mostly stalled. You can see some stuff at
https://github.com/certik/sympyx.
The problem is that the core is currently (and has been for some time)
a mess, mostly due to the old assumptions, making it hard to do things
with.
Ondrej might be able to comment more on any progr
The problem with this method is that looking at all combinations
becomes *very* inefficient for Muls with many terms. For example:
In [41]: %timeit integrate2(diff(x*sqrt(sin(x))), x)
1
2
1
2
1
2
1
2
1 loops, best of 3: 5.2 s per loop
At the end of the day, you'll get even worse performance than
With this seed, the process hangs. While doing that, it uses up a lot
of memory. It's hard for me to reproduce exactly, because Mac OS X
apparently will gladly give Python as much memory as it wants,
including virtual memory, until my hard disk fills up.
We really need to figure out why this is
Ah, well (*cough*), it's not really. There is some boilerplate that
needs to be done (i.e., risch_integrate() needs to be properly hooked
into integrate()), and the merge with master will be nasty, but
really, it's not that hard. It's more along the lines of me not
getting around to it, and putti
During a rebase, the computer just shut down (like the battery failed even
though there was about 50% power left). Now after restarting I cd to sympy
and cannot do anything. I get this message whenever I issue any git command:
chriss@CHRIS-LT ~/sympy ((...)|REBASE)
$ git log
fatal: Not a git rep
Restore from backup, if you have one.
Otherwise, you'll have to figure out what part of the .git directory
got messed up.
If you can't figure it out, and you've pushed everything to GitHub,
you can get a fresh start from there.
Aaron Meurer
On Sat, Jul 14, 2012 at 10:13 PM, smichr wrote:
> Dur
https://git.wiki.kernel.org/index.php/GitFaq#How_to_fix_a_broken_repository.3F
may also be useful.
Aaron Meurer
On Sat, Jul 14, 2012 at 10:35 PM, Aaron Meurer wrote:
> Restore from backup, if you have one.
>
> Otherwise, you'll have to figure out what part of the .git directory
> got messed up.
On Sun, Jul 15, 2012 at 10:21 AM, Aaron Meurer wrote:
> https://git.wiki.kernel.org/index.php/GitFaq#How_to_fix_a_broken_repository.3F
> may also be useful.
mv sympy bad
mkdir sympy
git clone git://github.com/sympy/sympy.git
cd sympy
cp .git/config config_bak
cp ../bad/.git/config .git/config
T
11 matches
Mail list logo
