[pythonmax]

Hello together,

I've started developing with pyS60 (Version 1.4.5 final) on my Nokia 6120 classic and everything works fine so far - except that I'm not able to load any external modules.
I need the csv module (http://docs.python.org/library/csv.html) and put the csv.py from my local Python installation (Ubuntu 8.10) into my Python Script folder on my mobile (E:\\Python) on the external memory card.

Then I start the interactive console on my phone and I get
>>> import csv
>>> Import Error: No module named csv

Same happens when I put a simple python file with "import csv" in the script folder (E:\\Python) and start the script from within Python.

Could anybody help me?

Thanks a lot!

[Rafael T.]

Originally Posted by pythonmax

Hello together,

I've started developing with pyS60 (Version 1.4.5 final) on my Nokia 6120 classic and everything works fine so far - except that I'm not able to load any external modules.
I need the csv module (http://docs.python.org/library/csv.html) and put the csv.py from my local Python installation (Ubuntu 8.10) into my Python Script folder on my mobile (E:\\Python) on the external memory card.

Then I start the interactive console on my phone and I get
>>> import csv
>>> Import Error: No module named csv

Same happens when I put a simple python file with "import csv" in the script folder (E:\\Python) and start the script from within Python.

Could anybody help me?

Thanks a lot!

You need to tell python the directory of the file you want to import:

import sys

sys.path.append('E:\\Python')

import csv

Hope it helps,

Rafael.

[marcelobarrosalmeida]

Python is prepared to look for scripts in e:\python\lib, besides other directories in C: (private\<id>, resource).
If you want to put it in e:\python, follow Rafael instructions.

My strategy is to put my scripts wherever I want and add an entry point in e:\python.

e:\python\myprogentry.py:

import sys
sys.path.append('e:\\mydir\\')
import mymodule

mymodule.run() # put your initialization code here

This way, I do not need to add a sys.path.append() call inside my scripts.

[JOM]

Originally Posted by marcelobarrosalmeida

My strategy is to put my scripts wherever I want and add an entry point in e:\python.

e:\python\myprogentry.py:

import sys
sys.path.append('e:\\mydir\\')
import mymodule

mymodule.run() # put your initialization code here

This way, I do not need to add a sys.path.append() call inside my scripts.

You force user to install your script/app on e-drive Not very nice... Then you also have to remember to force SIS installation only on e-drive!

On the other hand you could try to find out what is "current" directory or drive and just add that. Or an easier way might be to add both c and e drives on sys.path:

import sys
sys.path.append('c:\\mydir\\')
sys.path.append('e:\\mydir\\')
import mymodule

mymodule.run() # put your initialization code here

Cheers,

--jouni who wants to have TOTAL CONTROL over HIS OWN phone

[pythonmax]

Originally Posted by Rafael T.

Hope it helps,

Rafael.

Hi Rafael,

thanks a lot, you took me one step further.

But now I get the error:

no module named _csv

In csv.py line 7 states

from _csv import Error, .....

I found a _csv.so in my local python installation (under /usr/lib/python2.5/lib-dynload"), but it doesn't help to put it in E:\Python on my phone.

Any hints for me?

Thanks!

[marcelobarrosalmeida]

[quote=JOM;533648]You force user to install your script/app on e-drive Not very nice... Then you also have to remember to force SIS installation only on e-drive!
[/code]
No, that is not my point !
In fact, my code is free of any sys.path.append(). This is nice way for generating and testing .sis, without even testing if you are in emulator or not. That stub code is just for starting my application and it is not included in the application itself. When installed, the sys.path.append() is not necessary since all .py files will be together. However, if I am running scripts from memory card (not a sis), the stub code do the dirt job and add a call to append().

[JOM]

Hi,

No problem, I use something similar: have just-in-case code in default.py regardless whether I need it or not Glad to hear you prefer sw which can be installed anywhere! Hopefully PyS60 2.x will also support that.. 1.4.x has some mysterious bugs which require occasionally installation on exactly same drive as python runtime and maybe even on c-drive. Not clear why, but that's the way things are.

Cheers,

--jouni