BUG: DataFrame.at with CategoricalIndex
- [ ] closes #xxxx
- [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

release note? whatsnew added + green This is for 1.3? don't add things to 1.3
when we merge can add if appropriate  This has a release note in 1.3.0 whatsnew. if not 1.3 we need to request it moved. any suggestions how to track this. i undestand and it prob will be merged but let's look first
eg don't preemptively label (i may have done that here) its a bugfix so i wrote the note for 1.3, wont be the end of the world if it has to wait for the next one should i move release note to 1.4 file? > should i move release note to 1.4 file?

not yet. I think Jeff just didn't want stuff added to the 1.3 milestone for now. if the RC is put off until tomorrow, can this go in?  it is a blocker for #41956 Doesn't look like there's a fix for the wheel issue. So may release what we
have.

On Sat, 12 Jun 2021, 22:52 jbrockmendel, ***@***.***> wrote:

> if the RC is put off until tomorrow, can this go in? it is a blocker for
> #41956 <https://github.com/pandas-dev/pandas/pull/41956>
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/pandas-dev/pandas/pull/41846#issuecomment-860118003>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ADEMUXI6G5LUOT2QSZAPY5LTSPJKVANCNFSM46G2R5QA>
> .
>
 > Doesn't look like there's a fix for the wheel issue. So may release what we have.

tbc. I should have said we are not necessarily putting off the rc, and that if the wheel issue is not fixed quickly, we could release rc0 and then follow-up with a rc1. So the same backport rules apply. We have a rc0, but may not advertise the fact. So the rc is not put-off, it has effectively happened. @meeseeksdev backport 1.3.x Something went wrong ... Please have  a look at my logs.