dmuller

Hello, author here. I edited the article a bit for brevity. But, yes I started by checking all the fuses and relays. I didn't find any bad relays. Unplugging the ROOM fuse also fixed the problem, but at the expense of other interior features (like my stereo).

Hello, author here. I did do as you described first---I pulled the ROOM fuse and the draw also went away. But, at the expense of more interior features (e.g. my stereo).

In case it's helpful for anyone else, here's what publishing team had to say:

"Yes, your book will eventually show up on the O'Reilly Learning Platform, but it'll be a while still. Most of our books first appear there four to eight weeks after they go into print. So just keep an eye out on OLP, because it's coming."

I've not read Fluent Python, but its table of contents looks quite extensive, and covers a lot of good ground.

Intuitive Python does cover some things that aren't present in Fluent Python (as far as I can tell): checking your code for errors with flake8 + mypy, using pdb to debug, profiling with cprofile, running external programs with subprocess, using the sqlite3 module, tempfile module, datetime + timezones, the Python official Docker images, and pip.

Fluent Python's ~800 pages really give great coverage for much of the standard library and patterns your students will see in wild Python, but the more compact ~140 page Intuitive Python might layer on some additional knowledge too.

Hi - that's a good question about the O'Reilly platform. I can ask my editor and get back to you on that. What's the best way to reach you?

Yeah - I agree, I don't like the default behavior of subprocess.run either. As another commenter pointed out, passing the check=True argument makes subprocess.run raise an Exception if the underlying command doesn't return 0 (would have been nice if this was the default).

Those are two good use cases (using the lower level subprocess.Popen + process group signaling) that the book does not cover---thanks for bringing them up.

Hey - thanks for checking the book out.

Yeah, you are correct---the book does not cover packaging a Python program as a click and run style executable.

It's definitely a tricky problem. (Depending on the audience for the tools (e.g. if it's developers), one potential option might be to package your code in a Docker image and distribute it that way---although that's not without its own drawbacks.)

Other commenters have posted potential tools to check out too.

I think Python definitely has its drawbacks, and it's not fast. The other downsides listed in that article (whitespace, variable scoping, lambdas, mobile, etc.) may also be get in your way sometimes, but seems doubtful that they are language killers...I agree the argument presented in that article is weak.

I'm biased, but I think Python as your daily driver language is a great choice.