On Mon, Mar 5, 2012 at 12:37 PM, Ed Blackman
<address@hidden> wrote:
On Mon, Mar 05, 2012 at 07:57:42AM -0600, Kenneth Loafman wrote:
how could we make the backends initialize properly, but having them tell
that there is an error later?
I don't know. I do know that it's a catch-22. If we hide the error, then
it causes confusion, if we expose the error it causes confusion.
I don't know the duplicity internals enough to know whether this is feasible to implement, but one solution might be to hold on to the message until you know it's relevant.
When you initialize the backend, stash the messages rather than logging them. Later, when you know what backend will be used, log any saved messages for that backend. That way the messages won't be logged unless they could be relevant.
That's the route I was thinking about. Would someone mind posting a bug for this so we don't forget?
...Thanks,
...Ken