ubuntustudio-bugs team mailing list archive

[Mattia Rizzolo <mattia@xxxxxxxxxxx>]

> * Would you expect the shebang to be adjusted for python3 as well

Not really.  You are already calling `python path/to/script.py` right
now; that already ignores the shebang, and so I don't really care of
changing that right now.  Since it's used only a build time, I care even
less.

> * I suspect we should also make the binary name that is
>   hardcoded into the inkscape binary configurable in this case?

Honestly, the situation is currently way too messy especially across
multiple platforms and Linux distributions, as I said.  IMHO, the
probably best solution is for you to not rely on anything, and detect
the best interpreter at run time (here, perhaps due to my involvement in
Debian, I suggest preferring `python3`.

BTW, so how are the plugins invoked in 1.0?  In the past inkscape even
linked against libpython, but now it's not anymore.  Is it forking out
an external python process directly?  (that means I should be adding a
manual hard dependency on the python interpreter to the Debian package,
as otherwise it wouldn't get any…)

> Out of curiosity: Is this documented somewhere?

I'm sure it is somewhere, but I wouldn't know.  Most of my knowledge
comes from following the matters across multiple mailing lists and other
media…

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to inkscape in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1735363

Title:
  inkscape: Port to Python 3

Status in Inkscape:
  Fix Committed
Status in inkscape package in Ubuntu:
  Confirmed
Status in inkscape package in Debian:
  Confirmed
Status in inkscape package in Fedora:
  Invalid

Bug description:
  inkscape: Use/Port of Python3 needed, or considering demotion.

  Currently seeded in usb (???), owned by desktop-packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1735363/+subscriptions