On Thursday, March 10, 2016 at 6:23:51 PM UTC+1, William wrote: > > One thing it is not right now is: "setup a virtualenv with just the > Sage library" and go at it. I very much wish this was supported, > since a lot of people use SageMathCloud and want to do sage dev, but > it's way too heavy weight. If it were as simple as a virtualenv, it > would be a lot easier.
That sounds like a low-hanging fruit, you just set SAGE_LOCAL and PATH to an existing Sage binary and then install src/setup.py in your virtualenv. I tried and it doesn't work but thats probably just because of some simple path issues. In the just-released 7.1.rc0 we make some steps to using pkg-config for library detection (in particular, blas/lapack). Ideally you shouldn't have to set SAGE_LOCAL, all library dependencies should be detected via pkg-config. Then you'd only need to set PATH for the binary dependencies and for a suitable pkg-config. -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
