Ensure eventually generated folders contain `__init__.py` files

[ZanSara]

Ensure eventually generated folders contain `__init__.py` files

[zkovari]

I'm in favor of creating the __init__.py files, I just don't really like the current naming. What about --init-package with a default value of True?

Furthermore, the option should be available on the command line as well as in the input configuration file (yml). Plus it should be documented and tested.

@ZanSara would you like to work on this one or shall I assign to myself?

[ZanSara]

That's a very small modification to do, so I can do it (docs & tests included ofc), but I would wait for a clarification on the tests issue before submitting more PRs (see #22). For the naming I don't mind, I'll use --init-package then.

[zkovari]

ok, thanks! I assign to you then.

Regarding the tests, I think the following test cases should be considered:

• __init__.py is generated by default in output directory
• __init__.py generation can be disabled
• __init__.py is not re-created if already exists

Currently we don't test the command line interface itself but rather invoke the module's main method. So it's okay if you follow the same approach.

[zkovari]

1.2.0 was released. Thanks a lot!