Hi Dražen
There is very little in bin/foo, it simply calculates the path to the python files depending on whether the project is installed or not.
Seeing how bin/foo cannot be called from pydev easily how about
ln -s bin/foo bin/pydev-run.py
then you could create your pydev-entry.py file which does your pre-processing, glade xdg etc, then import pydev-run. The "quickly add" system actually patches the project files so could easily exclude these pydev* files from packaging. The assumption is that a project might process command line arguments so quickly uses subprocess. I assume pydev has its own way to handle that.
Hi Dražen
There is very little in bin/foo, it simply calculates the path to the python files depending on whether the project is installed or not.
Seeing how bin/foo cannot be called from pydev easily how about
ln -s bin/foo bin/pydev-run.py
then you could create your pydev-entry.py file which does your pre-processing, glade xdg etc, then import pydev-run. The "quickly add" system actually patches the project files so could easily exclude these pydev* files from packaging. The assumption is that a project might process command line arguments so quickly uses subprocess. I assume pydev has its own way to handle that.