The include syntax does have its semantic advantages over using and import which are more module related (with all namespace implied functionality). Sometimes being more verbose is simpler and clearer rather than hiding functionality behind seemingly arbitrarily cumbersome one-liners. This seems like package material though
Yup. I also do this for notebooks that other people will use. Telling 'em to
which contains a push! to their LOAD_PATH and several lines of using and/or include is a lot simpler than asking them to manage their LOAD_PATH on their own or add dependencies they may never have heard of. My coauthors and students appreciate this.