Patch for check_version_conflict to eliminate spurious UserWarnings

Create issue
Issue #134 resolved
Van Lindberg created an issue

I frequently symlink packages into my virtualenvs so that I only need to manage one copy. When one of those packages imports pkg_resources, though, the use of the normalize_path function in check_version_conflict creates a spurious warning as follows:

import pkg_resources /home/pm/projects/processmechanics/lib/python2.5/site-packages/pygments/ UserWarning: Module emailconfirmation was already imported from /home/pm/projects/processmechanics/lib/python2.5/site-packages/emailconfirmation/init.pyc, but /home/pm/projects/processmechanics/lib/python2.5/site-packages is being added to sys.path

Attached are two patches, one for tip, one for 0.6-maintenance, that suppress this warning if the the apparent path (not just the normalized path) match.

Comments (2)

  1. Log in to comment