It would be more consistent to name the EM stuff "EM" (uppercase).
Ben Webb wrote: > Daniel Russel wrote: > >> OK, then I'll work on moving the restraints and stuff I maintain into my >> svn repository. I'll put the general purpose restraints in IMP::dsr >> (unless someone has a better name to propose) and the npc dynamics ones >> into IMP::npc_dynamics. >> > > If you feel others are going to be using this stuff, it's probably > better in the long term to keep it in the main IMP repository, just like > domino and impEM. Trivial that way to keep it in the nightly builds (so > that you can see when the tests fail, for example). And moving a file > between modules in the same repository preserves history. Access rights > would be the same of course - only downside (depending on your > perspective) is that the SVN server enforces code standards. > > If you make a list of the things you want moved, I can do that for you. > (Or, I can just make an empty module for you, and you can 'svn cp' the > files into there. Then I'll 'svn rm' them from the kernel.) Plus that > way if anybody does use them, they can argue to keep them in the kernel, > or at least will be notified that things are changing. > > >> How do the python library names work for sub-libraries? i.e. IMP is >> _IMP.so so what is IMP.em? Does it just go in a dir called IMP in your >> python path? >> > > It'll just be called _em.so, since that's the name of the module. The > build system would be responsible for installing that into the IMP > directory. > > Ben >