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


Groups > linux.debian.user > #244841

Re: sparse dictionary

From The Wanderer <wanderer@fastmail.fm>
Newsgroups linux.debian.user
Subject Re: sparse dictionary
Date 2022-01-31 04:40 +0100
Message-ID <DLvHQ-7co-1@gated-at.bofh.it> (permalink)
References (2 earlier) <DLsAh-5k5-5@gated-at.bofh.it> <DLsTD-5qb-1@gated-at.bofh.it> <DLtG1-5Va-3@gated-at.bofh.it> <DLtG1-5Va-1@gated-at.bofh.it> <DLuLM-6wT-13@gated-at.bofh.it>
Organization This space intentionally left blank.

Show all headers | View raw


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

On 2022-01-30 at 21:07, Russell L. Harris wrote:

> On Sun, Jan 30, 2022 at 08:28:29PM -0500, Greg Wooledge wrote:

>> Well... according to packages.debian.org, dict-moby-thesaurus only
>> exists in oldstable and oldoldstable.  So, Debian 9 and 10.
>> 
>> <https://tracker.debian.org/pkg/dict-moby-thesaurus> shows the
>> dates it was removed from unstable and from testing.
>> 
>> <https://tracker.debian.org/news/1161371/removed-10-64-from-unstable/>
>> shows that it was removed because:
>> 
>> RoQA; dead upstream (10+ years); python2-only; no extrenal deps;
>> extremely low popcon
> 
> Thanks for taking the time to trace out the cause.  It truly is a
> sad loss.
> 
> I wish I knew enough about Python to know how much work it would
> take to make the data base compatible with Python 3 (or whatever
> dictionary currently is running on).  Meanwhile, it is back to
> Roget.

Speaking as someone who took a Python 2 codebase (moosic) that was being
dropped with the move to Python 3, and updated it to work with Python 3,
without having been more than can-read-it-well-enough familiar with
Python before that point:

It's entirely doable, but the degree of difficulty and amount of work
will depend on the specific codebase involved.

In my case, I started with the last Debian package version before the
removal, imported the source package into git, dropped the debian/
directory because that doesn't belong in the upstream codebase, ran the
'2to3' tool (from the package of the same name) against the codebase,
committed the result, and started doing "build" / run tests of the
updated code (including comparisons back and forth with the untouched
Python 2 version of the codebase).

Lots of things didn't work at first, but it only took me a day or so to
get it working far enough for a few of the program's features to be
functional, and another day or two to get the rest into shape. I've
since taken over as upstream maintainer, am working to get the package
back into Debian (although it's currently low project priority), and
have done a bit of work adding features and fixing bugs into the bargain.

The details in your case might be significantly different, but I assure
you that it *can* be done, it's just a matter of how opaque the codebase
is, and how many manual changes need to be made after what the 2to3
conversion tool does.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

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


Thread

sparse dictionary "Russell L. Harris" <russell@rlharris.org> - 2022-01-30 20:50 +0100
  Re: sparse dictionary Charlie <taoquester@gmail.com> - 2022-01-30 22:50 +0100
    Re: sparse dictionary "Russell L. Harris" <russell@rlharris.org> - 2022-01-31 01:20 +0100
      Re: sparse dictionary Greg Wooledge <greg@wooledge.org> - 2022-01-31 01:40 +0100
        Re: sparse dictionary Greg Wooledge <greg@wooledge.org> - 2022-01-31 02:30 +0100
          Re: sparse dictionary "Russell L. Harris" <russell@rlharris.org> - 2022-01-31 03:40 +0100
            Re: sparse dictionary The Wanderer <wanderer@fastmail.fm> - 2022-01-31 04:40 +0100
              converting Python2 to Python3 (was: sparse dictionary) Mike Kupfer <mkupfer@alum.berkeley.edu> - 2022-01-31 05:20 +0100
                Re: converting Python2 to Python3 The Wanderer <wanderer@fastmail.fm> - 2022-01-31 13:50 +0100
                Re: converting Python2 to Python3 Mike Kupfer <mkupfer@alum.berkeley.edu> - 2022-01-31 17:40 +0100
              Re: sparse dictionary "Russell L. Harris" <russell@rlharris.org> - 2022-01-31 06:20 +0100
                Re: sparse dictionary Charlie <taoquester@gmail.com> - 2022-01-31 06:50 +0100
                Re: sparse dictionary Polyna-Maude Racicot-Summerside <debian@polynamaude.com> - 2022-01-31 07:50 +0100
                Re: sparse dictionary The Wanderer <wanderer@fastmail.fm> - 2022-01-31 14:00 +0100
                Re: sparse dictionary Tixy <tixy@yxit.co.uk> - 2022-01-31 14:40 +0100
                Re: sparse dictionary The Wanderer <wanderer@fastmail.fm> - 2022-01-31 15:10 +0100
            Re: sparse dictionary Charlie <taoquester@gmail.com> - 2022-01-31 06:40 +0100
              Re: sparse dictionary Greg Wooledge <greg@wooledge.org> - 2022-01-31 13:40 +0100
          Re: sparse dictionary Polyna-Maude Racicot-Summerside <debian@polynamaude.com> - 2022-01-31 07:40 +0100
            Re: sparse dictionary David Wright <deblis@lionunicorn.co.uk> - 2022-01-31 17:50 +0100
        Re: sparse dictionary "Russell L. Harris" <russell@rlharris.org> - 2022-01-31 02:50 +0100

csiph-web