From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: python2-docutils (0.13.1-2 version) missing scripts
Date: Mon, 31 Jul 2017 01:16:00 -0000 [thread overview]
Message-ID: <1156c4a6-4ffa-b55d-9844-9f17a16d37df@cornell.edu> (raw)
In-Reply-To: <CA+fGtfA4+rrt21xtVaGwmmVtBowdDRcmxrA-5S7DRQZc0x9p+w@mail.gmail.com>
On 7/28/2017 7:55 PM, Daniel Fort wrote:
> Seems like a pay Peter to pay Paul situation. I was hesitant to use
> python3-docutils but it turns out that it doesn't force you into
> python3. Why not just do a python-docutils package to avoid confusion?
> Aren't they just scripts that can run under either version of python?
The scripts from python3-docutils have a shebang line that specifies
python3. If you invoke them by name (as opposed to 'python <script
name>'), they will be run by python3. It would be possible to package
both versions by including the python version as part of the name, as is
done with easy_install-2.7 and easy_install-3.6, for a good reason. But
I'm not aware of any such good reason to go to that trouble for the
docutils scripts.
See
https://fedoraproject.org/wiki/Packaging:Python#Avoiding_collisions_between_the_python_2_and_python_3_stacks
for a detailed discussion of how this issue is handled by Fedora. In
particular:
"If the executables provide the same functionality independent of
whether they are run on top of Python 2 or Python 3, then only the
Python 3 version of the executable should be packaged. Transitioning
from python2 to python3 is left to individual package maintainers...."
Ken
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-07-30 17:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-30 17:56 Daniel Fort
2017-07-30 19:54 ` Brian Inglis
2017-07-31 1:16 ` Ken Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-07-21 1:01 Daniel Fort
2017-07-22 15:16 ` Ken Brown
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=1156c4a6-4ffa-b55d-9844-9f17a16d37df@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).