{"id":6894,"date":"2021-07-31T13:00:33","date_gmt":"2021-07-31T13:00:33","guid":{"rendered":"http:\/\/TheNextWeb=1362454"},"modified":"2021-07-31T13:00:33","modified_gmt":"2021-07-31T13:00:33","slug":"how-to-get-the-most-out-of-python-classes","status":"publish","type":"post","link":"https:\/\/www.londonchiropracter.com\/?p=6894","title":{"rendered":"How to get the most out of Python classes"},"content":{"rendered":"\n

There should only be one \u2014 and preferably only one \u2014 obvious way to do it\u201d, says the Zen of Python<\/a>. Yet there are areas where even seasoned programmers debate what the right or wrong way to do things is.<\/p>\n

One of these areas is Python classes. Borrowed from Object-Oriented Programming, they\u2019re quite beautiful constructs that you can expand and modify as you code.<\/p>\n

The big problem is that classes can make your code more complicated than necessary, and make it harder to read and maintain. So when should you use classes, and when should you use standard functions instead?<\/p>\n

This story is a deeper dive into the matter. So if you\u2019re in a hurry, you can skip the following two sections and scroll right down to the sections When to use classes<\/em> and When classes are a bad idea<\/em>.<\/p>\n

Python classes: the very basics<\/strong><\/h2>\n

Classes are objects that allow you to group data structures and procedures in one place. For example, imagine you\u2019re writing a piece of code to organize the inventory of a clothes shop.<\/p>\n

You could create a class that takes each item of clothing in the shop, and stores key quantities such as the type of clothing, and its color and size. We\u2019ll add an option to add a price, too.<\/p>\n

\"classes\"