Aaron Hosford

My .so files had much longer names. I ended up running into the same issue as you, @surfindominator . @greatwolf , is there something we're getting wrong? I'd be happy...

FYI, I'm using Python 3.5 on Ubuntu, with virtualenv. I'm curious what environments the other folks having this issue are using. Maybe there is a commonality?

I'm using Lua 5.2.4. It builds two .so files: copying build/lib.linux-x86_64-3.5/lua-python.cpython-35m-x86_64-linux-gnu.so -> /home/hosford4/.virtualenvs/testenv/lib/python3.5/site-packages copying build/lib.linux-x86_64-3.5/lua.cpython-35m-x86_64-linux-gnu.so -> /home/hosford42/.virtualenvs/testenv/lib/python3.5/site-packages I tried renaming each of them to python.so, and got the same error...

@greatwolf, I looked a little closer and realized the message is not identical. It's failing to resolve `PyFloat_Type`, not `_Py_ZeroStruct`. After a bit of googling, I suspect maybe the issue...

I think I found a bug in the setup.py script. In `pkgconfig`, the `for` loop that runs pkg-config breaks if the first call is successful. This means that the lua...

I submitted a [pull request](https://github.com/bastibe/lunatic-python/pull/62) for the bug fix. This should resolve the linking issues. The .so naming issues are still outstanding.

I'm running into a new issue now. After `require` executes successfully, the `python` global is nil. Any idea what might cause this?

I'm also getting warnings that `python` is an undeclared global.

I submitted [another pull request](https://github.com/bastibe/lunatic-python/pull/63) for the `python` global being undefined.

Thanks, guys! Not sure how much I can help, but happy to when I can. On 10/07/2017 09:33 AM, Bastian Bechtold wrote: > > Well then, @hosford42 , welcome to...