I think that such a method would be fragile. I don't think a solution that requires maintainers to manually review code from new upstream releases to adjust dependencies is adequate. To do such a thing we'd need a tools to search the code and generate proper dependencies. I didn't think much on design though. I'm open to suggestions.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
