AFAIU this worked prior to r9248:
1) `pwd` is '/path/to/Inkscape.app'
2) set environment and launch inkscape-bin
3) $PYTHONPATH is set by inkscape-bin to "Contents/Resources/extensions:$PYTHONPATH"
4) full path of the shared extensions directory thus is
'/path/to/Inkscape.app/Contents/Resources/extensions'
Could it be that in recent revisions the spawned python process changes the working directory and starts from '~/.config/inkscape/extensions' and not in the directory that the inkscape-bin process was started from?
> I don't know if inkscape uses $INKSCAPE_SHAREDIR
> to find the resources
$INKSCAPE_SHAREDIR is not relevant for this bug:
Setting $PYTHONPATH to 'Contents/ Resources/ extensions' is relative to the working directory from which the sequence of launcher shell scripts execs the inkscape binary. bazaar. launchpad. net/~inkscape. dev/inkscape/ trunk/annotate/ head%3A/ packaging/ macosx/ Resources/ script# L47>
<http://
AFAIU this worked prior to r9248: to/Inkscape. app' Resources/ extensions: $PYTHONPATH" to/Inkscape. app/Contents/ Resources/ extensions'
1) `pwd` is '/path/
2) set environment and launch inkscape-bin
3) $PYTHONPATH is set by inkscape-bin to "Contents/
4) full path of the shared extensions directory thus is
'/path/
Could it be that in recent revisions the spawned python process changes the working directory and starts from '~/.config/ inkscape/ extensions' and not in the directory that the inkscape-bin process was started from?