You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I seriously get the impression that Pandas is actively being sabotaged. As a case in point, DataFrame.lookup was deprecated in v1.2.0. The problems with this are:
The doc for DataFrame.lookup says to see itself for an example. Well, there is no example in the doc page. The only example I'm aware of is here instead which is a different page.
The changelog for this deprecation points to GH18682 which looks to be wholly irrelevant to this change. A lot has gone wrong here.
There is significant user code that already uses lookup. Why break it? If the current implementation of lookup is suboptimal, shouldn't it be optimized instead?
Is your feature request related to a problem?
I seriously get the impression that Pandas is actively being sabotaged. As a case in point,
DataFrame.lookup
was deprecated in v1.2.0. The problems with this are:DataFrame.lookup
says to see itself for an example. Well, there is no example in the doc page. The only example I'm aware of is here instead which is a different page.lookup
. Why break it? If the current implementation oflookup
is suboptimal, shouldn't it be optimized instead?melt
whenlookup
works quite simply. For example, compare this simple answer usinglookup
with this complicated answer usingmelt
.Does nobody review changes, docs, and release notes anymore prior to release? It looks this way.
Describe the solution you'd like
lookup
.lookup
if attainable usingmelt
.The text was updated successfully, but these errors were encountered: