[sage-support] Re: Importing a Python module

2010-07-23 Thread KvS
On Jul 21, 2:34 am, Mike Hansen wrote: > On Tue, Jul 20, 2010 at 9:27 AM, KvS wrote: > > Thanks for the quick reply. I tried putting "from sage.all import *" > > Could you post the code tohttp://sage.pastebin.com.  It is better to > avoid using "import *" and explicitly list the things that you w

[sage-support] Re: Importing a Python module

2010-07-20 Thread KvS
On Jul 21, 2:34 am, Mike Hansen wrote: > On Tue, Jul 20, 2010 at 9:27 AM, KvS wrote: > > Thanks for the quick reply. I tried putting "from sage.all import *" > > Could you post the code tohttp://sage.pastebin.com.  It is better to > avoid using "import *" and explicitly list the things that you w

[sage-support] Re: Importing a Python module

2010-07-20 Thread KvS
On Jul 21, 2:34 am, Mike Hansen wrote: > On Tue, Jul 20, 2010 at 9:27 AM, KvS wrote: > > Thanks for the quick reply. I tried putting "from sage.all import *" > > Could you post the code tohttp://sage.pastebin.com.  It is better to > avoid using "import *" and explicitly list the things that you w

Re: [sage-support] Re: Importing a Python module

2010-07-20 Thread Mike Hansen
On Tue, Jul 20, 2010 at 9:27 AM, KvS wrote: > Thanks for the quick reply. I tried putting "from sage.all import *" Could you post the code to http://sage.pastebin.com . It is better to avoid using "import *" and explicitly list the things that you want to import. That way you know what objects

[sage-support] Re: Importing a Python module

2010-07-20 Thread KvS
On Jul 21, 2:01 am, Mike Hansen wrote: > On Tue, Jul 20, 2010 at 8:58 AM, KvS wrote: > > So I guess my problem is that I don't understand the namespaces > > involved somehow, since sgn() lives somewhere in a Sage namespace and > > importing doesn't place the code in the right name space or someth