Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: Christoph Biedl Newsgroups: linux.debian.maint.python Subject: Re: Namespace conflict for python-magic Date: Fri, 27 Oct 2017 21:50:02 +0200 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Fri Oct 27 19:49:58 2017 Old-Return-Path: X-Amavis-Spam-Status: No, score=-12.01 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, PGPSIGNATURE=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -6.1 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="cHMo6Wbp1wrKhbfi" Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) X-Mailing-List: archive/latest/15348 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/1509133304@msgid.manchmal.in-ulm.de Approved: robomod@news.nic.it Lines: 72 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python X-Original-Date: Fri, 27 Oct 2017 21:49:31 +0200 X-Original-Message-ID: <1509133304@msgid.manchmal.in-ulm.de> X-Original-References: <20170904174256.40241925@monsterix.mbehrle.de> <1504545692@msgid.manchmal.in-ulm.de> <20170905130017.1eb29221@monsterix.mbehrle.de> <1504628090@msgid.manchmal.in-ulm.de> <20170906102348.6587419c@monsterix.mbehrle.de> <20171005120116.3a92221a@monsterix.mbehrle.de> <1507271435@msgid.manchmal.in-ulm.de> <20171006092445.2f75350c@monsterix.mbehrle.de> Xref: csiph.com linux.debian.maint.python:9965 --cHMo6Wbp1wrKhbfi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable [ I'm not lost, just way too occupied with other issues, sorry ] Mathias Behrle wrote... > * Christoph Biedl: " Re: Namespace conflict for python-magic" (Fri, 6 Oct= 2017 > 08:34:04 +0200): >=20 > > In order to control the transition, I've filed in ITP (intent to > > package) for Adam's python-magic as https://bugs.debian.org/877849 >=20 > Did I misunderstand > | Ideally the upstream file package would take it over. > ? >=20 > Perhaps a little bit early, because we didn't see Adams solution, but I w= ould > like to understand the goals. Am I right that the intentions are >=20 > - Add a compatibility layer to python-magic[file] to support the feature = set of > python-magic[pypi] > - Provide in some way on Pypi the same featureset for file-magic and > python-magic As I understand, Adam will provide a [file] compatibility layer to python-magic[pypi]. Then there'll be no longer a need to ship python-magic[file], and eventually [file] upstream will drop it anyway. > If this would be the case, in my understanding there wouldn't be any need= for an > ITP or transition, but just the possibility for (Debian) packages needing > python-magic[pypi) to use the then compatible python-magic[file]. My goal is to have just one python-magic package that is usable for applications written for both, [file] and [pypi]. Assuming this will come from Adam[pypi], I filed the ITP. But it's all about the goal, not about how it's technically achieved. Hope this made things a bit more clear. Christoph --cHMo6Wbp1wrKhbfi Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJZ843LAAoJEMQsWOtZFJL9WuEQANriKoX6yMuQRpPOctitGxn7 19v7cxT0ioJb8U5SpnfVy8Vc11pBkcw1BsdKypsLrD9VLhRHhq9/iRBmjPKEV7/k +FrNoU5Gt17Dm9rFnivZXeDVpfwwDb1PE9fNdbw5mfEvmhFY9mQWOY2ZffoFOety ceI6j9AqBR8o1E//ETv8IJgcYIBKe3ydfXXm8qiUdgQQFphc1xoDz0lZrYoPstQ3 4g9nxkHPzTYL7Bpq22tvg1RJiJ4lIYQ9xAuOZFsHOhxLPb2y2unsGRHbC5m9lR8B GAEANV2Kebr9Xg8nO7e+iNQaCqivD9k7Nm0hTkHwkU0THI2v8mQMND6HHzGePGlV lqnl81sA1BoEicEVrjATm9g+yx259YZxAbwqkorGmRbxfCcwi4iqDP8YqiDkHZP2 CLZtJigELE7jOe29Jvl4o9OAIZXbWZ4URJGUBYkJmm0ZKsd/0RekhqSES4f7pXul Dg51mzE3iWh+h56zbJmlUzaBQG9bOCn616bU+EtwXc0t+1nu2Tn0u9q4yQP80bwO NPyQivSYEBocwdEkfwr7L9KRhab8pSGhIV7RGs2xBxpY+cO4QkCGRDWfCUlWl9NB jnToGrwJzlbBlyMRSHLXANJV0gesd2fIqGlwRKbpYDVkUH5WkQl+q8fTrRQWhyDj BSUkwEsKiLc3G73uxXH+ =2TP0 -----END PGP SIGNATURE----- --cHMo6Wbp1wrKhbfi--