Comment 9 for bug 1670243

That's still not clear to me.

Can we please clarify first what the problem is that we're trying to solve? That makes it a lot easier to determine if this is the correct approach. Is that problem solved by supporting pre-1970 dates but not pre-1900 dates?

I agree it's a problem that we print a traceback if the user passes a time string that Breezy doesn't support; at the very least we should be printing a proper error message in that case.

I'm unsure why it's necessary to increase the range of supported dates to pre-1970 but not pre-1900.

Martin mentions offline that another option to supporting wider time ranges times is to switch to using datetime internally, which would avoid the need to duplicate time.*.