WIP warn if parsing with du_parse

[MarcoGorelli]

• closes Inconsistent date parsing of to_datetime #12585 (Replace xxxx with the Github issue number)
• Tests added and passed if fixing a bug or adding a new feature
• All code checks passed.
• Added type annotations to new arguments/methods/functions.
• Added an entry in the latest doc/source/whatsnew/vX.X.X.rst file if fixing a bug or adding a new feature.

[MarcoGorelli]

The issue is that in

        df = DataFrame(
            [[1, 2], [3, 4]],
            columns=date_range("1/1/2013", "1/2/2013"),
            index=["A", "B"],
        )
        df.index.name = name

        with tm.assert_produces_warning(warn):
            result = df.reset_index()

, resetting the index will try to insert an element into a datetime index. hence, it'll try to parse the new element as a date, and this'll trigger the new warning

There's currently no way of catching multiple warnings, so perhaps that should be addressed first

EDIt: passing multiple warnings as a tuple works fine

[jbrockmendel]

is there an option that avoids importing from outside libs here?

[MarcoGorelli]

yup, could set it explicitly each time - I'll do that once I've sorted out the tests

[MarcoGorelli]

pd.to_datetime(["2000/1/1", "2010/1/1"]) doesn't raise, but pd.period_range("2000/1/1", "2010/1/1/", freq="M") does

don't know why, need to investigate

[jbrockmendel]

do we take a perf hit here?

[github-actions]

This pull request is stale because it has been open for thirty days with no activity. Please update and respond to this comment if you're still interested in working on this.

[MarcoGorelli]

This pull request is stale because it has been open for thirty days with no activity. Please update and respond to this comment if you're still interested in working on this.

still working on this

[MarcoGorelli]

closing, as from #12585 (comment) I don't think this is the right solution

log.txt