On Tue, Apr 14, 2015 at 3:36 PM, James Crist <[email protected]> wrote: > Side tracking the conversation a bit, PyCon was very productive for me. I > gave a talk to a group of Sage users, and they seemed excited about SymPy. > Apparently (at least according to them) the symbolic support in sage is > poor, and sympy is much better. It word be nice to get sympy/csympy to be > the main symbolics engine for sage, as the increased user base would > probably result in an increased development team.
Yes, that's exactly my plan, and there is a GSoC proposal this year from Isuru to do exactly that (i.e. work on csympy being the main symbolic engine for Sage --- obviously this is a long term project, so it's just a start). I have no doubt that if the SymPy ecosystem contains a very fast core (CSymPy) that is faster than other software, then people can consider SymPy very seriously for their work. It's just a question to figure out how to make it all work nicely together. Ondrej > > On Tue, Apr 14, 2015 at 4:31 PM, James Crist <[email protected]> wrote: >> >> > Have you tried git blame -CCC -M? According to the manpage it is >> > supposed to be smarter about stuff. >> >> I had not, but it looks better. I've rarely encountered this issue, I just >> thought I'd ask how the community felt about it. Personally, I still feel >> like cleaning up code should be done only around things the commiter just >> worked on, and in the same PR (not necessarily the same commit), but that's >> just a personal opinion. I agree that keeping the barrier to entry for SymPy >> as low as possible is *much* more important than things like this. Duly >> noted. >> >> >> >> On Tue, Apr 14, 2015 at 3:41 PM, Joachim Durchholz <[email protected]> >> wrote: >>> >>> Am 14.04.2015 um 19:54 schrieb James Crist: >>>> >>>> For example, say I make a tiny bug fix in function foo - I could also >>>> clean >>>> up some of the code in foo. That way the last person to touch foo is not >>>> someone who added a space between an operator, but someone who actually >>>> changed the functionality of foo. >>> >>> >>> +1 >>> It's what I've been doing all the time. >>> Well, being human: *trying* to do all the time :-) >>> >>> One exception: I don't apply that argument to adding or removing blank >>> lines, or where the change in functionality is more visible elsewhere (e.g. >>> when cleaning up import lists). >>> >>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "sympy" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/sympy/lVUoV2_Jzm0/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at http://groups.google.com/group/sympy. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/sympy/552D7B86.1040902%40durchholz.org. >>> >>> For more options, visit https://groups.google.com/d/optout. >> >> > > -- > You received this message because you are subscribed to the Google Groups > "sympy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/sympy. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sympy/CAJ2L7mdwPXSy%2BsOH2b4wHuj4PWGw%2BV%2BDGEnEiZCWfchKUS-qOg%40mail.gmail.com. > > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sympy. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CADDwiVBv_evtLtNSo61ZO1j%3D1ssjoro4KxrpiQWBDBLNcYTmmQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
