Re: numpydoc 1.6.0 available on salsa

[Chiara Marmo]

Dear list,

upstream kindly fixed the failing test in numpydoc for python 3.12 [1][2]
and I have patched the 1.6.0 version
Still autopkgetest is failing [3] because of an obsolete version of
python3-tabulate.
This is also stopping the upgrade of pandas [4].
Tabulate has been updated on salsa but not uploaded yet.

Is someone with upload rights available to upload tabulate?
This will help a lot

Thank you very much for your attention.

Best,

Chiara


[1] https://github.com/numpy/numpydoc/issues/512
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056431
[3] https://salsa.debian.org/python-team/packages/numpydoc/-/jobs/5136537
[4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051234


On Sun, Jan 7, 2024 at 8:51 PM Chiara Marmo  wrote:

> Apparently, I need some more time to understand why autopkgtest is
> failing...
> https://salsa.debian.org/python-team/packages/numpydoc/-/jobs/5128447
>
> Chiara
>
> On Sun, Jan 7, 2024 at 7:02 PM Chiara Marmo 
> wrote:
>
>> Dear list,
>>
>> I have uploaded to salsa numpydoc 1.6.0.
>> The new upstream version removes setup.py: rules and control are updated
>> accordingly.
>>
>> I have xfailed the failing test [1] and confirmed the failure upstream
>> [2].
>>
>> Let me know if some else is needed.
>> Thanks for your attention,
>> best,
>>
>> Chiara
>>
>> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056431
>> [2] https://github.com/numpy/numpydoc/issues/512
>>
>> --
>> GPG Key ID: ed25519/7611FA19766900CD
>> Fingerprint FD45 A232 211E DE9F 23E9  DDD5 7611 FA19 7669 00CD
>>
>

Re: Breaking changes in pytest 8

[Julian Gilbey]

Hi Timo,

Please can we hold back on uploading pytest 8 to unstable until the
current Python 3.12 transition is complete?  It is entirely possible
that several of the packages that currently break with pytest 8
already have newer upstream versions that address these issues, but
it's probably not wise to mix that in with the current transition.

Best wishes,

   Julian

On Mon, Jan 08, 2024 at 11:32:29PM +0100, Timo Röhling wrote:
> Hi,
> 
> I recently uploaded the pre-release pytest 8.0.0~rc1 to experimental as an
> early warning for the breaking changes which typically happen on major
> version bumps.
> 
> I've attached a dd-list of packages which exhibit autopkgtest regressions
> [1], with the intent of MBF'ing (with separate announcement) once pytest 8
> is released.
> 
> Typically, packages will fail if they
> - have deprecation warnings of type PytestRemovedIn8Warning, or
> - assume a particular pytest stdout/stderr output which might have
> changed, or
> - rely on the precise order in which pytest collects tests,   especially the
> behavior of the pytest.Package collector.
> 
> Please refer to the upstream changelog [2] for a complete list of breaking
> changes.
> 
> 
> Cheers
> Timo
> 
> [1] https://qa.debian.org/excuses.php?experimental=1&package=pytest
> [2] https://docs.pytest.org/en/latest/changelog.html

Re: sentry-python

[Carsten Schoenert]

Hi,

this package was on my list for some time, I picked the recent upstream 
version and prepared a upload yesterday.

Looks good so far, should be migrate to testing in two days.

Am 08.01.24 um 18:43 schrieb Gregor Riepl:

Hi Eberhard,


Is anyone working on updating sentry-python
 to prevent autoremoval
due to #1058422 ?


I did some debugging/testing, because this bug affects our Cura
packages, but I didn't get very far.

The root of the problem is a change in the Python 3.12 logging library:
https://docs.python.org/3/library/logging.html#logrecord-attributes
  > Changed in version 3.12: taskName was added.

The unit tests in Debian's sentry-sdk can't cope with that.

However, it seems like upstream has already done the work to fix Python
3.12 compatibility: https://github.com/getsentry/sentry-python/issues/2480

So, it should suffice to upgrade to at least 1.34.0 (or better yet, the
latest 1.x release).

Regards,
Gregor



--
Regards
Carsten

Re: Breaking changes in pytest 8

[Louis-Philippe Véronneau]

On 2024-01-09 12:45, Julian Gilbey wrote:

Hi Timo,

Please can we hold back on uploading pytest 8 to unstable until the
current Python 3.12 transition is complete?  It is entirely possible
that several of the packages that currently break with pytest 8
already have newer upstream versions that address these issues, but
it's probably not wise to mix that in with the current transition.


Agreed! There currently a lot of instability caused by 3.12 transition 
and waiting a little bit would certainly make things easier to deal with :)


--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄

Re: sentry-python

[Eberhard Beilharz]

Great!

Thanks,
    Eberhard

Carsten Schoenert wrote on 2024-01-09 18:57:

Hi,

this package was on my list for some time, I picked the recent 
upstream version and prepared a upload yesterday.

Looks good so far, should be migrate to testing in two days.

Am 08.01.24 um 18:43 schrieb Gregor Riepl:

Hi Eberhard,


Is anyone working on updating sentry-python
 to prevent autoremoval
due to #1058422 ?


I did some debugging/testing, because this bug affects our Cura
packages, but I didn't get very far.

The root of the problem is a change in the Python 3.12 logging library:
https://docs.python.org/3/library/logging.html#logrecord-attributes
  > Changed in version 3.12: taskName was added.

The unit tests in Debian's sentry-sdk can't cope with that.

However, it seems like upstream has already done the work to fix Python
3.12 compatibility: 
https://github.com/getsentry/sentry-python/issues/2480


So, it should suffice to upgrade to at least 1.34.0 (or better yet, the
latest 1.x release).

Regards,
Gregor





OpenPGP_0xE9140597606020D3.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Re: Breaking changes in pytest 8

[Timo Röhling]

Hi Julian,

* Julian Gilbey  [2024-01-09 17:45]:

Please can we hold back on uploading pytest 8 to unstable until the
current Python 3.12 transition is complete?
Sure! I'll keep it in experimental, and we can check what still 
needs fixing after the Python 3.12 dust has settled.



Cheers
Timo

--
⢀⣴⠾⠻⢶⣦⠀   ╭╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling   │
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄   ╰╯


signature.asc
Description: PGP signature