ConfigParser.NoSectionError: No section: 'log'

[regisrob]

ConfigParser.NoSectionError: No section: 'log'

[jpstroop]

Hmmm....that was a bug that I thought I fixed right before the tag. Hold on...

[jpstroop]

Hmm, the log section is there in both the latest version on the development banch:

https://github.com/pulibrary/loris/blob/development/etc/loris.conf#L29

and in the revision that was tagged:

https://github.com/pulibrary/loris/blob/9a1e320ba4df68efb861fc56ed1a2919045f8ae0/etc/loris.conf#L29

So you're not getting a fresh loris.conf file.

I just did a test on my machine, and indeed it looks like setuptools won't overwrite if the file exists. So, the safest thing to do would be for you to delete /etc/loris/loris.conf then run setup.py install and then configure. I just had a look around to see if there was a way to override this behavior (--force or something would be nice), but it doesn't look like it.

I'll add some info about this to the release notes. Thanks for catching it!

[regisrob]

Sorry it was my fault: I changed the conf directory and I forgot to change "prod_conf_fp" in "loris/log.py". That was the problem... But it means that test.py is testing against "/etc/loris/loris.conf" and not "etc/loris.conf", is that true ?

[jpstroop]

It's true for logging, unfortunately, and I don't like it.

https://github.com/pulibrary/loris/blob/development/loris/img_info.py#L16

I do point this out in the README, but it really does feel like a hack.

The problem right now is that loggers are instantiated at the module level, e.g.:

• https://github.com/pulibrary/loris/blob/development/loris/img.py#L19
• https://github.com/pulibrary/loris/blob/development/loris/img_info.py#L16

etc. And because of this I don't have the ability to pass get_logger() parameters, which means the only way to decide where to go/what to do is based on whether or not there's a file at /etc/loris/loris.conf or not.

There has to be a better way. I'll put in an issue for the next bit of work (likely to happen in later December...).

[jpstroop]

Submitted as issue #44

[jpstroop]

@regisrob see #44. This is in much better shape now. I will release shortly.