So, is there a supported way for the user to append paths to the
PYTHONPATH in the Sage installation (sage-env)?
On Tue, Jan 25, 2011 at 1:20 AM, Minh Nguyen nguyenmi...@gmail.com wrote:
Hi Ryan,
On Tue, Jan 25, 2011 at 3:10 PM, Ryan Krauss ryanwkra...@gmail.com wrote:
but I am assuming there
Hi Ryan,
On 25 Jan., 13:25, Ryan Krauss ryanwkra...@gmail.com wrote:
So, is there a supported way for the user to append paths to the
PYTHONPATH in the Sage installation (sage-env)?
AFAIK, it is not supported to work with your system-wide Python from
within Sage.
Hence, the supported way of
Thanks. That makes sense for installing third party packages. But it
seems like my hack is the only way to use my own packages (which are
continually under development and I don't install them).
Would it be possible to check for a user defined environment variable
(say SAGE_PYTHOPATH) and
On Tue, 25 Jan 2011 10:29:38 -0600
Ryan Krauss ryanwkra...@gmail.com wrote:
Would it be possible to check for a user defined environment variable
(say SAGE_PYTHOPATH) and append it to PYTHONPATH in sage-env if it is
defined (I have never really bothered to learn bash programming).
The
So, in trying to answer my own question, I came up with a hack that
seems to work, but also seems dangerous.
I found this line in SAGE_ROOT/local/bin/sage-env:
if [ -d $SAGE_ROOT/local/lib/python ]; then
PYTHONPATH=$SAGE_PATH:$SAGE_ROOT/local/lib/pythonexport PYTHONPATH
and added one of
Hi Ryan,
On Tue, Jan 25, 2011 at 3:10 PM, Ryan Krauss ryanwkra...@gmail.com wrote:
but I am assuming there has to be a better way.
When you import anything from within a Sage session, it's assumed that
the module to be imported is within the Python path local to your Sage
installation. So your
