If it is of interest to an academic community then it probably should be
part of Sage ;-)
On Friday, March 30, 2012 11:04:00 PM UTC+1, Emil wrote:
3) probably shouldn't be made part of everyone's Sage, but it would be
good if people could install it easily, as it will be of interest to a
Hi,
We actually run into the same problem. Sage process need $HOME for 2 cases
- 1) cython compilation 2) access to DATA - e.g. uploaded by UI.
We simply mounted $HOME over a cluster
the best
mk
On Wednesday, March 28, 2012 11:19:55 PM UTC+2, Maarten Derickx wrote:
Dear All,
I've
On 31 March 2012 12:47, Volker Braun vbraun.n...@gmail.com wrote:
If it is of interest to an academic community then it probably should be
part of Sage ;-)
I'm not against it being incorporated into Sage at some point, but
right now I'd rather keep it as a separate package that people can
I think you should make it an spkg because that is how people using sage expect
to install it.
Note that the install script in an spkg can contain arbitrary bash code so it
can do everything you want it to.
--
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe
On 2012-03-31, Emil emi...@gmail.com wrote:
On 31 March 2012 12:47, Volker Braun vbraun.n...@gmail.com wrote:
If it is of interest to an academic community then it probably should be
part of Sage ;-)
I'm not against it being incorporated into Sage at some point, but
right now I'd rather keep
When I run code :
%cython
cdef hello():
print 'hello world!'
I got two files , one is html file and another is C file.
Html contents are:
1:
2: include interrupt.pxi # ctrl-c interrupt block support
3: include stdsage.pxi # ctrl-c interrupt block support
4:
5: include cdefs.pxi
6:
