DEPR: Dropping nuisance columns in core.apply
See original GitHub issueRef: https://github.com/pandas-dev/pandas/pull/41475, https://github.com/pandas-dev/pandas/issues/39993#issuecomment-926281200
To keep the API consistent between groupby / non-groupby UDF methods (apply, agg, transform), we should not allow silent failure in core.apply
.
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (7 by maintainers)
Top Results From Across the Web
FutureWarning: Dropping of nuisance columns in DataFrame ...
The warning is due to deprecated dropping nuisance columns in DataFrame. You can read more about it here. If you want to get...
Read more >What's new in 1.3.0 (July 2, 2021) - Pandas
Deprecated dropping nuisance columns in DataFrame reductions and DataFrameGroupBy operations# ... Calling a reduction (e.g. .min , .max , .sum ) on a...
Read more >Nuisance Animals Coyotes (PDF) - Orono, MN
According to the Minnesota Department of Natural. Resources (DNR), the coyote population is on the rise in residential areas across the State. If...
Read more >How to Drop Columns in Pandas Tutorial - DataCamp
drop () method. Besides specifying the column name, you need to specify that you are dropping from the columns axis and that you...
Read more >Dealing with Nuisance Wildlife web hg90 - Maine.gov
Local Governments - U.S. Department of Agriculture Cooperating. The University of Maryland is equal opportunity. The University's policies, programs, ...
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
@jbrockmendel - I believe I left this open because there was some opposition to the changes. I’m still behind the deprecation, and it seems like conversation has ceased. I’m going to close for now, and can reopen if anyone would like to continue the discussion.
I hope you can provide some guidance to us @rhshadrach on whether it is appropriate to open up an issue to track dropping of nuisance columns not just in core.apply but elsewhere as well. At least, this sort of silent dropping is extremely useful in many contexts and to my recollection was widely relied upon when Pandas first became popular back in 2012(?)… In the past, one would have often have to manually clean data each time, arduously, before loading it into say a numpy recarray. Pandas opened up the possibility to just start working with mixed data without necessarily investing a huge amount of time pre-cleaning, as was necessary using other existing python solutions.
It’s sad to see what was a selling point or at least widely relied upon functionality dropped, even though I understand that inconsistent blackbox behavior like this is heavily frowned upon. It’s still extremely helpful for data analysis contexts.