... turns out that not only SymPy, but also GiNaC has a problem when expanding zeta around 1. However, it is more likely for the error to come from GiNaC -- so I'll do some more investigations, and then report the issue there as well.
In any case, thanks for help! Best wishes, Benjamin Am Dienstag, 7. April 2015 18:26:09 UTC+2 schrieb vdelecroix: > > Hello, > > On 07/04/2015, Benjamin Hackl <benjami...@aau.at <javascript:>> wrote: > > Hello everybody, > > > > today I had a look at http://trac.sagemath.org/ticket/15846 and I think > I > > may have tracked down the issue to SymPy (details in the comments of the > > ticket). > > Assuming what I found actually is the problem, I'm not quite sure how to > > proceed from there (i.e. reporting the issue upstream to SymPy etc.). > Could > > > > someone help me with that? > > As far as I know, sympy works with github and you can provide pull > requests. This is what has been done in #18085. > > > Also, is there a way to test how changes to, say, > > local/lib/python/site-packages/sympy/functions/special/zeta_functions.py > > affect my sage installation? > > As soon as you changed it, just restart sage and you get the new sympy > version when doing "import sympy". > The more Sagish way to do it is to provide a tarball and modify the > install scripts in "$SAGE_ROOT/build/pkgs/sympy/" accordingly. You can > also have a look in the developer guide > http://sagemath.org/doc/developer/packaging.html > > Vincent > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
