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

Daniele Tricoli eriol at mornie.org
Wed May 6 22:08:12 UTC 2015


Hello porters,

On Thursday 16 April 2015 18:06:13 Paul Tagliamonte wrote:
> I'd love to swap dput(1) to use Python 3 out of the box :)

WIP is here: https://github.com/eriol/dput-ng/tree/py3-port 

I have already tested and fixed the only Python 3 incompatibility[¹]
but I need a clarification: you are talking about swap dput to use
Python 3, this mean can I simply ship Python 3 versions of dcut,
dirt and dput inside package dput-ng? I'm asking because right now
I build python-dput both for Python 2 and Python 3.
At first I tought we need to ship both Python 2 and Python 3 versions,
but reading again the above sentence made me think I'm probably
misunderstanding.

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.

What do you think/suggest?

Many thanks!

Kind regards,

[¹] https://github.com/eriol/dput-ng/commit/395bc429bc6f2acb0cb9581a8f3927e97c4d0db4

-- 
 Daniele Tricoli 'Eriol'
 https://mornie.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/py3porters-devel/attachments/20150507/5ad66dd1/attachment-0001.sig>


More information about the py3porters-devel mailing list