Hi Andrew and ftpmasters, Andrey Rahmatullin <w...@debian.org> writes:
> On Wed, Nov 24, 2021 at 04:18:23PM -0500, Nicholas D Steeves wrote:
[snip]
>>
>> Thank you for reminding me about this upstream thread. Yes, it's
>> definitely time that I post another follow-up message there.
>>
>> Could we please defer this removal until at least 2022-03-07 as a
>> reasonable compromise?
[snip]
> Hi Nicholas. This is now up to ftp-masters but I'll state my opinion on
> this.
> Out of 8 or so RM requests for Python FTBFS stuff not in testing that I
> filed yesterday this one was the hardest, but I decided to send it both
> because a maintainer can object to it and because removing a package even
> from sid is not the end of life for the package.
[snip]
> So on one hand I'm fine with keeping this package in sid if it provides
> some value to its users and will keep doing that when Python 3.10 is the
> default in sid, though the FTP/Release/Security teams may have another
> view on this as it FTBFS, and on the other hand I don't see a huge problem
> with removing it, especially if it doesn't work, as it can always be
> reinstated.
>
>> I'm also not sure what would be a sensitive way to broach a deadline
>> upstream.
> As mentioned above, I don't think this is necessary. What is necessary is
> fixing the RC bugs which can be done by the community.
>
Thanks for the rationale tip! I didn't mention the deadline I had in
mind anywhere else nor to anyone else.
With that date fast approaching, I decided it was time to test another
snapshot. elpy_1.35.0+48.g4248dcc-1 (unreleased in git) is much
improved. With Python 3.9 it now shows:
Ran 466 tests, 438 results as expected, 3 unexpected, 25 skipped (2022-02-26
15:12:25+0000, 46.147115 sec)
3 unexpected results:
FAILED elpy-pdb-debug-buffer-from-beginning-should-enter-pdb
FAILED elpy-profile-buffer-or-region-test-fail
FAILED elpy-profile-buffer-or-region-test-indir-failed
and with Python 3.10:
Ran 466 tests, 440 results as expected, 1 unexpected, 25 skipped (2022-02-26
15:53:30+0000, 34.279938 sec)
1 unexpected results:
FAILED elpy-pdb-debug-buffer-from-beginning-should-enter-pdb
The community is slow moving, but is making progress. I won't be able
to properly investigate the single failing test (down from hundreds
IIRC) relevant to bookworm before late March. Given the progress
upstream has made, I believe this bug may be closed, because the current
state of Elpy (on Salsa) is now a single failing test, where it was
hundreds with stalled upstream development before. If kept open, please
feel free to ping me in April if progress on the remaining issue appears
to have stalled.
Best,
Nicholas
signature.asc
Description: PGP signature
