Confirmed for 3.11 in Windows. 

The C datetime code can be trivially fixed so your equality test returns True, but there are two Python tests that depend on current behavior so it might not be so easy. They were added with current code in issue 24773, to implement PEP 495 -- Local Time Disambiguation.

Also, using a timezone implementation from the test suite makes the equality work, so maybe the bug depends on zoneinfo.

If you change datetimemodule.c line 5761 from "diff = 1;" to "diff = 0;", two tests fail and your code works.

See attached file for the tests that fail and using the timezone implementation mentioned above.