Phyton Export Skritp, wrong paths... (WINDOWS)

[Gabriel]

The script has funny absolute paths!

sys.path.append('C:\Program Files (x86)\Inkscape\share\extensions')

and the function for finding the command is crucial otherwise the script does not work:

with the new python2.7(folder ) (renamed to python) inside the inkscape folder

# Function to try and find the correct command to invoke Inkscape.
 def findInkscapeCommand(self):
  commands = []
  commands.append("inkscape")
        commands.append("..\..\inkscape.exe")
  # commands.append("\"C:\Program Files (x86)\Inkscape\inkscape.exe\"")
  commands.append("/Applications/Inkscape.app/Contents/Resources/bin/inkscape")

  for command in commands:
   proc = subprocess.Popen(command + " --without-gui --version", shell=True, stdout=subprocess.PIPE, stderr=subprocess.PIPE)
   stdout_value, stderr_value = proc.communicate()

   if proc.returncode == 0:
    return command

  return None

[Gabriel (gnuetzi)]

proc = subprocess.Popen(command + " --without-gui --version", shell=True, stdout=subprocess.PIPE, stderr=subprocess.PIPE)

I REMOVED THE brackets [] in this command

and in another one above in the code, where the layer gets exportet :-)

[Hannes Hochreiner (hannes-hochreiner)]

Hi Gabriel:

Thanks for the hint. Just out of interest: where did you get the export script with this path from. Since the path is not in repository like this I would suspect that it was a packaging modification.

[Gabriel (gnuetzi)]

Hello :-). ehm - i got the script.with the inkscape installation. There are
funny absolute paths and take.a.closet look at the subprocess command : ( i
am no phyton expert :-), but this command :

proc = subprocess.Popen(command + " --without-gui --version", shell=True,
stdout=subprocess.PIPE, stderr=subprocess.PIPE)

works only in this.form without the brackets [...] !!!
there are two such lines in tje export script....
Does.this.makes.sense?

br gabriel
Am 16.06.2012 10:30 schrieb "Hannes Hochreiner" <email address hidden>:

[Hannes Hochreiner (hannes-hochreiner)]

Going by my experience and the python documentation, I think that the brackets don't matter in this case. True, they are not necessary, but as I understand it they don't do any harm. I would guess they are left over from test with separating the arguments. For documentation on the subprocess.Popen command please refer to:

http://docs.python.org/dev/library/subprocess#subprocess.Popen

As for the path, if relative paths work they are definitely preferable. I don't have a Windows box to test that out. I would guess the Inkscape package you have was prepared for 64 bit Windows with Inkscape installed as a 32 bit application. In this case the path would look reasonable (although I can't say whether it is correct or not).

My suggestion would be to use the relative path you posted in addition to the absolute paths already in the script. Do you think that's a reasonable solution?