Python Forum

There are only two answers there, and neither supports using a class where a function will do.

A few recommendations to others using this thread for example code:

Don't overcomplicate code.
Different languages do things in ways that make sense for them, don't force all languages to use the some patterns.
A copy-pastable version of the spirit of this code is

def has_internet():
   return '127.0.0.1' != socket.gethostbyname(socket.gethostname())

(Oct-12-2016, 11:38 PM)wavic Wrote: [ -> ]This video is quite popular. I think it tells everything

I actually quite dislike that video.  He comes off pretty damn condescending.  Yes you shouldn't write a class when you don't need one which are the examples he shows.  But if you do need one you should use one.

His examples deal with a lot of cases where people write place holders for future potential use cases.  So yes, don't overthink and write a bunch of useless code for the ostensible reason of "future proofing" but nonetheless, if you need encapsulated state with associated methods, you should be writing classes.

Hey did criticize the the standard libs for not using a Heap class. He's definitely more anti-class than I am, but he's still not really anti-class. And I think this OP is an example that makes his video worth having done.