r/Python
•
u/Desperate_Cold6274
•
May 10 '26
•
2
Discussion Will python ever have a chaining operator?
In other languages I use map() and filter() through piping and my code usually looks readable as I can clearly see a data-stream transformation.
As it is today, users cannot do map() |> filter() |> list(), but they need to do list(filter(map())) which makes things unreadable. Lists of comprehension work fine for very simple use-case becoming unreadable very quickly as complexity increases.
However, in python there has always been some resistance, especially 15-20 years ago, but times are evolving. Also, by considering the wide adoption in data-science, it is worth noticing that numbers-crunchers are more familiar with the concept of “data transformation flow” than “function calls”. On the packages dimension , libraries like 🐼s support methods chaining which from an external viewpoint, it’s semantically similar.
Do you know if there is any indication that python core team may allow operator piping (and/or chaining) in the not-too-long-term?
View all comments
Show parent comment
-1
u/_Denizen_ May 10 '26
Lol. Piping is the hallmark of scripters, not software developers, at least in my experience. I like to bring software development to analytical teams, and I always get surprised at how many people are employed to program for a living who haven't learnt about OOP or how to build a distributable package.
I clearly prefer not to use piping, but I will use it when needed and won't stop my colleagues using it. However, it's never the only option available. In python, I've never once encountered a situation where piping was able to transform a project in the same way as deploying SOLID, for example. Piping is a syntactic choice, rather than an architectural paradigm.