-
Notifications
You must be signed in to change notification settings - Fork 37
Make order of arguments for groupby consistent with other iterators. #30
Make order of arguments for groupby consistent with other iterators. #30
Conversation
The order argument makes sense to me, but I think the current version matches the ordering in DataFrames. There is an issue open there to change the order there as well (JuliaData/DataFrames.jl#580), but it hasn't had much traffic recently. Might want to comment there. While we wait for other comments, can you move the GroupBy2 benchmark fix to a separate PR? |
Anything holding this up other than the already-merged test change needing to be removed from the PR? FWIF, the referenced DataFrames method takes a Function as the first argument now (defined both ways). |
Bump. Anyone anyone with write access have an opinion? |
Makes sense to me, and the implementation looks reasonable at a glance. The merge conflict will have to be resolved. |
I'll fix the merge conflicts later this week or weekend unless someone else
|
Sounds good! |
Great! |
29509b6
to
6267fa7
Compare
6267fa7
to
981583b
Compare
…Fix groupby performance test.
981583b
to
61cf20e
Compare
I haven't been following julia issues closely lately but I think the travis failure for 0.4 is due to JuliaLang/julia#9947. |
This passes locally for me on master and release-0.3. Anyone willing to either click the Restart Build button from within Travis or merge? |
I restarted the build, but it failed again. It looks like the nightly hasn't been updated in 10 days because of JuliaLang/julia#10027. |
Make order of arguments for groupby consistent with other iterators.
Ah, I see. Thanks! On Fri, Feb 13, 2015 at 11:04 AM, Simon Kornblith notifications@github.com
|
This switches the order of the function and collection arguments in
groupby
so that it is consistent with theimap
anditerate
iterators and higher order functions in Base such asmap
. A warning is issued ifgroupby
is called with arguments in the old order.Also, the
GroupBy2
benchmark was not being run, and I assume that was omitted by mistake.GroupBy2
is now run.