The Zen of Python
Let us start by understanding the design philosophy of Python.
I have reproduced below what is called the The Zen of Python. Have a quick read.
Beautiful is better than ugly. Explicit is better than implicit. Simple is better than complex. Complex is better than complicated. Flat is better than nested. Sparse is better than dense. Readability counts. Special cases aren't special enough to break the rules. Although practicality beats purity. Errors should never pass silently. Unless explicitly silenced. In the face of ambiguity, refuse the temptation to guess. There should be one-- and preferably only one --obvious way to do it. Although that way may not be obvious at first unless you're Dutch. Now is better than never. Although never is often better than *right* now. If the implementation is hard to explain, it's a bad idea. If the implementation is easy to explain, it may be a good idea. Namespaces are one honking great idea -- let's do more of those!
As you can infer from the text, Python codes are designed to be simple and readable.
This allows you to concentrate on solving problems at a higher-level of abstraction, without having to worry about the minute lower-level details (like memory allocation or deallocation), as you may have been used to with C++. Depending on which area of Computing you work on, you may find that you will often not need such low level of control. This compromise will allow you to develop your code faster, and hopefully make the process of writing code much more enjoyable, since you will be writing more abstracted, readable code. This ability is especially useful for Machine Learning or Data Science experimentations, where problem solving, flexibility, and the ability to make quick changes are important. You can leave any low-level optimisations to those who specialise in them.