What does "import safe" mean in Python?

Question

I just hit the behaviour where nose will not run tests marked as executable (as described in a previous question). I found this surprising, and I wasted some time trying to find out why nose wasn't running my tests before I learned about nose's behaviour here.

In the manpage for nosetests, it describes an option to override the default behaviour:

--exe               Look for tests in python modules that are executable.
                    Normal behavior is to exclude executable modules,
                    since they may not be import-safe [NOSE_INCLUDE_EXE]

My question is: what does "import-safe" mean? What is an example of a non-import-safe module? And can a non-import-safe module be made import-safe by removing the executable bit, or is there more to it than that?

score 5 · Answer 1 · answered Apr 26 '12 at 09:29

5

"import-safe" doesn't have a specific, defined meaning. In this case, the point is that Python modules can do something when they are imported (remember, importing a module just means executing it and saving all the things in its namespace).

If the module is marked with the executable bit, nose assumes that this is the case -- and since you probably don't want that stuff to happen every time you run your tests, it will skip the module.

answered Apr 26 '12 at 09:29

Katriel

120,462
19
136
170

@NiklasB. Sorry, I don't understand your question. What is `it`? – Katriel Apr 26 '12 at 09:31
Never mind. I was referring to `nose`, but according to the error message, it just checks the exec bit. – Niklas B. Apr 26 '12 at 09:32

score 5 · Accepted Answer · answered Apr 26 '12 at 09:35

I'm not familiar with nose, but I'm pretty sure what it means by "import safe" is that importing the module will just define things, not go off and run stuff.

The idea would be that if a .py file is designed to be executed as a script, then its functionality will be initiated while executing module-scope code. This could be guarded against importing with the __name__ == '__main__' trick, but it might not be. If it isn't, importing it will probably do the same thing it would do as a script when invoked with no arguments, which in some cases could be bad.

So, you can explicitly tell nose that there are no such executable scripts that would be dangerous to import by passing the --exe flag, or you can clear the executable permission from your scripts.

score 4 · Answer 3 · edited Aug 01 '16 at 08:18

4

It refers to modules that can be both imported or executed as a script. This is usually done by the following piece of code:

if __name__ == "__main__":
    print "running as script"

If a script that was meant to be executable does not have this check, importing will immediately execute it which will probably end with unwanted side effects or exception raised.

edited Aug 01 '16 at 08:18

Eric O. Lebigot

91,433
48
218
260

answered Apr 26 '12 at 09:27

hamstergene

24,039
5
57
72

What does "import safe" mean in Python?

3 Answers3

Linked