Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DEPR: remove deprecated verbose, private_key kwargs for gbq #30200

Merged
merged 6 commits into from
Dec 13, 2019

Conversation

jbrockmendel
Copy link
Member

@jbrockmendel jbrockmendel commented Dec 11, 2019

The deprecation didn't have a whatsnew note or actually use deprecate_kwarg, so im not sure how formal the removal should be.

xref #20564.

@jreback jreback added Deprecate Functionality to remove in pandas IO Google labels Dec 11, 2019
@jreback jreback added this to the 1.0 milestone Dec 11, 2019
@jreback
Copy link
Contributor

jreback commented Dec 11, 2019

need to modify these tests too: > test_read_gbq_with_deprecated_kwargs

@jbrockmendel
Copy link
Member Author

removed test, added a whatsnew note that didnt make it into #30199

@@ -534,6 +534,7 @@ or ``matplotlib.Axes.plot``. See :ref:`plotting.formatters` for more.
- :meth:`Series.plot` no longer accepts positional arguments, pass keyword arguments instead (:issue:`30003`)
- :meth:`DataFrame.hist` and :meth:`Series.hist` no longer allows ``figsize="default"``, specify figure size by passinig a tuple instead (:issue:`30003`)
- Floordiv of integer-dtyped array by :class:`Timedelta` now raises ``TypeError`` (:issue:`21036`)
- :class:`TimedeltaIndex` and :class:`DatetimeIndex` no longer accept non-nanosecond dtype strings like "timedelta64" or "datetime64", use "timedelta64[ns]" and "datetime64[ns]" instead (:issue:`24806`)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't seem related to this change.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

correct, see comment #30200 (comment)

@jreback
Copy link
Contributor

jreback commented Dec 12, 2019

IIRC I remember seeing something about private_key still in pandas-gbq? @tswast

@tswast
Copy link
Contributor

tswast commented Dec 12, 2019

That's right. I filed googleapis/python-bigquery-pandas#301 to actually remove it. I'll do that and cut a pandas-gbq release today.

@jbrockmendel
Copy link
Member Author

so should i revert the private_key change here? warn?

@tswast
Copy link
Contributor

tswast commented Dec 12, 2019

It's okay to remove. We've been showing a warning since we deprecated it in pandas 0.24.0. Soon it'll hard fail if it's ever supplied.

Copy link
Member

@WillAyd WillAyd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Can you add a whatsnew for this change?

@WillAyd WillAyd merged commit fa9ada7 into pandas-dev:master Dec 13, 2019
@WillAyd
Copy link
Member

WillAyd commented Dec 13, 2019

Thanks @jbrockmendel

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Deprecate Functionality to remove in pandas
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants