Sai Yalamarty
@ysai.me
@lukasz.langa.pl Hey Łukasz! Implemented this after listening to your conversation about pyscript in the latest core. py episode (pycon recap).
It also captures and outputs any python code errors to the terminal.
It's built on top of pyscript!
It also captures and outputs any python code errors to the terminal.
It's built on top of pyscript!
July 2, 2025 at 7:24 PM
@lukasz.langa.pl Hey Łukasz! Implemented this after listening to your conversation about pyscript in the latest core. py episode (pycon recap).
It also captures and outputs any python code errors to the terminal.
It's built on top of pyscript!
It also captures and outputs any python code errors to the terminal.
It's built on top of pyscript!
Also works with the `git blame` cli command when used with a flag --ignore-revs-file
April 8, 2025 at 8:16 PM
Also works with the `git blame` cli command when used with a flag --ignore-revs-file
Definite yay.
But I think a “for…else” doesn’t feel intuitive and hence I tend to get confused when the else is executed. If it was something I used regularly, then I would remember.
But “try..except..else..finally” does feel intuitive.
But I think a “for…else” doesn’t feel intuitive and hence I tend to get confused when the else is executed. If it was something I used regularly, then I would remember.
But “try..except..else..finally” does feel intuitive.
December 3, 2024 at 7:02 AM
Definite yay.
But I think a “for…else” doesn’t feel intuitive and hence I tend to get confused when the else is executed. If it was something I used regularly, then I would remember.
But “try..except..else..finally” does feel intuitive.
But I think a “for…else” doesn’t feel intuitive and hence I tend to get confused when the else is executed. If it was something I used regularly, then I would remember.
But “try..except..else..finally” does feel intuitive.