Path: csiph.com!eternal-september.org!feeder.eternal-september.org!aioe.org!bofh.it!news.nic.it!robomod From: Christoph Biedl Newsgroups: linux.debian.maint.python Subject: Re: Namespace conflict for python-magic Date: Tue, 05 Sep 2017 18:30:01 +0200 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Tue Sep 5 16:24:52 2017 Old-Return-Path: X-Amavis-Spam-Status: No, score=-10.981 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DIGITS_LETTERS=1, FVGT_m_MULTI_ODD=0.02, LDO_WHITELIST=-5, PGPSIGNATURE=-5, RP_MATCHES_RCVD=-0.001] 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="ZYOWEO2dMm2Af3e3" Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) X-Mailing-List: archive/latest/15167 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/1504628090@msgid.manchmal.in-ulm.de Approved: robomod@news.nic.it Lines: 111 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Tue, 5 Sep 2017 18:24:25 +0200 X-Original-Message-ID: <1504628090@msgid.manchmal.in-ulm.de> X-Original-References: <20170904174256.40241925@monsterix.mbehrle.de> <1504545692@msgid.manchmal.in-ulm.de> <20170905130017.1eb29221@monsterix.mbehrle.de> Xref: csiph.com linux.debian.maint.python:9785 --ZYOWEO2dMm2Af3e3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Mathias Behrle wrote... > * Christoph Biedl: " Re: Namespace conflict for python-magic" (Mon, 4 Sep 2017 > 19:38:56 +0200): > > The cleanest solution indeed was to bring both upstreams together and > > ask them to reconcile the APIs and eventually make one of the both > > implementations obsolete. As things happen such an attempt was started > > two years ago but appearently never came to a result.[1] > > Agreed, that this would be the cleanest solution, but as you say there is > little probability, that the two upstreams will work together to merge their > implementations. Still this should be tried first. Also, I'm not that pessimistic, see below. So let's bring the parties involved into the loop: Hello * Christos Zoulas for file(1), and * Adam Hupp for python-magic. A while ago, almost two years by now, there was a short discussion on the file(1) mailing list concerning a merge of the libmagic python bindings. In summary, Adam proposed to end the long-standing confusion[2], Christos agreed and suggested a possible solution[3]. After that however, nothing visible happened. But now I'd like to give that idea a push. Mostly since on the Debian Python mailing list (also in Cc:) a proposal was made to exchange python-magic in Debian, from the file(1) to the PyPi one. Wearing the maintainer's hat for file(1) in Debian, I opposed this for the sole reason this will break applications that rely on the file(1) version. Resolving this issue upstream will bring benefit for everybody, even at the risk of a bumpy but one-time only transition. What is the status of your project? Do you need some input, suggestions or other incentive to finish this project? Cheers, Christoph > > [1] The file mailing list server is currently down, so I cannot provide > > URLs. The Message-IDs are > > > > <20151020133008.9B79517FDAB@rebar.astron.com> > > Still down:(, If you could provide some content for me that would be nice. Certainly: [2] [ Adam: ] (...) | Sadly, this has led to regular confusion for our users. I'd be happy | to shutdown my version to avoid more confusion but it seems to be | fairly widely used (200k downloads from pypi last month). It also has | a number of fixes for various issues: libmagic bugs, thread safety, | support for other platforms, etc. | | I'd like to gauge interest in merging these bindings into a single | codebase. Specifically, this would mean: | | - merge magic.py from each package to produce something reasonably | close to API-compatible to both, with some methods marked as | deprecated where it makes sense. | - the merged package would live under the python-magic name in pypi | and in the `file` source distribution. | | I think this would be ideal for everyone involved, but wanted to gauge | your interest before I went to the trouble. (...) [3] [ Christos: ] | Sure, it would be nice for the users if there was a definitive | python package that had the best features from both. Someone recently | filed a bug report about it: http://bugs.gw.com/view.php?id=477. | Why don't you go ahead and merge them and I will copy the result | over mine, and put a link to your package in the file sources (or | even delete mine, and put a link to your package). --ZYOWEO2dMm2Af3e3 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJZrs+4AAoJEMQsWOtZFJL9RnoQAI6SbfMB3PWdc97FtE4t+GOO QIO0Oty9AGYsSELqebZT19FIOpSwIjOhckU39dIZ2VEG6AssL04Mn3mEczK8SKvj Xf8JqOQGGA9itKzLFgm5zjCt5+8fOlhSBjIj667jJ9ZQaY9U7hQm8DlmD/k4Lk/7 cfGr9uZ/kKTcd6sFTnvj50beAEueQpUeWZVuZJnFZ0JSmrK320Effy7usYWBAO5m B6T0uCOV2MLr3yUDDltvM5gpynK1GkDISJEdVRtFiE/nLAIaiVJ1SXld5BdM8DSX 0q/gVl9/UlX78A4l/tbGm2H44t9HrpHVBileTnrxF/tUS44e3Xn8vC5zKGaXCRa/ frtJzZhklwEY+idXQTlExVGhlc8ZjlrPCSMDyW4DtDQXZSwxNKe1LsVj/hpYVHT+ g00AwbDRC3+fOovm0J51t8LIVh061Wka98XZaAwTW6Xn7gGLdK2gg+e8Lj3sDHtS 8oi5TlRstRiWV15wtLgQ8b3CuNmqbloXn3GR0SJ/2+o/VNAJ1RtSp6ReF4bWUvKN 0p7eqoZmq0F19YTfy2AaeS/iQIKqBLGn+e2Avyie241IFXlZ/SzLdIc+Az3oy7mC KXL8uKbJENbx2Rjb2NfVzAEj7xgY8IdLajxT7uingwWr2W5ZUzw6uM6C9ilG+RS5 Mc394vEMEqQANuS7fG1X =B0+S -----END PGP SIGNATURE----- --ZYOWEO2dMm2Af3e3--