DEPR: Timestamp.freq
- [x] closes #15146
- [x] tests added / passed
- [x] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#code-standards) for how to run them
- [x] whatsnew entry

This in turn will allow us to remove DatetimeArray.freq and TimedeltaArray.freq, which is needed for #31218
Changed your post to avoid closing the other issue too this would be good to get in the rc > this would be good to get in the rc

what's the soft-deadline for this? > > this would be good to get in the rc
> 
> what's the soft-deadline for this?

soonish

cc @simonjayhawkins  Repeating my non-inline review comment again here to ensure it was noticed:

> Accessing the `.freq` attribute of a Timestamp instance itself is not yet deprecated? That should also be deprecated to be able to remove it? > Repeating my non-inline review comment again here to ensure it was noticed:

Thanks, will get to that shortly. > > > this would be good to get in the rc
> > 
> > 
> > what's the soft-deadline for this?
> 
> soonish

I'll put the blocker on this also for now.

will release 1.2.5 first. so still got a few days for this. merging, @jbrockmendel can you followup with respect to any open comments (i think just the whatsnew but maybe more) This resulted in a performance regression https://pandas.pydata.org/speed/pandas/#tslibs.timestamp.TimestampProperties.time_freqstr?Cython=0.29.21&jinja2=&python=3.8

however, we will be ignoring this https://github.com/pandas-dev/pandas/pull/40008#issuecomment-872368316

> BTW looking at the regressions listed, I think we can hit "ignore" for the TimestampProperties.time_freqstr ones, since those are driven by a deprecation of freqstr (and are still measured in ns)