Not a channel, but talks by David Beazley on Python topics are gems. High insight density. The presentation are often 60+ pages, and you can spend hours playing with each concept in every 'slide'. His talks are rabbit holes.
Raymond Hettinger tweets snippets of code that are delicious. His talks are really useful, too. Specifically, the one entitled 'Beyond PEP8' which focuses you on the impact you can have by zooming out of details and concentrate on good design.
This is something I've been using. I write code that uses a yet to be API, and ask myself and colleagues if it makes sense for them to use it.
For example, I'm writing a Python wrapper for MinIO's admin command line interfaces 'mc' and 'minio' which the Python client lacks. Put up the docs first at https://big-mama-tech.gitlab.io/bmc and asked colleagues and the MinIO folks if it's acceptable/useful before really going for parity.
"I'm going to watch a David Beazley video on generators". Start playing the video. He shows the first slide and explains a few things. I read the code in the slide, then go to a terminal and launch a Python interpreter, and write the code without looking at the screen, to cement the concept more than if I simply had copied it or, God forbid, just watched the video.
Here's the problem: every slide shows some weird behavior or using something I use daily in a way I didn't know it could be used, and I do read the Python language reference for fun. Next thing you know, I spent one hour on the first slide playing with the concept, and writing snippets to show how I could use it to solve problems I had faced before. The presentation is 60+ slides or the talk is 3 hours. More often than not live coding the whole thing.
Raymond Hettinger tweets snippets of code that are delicious. His talks are really useful, too. Specifically, the one entitled 'Beyond PEP8' which focuses you on the impact you can have by zooming out of details and concentrate on good design.
This is something I've been using. I write code that uses a yet to be API, and ask myself and colleagues if it makes sense for them to use it.
For example, I'm writing a Python wrapper for MinIO's admin command line interfaces 'mc' and 'minio' which the Python client lacks. Put up the docs first at https://big-mama-tech.gitlab.io/bmc and asked colleagues and the MinIO folks if it's acceptable/useful before really going for parity.