[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#988421: unblock: pypy3/7.3.4+dfsg-2



Control: tags -1 moreinfo

Hi Stefano,

[Your report didn't make it to the list due to the large debdiff].

On Wed, 12 May 2021 11:24:53 -0400 Stefano Rivera <stefanor@debian.org>
wrote:
> Please unblock package pypy3
> 
> This is a long-shot request.

Boo, I hate those (jesting, but partially serious, see [1] ).

> [ Reason ]
> 
> Updating bullseye to pypy3 7.3.4, targeting Python 3.7 instead of 3.6
> will fix a bug that I've been trying to get my head around for a couple
> of months (on and off): #962654.
> 
> I am unable to come up with a reasonable minimal patch for this bug.
> 
> [ Impact ]
> Debian's pip won't correctly build pep517 packages with the Python 3.6
> stdlib. The way we de-bundle the pep517 library breaks its use with pip.
> Upstream implemented a fix for this (which is why it only affects pypy,
> not cpython), but that fix requires the 3.7 stdlib.

As I have zero experience with pip, how much of use cases are we talking
about here, 0%, 100%, somewhere in the middle? Is this bug RC in the
sense that it makes the package unusable, or is it "just" breaking a
minor set of valid uses? Would it be (remotely) acceptable to "just"
mention this in the Release Notes?

> The workaround is for the user to upgrade pip to the latest upstream
> version, after creating a pypy3 virtualenv. That will have a bundled
> pep517 module that works correctly.

Do you need the current pip for that?

> [ Tests ]
> We run the upstream test suite for pypy (but ignore the results, because
> there are always known failures.

I guess you could manually conclude something from (the *delta* of) the
failures? What did you conclude?

> Getting to the bottom of that is a job
> for another day...
> 
> [ Risks ]
> This is a new upstream point release, and a switch from the 3.6 to 3.7
> branches of stdlib. That comes to a 12MiB debdiff...
> 
> pypy3 is a leaf package.
> The new version has been in experimental, and Ubuntu impish, with no
> reported issues.
> 
> pypy is not a leaf package. We could update them both - I generally keep
> pypy and pypy3 in step with each other, but there's no specific need to.

I propose to not even think about this.

> unblock pypy3/7.3.4+dfsg-2

Paul

[1] https://release.debian.org/bullseye/FAQ.html intro

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


Reply to: