It's turned out that this issue is caused by outdated *.pyc files. I
have the same issue after upgrading from Hardy to Inprepid. But, after
running python in root (sudo python -c 'import matplotlib'), which will
regenerate *.pyc files after checking timestamp, the problem disappear.
- Michael
--
yeah, I confirmed this on another machine upgraded from Hardy to
Intrepid. The warning is caused by outdated *.pyc files.
It seems that the current manner to install/remove python libraries has
potential issue, especially during system upgrading. Since some python
packages' *.pyc files are generat
look this thread
https://bugs.launchpad.net/ubuntu/+source/matplotlib/+bug/299381/comments/5,
this issue has workaround or temporary fixing method.
--
Python: importing pytz triggers warning
https://bugs.launchpad.net/bugs/281991
You received this bug notification because you are a member of Ubun
it seems this issue isn't solved fundamentally. Look this
https://bugs.launchpad.net/ubuntu/+source/matplotlib/+bug/299381/comments/5.
The issue should be caused by an incomplete cleanup.
--
cannot get it working on 8.10 intebid ibex (beta)
https://bugs.launchpad.net/bugs/283267
You received this
I am experiencing the same issue, but with python-pip instead of python-
pip3. Also on Ubuntu 16.04 and have python-pip 8.1.1-2 installed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579196
Title:
It's because that plugin (dragonegg) is built against 4.5.3,which
mismatches the gcc version (4.5.4). Just rebuild dragonegg on 11.10
solve this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/712
ignore the last post, it just remove the warning "Potential incompatible
plugin version. GCC: 4.5.3. Expected: 4.5.4" but still cannot emit bc
file.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/712199
ok, I see the difference, it's not bug at all. as dragonegg uses
different option to trigger LLVM IR generation. You need use '-flto' to
generate LLVM IR instead of the previous '-emit-llvm'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
