Jan Janssen

This might be related to https://github.com/pyiron/pyiron/issues/1421

@pmrv What is the current status of this issue? I thought this is fixed, right?

The ValueError is raised in https://github.com/pyiron/pyiron_base/blob/master/pyiron_base/generic/hdfio.py#L166 - so we could change it to a `TypeError` but I am not sure if that would help. The reason why we return `None`...

> Is this the full `.pyiron` file? So far I do not get it - will have another look, tomorrow. Yes, that is all.

> I don't think it's a problem that you say "please don't use these features" but your config file still has parameters available for utilizing those features in case you...

@niklassiemer Yes, you are right - most likely I still had the project path in there and assumed it would be overwritten with `project_check_enabled`. But the issue should be solved...

But that is the whole purpose of `project_check_enabled` enabled, is not it?

The old behavior was that when `project_check_enabled` is false the `project_path` variable is ignored and all I am asking for is to revert this change.

And the second part is that the `sql_*` keys are confusing when I did not configure them. In particular when users try to run pyiron without database. That is why...

> I strongly disagree. They are there even though you didn't configure them because they're the default values-- that is not so confusing, or? The current behavior is less confusing...