Include epoch microseconds in DT comparison methods. Closes #156

[timofurrer]

No description provided.

[kennethreitz]

This was originally done intentionally. Please make careful considerations before making this change.

[kennethreitz]

e.g. two nows generated “apparently” simultaneously, then compared equal.

I agree the microseconds are a better design decision.

[kennethreitz]

This is a major design change, though, and warrants a minor (or maybe even major) version bump.

[timofurrer]

This was originally done intentionally

What was the reason for that?

e.g. two nows generated “apparently” simultaneously, then compared equal.

Well, I hope no one bet one the that. It could easily happen that two nows generated “apparently” simultaneously would led to two datetimes with a different second and therefore not evaluate equal.

This is a major design change, though, and warrants a minor (or maybe even major) version bump.

That's right. The question even is if internally we should calculate with the total microseconds after the epoch start to avoid floating point numbers.

[github-actions]

This Pull Request is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days