Hi Brad,
I think this is a very interesting idea worth investigating.
I wonder how hard it would be to have ~/.config/inkscape/extensions be a virtualenv (or maybe the system one), or even if it's possible to use an external python build. It would make including an inkscape extension search and install (and uninstall) feature in side the app a bit easier to do too, since pip would control the IO.
What do other people think about virtualenv? I know there's a bunch of baggage to consider, but it might get rid of a family of problems.
What do windows and Mac packagers think? Is the Mac/Python problem too hard to leverage this?
Martin,
On 29 May 2015 at 18:54, Brad Pitcher <bradpitcher@...400...> wrote:
Hi folks,
I'm toying with the idea of installing Inkscape plugins using pip. In fact, at this very moment, my OpenSCAD DXF Output plugin (https://github.com/brad/Inkscape-OpenSCAD-DXF-Export) can be installed like this:
pip install --target=<installation_dir> inkscape-openscad-dxf
The only downside I can see is that in addition to the plugin files it installs a little cruft: easy_install.py, inkscape_openscad_dxf-0.0.1-py2.7.egg-info, _markerlib, pkg_resources, setuptools, and setuptools-17.0.dist-info
However, I don't think those extra files would be any problem. The big upsides to this approach are that dependencies are automatically included and that PyPi (https://pypi.python.org/pypi) is searchable.
What do you all think of this approach? Is it a good/bad idea?
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel