Spurious "Module ... has already been imported" warnings
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pygments (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Upon upgrading to lucid, I noticed some bzr commands throwing warnings. Traced to a minimal repro case:
$ python -c 'import pygments.plugin'
Which warns:
/usr/lib/
import pkg_resources
Which seems confusing. Therefore I patched pkg_resources.py to display the actual strings being compared, which gave:
/usr/lib/
import pkg_resources
Therefore it can be seen that the code is being upset by the /usr/lib/pymodules vs. /usr/share/pyshared split layout with symlinks. I'm unsure what to do about it though.
ProblemType: Bug
Architecture: i386
Date: Sat Dec 26 20:18:41 2009
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
Package: python-
PackageArchitec
ProcEnviron:
LC_COLLATE=C
PATH=(custom, user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: distribute
Tags: lucid
Uname: Linux 2.6.32-9-generic i686
affects: | distribute (Ubuntu) → pygments (Ubuntu) |
Changed in pygments (Ubuntu): | |
status: | New → Confirmed |
This would seem to have something to do with pygments.__file__ being the path to the .pyc file (which is not a symlink) on karmic, but being the path to the .py file (which is a symlink) on lucid.