Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #9785

Re: Namespace conflict for python-magic

From Christoph Biedl <debian.axhn@manchmal.in-ulm.de>
Newsgroups linux.debian.maint.python
Subject Re: Namespace conflict for python-magic
Date 2017-09-05 18:30 +0200
Message-ID <umoTD-55T-11@gated-at.bofh.it> (permalink)
References <um26J-7EI-15@gated-at.bofh.it> <um3vQ-8os-31@gated-at.bofh.it> <umjTZ-1V1-33@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

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
> >     <CAJTao09xATQYZ3qR-4CR+oOrrqB_W=kYUJV8esOe4b3bdA5nwA@mail.gmail.com>
> >     <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).

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Namespace conflict for python-magic Mathias Behrle <mbehrle@debian.org> - 2017-09-04 18:10 +0200
  Re: Namespace conflict for python-magic Scott Kitterman <debian@kitterman.com> - 2017-09-04 18:20 +0200
  Re: Namespace conflict for python-magic Christoph Biedl <debian.axhn@manchmal.in-ulm.de> - 2017-09-04 19:40 +0200
    Re: Namespace conflict for python-magic Mathias Behrle <mbehrle@debian.org> - 2017-09-05 13:10 +0200
      Re: Namespace conflict for python-magic Christoph Biedl <debian.axhn@manchmal.in-ulm.de> - 2017-09-05 18:30 +0200
        Re: Namespace conflict for python-magic Mathias Behrle <mbehrle@debian.org> - 2017-09-06 10:30 +0200
          Re: Namespace conflict for python-magic Adam Hupp <adam@hupp.org> - 2017-10-03 20:30 +0200
            Re: Namespace conflict for python-magic Mathias Behrle <mbehrle@debian.org> - 2017-10-05 12:20 +0200
              Re: Namespace conflict for python-magic Christoph Biedl <debian.axhn@manchmal.in-ulm.de> - 2017-10-06 08:40 +0200
                Re: Namespace conflict for python-magic Mathias Behrle <mbehrle@debian.org> - 2017-10-06 09:30 +0200
                Re: Namespace conflict for python-magic Christoph Biedl <debian.axhn@manchmal.in-ulm.de> - 2017-10-27 21:50 +0200
              Re: [tryton-debian] Namespace conflict for python-magic Mathias Behrle <mathiasb@m9s.biz> - 2017-10-27 14:50 +0200
                Re: [tryton-debian] Namespace conflict for python-magic Adam Hupp <adam@hupp.org> - 2017-12-04 21:20 +0100
                Re: [tryton-debian] Namespace conflict for python-magic Mathias Behrle <mbehrle@debian.org> - 2017-12-04 23:10 +0100
                Re: [tryton-debian] Namespace conflict for python-magic Mathias Behrle <mbehrle@debian.org> - 2018-01-01 15:10 +0100
                Re: [tryton-debian] Namespace conflict for python-magic Christoph Biedl <debian.axhn@manchmal.in-ulm.de> - 2018-01-06 20:30 +0100
                Bug#877849: [tryton-debian] Namespace conflict for python-magic Christoph Biedl <debian.axhn@manchmal.in-ulm.de> - 2018-01-08 12:00 +0100
                Bug#877849: [tryton-debian] Namespace conflict for python-magic Christoph Biedl <debian.axhn@manchmal.in-ulm.de> - 2018-01-08 13:30 +0100
                Bug#877849: [tryton-debian] Namespace conflict for python-magic Adam Hupp <adam@hupp.org> - 2018-01-15 07:50 +0100
                Bug#877849: [tryton-debian] Namespace conflict for python-magic Christoph Biedl <debian.axhn@manchmal.in-ulm.de> - 2018-01-16 20:20 +0100
                Bug#877849: [tryton-debian] Namespace conflict for python-magic Christoph Biedl <debian.axhn@manchmal.in-ulm.de> - 2018-01-16 20:50 +0100
                Bug#877849: [tryton-debian] Namespace conflict for python-magic Christoph Biedl <debian.axhn@manchmal.in-ulm.de> - 2018-01-14 21:40 +0100
                Bug#877849: [tryton-debian] Namespace conflict for python-magic Mathias Behrle <mbehrle@debian.org> - 2018-01-14 23:10 +0100
                Bug#877849: [tryton-debian] Namespace conflict for python-magic Christoph Biedl <debian.axhn@manchmal.in-ulm.de> - 2018-01-15 09:40 +0100
                Bug#877849: [tryton-debian] Bug#877849: Namespace conflict for python-magic Mathias Behrle <mbehrle@debian.org> - 2018-01-19 19:10 +0100
                Re: [tryton-debian] Bug#877849: Namespace conflict for python-magic Christoph Biedl <debian.axhn@manchmal.in-ulm.de> - 2018-01-21 17:30 +0100
      Re: Namespace conflict for python-magic Christoph Biedl <debian.axhn@manchmal.in-ulm.de> - 2017-09-05 18:50 +0200
        Re: Namespace conflict for python-magic Mathias Behrle <mbehrle@debian.org> - 2017-09-06 11:00 +0200
  Bug#877849: ITP: python-magic -- A python wrapper for libmagic Christoph Biedl <debian.axhn@manchmal.in-ulm.de> - 2017-10-06 08:40 +0200

csiph-web