On Sun, Apr 19, 2020 at 1:36 PM Debian Bug Tracking System <ow...@bugs.debian.org> wrote: > > This is an automatic notification regarding your Bug report > which was filed against the python3-all package: > > #958166: python3-all: python3 can't import gmpy2 > > It has been closed by Scott Kitterman <deb...@kitterman.com>. > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Scott Kitterman > <deb...@kitterman.com> by > replying to this email. > > > -- > 958166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958166 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > > > > ---------- Forwarded message ---------- > From: Scott Kitterman <deb...@kitterman.com> > To: 958166-d...@bugs.debian.org > Cc: 958...@bugs.debian.org > Bcc: > Date: Sun, 19 Apr 2020 12:32:31 +0000 > Subject: Re: [Python-modules-team] [critical] #958166 - python3-all has had > python3.7 removed > Alternately, you could just update python3-gmpy2 to the latest version of the > package, which is built to support python3.8: > > https://packages.debian.org/sid/amd64/python3-gmpy2/filelist > > Python3.7 is no longer supported in Debian Unstable and Testing and will be > removed shortly.
this is a serious mistake. did you not read what i wrote? did you not learn from the lesson of ubuntu when it made the same mistake, with apt depending on the version that was removed, at the time? > What you are observing is a perfectly normal transition to a newer version of > python3. If such things bother you this much, you should probably stick to a > Debian Stable release. that's absolutely impossible. i cannot believe that you are seriously asking that people quotes stick to debian stable quotes as a quotes solution quotes. did you not read that i have over 5 million source code files on this system? did you imagine that as a software developer i would be *able* to quotes use debian stable quotes? software developers *need* to be able to use debian/testing, if debian/stable does not do what they need. expecting them to compile up packages and custom-maintain vast swathes of packages from source in /usr/local is hopelessly unrealistic and is precisely why distros exist in the first place. do you not understand how seriously cavalier and unthinking your response is? > This is the 7th time we've done this for Python3. that would explain why i have encountered problems like this in the past. question. was a version removed that happened to also be the "stable" version? did you not read what i wrote? > It happens once or twice a release cycle. > There's no bug at all here. that is false: what it means is that you do not understand the serious consequences of the decision that's being made. you have completely failed to acknowledge what i wrote, choosing instead to selectively quote your own past experience. not only that, you've closed this critical bugreport without a wider consultation. why did you do that? l.
