Skip to content

DOC - Moving Tips and Trick from wiki to Style Guide - added Reading … #34366

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

Merged

Conversation

vijaysaimutyala
Copy link
Contributor

This changes referring to #30964 is for removing tips and tricks section page from the wiki to the Code Style guide.

Since this is my first contribution, I've tried to keep this as simple as possible. @simonjayhawkins mentioned that the conventions for urlopen and ZipFile should be captured under our contributing style guide, testing section. I've seen that there is no Testing section and have created a new section and added these two sections from the Wiki post here. Enabling the Travis-CI and Azure CI pipeline build seemed a bit tough for me. I will try to do the build from my side in my next PR.

Let me know if any corrections are needed.

Copy link
Member

@simonjayhawkins simonjayhawkins left a comment

Choose a reason for hiding this comment

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

Thanks @vijaysaimutyala generally lgtm.

@simonjayhawkins simonjayhawkins added this to the 1.1 milestone May 25, 2020
@MarcoGorelli
Copy link
Member

Hi @VijayantSoni - is this still active? If so, can you address Simon's comment?

@vijaysaimutyala
Copy link
Contributor Author

Sorry I somehow missed the comment. I'll add this and update here.

@vijaysaimutyala
Copy link
Contributor Author

@MarcoGorelli Updated the PR with comments. Somehow my local build of the docs got pushed. Is there something I should do in future to avoid this or will the local build be ignored ?

Also, should I be closing the PR if I don't have any further changes on this or will it be done automatically ?

@MarcoGorelli MarcoGorelli self-requested a review June 19, 2020 17:55
@MarcoGorelli
Copy link
Member

MarcoGorelli commented Jun 19, 2020

Thanks for updating, @vijaysaimutyala !

Somehow my local build of the docs got pushed. Is there something I should do in future to avoid this or will the local build be ignored ?

It's generally safer to stage the files you want to commit with git add <file> rather than git add ., which can end up with you adding a lot more than you intended. Though to be honest I'm not sure how you ended up with those files, I thought they would be in doc/_build (which git will ignore) - did you follow the instructions here?

If you could remove the extra files, that'd be great.

git rm -rf doc/source/_build
git commit -m "<some descriptive commit message>"
git push origin <your branch name>

should work, I think.

Also, should I be closing the PR if I don't have any further changes on this or will it be done automatically ?

If the core team is happy with it, they'll merge it in :)

@vijaysaimutyala
Copy link
Contributor Author

Thanks for the clear answers @MarcoGorelli . Honestly I didn't look at the gitignore but was hoping they would be ignored, but they somehow ended up in my commit. I'll be careful from here on.

I'll try out what you've mentioned. Thanks again 🙂

Copy link
Member

@MarcoGorelli MarcoGorelli left a comment

Choose a reason for hiding this comment

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

Thanks @vijaysaimutyala, looks like you've successfully removed the unrelated files

vijaysaimutyala added a commit to vijaysaimutyala/pandas that referenced this pull request Jun 22, 2020
Copy link
Member

@simonjayhawkins simonjayhawkins left a comment

Choose a reason for hiding this comment

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

Thanks @vijaysaimutyala lgtm pending green

@WillAyd
Copy link
Member

WillAyd commented Jun 23, 2020

I think we can just delete this wiki entry instead of moving it as its pretty outdated. The second code snippet won't run

@simonjayhawkins
Copy link
Member

I think we can just delete this wiki entry instead of moving it as its pretty outdated.

see #30964 (comment)

The content of this PR is not outdated AFAIK, our standard is to use urlopen and ZipFile from pandas.io.common. This PR documents that?

@simonjayhawkins
Copy link
Member

Travis CI passed but not updated here. will merge shortly if no objections.

@WillAyd
Copy link
Member

WillAyd commented Jun 23, 2020 via email

@simonjayhawkins
Copy link
Member

Does ZipFile even exist? I didn’t see it there maybe overlooked. Thought we just used stdlib

Sent from my iPhone
On Jun 23, 2020, at 11:52 AM, Simon Hawkins @.***> wrote:  Travis CI passed but not updated here. will merge shortly if no objections. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

no it's no longer there. we only have _BytesZipFile now.

@vijaysaimutyala can you remove the ZipFile bit.

@WillAyd OK with urlopen? I think if we maybe add "Lazy-import wrapper for stdlib urlopen, as that imports a big chunk of
the stdlib." might help?

@vijaysaimutyala
Copy link
Contributor Author

Does ZipFile even exist? I didn’t see it there maybe overlooked. Thought we just used stdlib

Sent from my iPhone
On Jun 23, 2020, at 11:52 AM, Simon Hawkins @.***> wrote:  Travis CI passed but not updated here. will merge shortly if no objections. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

no it's no longer there. we only have _BytesZipFile now.

@vijaysaimutyala can you remove the ZipFile bit.

@WillAyd OK with urlopen? I think if we maybe add "Lazy-import wrapper for stdlib urlopen, as that imports a big chunk of
the stdlib." might help?

Sure. Let me know if you want me to add anything else.

@simonjayhawkins
Copy link
Member

Thanks @vijaysaimutyala . the CI failures are probably unrelated and fixed on master. can you merge upstream/master to get ci to green to be sure.

@vijaysaimutyala
Copy link
Contributor Author

@simonjayhawkins I merged from upstream and everything looks good. How do I get the CI to run again ?

image

@MarcoGorelli
Copy link
Member

@vijaysaimutyala if you just push again, the CI process will restart.

(terminology nitpick, but it looks like you did a rebase instead of a merge, in which case you would need to do a forced push)

@vijaysaimutyala vijaysaimutyala force-pushed the move_tips_and_tricks_from_wiki branch from 493ed60 to 6ada273 Compare July 7, 2020 10:20
@vijaysaimutyala
Copy link
Contributor Author

vijaysaimutyala commented Jul 7, 2020

Done :) Little confused.

Copy link
Member

@simonjayhawkins simonjayhawkins left a comment

Choose a reason for hiding this comment

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

lgtm @WillAyd

@WillAyd WillAyd merged commit 74f77a1 into pandas-dev:master Jul 8, 2020
@WillAyd
Copy link
Member

WillAyd commented Jul 8, 2020

Thanks @vijaysaimutyala

@vijaysaimutyala
Copy link
Contributor Author

Thanks to you guys for holding my hand throughout. Though this is a small documentation that might not take much time for you, all of you were patient enough for me to understand and move in a proper direction. I use pandas on a daily basis at work and now I'm proud that I too have put in a little effort. Looking forward for big ones 😁

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

Successfully merging this pull request may close these issues.

4 participants