Hi,
Here's the relationship between the data_path variable in ~/.fuelrc and the FUEL_DATA_PATH environment variable: they both set fuel.config.data_path, which is used internally to determine where to look for built-in dataset files. FUEL_DATA_PATH has precedence over the ~/.fuelrc setting, which lets you momentarily override the data path like so:
FUEL_DATA_PATH=/some/other/data/path python my_script.py
Note that fuel.config.data_path recently got overhauled and now supports multiple paths in a PATH-like fashion. Fuel will cycle through each path in the sequence and use the first file found.
The fact that fuel-download puts the downloaded files in the current directory by default is expected behaviour: since there are multiple possible data paths, there's a legitimate question as to where to put the files by default. We chose to use the current directory by default and let the user explicitly define where to put the downloaded files like so:
fuel-download mnist -d /one/of/my/data/paths