bollard

Thanks for your comments and taking a look at the issue. On the first point, I think it is at least unexpected that `pd.Grouper(..., freq="D")` creates an empty group on...

Sure, apologies if my point here isn't clear. In the above code snippet, I have `pd.DataFrame` with timestamp indices (`df_ts`), and another one with date indices (`df_date`). In both cases...

Yes, you can replicate an empty `.groupby()` with an empty `pd.Grouper(..., freq=None`) but this interoperability fails when you actually try and do something useful... It still feels like a bug...

By "fails when you actually try and so something useful", I mean `pd.Grouper(..., freq="D")` and `.groupby("date")`. To me it seems strange that two functions are understood to operate the same...

Sure, if that is the expected behaviour then I think that should be * Documented (complete with exactly what a "resampling like approach" means for the result) * Documented in...

EDIT: I take all (well almost all) of my previous comment back. The workaround [here](https://github.com/bjcairns/fs/wiki/Solving-network-drive-%22operation-not-permitted%22-errors-(r-lib-fs%23147)) by @[bjcairns](https://github.com/bjcairns) does indeed work (thank you very much!), but crucially only the `path-real-fallback-cran` branch....

And AR can still can continue to map Base#id to whatever it wants... ``` def visit_ActiveRecord_Base(o, parent) if some_condition o.id # Call Base#id and retrieve primary key else # some...

I agree it is certainly not an ideal situation to be in, however when making such invasive changes to Rails we were always going to have to patch a number...

Is there any prospect of this being merged and released? Would be a really useful feature. Thanks