[py3porters-devel] [Needs Port] dput-ng

[Barry Warsaw]

On May 07, 2015, at 12:08 AM, Daniele Tricoli wrote:

>So, to recap, I see the following scenarios:
>1) build only Python 3 version;
>2) build both Python 2 and Python 3 (including scripts):
>   In this case, should I have to put dcut3, dirt3, dput3
>   inside dput-ng package and make it depends on both
>   Python 2 and Python 3?
>3) build python-dput and python3-dput packages but ship only
>   Python 3 version of dcut, dirt and dput inside dput-ng
>   package.
>
>I'm for scenario 1: it seems the right thing to do. I really don't like
>scripts ending with '3', but if we have to ship both versions (Python 2 and
>Python 3) I don't see any other possible option compared to scenario 2.
>Scenario 3 seems not useful since python-dput dependants is only dput-ng.

The general principle should be that leaf applications need only be shipped
for Python 3, but libraries can ship with support for both Python 2 and Python
3.

It's fine of course if upstream, the application continues to work for Python
2, and you can use tox to verify this, but in the archive, there's very little
need to ship both a Python 2 and 3 shebanged script.

There are a few exception, where the script has to work for one Python or the
other, e.g. pip.  But these should be rare and IMHO, it's better if they were
invoked with `$python -m script`.  That's not as convenient for people though
unfortunately.

(And yeah, I also dislike foo and foo3 versions of things. ;)

Cheers,
-Barry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/py3porters-devel/attachments/20150507/944f82fb/attachment.sig>