From: Mike Gilbert <floppym@gentoo.org>
To: "Michał Górny" <mgorny@gentoo.org>, gentoo-python@lists.gentoo.org
Subject: Re: [gentoo-python] Wrapping scripts for multiple Python implementations: executable wrapper or symlinks?
Date: Sat, 29 Sep 2012 23:42:19 -0400 [thread overview]
Message-ID: <CAJ0EP41YAG8=MiMUAEp=O8d9KNGpcpoarzP6Fa4zN=BhZJX5nw@mail.gmail.com> (raw)
In-Reply-To: <20120929224625.0e2c5ba3@pomiocik.lan>
On Sat, Sep 29, 2012 at 4:46 PM, Michał Górny <mgorny@gentoo.org> wrote:
> Hello,
>
> Right now we have two different ways of 'wrapping' Python scripts
> 'converted' for various Python implementations. One of them
> is the wrapper script installed by python.eclass, the other symlinking
> done by python-distutils-ng.eclass.
>
> I would like to ask you which one do you consider better, and thus
> which one should I use for python-r1/distutils-r1.
>
Of the choices, the wrapper idea (option 1) would be my preference.
Functionality-wise, it is closest to what we have with the generated
wrappers.
The symlink option sucks given the way eselect python works.
Another problem with option 3 (generic shebangs) is how to decide
which version of the script should be the one installed with a generic
shebang. It is possible that a package may run 2to3 as one of the
installation steps, which would mean that you would not have a script
that would work in both python2 and python3.
next prev parent reply other threads:[~2012-09-30 3:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-29 20:46 [gentoo-python] Wrapping scripts for multiple Python implementations: executable wrapper or symlinks? Michał Górny
2012-09-30 3:42 ` Mike Gilbert [this message]
2012-09-30 5:21 ` Ben de Groot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ0EP41YAG8=MiMUAEp=O8d9KNGpcpoarzP6Fa4zN=BhZJX5nw@mail.gmail.com' \
--to=floppym@gentoo.org \
--cc=gentoo-python@lists.gentoo.org \
--cc=mgorny@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox