Discussion Overview
The discussion centers around the structure of the quakelib package within a software project, specifically addressing how it is organized and imported in relation to Python's package requirements. Participants explore the implications of the directory structure and the nature of quakelib as it relates to Python and C libraries.
Discussion Character
- Technical explanation
- Debate/contested
Main Points Raised
- One participant notes that quakelib is imported in the file pyvq.py but questions its status as a package due to the absence of a quakelib.py file and the presence of __init__.py only in a subdirectory.
- Another participant suggests consulting the Python documentation for clarification on package structure and import behavior, referencing a specific page for Python 3.3.
- A participant acknowledges reading the Python documentation but indicates it did not resolve their confusion, particularly regarding Python 2.7.
- One participant proposes that quakelib may actually be a C library rather than a Python package, suggesting the possibility of an interface being built using SWIG.
- The mention of LD_LIB_PATH in Linux environments is brought up as a factor in locating shared libraries.
Areas of Agreement / Disagreement
Participants express differing views on whether quakelib is a Python package or a C library, indicating a lack of consensus on its classification and the implications for its importation.
Contextual Notes
There is uncertainty regarding the specific requirements for Python package structure and how they apply to the quakelib directory. Additionally, the discussion does not resolve the differences in behavior between Python 2.7 and Python 3.x.