It is possible, but in practice there are some complications.

There is not an established way to map packages to files they install, so it’d be very difficult to answer the generic question “is there another package that install the same things as mine does” (except you crawl the whole PyPI). Here’s a similar request:

It is more plausible, on the other hand, when given two packages, to answer whether they would install conflicting files. This is still complicated by the fact that can do literally anything, and there is no theoretical way to be 100% sure until you actually install it, but it is possible to make a (very) educated guess via wheels. Each .whl archive contains a RECORD file that lists files to copy, so you can compare them to know whether conflicts exist.


On 19/2/2019, at 20:07, Robin Becker <> wrote:

Is there a way for a package to recognize that its content clashes with that of another package? This can happen when a package becomes unmaintained and another differently named package takes over with perhaps clashing modules/__package__ paths.
Robin Becker
Distutils-SIG mailing list --
To unsubscribe send an email to
Message archived at