error in Python scripting node

KNIME Analytics Platform
1

dear,

i start to use python in knime but i have found that when i change the temp for knime to a folder different to disk C: for example D:...i found that error (with python scripting workflow)

ERROR PythonPlotNodeModel Traceback (most recent call last):

ERROR PythonPlotNodeModel File "E:\tempknime\analyze8172415773159922615.py", line 217, in <module>

ERROR PythonPlotNodeModel kIn = read_csv("E:\tempknime\knime2python235537943648298055.csv", True)

ERROR PythonPlotNodeModel File "E:\tempknime\analyze8172415773159922615.py", line 146, in read_csv

ERROR PythonPlotNodeModel types = get_column_types(csv_filename)

ERROR PythonPlotNodeModel File "E:\tempknime\analyze8172415773159922615.py", line 68, in get_column_types

ERROR PythonPlotNodeModel csv_reader = csv.reader(open(csv_filename, 'rb'), delimiter=',', quotechar='"')

ERROR PythonPlotNodeModel IOError: [Errno 22] invalid mode ('rb') or filename: 'E:\tempknime\\knime2python235537943648298055.csv'

ERROR Python Plot Execute failed: No output image found

when i change back this works well

Can you fix this bug?

thanks

2

could you please check the version of the corresponding plugin

go to the plugin-folder of your KNIME installation, the plugin called

de.mpicbg.tds.knime.scripting.python_???.jar

(or look at "About KNIME" > "Installation Details" at your running KNIME instance)

3

dear ,

I have the version 2.5.0.0031109 installed and 2.6 of python

4

Now I'm confused. You use the python extension from the community contributions? If yes, I need to know the version of this plugin (which is certainly nothing like 2.5.xxx). If no, I'm not the one who can help you.

5

sorry ,

I made a mistake i wrote the jython version....i have installed python scripting extension 1.1.0.201112121427 and  KNIME Scripting extension core 1.0.0.201112121427 

6

Hi,

could you please try to update the python integration tomorrow from the nightly build? We had a problems with path names in Windows already in February and my colleague did some bugfixes. I'd like to know whether this also solves your problem.