BackupGGCode / llvm-py

Python bindings for LLVM
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Bad module setup #2

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. I installed python-0.2.1 with some difficulty unrelated to this bug.
2. I tried the example python program. It failed because it couldn't find the 
module '_core'. 
Whoops!

I found that I could remove this bug by changing the top of llvm/core.py from

import ._core            # C wrappers
from _util import *     # utility functions

to 

import llvm._core as _core            # C wrappers
from llvm._util import *     # utility functions

Cheers! -Duane

Original issue reported on code.google.com by Bailey.D.R@gmail.com on 19 Jun 2008 at 12:41

GoogleCodeExporter commented 9 years ago
That's strange. llvm/core.py only does a "import _core" and not a "import 
._core".
The "." would make it relative, which is not what we want. Did you try with the
official .tar.bz2?

(Sorry for the late response; google does not seem interested in notifying me 
about
new issues logged.)

Original comment by mdevan.f...@gmail.com on 29 Jun 2008 at 4:33

GoogleCodeExporter commented 9 years ago

Original comment by mdevan.f...@gmail.com on 29 Jun 2008 at 5:49

GoogleCodeExporter commented 9 years ago
The example on the website is out of date to the example in the SVN. It causes 
an
error similar to this problem. The example in the SVN works without problem.

Original comment by jaros...@gmail.com on 22 Jul 2008 at 12:35

GoogleCodeExporter commented 9 years ago
Which versions of Python, LLVM and gcc are you using? On which OS? Which SVN 
revision
of llvm-py (and LLVM, if applicable)?

Thanks.

Original comment by mdevan.f...@gmail.com on 22 Jul 2008 at 2:14

GoogleCodeExporter commented 9 years ago
Should be working in 0.3 now. Only absolute imports are used now. Cyclic 
dependencies
have been removed.

Original comment by mdevan.f...@gmail.com on 9 Sep 2008 at 2:32