Brad Bondurant

@lriesebos by the way this actually (kind of) allows git integration with our directory structure if you add a top-level `__init__.py` and start the master with something along the lines...

Here's what I've done to test so far (repos are public): ``` # running in a dev shell with the changes I've made # setup mkdir tmp && cd tmp...

How about something like this instead? ```python def file_import(filename, prefix="file_import_", repository_path=None): filename = pathlib.Path(filename) modname = prefix + filename.stem if repository_path: # find any importable modules for path in os.listdir(repository_path):...

Okay just kidding, nothing that I did in a151b572f4c1d5b5b1f3c017e0f625c9c7a7a6b3 actually fixed anything and I wasn't actually testing the thing that needed to be tested (i.e. the original scenario presented in...

> and would also be understood by automatic error checkers / linters FWIW, that's relatively easy to get around with most tools - e.g. in PyCharm, a simple right click...

^ Meh? Obviously the UI could use some work but the basic functionality seems to be there. edit: Never mind, I got ahead of myself and didn't test well enough....

Hm. So, the above commit works for the `examine` call when the file is opened in the dashboard, but I don't see a way to do the same thing for...

Additionally, adding `"repo_dir"` (IMO more expressive than `"wd"`) to the `expid` would probably make #1571 redundant.

Okay I think that takes care of things for submissions from the dashboard (functionally, at least). Now, for other interfaces: - `artiq_client`: seeing as this goes through the master, adding...

I could see that being really useful. If, instead of having the `-g` as a `store_true` type argument, we switch it to being a path like `-r` (or just add...