Remove number of deprecated parameters/functions/classes [fix #6641] by jsexauer · Pull Request #6813 · pandas-dev/pandas (original) (raw)

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 andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Conversation25 Commits1 Checks0 Files changed

Conversation

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters

[ Show hidden characters]({{ revealButtonHref }})

jsexauer

Fixes #6641

Line numbers as of commit 70de129:

Deprecated since 0.11 or before

The following are fixed in this PR:

Deprecated since 0.12 or after

Issue #6581 documents the following for future removal. These are not included in this PR

@jsexauer

Wanted to double-check that you want me to remove DateRange as it will be a more significant undertaking than the other ones. In addition to being available at the base of the API, it's used throughout the codebase, so I'll have to refactor all that too. Not a problem to do, but wanted to double-check before doing so.

@jreback

can certainly leave that for now
but do it a separate pr if u can
it's just really a name for DatetimeIndex

FYI also need to check/update vbenches for any of these deprs

@jsexauer

@jtratner

@jsexauer - let's leave out deprecating DateRange for another issue so we can make this a minor change that we can accept. If it's still used within pandas and on the vbenches, it doesn't really feel like DateRange is deprecated.

@jtratner

i.e. you can just open a separate PR that handles the refactor and deprecation for DateRange.

jtratner

yearfirst=yearfirst)
else:
data = tools.to_datetime(data, errors='raise')
data.offset = offset
data.offset = freq

Choose a reason for hiding this comment

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

this is slightly confusing to me - we deprecated offset as a parameter but not the actual offset property on the object?

Choose a reason for hiding this comment

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

@jsexauer

@jsexauer

Ok I will do the DateRange one next. Just made a small change I saw in updating the docs (shouldn't affect tests). I think this one is ready for closing; let me know if more work is needed.

@jreback

can you edit #6581 to update the >= 0.12 (that we are going to deprecate in the future)?

thanks

@jreback

@cpcloud

Looks good, but I don't see the html.py removal listed in the task list.

@jsexauer

@cpcloud It is the second to last item in the "Deprecated since 0.12" list. I see that the warning message says to remove in 0.14, but warning was given only in 0.13. Let me know if you want me to remove anyways.

@cpcloud

oh ok ... you're right ... sorry i haven't looked at html stuff in a while, carry on

@jreback

yep....only doing < 0.12 announced deprecations (which their are a lot!)

@wesm

I'm pretty wary of removing load and save since they're used in The Book. I'm not sure if any of these other deprecation will affect the book but should try to avoid if possible, I guess.

@jreback

save/load not on the table as those where from. 0.12

@jsexauer in the list can u out the version that the depr happened (I know I have the commit but for reference) thanks

@jsexauer

@wesm I don't own a copy of The Book unfortunately, but assuming it was written for v0.9 (given publish in Oct 2012) the only two of these that might affect it are

Do you know if either of these were used?

@jreback Modified inital PR comment to include versions of first deprecation. Also moved all deprecations not pulled out in this PR into #6581.

@hayd

Neither of those are used in wes' book.

@jreback

yep...i think this is all fine.

@jreback

@jreback

@jsexauer

What should I do for the ones that that didn't have issues?

@jreback

if u have a commit reference then u can use that (though u may have to do an inline reference)
if u can get it to work great if leave the existing referemce

@jsexauer

Have an example you could point me to?

@jreback

oh...looking in cookbook.rst, its just another external link. (The issues render differently/automatically, via the issue number), but a commit is just a reference like any other HTML link.