DEPR: enforce deprecations in core.internals
Not sure if the whatsnew is needed for this; IIRC it was mainly pyarrow/fastparquet that were using these keywords
lgtm. rebase and merge. the travis-36-locale build uses fastparquet=0.2.1 which apparently still passes dtype to make_block_same_class.  any objection to bumping the required version? Looks like we last bumped the fastparquet version in #24590 Yes, I think bumping the minimum fastparquet version is fine. 
cc @TomAugspurger  > Yes, I think bumping the minimum fastparquet version is fine.
> cc @TomAugspurger

agreed here as well. Happy to bump.

On Wed, Nov 20, 2019 at 5:32 PM jbrockmendel <notifications@github.com>
wrote:

> Looks like we last bumped the fastparquet version in #24590
> <https://github.com/pandas-dev/pandas/pull/24590>
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/pandas-dev/pandas/pull/29723?email_source=notifications&email_token=AAKAOIT3P4CQOUA7FP5TQIDQUXCIJA5CNFSM4JPKHGJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEWEFYA#issuecomment-556548832>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAKAOIXB2FXCSVDBUSTVBBDQUXCIJANCNFSM4JPKHGJQ>
> .
>
 bumped fastparquet to 0.3.0.  Wasnt sure what to put in the whatsnew, so I copied the whole minimum-version section from 0.25.0, updated the fastparquet entry, and cut the sentence about py27 having just been dropped. Looks like 0.3.2 is the version when fastparquet stopped using the deprecated keyword, but that is also the most recent version.  are we OK with bumping that far? looks good, IIRC you have a nother PR where you add the Change column, can update then.