How Python creates a new process

The recent maintenance of the Nuke toolkit in the synthesis department found that many tools were used in a personal way, without documentation. This also led to artist in the use of tools when the more sensitive, adjust the parameters when the lack of logic, in the long-time, artist will produce this consciousness: just the last call to effect OK on the line, as to how to tune, is a personal matter. Even a lot of artist will reject this kind of toolkit, and think that it is not only difficult to use, but also not obvious.

There is no doubt that any tool will be more effective when it is fully mastered, thinking it through, and decide to write a document for each tool.

After writing, the document can be opened in menu.py through the Os.system (path) method.

But the problem arises. This document is opened with Word will occupy the nuke process, causing nuke into suspended animation state. Only turn off word to dismiss nuke suspended animation.

In other words, word and nuke are actually sharing the same process, which is obviously unacceptable. A script was written to open a new process for the newly opened Word program.

The code blocks are as follows:

Import Threading:
def threading_document (path):
Thread = Threading. Thread (target = Os.system,args = (path,))
Thread.setdaemon (True)
Thread.Start ()

With this function, you can avoid the bug of sharing a process.

How Python creates a new process