From: Christopher Schwan <cschwan@students.uni-mainz.de>
To: <gentoo-science@lists.gentoo.org>
Subject: Re: [gentoo-science] [sage-on-gentoo] fortran scripts
Date: Thu, 12 Aug 2010 22:16:44 +0200 [thread overview]
Message-ID: <201008122216.45191.cschwan@students.uni-mainz.de> (raw)
In-Reply-To: <1281627462.27643.0@pavilion64>
Hi,
On Thursday 12 August 2010 17:37:34 Steven Trogdon wrote:
> Hi:
>
> I had apparently installed the Sage-provided scripts
>
> sage-g77_shared
> sage_fortran
>
> when Sage was under /opt to get some fortran functionality from within the
> notebook. Of course that functionality is missing with Sage under /usr.
> Both scripts are needed. See, from the notebook,
>
> Help -> Fast Static Versions -> Numerical Sage -> f2py
>
> for a cut-N-paste example. This example is included (command line version)
> in inline_fortran.py, the InlineFortran class under
> site-packages/sage/misc. The sage-g77_shared script calls sage_fortran and
> sage-g77_shared is hardcoded in the InlineFortran class. I suppose it is
> somewhat awkward to have these two scripts, but thought I would point out
> that some functionality is missing without them. Perhaps there is a better
> way, without messing around with the InlineFortran class, to achieve the
> same result.
Thats absolutely right - thank you for pointing that out. I have added these
files for now, but I think I will write a fix so we wont need these.
>
> Steve
Christopher
next prev parent reply other threads:[~2010-08-12 20:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 15:37 [gentoo-science] [sage-on-gentoo] fortran scripts Steven Trogdon
2010-08-12 20:16 ` Christopher Schwan [this message]
2010-08-12 22:54 ` Steven Trogdon
2010-08-13 8:34 ` Christopher Schwan
2010-08-13 12:20 ` Steven Trogdon
2010-08-13 14:32 ` Christopher Schwan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201008122216.45191.cschwan@students.uni-mainz.de \
--to=cschwan@students.uni-mainz.de \
--cc=gentoo-science@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox