#zenofpython — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #zenofpython, aggregated by home.social.
-
as a fan of @pythonbytes, @realpython, and @talkpython - i especially enjoyed this podclash. Some very reasonable observations on cloud, microservices, data protection, web analytics and more - this show felt quite the #zenofpython https://realpython.com/podcasts/rpp/272/
-
as a fan of @pythonbytes, @realpython, and @talkpython - i especially enjoyed this podclash. Some very reasonable observations on cloud, microservices, data protection, web analytics and more - this show felt quite the #zenofpython https://realpython.com/podcasts/rpp/272/
-
as a fan of @pythonbytes, @realpython, and @talkpython - i especially enjoyed this podclash. Some very reasonable observations on cloud, microservices, data protection, web analytics and more - this show felt quite the #zenofpython https://realpython.com/podcasts/rpp/272/
-
as a fan of @pythonbytes, @realpython, and @talkpython - i especially enjoyed this podclash. Some very reasonable observations on cloud, microservices, data protection, web analytics and more - this show felt quite the #zenofpython https://realpython.com/podcasts/rpp/272/
-
as a fan of @pythonbytes, @realpython, and @talkpython - i especially enjoyed this podclash. Some very reasonable observations on cloud, microservices, data protection, web analytics and more - this show felt quite the #zenofpython https://realpython.com/podcasts/rpp/272/
-
When people have pushed that around me, I show them the Zen of Python. It's important enough that it's the climactic line.
> Namespaces are one honking great idea -- let's do more of those!
`from x import y` throws one of Python's greatest features in the trash, and mashes everything into a single namespace, with all the opportunities for collisions, accidental overwrites, thinkos, and other problems.
Don't do it.
-
When people have pushed that around me, I show them the Zen of Python. It's important enough that it's the climactic line.
> Namespaces are one honking great idea -- let's do more of those!
`from x import y` throws one of Python's greatest features in the trash, and mashes everything into a single namespace, with all the opportunities for collisions, accidental overwrites, thinkos, and other problems.
Don't do it.
-
When people have pushed that around me, I show them the Zen of Python. It's important enough that it's the climactic line.
> Namespaces are one honking great idea -- let's do more of those!
`from x import y` throws one of Python's greatest features in the trash, and mashes everything into a single namespace, with all the opportunities for collisions, accidental overwrites, thinkos, and other problems.
Don't do it.
-
When people have pushed that around me, I show them the Zen of Python. It's important enough that it's the climactic line.
> Namespaces are one honking great idea -- let's do more of those!
`from x import y` throws one of Python's greatest features in the trash, and mashes everything into a single namespace, with all the opportunities for collisions, accidental overwrites, thinkos, and other problems.
Don't do it.
-
When people have pushed that around me, I show them the Zen of Python. It's important enough that it's the climactic line.
> Namespaces are one honking great idea -- let's do more of those!
`from x import y` throws one of Python's greatest features in the trash, and mashes everything into a single namespace, with all the opportunities for collisions, accidental overwrites, thinkos, and other problems.
Don't do it.
-
Unlock the secrets of Pythonic programming! Dive into the Zen of Python and learn how to write cleaner, more efficient code. From simplicity to readability, discover the principles that make Python unique. #Python #CodingTips #ZenOfPython
https://teguhteja.id/the-zen-of-python-guide-pythonic-programming/
-
Unlock the secrets of Pythonic programming! Dive into the Zen of Python and learn how to write cleaner, more efficient code. From simplicity to readability, discover the principles that make Python unique. #Python #CodingTips #ZenOfPython
https://teguhteja.id/the-zen-of-python-guide-pythonic-programming/
-
Unlock the secrets of Pythonic programming! Dive into the Zen of Python and learn how to write cleaner, more efficient code. From simplicity to readability, discover the principles that make Python unique. #Python #CodingTips #ZenOfPython
https://teguhteja.id/the-zen-of-python-guide-pythonic-programming/
-
Unlock the secrets of Pythonic programming! Dive into the Zen of Python and learn how to write cleaner, more efficient code. From simplicity to readability, discover the principles that make Python unique. #Python #CodingTips #ZenOfPython
https://teguhteja.id/the-zen-of-python-guide-pythonic-programming/
-
Unlock the secrets of Pythonic programming! Dive into the Zen of Python and learn how to write cleaner, more efficient code. From simplicity to readability, discover the principles that make Python unique. #Python #CodingTips #ZenOfPython
https://teguhteja.id/the-zen-of-python-guide-pythonic-programming/
-
Namespaces are one #honking great idea – let's do more of those! (t p) #ZenOfPython
-
Just found myself considering when/whether to work on a particular blog post that’s been bobbing about in my brain, and I answered myself with “Now is better than never. Although never is often better than *right* now.”
I have been assimilated.
-
Just found myself considering when/whether to work on a particular blog post that’s been bobbing about in my brain, and I answered myself with “Now is better than never. Although never is often better than *right* now.”
I have been assimilated.
-
Just found myself considering when/whether to work on a particular blog post that’s been bobbing about in my brain, and I answered myself with “Now is better than never. Although never is often better than *right* now.”
I have been assimilated.
-
Just found myself considering when/whether to work on a particular blog post that’s been bobbing about in my brain, and I answered myself with “Now is better than never. Although never is often better than *right* now.”
I have been assimilated.
-
Just found myself considering when/whether to work on a particular blog post that’s been bobbing about in my brain, and I answered myself with “Now is better than never. Although never is often better than *right* now.”
I have been assimilated.
-
#Python query: should the string message inside Exception (sub)classes be considered part of the API / contract?
On one hand, client code performing "stringly typed" comparisons to a caught exception's text, is a code smell. Changing to raise a subclass of the old exception, w/ a different message, "should" be backwards compatible.
OTOH, esp when a codebase historically had too-broad exception classing, users have to #ZenOfPython rule 9 & do that string compare. Now they're broken. Ugh.
-
#Python query: should the string message inside Exception (sub)classes be considered part of the API / contract?
On one hand, client code performing "stringly typed" comparisons to a caught exception's text, is a code smell. Changing to raise a subclass of the old exception, w/ a different message, "should" be backwards compatible.
OTOH, esp when a codebase historically had too-broad exception classing, users have to #ZenOfPython rule 9 & do that string compare. Now they're broken. Ugh.
-
#Python query: should the string message inside Exception (sub)classes be considered part of the API / contract?
On one hand, client code performing "stringly typed" comparisons to a caught exception's text, is a code smell. Changing to raise a subclass of the old exception, w/ a different message, "should" be backwards compatible.
OTOH, esp when a codebase historically had too-broad exception classing, users have to #ZenOfPython rule 9 & do that string compare. Now they're broken. Ugh.
-
#Python query: should the string message inside Exception (sub)classes be considered part of the API / contract?
On one hand, client code performing "stringly typed" comparisons to a caught exception's text, is a code smell. Changing to raise a subclass of the old exception, w/ a different message, "should" be backwards compatible.
OTOH, esp when a codebase historically had too-broad exception classing, users have to #ZenOfPython rule 9 & do that string compare. Now they're broken. Ugh.
-
#Python query: should the string message inside Exception (sub)classes be considered part of the API / contract?
On one hand, client code performing "stringly typed" comparisons to a caught exception's text, is a code smell. Changing to raise a subclass of the old exception, w/ a different message, "should" be backwards compatible.
OTOH, esp when a codebase historically had too-broad exception classing, users have to #ZenOfPython rule 9 & do that string compare. Now they're broken. Ugh.
-
Go Proverbs - https://go-proverbs.github.io/
Like #ZenOfPython but for #Go.
„Clear is better than clever“ and „A little copying saves a dependency“ are my favs. What are yours?
-
Go Proverbs - https://go-proverbs.github.io/
Like #ZenOfPython but for #Go.
„Clear is better than clever“ and „A little copying saves a dependency“ are my favs. What are yours?
-
Go Proverbs - https://go-proverbs.github.io/
Like #ZenOfPython but for #Go.
„Clear is better than clever“ and „A little copying saves a dependency“ are my favs. What are yours?
-
