@exarkun commented

Surely you mean log.err(None, "...")?

	@radix set owner to @radix @radix set status to assigned

lol.

I don't mean that, because that would cause the traceback to still be printed. That's what I'm trying to avoid.

	@exarkun commented

I'm not sure it's an improvement to make a system misconfiguration less visible.

In any case, the message should not start with warning. The rest of the example sentence conveys just as much information without the prefix.

	@glyph commented

I do believe that the most common error - that the dropin.cache file cannot be opened for writing - should be caught and logged as a warning rather than an error. I'll file a separate ticket for that.

	@glyph commented

(by "logged as a warning" I mean "warnings.warn", not log.err("something misleading")).

	@radix commented

Replying to glyph:

I do believe that the most common error - that the dropin.cache file cannot be opened for writing - should be caught and logged as a warning rather than an error. I'll file a separate ticket for that.

Does such a ticket exist yet? I can't find it. But actually, that particular case is all I was referring to when I made this ticket, so I don't think a separate ticket needs to be filed.

	@glyph commented

Replying to radix:

Replying to glyph:

I do believe that the most common error - that the dropin.cache file cannot be opened for writing - should be caught and logged as a warning rather than an error.

Does such a ticket exist yet?

I believe #2409 is the ticket in question. Is this a duplicate now?

	@exarkun set status to closed

Yes. Thanks for finding that.