Errors while writing dropin.cache should show a less horrible error message

[radix]

I suggest doing something like

log.err("warning: Couldn't write dropin.cache file because %s" % (e,))

instead of log.err()

[Jean-Paul Calderone]

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

[radix]

lol.

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

[Jean-Paul Calderone]

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]

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]

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

[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. 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]

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?

[Jean-Paul Calderone]

Yes. Thanks for finding that.