In my opinion, learning anything requires talent. Without talent, hard work alone is useless. Of course, most people have something they are good at. Talent is innate, but it is not obvious and usually requires hard work to discover.

People who are stupid will definitely not be able to learn python. The grammar of python is simple enough. But having said that, it doesn’t take long for the subject to learn python, and he can still figure out django blog (although I think it’s easy). It shows that you are not too "stupid" to learn python.

You feel that you are "stupid" not in terms of IQ, but more in terms of programming experience. Learning a language is actually not difficult, but mastering a language to develop an application or even a system still requires a lot of knowledge. On the one hand, this knowledge can be learned systematically, such as reading documents and consulting predecessors. On the other hand, through encountering, solving, summarizing and gradually accumulating in actual development.

It’s like a martial arts. If you want to improve your skills, you probably have to practice hard or go into actual combat. Others have given you martial arts tips, but if you don't practice them yourself, your internal strength won't grow on its own. Not everyone can directly teach internal skills to masters like Duan Yu and Xu Zhu.

In short, learn more, do more, think more, summarize more, and share more.

Go and write the code for the producer-consumer problem

I was the same way at the beginning, and I was confused about Python’s threading and multiprocessing libraries.

It’s a pity that I first found a few relatively simple examples on the Internet to experience it (it still feels different from the style of Java, which is straightforward and easy to understand)

LZ, I am in the same situation as you. I am self-taught in py. With your behavior, I think I am "stupid" than you. But I think it’s more important to understand the concepts and essential aspects of many things

I also want to know what your problem is

Why do you feel like you are talking about me?

The reason is simple.

To understand multi-processing and distribution, you need to at least understand:
1. Single process bottleneck.
2. Multi-process working principle.
3. Multi-process operation method under Python
Just wait for a bunch of questions.

If you go online every day to look for Python multi-process examples, you will definitely not be able to figure them out.

1. It’s only four months. You don’t need to ask for so much. The person who “can write a Python-based Douban FM command line in one month” may have been working for more than four years. 2. It’s good to be able to understand it with just a search. Many people don’t know how to search. It’s like this with tools, the more you use them, the more familiar you become.

In addition, the object-oriented view of Django is only available in later versions of Django. It was also a functional view at the beginning. Python itself is an object-oriented and procedural language. It is enough to solve the problem instead of using objects. The more advanced you can get, the more low-level the process becomes. When you need an object to even write a HelloWorld, you will realize how disgusting it is.

Finally, I still want to say that a tool is a tool. Doubting your intellectual talent because of a tool makes you feel aggrieved. Hahaha, I just want to laugh when I think about it. . .

It would be best to post a piece of code as an example. . .

Follow the following steps:

1. There are several ways to collect python to implement multi-process
2. Compare the differences between several methods, what technologies are used, and what are the principles
3. Try to write some consumption code yourself (such as the daemon of the consumption queue)
4. Go back to 2 and continue trying