Repository navigation
Source file locations #444
Description
Place all source files for compiled shared object files into the same folder as the final shared object file.
*.pyx files and cython-generated *.c would be in the same directory as the *.so. While external dependend C/C++/Fortran libraries are in dedicate src and include folders. See the following tree as an example.
MDAnalysis
|--lib
| |-- _distances.so
| |-- distances.pyx
| |-- distances.c
|-- coordinates
|-- _dcdmodule.so
|-- src
|-- dcd.c
|-- include
|-- dcd.h
This is standard see numpy, scipy, scikit-learn. mdtraj
Activity
orbeckst commentedon Sep 24, 2015
Why not? If it makes clearer what belongs together I have no objections.
orbeckst commentedon Sep 27, 2015
I am officially in favor of the proposal. Any other voices?
hainm commentedon Sep 27, 2015
I always favor following common concept in ecosystem. so +1.
kain88-de commentedon Oct 1, 2015
could we maybe add an easy tag to this?
orbeckst commentedon Oct 1, 2015
Something like the 'repository' tag that I just added (basically, anything relating to how we organize code), or do you want something more specific?
kain88-de commentedon Oct 1, 2015
I thought about an easy tag meaning they are bugs easy to solve. It would be a mark to show people who want to contribute what good bugs to pick are at the beginning.
orbeckst commentedon Oct 1, 2015
Ok, I added tag Difficulty-easy and tag Difficulty-hard to the list; obviously, that lies somewhat in the eye of the beholder but please: tag away!
(I purposefully omitted Difficulty-medium to avoid swamping issues with a default tag...)
Moved many extensions files alongside the python code (Issue #444)
Merge pull request #468 from MDAnalysis/issue-444
added compiled code locations from MDAnalysis#444