thyandrecardoso

startup.py and scripting.py Doubts

Discussion created by thyandrecardoso on Mar 5, 2012
Latest reply on Apr 16, 2012 by AUlmer-esristaff
Hello :)

I have two questions regarding the startup.py and the scripting.py:

1: As described in the docs, the startup.py common use is to load custom scripts on CE load (sys.path.append(), import); What is the common use case for the scripting.py ? What should I not do in either one?

2: I have created a startup.py on the workspace root (actually, it is a symbolic link) and I put some debugging "prints" to see if it worked. Upon CE loading, I see those messages written on the Console. However, when I open the Jython console, and try to access the modules imported inside the startup.py, it does not work. I'm forced to rewrite the code inside the startup.py file in order to access the desired functions... After reading the docs about the startup.py script, I got the impression this was one of its purposes. Can you help me here? Am I doing something wrong?

Thanks!
André

Outcomes