We could also move more tools outside the main systemd package and into PIP. PIP alters the top of any registered Python executable to use the version of Python corresponding to the version of PIP used to install it. Fedora packages both Python 2.7 and Python 3.2/3.3 PIP clients.
On Fri, Nov 30, 2012 at 1:03 PM, Colin Walters <walt...@verbum.org> wrote: > On Fri, 2012-11-30 at 21:49 +0100, Michael Biebl wrote: >> 2012/11/30 Ramkumar Ramachandra <artag...@gmail.com>: >> > Execute python using "/usr/bin/env python" instead of hard-coding the >> >> I'm not really a fan of using /usr/bin/env, as you can pick up a >> random python version depending on how your PATH is setup. >> Besides, you need to spawn an additional binary. >> I would assume that pretty much every distro ships the python >> interpreter as /usr/bin/python. > > > The conclusion we came to in GNOME is that components should accept a > --with-python=/path/to/python option for configure to specify which > python should be used. If not provided, then falling back > to /usr/bin/env is probably fine. > > https://mail.gnome.org/archives/desktop-devel-list/2012-November/msg00014.html > > > _______________________________________________ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- David Strauss | da...@davidstrauss.net | +1 512 577 5827 [mobile] _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
