[sage-support] Re: problem with python within python

2008-09-09 Thread Marshall Hampton

It just seems weird to me, regardless of what sys.path is, that
os.system('/path/to/command/command')
would run a different version of 'command' than what is specified.

I'm not sure I can easily give steps to reproduce exactly what I'm
doing, but you could try running any python script you like in the
above way (in the Sage notebook) and see which python is used (perhaps
by using something you only have installed in the framework).

Its not worth my time to try to get Sage to compile a framework
version. Actually, all I want to do is manipulate an image for a
linear algebra class.  There are some open tickets that try to improve
image importing in Sage (without the PIL) but I think progress on them
has stalled.

-M. Hampton

On Sep 8, 3:47 pm, David Philp [EMAIL PROTECTED] wrote:
 On 09/09/2008, at 2:25 AM, Marshall Hampton wrote:

  I am trying to use the Python Imaging Library which I can only manage
  to install in my OS X framework verison of python.  So as a kludge I
  am trying to run that system python from within Sage's python.  But
  when I do:

  import os
  os.system('/Library/Frameworks/Python.framework/Versions/Current/bin/
  python ' + DATA+'im.py')

  to run my script im.py, it seems that the sage python version is used,
  not the one in the explicit path I gave.  Why is this happening and
  how do I work around it?

 When fooling around with system python vs sage python, I've made
 mileage by manipulating sys.path... when Sage starts up, it sets
 sys.path to a very different value to what system python uses.

 Can you give steps to reproduce?  (How are you running system python
 from sage's python?)

 And... ahem... this may not be the best place to mention it, but if
 you're up for some pain, you can configure sage such that python is
 compiled as an OS X framework.  You then hopefully wouldn't need the
 system python from within Sage's python kludge.

 D
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---



[sage-support] Re: problem with python within python

2008-09-08 Thread David Philp


On 09/09/2008, at 2:25 AM, Marshall Hampton wrote:

 I am trying to use the Python Imaging Library which I can only manage
 to install in my OS X framework verison of python.  So as a kludge I
 am trying to run that system python from within Sage's python.  But
 when I do:

 import os
 os.system('/Library/Frameworks/Python.framework/Versions/Current/bin/
 python ' + DATA+'im.py')

 to run my script im.py, it seems that the sage python version is used,
 not the one in the explicit path I gave.  Why is this happening and
 how do I work around it?

When fooling around with system python vs sage python, I've made  
mileage by manipulating sys.path... when Sage starts up, it sets  
sys.path to a very different value to what system python uses.

Can you give steps to reproduce?  (How are you running system python  
from sage's python?)

And... ahem... this may not be the best place to mention it, but if  
you're up for some pain, you can configure sage such that python is  
compiled as an OS X framework.  You then hopefully wouldn't need the  
system python from within Sage's python kludge.

D



--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---