-
Notifications
You must be signed in to change notification settings - Fork 664
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Source file locations #444
Comments
Why not? If it makes clearer what belongs together I have no objections. |
I am officially in favor of the proposal. Any other voices? |
I always favor following common concept in ecosystem. so +1. |
could we maybe add an easy tag to this? |
Something like the 'repository' tag that I just added (basically, anything relating to how we organize code), or do you want something more specific? |
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. |
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 source for coordinates.dcd, lib.distances, lib.transformations, lib.pyqcprot and coordinates.libxdrfile. Removed deprecated src files Updated c files for Cython
Moved many extensions files alongside the python code (Issue #444)
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 dedicatesrc
andinclude
folders. See the following tree as an example.This is standard see numpy, scipy, scikit-learn. mdtraj
The text was updated successfully, but these errors were encountered: