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

Added the ability to list rows and delete rows by passing in row objects or row numbers. #390

Closed
wants to merge 2 commits into from

Conversation

seandmatthews
Copy link

…Added the ability to list rows and delete rows by passing in row objects or row numbers. Wrote tests to confirm listing and deleting rows works as advertised.

…Added the ability to list rows and delete rows by passing in row objects or row numbers. Wrote tests to confirm listing and deleting rows works as advertised.
@burnash
Copy link
Owner

burnash commented Jul 2, 2016

Thanks for the PR. Please consider splitting the PR in two. There should be one PR per issue (even the small one).

@@ -39,7 +39,7 @@ class Client(object):
:param http_session: (optional) A session object capable of making HTTP requests while persisting headers.
Defaults to :class:`~gspread.httpsession.HTTPSession`.

>>> c = gspread.Client(auth=OAuthCredentialObject)
>>> c = gspread.Client(auth=OAuthCredentialObject)>
Copy link
Owner

Choose a reason for hiding this comment

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

There's an extra '>' character at the end of the line.

re-broke the HTTPError so that it can be fixed in a separate PR
@seandmatthews seandmatthews changed the title HTTPErrors no longer try to display a nonexistant message attribute. … Added the ability to list rows and delete rows by passing in row objects or row numbers. Jul 2, 2016
@seandmatthews
Copy link
Author

I removed the fix for the attribute error so that can be addressed in a separate PR and got rid of the extra '>'

Is there anything else you'd like me to clean up before you merge it?

@techguydave
Copy link

@burnash Is there anything else that this is waiting on?

@seandmatthews
Copy link
Author

I'd like to see this (or something like this) merged. This is a feature that a lot of people (including me) want and have wanted for quite some time.

You said that if I and others wanted this feature so badly, that I should write it and submit a PR. I did that and it doesn't seem to have done much good.

If there's a problem with the PR I can try and solve it, but if it sits here while you ignore it there's not a lot I can do.

@techguydave
Copy link

@burnash Are there authorized contributors set up on this project? If not, it'd be nice if we could get that so the community could keep it going.

@pmochocki
Copy link

It would be really great if we could get this in.

@shopro
Copy link

shopro commented Oct 8, 2016

Also very interested in seeing this feature. Any ETA?

@techguydave
Copy link

Just checking in on this PR again. @burnash, if this were to get updated is it good to go?

@burnash
Copy link
Owner

burnash commented Oct 18, 2018

@NotLeet Thank you again for the contribution. I'm really sorry for such a late reply. API v3 has been deprecated for quite a while. I have put all of the time I had for gspread into porting it to API v4.

I'm afraid the changes in this PR are not relevant anymore.

@synth3tk part of the functionality proposed in this PR (Worksheet.delete_row()) has been added in #337.

I'm closing this pull request.

@burnash burnash closed this Oct 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants