BUG: default for pd.Interval of closed/inclusive changed on main from right to both

[phofl]

Pandas version checks

• I have checked that this issue has not already been reported.

• I have confirmed this bug exists on the latest version of pandas.

• I have confirmed this bug exists on the main branch of pandas.

Reproducible Example

print(pd.__version__)
i = pd.Interval(pd.Timestamp("2020-01-01"), pd.Timestamp("2020-01-02"))
print(repr(i))
print(i)

1.4.2
Interval('2020-01-01', '2020-01-02', closed='right')
(2020-01-01, 2020-01-02]

1.5.0.dev0+958.gf7be58a477
Interval('2020-01-01', '2020-01-02', inclusive='both')
[2020-01-01, 2020-01-02]

Issue Description

This isn't mentioned in the release notes. We should decide on how to proceed.

Expected Behavior

cc @simonjayhawkins

Installed Versions

Replace this line with the output of pd.show_versions()

[jreback]

on the PR changing to use inclusive this must have been accid changed
should change it back for the default o these cases

[phofl]

One additional thing: The class attributes were also renamend, e.g.

x = pd.IntervalDtype(subtype='int64')

x.closed

raises now. Are these considered public or private?

[jreback]

hmm let's add that back (and add a depreciation warning for it)

thanks!

[simonjayhawkins]

is it ok for the repr change in a minor release or should this be changed back too?

[jreback]

no this is for 1.5 only (as keyword change / deprecation)

[phofl]

We will change the attribute back too.

One other thing: The argument order changed, but I think we can live with that?

[simonjayhawkins]

One other thing: The argument order changed, but I think we can live with that?

not sure, it's only the third argument, so maybe a few users will be using positional here.

looking through #46522, i'm wondering whether to revert for now and redo it in smaller parts.

[phofl]

I would like to give it a try on Friday, if this does not work out, reverting is probably the best option