Just for closure on this. I was able to get the functionality I needed into Sage by extracting and modifying functions and dependencies as needed in the source code. It was tedious but not too difficult. So to all who answered this:Thanks again for the assistance!
On Jan 2, 8:23 pm, DavidG <davidgrudo...@gmail.com> wrote: > Thanks for the help Simon, > I was able to build scikit-learn following your instructions however > when I tried to import the module it reported a Scipy error during the > import. > I then reinstalled SciPy thinking there was an error and after > installing SciPy Sage returned the "make" error while importing > sklearn. > I built the original sklearn from my Python 2.6 (32 bit) and it runs > fine outside of Sage. Ifigured that since it was compiled under a 32 > bit system if I ran a 32 bit version of Sage i could import the module > directly. Well that didn't work either. So I guess its a problem with > the sklearn package and I'll just have to use it with a different IDE. > At the least I now know how to install a package using the Sage shell > method. > Thanks Again > David > > On Jan 2, 12:56 pm, Simon King <simon.k...@uni-jena.de> wrote: > > > > > > > > > Hi David, > > > On 2 Jan., 19:00, DavidG <davidgrudo...@gmail.com> wrote: > > > > I used my default python2.6 which is running in 32 bit architecture to > > > compile the sklearn module > > > I'm running a 64 bit version of SAGE, hence the incompatability. > > > No. Sage has its own installation of Python, Maxima, Gap, > > Singular, ... (also known as "Sage comes with batteries included"). > > Your default python2.6 is totally irrelevant to Sage. > > > > Given the error and instruction to run "Make" first. How can I run > > > make from within sage. > > > Also using the command "sage -sh" from my terminal gives the error: > > > > $ sage -sh > > > -bash: sage: command not found > > > Then how do you start a Sage session from the command line? > > > > opening a sage session and using the sage terminal: > > > cd to the source directory and typing setup results in: > > > > NameError: name 'setup' is not defined > > > sage: > > > That is a Sage session, but not a Sage shell. > > > Let us assume that you installed Sage in the folder ~/SAGE/sage-4.7.2. > > You will find an executable "sage" there. > > If it is not in your path, then just doing "sage" or "sage -sh" will, > > of course, not work and result in a "command not found" error. > > > But being in that folder, you can start a sage session by ./sage. > > You can start a session of Sage's python by ./sage -python, of Sage's > > Singular by ./sage -singular, and so on. > > > And if you want to install a package into Sage's python, then you can > > open a Sage shell (by ./sage -sh if you are in the afore-mentioned > > folder, by /path/to/that/folder/sage -sh if you aren't, and by sage - > > sh if sage is in your path), and then you can do all the necessary > > steps to install your package. > > > Best regards, > > Simon -- To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
