-
-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
ENH: add method='dense' to rank #6514
Conversation
looks good then good. 2 go |
are their frame tests at all? |
Yeah, |
ahh ok makes sense |
perfect pls just add release notes and can merge |
So does this go under "Improvements to existing features" for 0.14.0? |
that works |
…into add_dense_rank_v5
It is my considered opinion that git is sufficiently complicated that having a tutorial reference open while using it is useless, because there is always some state I'm in which prevents the command from working as it's supposed to. And this is a fact which beginners have no way to know until they've done it and made things worse. Right now the last the last three log events in my local branch add_dense_rank_v5 are (1) the original commit, (2) 7ec7662's commit, and (3) a merge which was introduced when trying to follow instructions to avoid the "Updates were rejected because a pushed branch tip is behind its remote" error. |
hmmm...I avoid merging (except when actually merging other people commits)... my workflow is something like this: update master
fix conflicts (if needed)
add commits rebase when needed to reorder/squash
|
you can just delete that merge commit FYI (I am going to remove it when I merge you in a moment anyhow) |
merged via 61b141b |
thanks as always! |
Addresses #6333.
(Let's see how it goes on Travis; last time there was some strange behaviour which I think turned out to be because of an uninitialized variable which was behaving differently on my system than on the buildbots.)