Have replied to you from the respective bugs.
Thank you,
Ana
On Tue, Nov 14, 2017, at 10:36 PM, Ghislain Vaillant wrote:
> What about the patches fixing the other two bugs affecting yapf?
> Please consider checking the BTS.>
> Ghis
>
>
> Le 14 nov. 2017 22:25, "Ana C. Custura" <a...@netstat.org.uk> a écrit :>> Hi
> Ghis,
>>
>> Thank you for the reply. There is a package on mentors that addresses>> both
>> this bug (88958) and the split (879196) bug you raised. I am
>> waiting for my mentor to review it before uploading.
>>
>> Ana
>>
>> On Tue, Nov 14, 2017, at 08:59 AM, Ghislain Vaillant wrote:
>> > Thank you Matthias for raising this issue. CC'ing the maintainer
>> > in case>> > she's not subscribed.
>> >
>> > On Mon, 6 Nov 2017 11:52:00 +0100 Matthias Klose <d...@debian.org>
>> > wrote:>> > > Package: yapf3
>> > > Version: 0.17.0-1
>> > > Severity: serious
>> > > Tags: sid buster
>> > >
>> > > yapf3 explicitly depends on python3.5. One mistake certainly is
>> > > the b-d on>> > > python3-all, which is wrong for an application-only
>> > > package.
>> >
>> > The application is not compliant with the Python packaging
>> > guidelines.>> > The public modules should be split from the application
>> > package. See>> > #879196 for a discussion about it.
>> >
>> > I have proposed a patch offline but it has yet to be applied.
>> > Fixing>> > #879196 will transitively fix the issue you just reported.
>> >
>> > > And if this package is application-only, why ship both Python2
>> > > and Python3 vesions?>> >
>> > It is nether application-only, nor Python 3 specific.
>> >
>> > Cheers,
>> > Ghis
