Talk:NsPython plug-in - Revision history

Kelvie: /* ExecFile not working */

2012-10-10T18:59:06Z

ExecFile not working

â† Older revision		Revision as of 18:59, 10 October 2012
Line 63:		Line 63:

	Easiest workaround is nsPython::exec "execfile('file.py')"		Easiest workaround is nsPython::exec "execfile('file.py')"

			I've fixed this in the latest 2.7 version I've uploaded [[User:Kelvie\|Kelvie]] 18:59, 10 October 2012 (UTC)

83.145.204.137: /* ExecFile not working */ new section

2010-10-06T13:40:33Z

ExecFile not working: new section

â† Older revision		Revision as of 13:40, 6 October 2010
Line 57:		Line 57:

	--[[User:Wulmer\|wulmer]] 14:06, 4 May 2007 (PDT)		--[[User:Wulmer\|wulmer]] 14:06, 4 May 2007 (PDT)

			== ExecFile not working ==

			I noticed that nsPython::execFile statement does not work. By reading source code it is quite obvious as it is missing popstring(filename) in callPythonFile function in nsPython.c. (compare to popstring(command) in callPython function).

			Easiest workaround is nsPython::exec "execfile('file.py')"

Wulmer at 21:06, 4 May 2007

2007-05-04T21:06:43Z

â† Older revision		Revision as of 21:06, 4 May 2007
Line 1:		Line 1:
			== My Problem ==
	Hello,		Hello,

Line 5:		Line 6:
	I found out by using FileMon, that the '''module python files were searched in a subdirectory "python23.zip"'''.		I found out by using FileMon, that the '''module python files were searched in a subdirectory "python23.zip"'''.

			== Solution 1 ==
	I am using the following '''source directory structure''' with the following files:		I am using the following '''source directory structure''' with the following files:
	<pre>		<pre>
Line 38:		Line 40:

	With this setting I was able to use the nsPython plugin without problems. If you need other modules, you get an error message from the nsPython plugin naming the module. Simply copy the module.py file into the python23.zip/ directory.		With this setting I was able to use the nsPython plugin without problems. If you need other modules, you get an error message from the nsPython plugin naming the module. Simply copy the module.py file into the python23.zip/ directory.

			== Solution 2 ==

			Another alternative is to adjust the python search path before importing additional libraries. Start your python file with (not tested yet)
			<highlight-python>
			import sys
			sys.path.append("./Lib/")
			import ...
			</highlight-python>
			where you specify the path containing the module files.


			== Questions ? Comments ? ==

	If you have comments about this, mail me at wulmer{@}web{.}de		If you have comments about this, mail me at wulmer{@}web{.}de

	----		--[[User:Wulmer\|wulmer]] 14:06, 4 May 2007 (PDT)

194.39.218.10 at 14:43, 4 May 2007

2007-05-04T14:43:01Z

New page

Hello,

I had a problem that '''no modules were found by python23.dll''', even the test installer in the ZIP file did not work with the external test.py file.

I found out by using FileMon, that the '''module python files were searched in a subdirectory "python23.zip"'''.

I am using the following '''source directory structure''' with the following files:
<pre>
./
./nsPython/
./nsPython/python23.dll
./nsPython/python23.zip/
./nsPython/python23.zip/copy_reg.py
./nsPython/python23.zip/ntpath.py
./nsPython/python23.zip/os.py
./nsPython/python23.zip/shutil.py
./nsPython/python23.zip/stat.py
./nsPython/python23.zip/types.py
./nsPython/python23.zip/UserDict.py
</pre>

'''In the NSI file''', I have at the beginning:

<highlight-nsis>
ReserveFile "nsPython\python23.dll"
ReserveFile "nsPython\python23.zip\*.*"
</highlight-nsis>

Then in .onInit I have:

<highlight-nsis>
Function .onInit
InitPluginsDir
SetOutPath "$PLUGINSDIR"
File /r "nsPython\*.*"
...
</highlight-nsis>

With this setting I was able to use the nsPython plugin without problems. If you need other modules, you get an error message from the nsPython plugin naming the module. Simply copy the module.py file into the python23.zip/ directory.

If you have comments about this, mail me at wulmer{@}web{.}de

----