Re: [sage-devel] cross-post from flint-devel: python bindings for Flint and Arb (work in progress)

On 2015-01-08 18:49, Fredrik Johansson wrote: > On Thu, Jan 8, 2015 at 5:19 PM, William Stein wrote: >> On Thu, Jan 8, 2015 at 5:56 AM, John Cremona wrote: >>> http://fredrikj.net/blog/2015/01/arb-and-flint-in-python/ >> >> Hi Fredrik, >> >> Any chance you could make this trivial to install into

[sage-devel] Re: flint-2.4.4 compile error for Sage-6.4 on MacOSX Mavericks

Sage is compiled with GCC. Can you enter a sage shell "sage -sh" and then try again the compilation, then that'll use the same compiler. Also, your header search path should be something like: $ sage -sh Starting subshell with Sage environment variables set. Don't forget to exit when you are d

[sage-devel] Re: flint-2.4.4 compile error for Sage-6.4 on MacOSX Mavericks

Volker - I'm in over my head here. Can you be more specific about which commands you want me to run? Or do you just want to see the output of the commands you used below? If the latter, they're below. -Xander ` Xanders-MacBook-Pro:~ xander$ cd '/Users/xander/sage/local/var/tmp/sage/build/f

[sage-devel] Re: GSoC 2015

Update. On Monday, January 26, 2015 at 2:06:23 PM UTC+1, Harald Schilly wrote: > > In two weeks... > Tomorrow, the application period starts. A major and important part of the application is a good list of prospective projects. This is a list of ideas on what students can base their project pr

Re: [sage-devel] Is CMake OK for a standard spkg?

>Anyway, as mentioned before, according to this thread: > http://groups.google.com/group/sage-devel/browse_thread/thread/e91a204a2902afd/ccbdaa4792872282?lnk=gst&q=Heads+up#ccbdaa4792872282 >singular is migrating to CMake. For good or bad, Singular did not migrate to CMake. There was too muc

[sage-devel] Re: Integrate sage into spyder

On Saturday, February 7, 2015 at 4:14:08 PM UTC+1, mmarco wrote: > > I thinki it would be good to have some kind of IDE to work on sage > development. > I have a (limited, but for our purposes fine) group license for PyCharm under the name of the Sage OSS project. Anyone who is interested, ple

[sage-devel] Re: flint-2.4.4 compile error for Sage-6.4 on MacOSX Mavericks

On Sunday, February 8, 2015 at 1:55:26 PM UTC+1, Xander Faber wrote: > > #include "..." search starts here: > #include <...> search starts here: > /usr/local/include > /Users/xander/sage/local/lib/gcc/x86_64-apple-darwin14.1.0/4.9.2/include > /Users/xander/sage/local/include > I'm guessing yo

[sage-devel] self in the INPUT section of the docstring

Hello. This post is motivated by #17567 . There I implemented a method which is only defined for vectors of length 3 and 7. I felt like documenting the fact “self has to be length 3 or 7” in the INPUT section of the docstring would be a good ide

Re: [sage-devel] self in the INPUT section of the docstring

As long as the restriction is documented somewhere in the docstring, and there is a reasonable error raised when the conditions are not met, it does not seem to me to be essential to include self in the INPUT block. For a common example I looked at the factor() method for ZZ, which certainly does

[sage-devel] Re: self in the INPUT section of the docstring

IMHO thats unnecessarily confusing for novices. You shouldn't have to understand Python OOP to be able to read the documentation. INPUT documents the parameters, and nothing else. Of course such restrictions need to be mentioned elsewhere in the docstring. On Sunday, February 8, 2015 at 10:19

Re: [sage-devel] Re: flint-2.4.4 compile error for Sage-6.4 on MacOSX Mavericks

Woot! Successful build! Yes, I had my own install of gmp. I renamed /usr/local before the build and everything went smoothly. Many thanks, Volker and Bill, for diagnosing the problem. Cheers, Xander On Sun, Feb 8, 2015 at 9:38 AM, Volker Braun wrote: > On Sunday, February 8, 2015 at 1:55:26