Databases
StackOverflow2013
Postsdbo
POpython modules missing in sage
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POpython modules missing in sage
    primarykey
    data
    text
    <p>I have Sage 4.7.1 installed and have run into an odd problem. Many of my older scripts that use functions like deepcopy() and uniq() no longer recognize them as global names. I have been able to fix this by importing the python modules one by one, but this is quite tedious. But when I start the command-line Sage interface, I can type "list2=deepcopy(list1)" without importing the copy module, and this works fine. How is it possible that the command line Sage can recognize global name 'deepcopy' but if I load my script that uses the same name it doesn't recognize it?</p> <p>oops, sorry, not familiar with stackoverflow yet. I type: 'sage_4.7.1/sage" to start the command line interface; then, I type "load jbom.py" to load up all the functions I defined in a python script. When I use one of the functions from the script, it runs for a few seconds (complex function) then hits a spot where I use some function that Sage normally has as a global name (deepcopy, uniq, etc) but for some reason the script I loaded does not know what the function is. And to reiterate, my script jbom.py used to work the last time I was working on this particular research, just as I described.</p> <p>It also makes no difference if I use 'load jbom.py' or 'import jbom'. Both methods get the functions I defined in my script (but I have to use jbom. in the second case) and both get the same error about 'deepcopy' not being a global name.</p> <p>REPLY TO DSM: I have been sloppy about describing the problem, for which I am sorry. I have created a new script 'experiment.py' that has "import jbom" as its first line. Executing the function in experiment.py recognizes the functions in jbom.py but deepcopy is not recognized. I tried loading jbom.py as "load jbom.py" and I can use the functions just like I did months ago. So, is this all just a problem of layering scripts without proper usage of import/load etc?</p> <p>SOLVED: I added "from sage.all import *" to the beginning of jbom.py and now I can load experiment.py and execute the functions calling jbom.py functions without any problems. From the Sage doc on import/load I can't really tell what I was doing wrong exactly.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USmjenista
    1. USmjenista
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COHow did you install sage? Compiling from source?.. As I recall, it has its own python and everything. You could force running your older scripts with your stock python, to isolate issues.
      singulars
      1. POpython modules missing in sage
      1. USspacediver
    2. COWhat does "load my script" mean? Sage 4.7.1 should have `deepcopy` available.
      singulars
      1. POpython modules missing in sage
      1. USDSM
    3. COI can't reproduce this, although the oldest Sage I have at hand is 4.7.2. A 1-line program `print deepcopy` works for me when I `load jbom.py` (because it's a glorified `execfile`, and so `deepcopy` is in scope even though it's not being preparsed because it's a `.py` file), but not when I import it (because said Python module doesn't magically get access to Sage names, and requires `from sage.all import *`). Could you cut everything out from your `jbom.py` file except that needed to reproduce the problem and paste that?
      singulars
      1. POpython modules missing in sage
      1. USDSM
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload