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'm doing a Kaggle contest this weekend and noting a couple of patterns in typical EDA Python work that are awkward in Hy.
Multidimensional slicing like X[i,j], X[a:b,j], X[i,:].
Conditional slices like X[X.type == "N"]
Chained slices like X[X.type == "N"]["value"]
The latter, for example, looks like
(get (get X (= (get X "type") "N")) "value"))
Can we consider this a feature request? It takes learning some numpy to figure out what are the explicit functions behind the syntax sugar, so it may not get done in any foreseeable future -- but it's a common Python use case and thus a major selling point for Hy.
The text was updated successfully, but these errors were encountered:
I'm doing a Kaggle contest this weekend and noting a couple of patterns in typical EDA Python work that are awkward in Hy.
X[i,j]
,X[a:b,j]
,X[i,:]
.The latter, for example, looks like
Can we consider this a feature request? It takes learning some numpy to figure out what are the explicit functions behind the syntax sugar, so it may not get done in any foreseeable future -- but it's a common Python use case and thus a major selling point for Hy.
The text was updated successfully, but these errors were encountered: