STY: rename QueryCompiler.view to something more consistent
See original GitHub issueQueryCompiler.view seems to behave more like PandasDataframe.mask (which in turn is completely different from pandas.DataFrame.mask).
I propose that both QueryCompiler.view and PandasDataframe.mask (and whatever other relevant methods are out there) be renamed to something like take_2d
or possibly take_or_slice_2d
Issue Analytics
- State:
- Created a year ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
STY: rename QueryCompiler.view to something more consistent ...
QueryCompiler.view seems to behave more like PandasDataframe.mask (which in turn is completely different from pandas.DataFrame.mask). I propose that both ...
Read more >How to rename a Consistency Group using the RecoverPoint ...
For more Information, check our Knowledge Base: https://dell.to/3pAYaadThis video demonstrates how to rename a Consistency Group in ...
Read more >XML Prague 2019
We next briefly examine the original vision for XPath, XQuery, ... more, multi-threading of xsl:for-each instructions using a MapReduce.
Read more >(PDF) A Platform for Big Data Analytics on Distributed Scale ...
According to the evaluation analysis, the proposed big data platform provides better scalability, fault tolerance, and faster query response ...
Read more >SOQE 2021 The Second Workshop on Second-Order ...
The underlying idea of separating a logical/conceptual view of how ... use abducibles, justification patterns, or something else).
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Doesn’t this conflict with
?
It does. I think my second statement is correct. I should correct my first statement about “actually use the same partitions pointing to the same data” to say that it only seems to apply to copies (either deep or not) and full slices like
loc[:]
.