On Sunday, January 19, 2014 1:37:07 AM UTC-8, Bernhard Spinnler wrote: > > It's a pity that there doesn't seem to be an easy fix for this.
There is, as diagnosed above. It's just so trivial that the administrative burden of applying it to sage becomes significant by comparison, and dealing with admin is never attractive. There is now http://trac.sagemath.org/ticket/10963 > This problem essentially breaks Sage as an efficient and friendly > environment for me (and probably most of the engineering tasks that always > involve Complex numbers). I extremely like the Sage notebook for trying out > new ideas before converting the Sage notebook into a Python/numpy/scipy > script. Unfortunately my experience with Sage's internals is too limited to > be able to help much here. If there's anything where I can help (testing, > …) let me know. > Hopefully with the ticket in place (and the basic fix), you now have a lead to test the solution and/or amend it. In order to get it merged you'll also have to add documentation (a test that shows it fixes what used to be a problem) -- 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/groups/opt_out.
