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

Re: Dealing with renamed source packages during CVE triaging

Brian May <bam@debian.org> writes:

> So we could write a script, lets say:
> bin/list-potential-packages-affected-by-code-copies

In investigating the possibility of this, I noticed the scripts in
lib/python/sectracker use legacy python coding standards.

I have updated these files on my local box to work with Python 3, but
refraining from pushing for now, because of the possibilty I might break
something important.

Is Python 2 compatability still required?
Brian May <bam@debian.org>

Reply to: