Perhaps something to do with where the package is installed? Maybe pkg_resources doesn't know how to handle all the unconventional package locations created by debian's python policy.
Perhaps something to do with where the package is installed? Maybe pkg_resources doesn't know how to handle all the unconventional package locations created by debian's python policy.