[Bug 1735363] Re: inkscape: Port to Python 3
> Maybe you could add a cmake option to let the user > select the python binary? That sounds like a reasonable approach, however I wonder: * Would you expect the shebang to be adjusted for python3 as well (which would require us to configure .py files as a build step in this case and seems like a lot of likely unneccessary hassle), or would it be fine to call "${python} script.py" from within cmake and ignore the shebang? * I suspect we should also make the binary name that is hardcoded into the inkscape binary configurable in this case? While possible, I'm a bit afraid it might be unflexible or even unpredictable for users: Nowadays, they just expect Inkscape to call "python" (so they can predict which version of python Inkscape will use by running "python --version" from the command line). Now we would hardcode any of "python", "python2" or "python3" as "default interpreter" with no immediately obvious way for users to know which it is. Are we sure this would not cause problems in the long run? On Windows for example official CPython packages even use "python.exe" no matter whether it's Python2 or Python3, so at least on this platform I probably wouldn't want to make the default call anything else (even if I could make sure the bundled Python is called "python3"). > So we have decided long ago to just make the /usr/bin/python symlink > disappear: that simply removes a whole lot of uncertainties. Out of curiosity: Is this documented somewhere? Making packages to call an explicit version because "python" is going to be removed sounds a lot more sane than making packages call "python3" while keeping "python" as an implicit fallback to "python2". Then again from a general point of view the question is whether it really makes sense to treat Python differently from most other versioned software and hardcode a version number into the executable name to start with. (Nobody would consider directly calling "python3.x", because it would just not be practical either, while 3.x versions are not always API compatible either) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1735363 Title: inkscape: Port to Python 3 To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1735363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1735363] Re: inkscape: Port to Python 3
Yes, we still support Python 2, although the preference is to use Python 3 together with Inkscape 1.0. For example Mac and Windows packages ship with Python 3, so extensions not compatible with Python 3 won't run out-of-the-box. Everything shipped with Inkscape is supposed to run with both Python 2 and Python3, though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1735363 Title: inkscape: Port to Python 3 To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1735363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1735363] Re: inkscape: Port to Python 3
I see... so some distros basically want to push towards Python 3 but are too afraid to do it "properly" by also switching the target of "python". ;-) I'd be totally fine with replacing "python" with "python3" on the Inkscape-side if we targeted python3 only. However the idea for Inkscape (at least the "LTS" branch 0.92.x) is to support both, python2 and python3, and we can't offer that level of compatibility by forcing calls to python3. So yes, I think patching on your side is the way to go for now. If you should find any scripts that are *not* compatible with python3 let us know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1735363 Title: inkscape: Port to Python 3 To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1735363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1735363] Re: inkscape: Port to Python 3
What's the problem with calling "python" (without version number)? If there's no version number, it's supposed to be the system's preferred version of python (which might well be python3). Therefore I don't see an explicit dependency on Python 2, as long as all build scripts are compatible with Python 3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1735363 Title: inkscape: Port to Python 3 To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1735363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803021] Re: No tutorials
** Changed in: inkscape Milestone: 1.0 => 0.92.5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803021 Title: No tutorials To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1803021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803021] Re: No tutorials
> I know, but the thing is that I haven't heard of any real transition plan. That's because we actually decided not to do a full transition of all bugs (you mention the huge number yourself - many of them are are likely not valid anymore). A "Migration Game" is currently in the works that aims to motivate original reporters and other interested parties to re-test with current versions and re-file bugs that are still reproducible (more on that will be made public once it's officially launched). Apart from that everybody is welcome to migrate bugs on their own schedule (e.g. bugs reported or affecting oneself). There's no official decision yet what will happen with the rest of the bugs (some are still optimistic all of them could be migrated manually) but the most likely cases a) they're left for dead; b) they're closed; c) the whole tracker will be closed eventually. > I understand the pain though, and I definitely do not plan on > helping out with handling the ton of bugs that are stuck here, > I'm way too scared by their number! :) Oh, that was not my intention. The idea was mainly to give you the possibility to set milestones and/or close bugs that also affect Ubuntu and that you already watch anyway (i.e. to avoid having to ask somebody else to do it like above). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803021 Title: No tutorials To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1803021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803021] Re: No tutorials
I guess this makes also sense to back-port to 0.92.x for us. Would you mind crating an MR Max (or just commit directly; I think you have permissions)? Regarding bugs: Have you heard already that we're migrating away from Launchpad and will do our issue tracking on GitLab going forward Mattia? While we can obviously try to keep Launchpad in order during the transition period we'll stop using it eventually on our side. If you'd like I could also add you to the Inkscape bug team for the time being, just let me know. ** Changed in: inkscape Milestone: None => 1.0 ** Changed in: inkscape Assignee: (unassigned) => Max Gaukler (mgmax) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803021 Title: No tutorials To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1803021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 171390] Re: Extended Raster export support please (e.g. JPG)
** Summary changed: - Extended Raster export support please + Extended Raster export support please (e.g. JPG) ** Changed in: inkscape Assignee: John Cliff (johncliff) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/171390 Title: Extended Raster export support please (e.g. JPG) To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/171390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 170049] Re: Inverted ruler co-ordinate system
** Changed in: inkscape Milestone: 1.0-old => 1.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/170049 Title: Inverted ruler co-ordinate system To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/170049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs