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/

I took the liberty of adding @kevinrenskers "Django views versus the Zen of Python" to the https://github.com/filiplajszczak/awesome-zen-of-python list #django #python #zenofpython

@yantor3d

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.

#python #namespace #namespaces #ZenOfPython #zen #import

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

Are you following the Zen of Python when it comes to best practices for environment settings and versioning? 🧘

Learn the tools and techniques for “Bootstrapping your Local Python Environment.” 🎥 👉 https://loom.ly/48Al9vk

#PyConUS #ZenofPython #PythonDevelopment

New article:

⚠️Why you should avoid import * in Python 🐍
https://pybit.es/articles/why-you-should-avoid-import-in-python/

Covering:
- Why modules are great and namespacing explained
- Why import * is a problem
- A practical example where a function gets overriden
- The recommended way to do imports
- What PEP8 has to say about this
- Protection workaround, use __all__ to define your module's public interface

#python #pythonprogramming #modules #encapsulation #namespacing #zenofpython #bestpractices #pitfalls #imports #dundermethods

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 #ZenOfPython

#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?

#GoProverbs #Golang

one_obvious = "more than one"

print(f'There should be {one_obvious} way to do it.')

#ZenOfPython

The Zen of Go https://hackeroo.co/314335

#ZenOfPython

@urahito_solution

> というかあれに仮に著作権が存
> 在したらと考えると
> https://qiitadon.com/web/statuses/99370803095200799

#ZenOfPython パブリック・ドメインらしいので大丈夫じゃないですかね？

https://en.wikipedia.org/wiki/Zen_of_Python

ぜひ萌え要素も入れて薄い本で！（そっちが怒られる）

@Lomig Pardon désoler j'aurais du faire plus attention (faudrait il une instance mastondon pour les bretonnant ?). Pour moi le beurre doux n'existe pas c'est du beurre sans sel, je précise beurre salé car //explicite is better than implicite// #zenOfPython