Comment 10 for bug 1853809

If you look at
https://code.launchpad.net/~duplicity-team/+recipe/duplicity-daily-dev you
will see that, as released, Bionic, Disco, Eoan, and Focal all pass without
deprecation errors.

Are we testing in the same environment?

Are you patching the code before testing?

On Mon, Jan 6, 2020 at 11:31 AM Kenneth Loafman <email address hidden> wrote:

> Giving up on search for kenneth-loafman as reporter. Can't find anything
> with LP Search All.
>
> Once this set of builds finish on duplicity-daily-dev, I'll change back to
> testing after build. I'm not seeing any deprecation warnings and I'm
> testing up to py38.
>
>
> On Mon, Jan 6, 2020 at 3:00 AM Sebastien Bacher <email address hidden> wrote:
>
>> @Kenneth, can you give the reference to that ubuntu-builder bug you
>> mentioned? Turning off the testsuite seems suboptimal...
>>
>> --
>> You received this bug notification because you are subscribed to
>> Duplicity.
>> https://bugs.launchpad.net/bugs/1853809
>>
>> Title:
>> Tests fail with python 3.8 due to deprecation warnings
>>
>> Status in Duplicity:
>> Fix Released
>>
>> Bug description:
>> The issue has been reported to Debian and is also impacting Ubuntu
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945423
>>
>> The warnings are
>> 'DeprecationWarning: PY_SSIZE_T_CLEAN will be required for '#' formats'
>>
>> These were introduced by https://bugs.python.org/issue36381 to warn
>> about an upcoming Python C API change. The meaning of PY_SSIZE_T_CLEAN
>> is described in https://python.readthedocs.io/en/stable/c-api/arg.html
>> #strings-and-buffers.
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/duplicity/+bug/1853809/+subscriptions
>>
>