3 ms·

That's going to break following this change anyway.

• sanderjd 3y ago
  But in a much more obvious way. Noisy errors are better than quiet inaccuracy. They screwed up these methods from the start, and removing them is the only way to get rid of the confusion, without introducing subtle breakage.
  • BugsJustFindMe 3y ago
    It would still be a noisy error, just a different one that you can't compare non-naive and naive datetimes.
    • sanderjd 3y ago
      Unless you never compare it anywhere. Whereas it fails immediately if you try to do `datetime.utcnow` and that method doesn't exist.