How is the quakelib package structured in this software?

[ShayanJ]

I'm trying to understand the structure of this software. If you look at the file vq/PyVQ/pyvq/pyvq.py, you can see that a package named quakelib is imported. I call it a package because I couldn't find a quakelib.py file, and there was just a quakelib directory. But a directory should contain a __init__.py file directly under it to be a package. Instead, quakelib has a __init__.py inside its python subdirectory. So how is this a package?
Another problem is that the quakelib directory is not in the same directory as the pyvq.py that imports it. So how can it import quakelib?
Thanks

 

[jedishrfu]

Have you read the python docs?

I found this reference that may help:

https://docs.python.org/3.6/reference/import.html

This is for python 3.3, python 2.7+ may work differently.

 

[ShayanJ]

Yeah, I've read python docs, not that particular page though. But it didn't help. I also couldn't find the corresponding page for python 2.7.
Could you take a look at the link I gave in the OP?

 

[jedishrfu]

From what I saw quakelib is a C library not a python package. However, they may have an interface to it somewhere.

The linux environment will have the LD_LIB_PATH set to indicate where shared libs are located.

It seems they are using SWIG to build an interface to it.

https://en.wikipedia.org/wiki/SWIG

http://www.swig.org/Doc1.3/Python.html#Python_nn4