DEPR: Index.contains, DatetimeIndex.offset
DatetimeIndex.offset I thought was removed in #29801, but apparently slipped through the cracks.
reverted the RangeIndex bits since fastparquet still uses them Also, the start/stop/step were only at deprecation warning, we should maybe first elevate that to future warning? The offset note made it into #29801, just the actual removal fell through the cracks > Also, the start/stop/step were only at deprecation warning, we should maybe first elevate that to future warning?

Seems reasonable.  Should we have a section in #6581 for DeprecationWarnings to upgrade to FutureWarnings? (or a separate tracker, but id prefer to keep it unified) > > Also, the start/stop/step were only at deprecation warning, we should maybe first elevate that to future warning?
> 
> Seems reasonable. Should we have a section in #6581 for DeprecationWarnings to upgrade to FutureWarnings? (or a separate tracker, but id prefer to keep it unified)

we usually create a specific issue on that milestone, e.g. 1.1 or whatever (and/or can put on a unified tracker) pls rebase rebased + green thanks @jbrockmendel 