Bugs similar to this one were filed for python 2.7 and python 3. There
they were fixed by removing those files. They could be fixed for this
package in the same way. Is it because python 2.6 is about to be removed
anyway that this didn't happen?

Attachment: signature.asc
Description: Digital signature



Reply via email to