Please do not create folders/config at import

[BenediktBurger]

Thank you for updating HAPI.

I just tried hapi2 and found out, that it creates a config file and two folders in my current working directory on import of hapi2. That creates major problems as I am not always in the folder in which the file is.

Please ask, whether a new config file (and folders) are created, if you did not find a config file.

Maybe you could move the configuration detection to its own method, e.g. hapi2.init, such that you can call it at leasure (instead at import time). This method could accept a path to a config file as well.

EDIT: If you want, I can open a pull request with a suggestion.

[RomanKochanov]

Hi Benedikt,

Thanks for the suggestion! You are right that creating the folders in the working dir can cause problems sometimes. One of the solutions could be using the home dir for the default configuration file and scratch folders (tmp, provenance etc...) with the possibility to be overridden by the local config file, if present.

If you want, I can open a pull request with a suggestion.

Sure, that would be great.

Best wishes,
Roman

[BenediktBurger]

Hey Roman,

I found out that os.path.expanduser replaces "~" with the hone directory, independent of the operating system.

I do not like the idea to have some "config.json" in the home directory. Would you prefer to rename the file (for example "hapi2.json") or search for a "hapi" (or hapi2) folder in the user directory?

Additionally, I propose to not create the config automatically (at least not at import time):

• first step is import of hapi2
• second step is to initialize it, for example hapi2.init() which will accept a path to a config file as an argument (default: search in current directory and in home folder) and a flag whether to create the config, if it not yet exists (default false).

What do you think?

[BenediktBurger]

In a first PR I raise an error if the file is not found in the current directory.

I tried to make it possible to look for a global config file (e.g. in the home directory), which works fine. But then the problem is, the other files are still created relative to the current working directory, regardless where the config file is.

We could introduce some "root path" (based on the config file) such that the database etc. are always relative to the config file.

Tell me, if you want to go that path (requires rework in all the file related places).