Path: csiph.com!news.freedyn.net!newsfeed.datemas.de!weretis.net!feeder4.news.weretis.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From: "Diego M. Rodriguez" <diego.plan9@gmail.com>
Newsgroups: linux.debian.maint.python
Subject: Re: Enabling Python bindings for jellyfish
Date: Thu, 31 Dec 2015 18:40:01 +0100
Message-ID: <qLPmF-7nK-9@gated-at.bofh.it>
References: <qKPyp-zX-1@gated-at.bofh.it> <qL5Wy-3oe-1@gated-at.bofh.it> <qL6fU-3vf-15@gated-at.bofh.it> <qL6IW-3H5-7@gated-at.bofh.it> <qL7bY-46z-7@gated-at.bofh.it> <qL7OF-4A4-7@gated-at.bofh.it>
Old-Return-Path: <diego.plan9@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="y0ulUmNC+osPPQO6"
Content-Disposition: inline
User-Agent: Mutt/1.5.23 (2014-03-12)
Approved: robomod@news.nic.it
Lines: 114
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:8034


--y0ulUmNC+osPPQO6
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Dec 29, 2015 at 02:07:05PM -0500, Paul Tagliamonte wrote:
> That won't solve the problem, since both will provide the python module
> jellyfish

Fair point indeed, and I fully agree that ideally the problem should be sol=
ved
at the python module level.

I'm wondering if you or other senior, more experienced developers could
suggest what would be the recommended solution for the namespace conflict,
taking into account:

a) DNA-jellyfish is an stablished Debian package since 2011 [1]
b) STR-jellyfish is on PyPI [2] since 2010 (version 0.1)
c) both packages started their Github repos around the same time (summer 20=
10)
d) both packages seem to be a bit "niche" (popcon stats for "jellyfish" [3]=
 and
"beets" [4], the package that would depend on STR-jellyfish, seem to hint t=
hat
they are both modestly used within Debian and cater to specific groups of
users)
e) other considerations I'm probably missing!

I would personally place a bit more weight on the fact that STR-jellyfish is
already on PyPI (based on the rationale that it is arguably the "de facto"
repository for Python packaging); but, again, I am relatively new to
Debian practices and arguing for keeping consistency within the Debian
repository seems reasonable to me as well.

Best regards,

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D644925
[2] https://pypi.python.org/pypi/jellyfish
[3] https://qa.debian.org/popcon.php?package=3Djellyfish
[4] https://qa.debian.org/popcon.php?package=3Dbeets

>=20
> On Tue, Dec 29, 2015 at 1:24 PM, Diego M. Rodriguez <diego.plan9@gmail.co=
m>
> wrote:
>=20
> > On Tue, Dec 29, 2015 at 12:56:20PM -0500, Scott Kitterman wrote:
> > > I think the respective maintainers should talk and then discuss with
> > their
> > > upstreams as the collision potential isn't just in Debian.
> >
> > I'm chiming in as the (prospective) maintainer of the ITP python-jellyf=
ish
> > package, just to note that I have discussed it with Andreas [1] and ful=
ly
> > agreed to rename "my" package. The choice of name was due to not being
> > aware
> > of the Python bindings on the existing DNA-jelyfish package (and in part
> > also
> > due to my inexperience on these matters), and I have contacted upstream
> > earlier today in the hopes of coming up with a good alternative name.
> >
> > I'd be happy to follow up on the discussion with upstream once I get a
> > reply,
> > in order to find out if he would be open to solving the conflict at a
> > "higher"
> > level.
> >
> > Best regards,
> >
> > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D806716#42
> > --
> > Diego M. Rodriguez
> > 36B3 42A9 9F2F 2CFB F79B  FF9B B6C4 B901 06BC E232
> >
> >
>=20
>=20
> --=20
> All programmers are playwrights, and all computers are lousy actors.
>=20
> #define sizeof(x) rand()
> :wq

--=20
Diego M. Rodriguez
36B3 42A9 9F2F 2CFB F79B  FF9B B6C4 B901 06BC E232


--y0ulUmNC+osPPQO6
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJWhWa4AAoJELbEuQEGvOIyw5UP/1qEpWuoGdODVqKFDw4mn8vT
U+i1tpypNiWklURTDia4bIDJdJG26nYUkFa+1h9fNnt5wdHVxMCUbqR0JCtK5YUw
nBcPMP0C8EhbdNQUUA4oEHn9jCpEYrXxSqpt4nD26k/Lhrp/Iay9A8gb6qzaz4gV
ZzB+l+jemRAH+dxLm5sACeqz89q32pJFfLdk/d64XeWN3ysrXow4GQOOlPvknpR6
OW93gBBrgaceReaUBD+aOpKkhYe02DotK0zVmfwpUzlY3mraSMvsmDrxn/9tt9v0
EE6SwFV1TufSbTuf4/rpkVy2P+eYtjfzCyGPquMxV3F5XJ3Aqm4bXoYDdeCAfaw6
uIljtRSN8kYLdOLTBd3Wa5ficWGWTZYuZy6ApkPodJic7pqfIRZ7+ydhk7fIuzvM
zoSgBmxCcGZv34XEqPF8yUy1uE/9d2Ml0Iqj6v5zHGnnSmxRyH5VEKTm+R96ZExy
RFjUOrUT2IoH2njvfz06H6zdLMapCJRVbbjV/cg+31qTFg6jmP16JZzDyMlZcN89
14wInM3gW5jxAheYrKCM3hQGonbCZm01uC9TpPObbXQsq0Ifpqb/SpUZZYJH+a6a
mzbnDgPB/5a5Mna9Je4UCzQ3HvqCLw9rEOCfEip5UnMTJtkHGrGhJwnQSUgYTfkZ
d0ejL2cHLCuon/tGVgWM
=bYmT
-----END PGP SIGNATURE-----

--y0ulUmNC+osPPQO6--