Rachel Bittner

> At the moment, each mirdata module automatically loads its index during import. If searching for loaders requires to import the modules, then our search function is going to be...

Edit: > > (1) mirdata modules no longer load index during import > > That's totally feasible - we already do this for the "LargeData" object - we could tread...

>> Hi mirdata team, > > I'm struggling to pass some of the tests, despite my best efforts… Firstly, there is failure in buildpy36/37/38 due to the lack of exception...

@dave-foster quick question - in the download info, you mention a script to run: ``` python Scripts/Compile_Backing.py -version full ``` I had a quick look at the conversation in the...

Maybe we should wait for #265 to be implemented and then we can use `giantsteps_key` as a first example?

Question for @PRamoneda - what's the difference between the old and the new versions of the datasets? Is it corrections, new tracks, new annotations, etc?

I don't have a windows machine, but we can try adding windows as a test environment and see if we can reproduce there?

@prachitui in the meantime, this [stack overflow issue](https://stackoverflow.com/questions/42757759/git-windows-cannot-clone-checkout-repository-paths-with-spaces) seems very related - can you try out the suggested solution and let us know if it fixes it?

For most namespace, I'd actually vote for this to be hardcoded in the module. If it's created by parsing e.g. track objects over `.track_ids()`, it would require instantiating the whole...

> @rabitt what do you mean, hardcoded? as constants? directly in the code of the module or in a JSON file? I mean a very simple hardcoded function that is...