:imooc。 /course/list? c=python
:tutorialspoint。 /python/index.htm
Python tutorials on the above two websites are both quite good.
How do girls learn python? Hello, if you want to learn python, I suggest you sign up for a training class, so you can take fewer detours. If you want to teach yourself, you can buy some introductory books and practice more code, and your ability will naturally go up.
How do novices learn python and learn python well? I advise beginners not to download integrated development environments with IDE functions, such as Eclipse plug-ins. 2) After downloading, you can start learning. In the process of learning, I suggest downloading some python learning documents, such as dive into python, OReilly-Learning Python and so on. By learning grammar, you can master keyword grammar, function grammar, mathematical expressions and so on in python. 3) After learning the basic grammar, you can learn interactively. Python has a good interactive learning mode. For the examples in the book, you can practice through the interactive platform, deepen your impression through practice, and achieve the purpose of learning and mastering. 4) After learning the above three steps, we have roughly mastered the common methods, keyword usage and function grammar of python. In the next study, you can start to learn the use of commonly used modules, such as os, os.path, sys, string module and so on. We can get familiar with using the functions in the interactive environment first. If we encounter problems when using functions, we can refer to the chm help file that comes with python installation. 5) In order to master python better, our study can't just stay at the stage of learning some grammars or APIs. At this stage, we can try to solve some problems in our project with python. If the project is not developed in python, then we can think about whether we can use python to make some utilities that the project team can use, which can simplify the tasks of the project team members and improve our work efficiency. If there are no projects, you can also find some topics to practice. 6) After the above exercises, our python knowledge level is definitely getting higher and higher. Next time we study, we will walk up a flight of stairs. In order to apply what they have learned to project development or product development, they must also learn the knowledge of network and database that must be mastered in enterprise application development. Learning here is more than just learning python itself. If you haven't learned and mastered the knowledge of network and database before, you can take this opportunity to make up for it at this stage. 7) Here, I think we are familiar with the usage of python. Even if we forget the usage of api, we can use api in a short time by looking at the documentation. So what are we going to learn next? That is the ability to design. In the process of learning design ability, if you are not clear about object-oriented concepts such as classes, you can also learn or consolidate them at this stage. Just as airplane designers design airplanes by learning patterns, we can also learn design by learning classic examples from books. With the basic concept of design, we can begin to design our program. At this stage, it is important for us to learn to extract the ideas of images and design our modules by isolating the change points. 8) At this stage, we have really started. In the next work, we need to serve the project quickly through what we have learned. At this stage, besides mastering python's own modules, we'd better master some open source frameworks widely used in the industry, such as isted, peak, django, xml and so on. Using them skillfully can realize lightning development and greatly save valuable time of the project. 9) You are already an expert in python. At this stage, we will encounter some deep-seated concrete difficulties in our work. Facing these problems, we have our own thinking direction and way.
It is easy to learn python well and get familiar with grammar. If you really want to do something, you still have to study and practice. I'm a beginner, too. I don't feel so familiar.
Practice. Practice.
This is true of learning any language.
Then read and practice reading.
It is best to find a job or a project.
It is over; be doomed
How to Learn Python Crawlers It is suggested to learn native crawlers first, and then use the crawler framework. Recommended materials and learning process can be viewed on this page:
:zhuan LAN . zhi Hu/p/2 1479334
How to learn Python GUI programming? Personally recommend PyQt.
There is a good textbook.
Just search English online.
Write more, practice more and debug more.
Choose a GUI, read official website's guide, step by step, is there a market for python GUI? Python version of QT is recommended.
I always think that for a beginner, the technical trend in the IT field can't catch up, and I have no ability to catch up. I often see my DDMM students throw away their textbooks and sell some expensive books, such as C # and VB.Net, which makes me feel very sad. And many BBS friends who don't know what pointers are, are happy to discuss that there can't be pointers in C#, which makes me feel funny. C# is like ASP in those days, "like a strong wind in spring, which blows at night and blows open the petals of ten thousand pear trees". As a result, the information colleges of many schools have become "network colleges". Many college students in Grade 96 and Grade 97 have gone online. Of course, I don't have any consciousness of discriminating against a certain industry. I just think they can go further if they spend more time in basic courses to catch up with these fashionable technologies. Several misunderstandings Beginners' pursuit of the C# trend is actually just one of several misunderstandings often encountered in the learning process. I will use some practical examples to illustrate these phenomena. You can see if you belong to one or several of them step by step: think that computer technology is equal to programming technology: some people have this impulse subconsciously even if they don't have this idea. To my surprise, many students in the School of Information also have this idea. He thinks that computer major is programming major, and he ignores all courses that have nothing to do with programming or are not very relevant. Extreme students don't read books as long as they don't have the word "programming" In fact, programming is only a kind of labor with the lowest complexity in the application of computer technology, which is why people at the bottom of the IT industry are coders. Computer technology includes multimedia, computer network, artificial intelligence, pattern recognition, management information system and so on. Programming is only the process of expressing the algorithm in the theoretical research or engineering practice of these specific technologies. Programmers do not necessarily have high knowledge of computer technology. An interesting phenomenon is that many researchers who master computer technology do not know how to program. Online hype and good working conditions in reality confuse the labor of programming. In fact, every programmer knows in his heart that these things are not more difficult to learn than other majors, so naturally they will not be high-end. I have read a textbook "Principles of Computer Network" written by a girl. This girl, like a primary school student, draws all the lines on the book, and her notes are full, so it must be thicker when printed. What I don't understand is, is it necessary to take notes in a course like the principle of computer network? Our exam-oriented education has really harmed many students. When studying principles and other courses, many students recite their memories word for word like studying the principles of Marxism-Leninism. This is the stupidest behavior I have ever seen. The so-called "principle" means that you need to master why it does this and learn why, not how. Extremely serious students memorize the maximum length of Ethernet cable, the length of data frame, the meaning of each field, the format of IP header, etc., but forget the principle of routing and the purpose of TCP/IP protocol design. In short, many people spend a lot of time reciting, but they have learned nothing. The same is true of these students learning programming. They remember every detail of C++ grammar accurately. I read the C++ tutorial and Thinking with C++ (it's really a good book), in which C++, C++ references, this C++, that C++ ... and then I found myself forgetting some C++grammar, and finally I went back to make up. A younger brother said to me, "C++ is too difficult. You study here and forget there. When you learn inheritance, you forget the template. " My answer is, "It's easy not to study". I didn't teach him badly. I just told him that adhering to the grammar of C++ is as meaningless as Kong has shown off several ways to write fennel words of fennel beans. You don't need to care too much about the grammar of C++, just start programming. If you don't remember anything, check MSDN and get it done immediately. I have a conclusion that the understanding of program grammar is the most insignificant knowledge in the actual development process. That's why when I was writing a small program in Basic for my classmates (I didn't learn it before), I only spent half an hour reading grammar, then finished writing the program in half an hour, and forgot all the keywords in Basic after one hour. Regardless of the foundation, blindly catch up with fashionable technology: finally, focus on the topic. Most people want their things to run immediately and turn into money. This idea makes sense for a programmer or project manager who enters the professional field. IT technology is progressing too fast, and if he doesn't follow up, he will lose his job. But for beginners (especially college students with plenty of time), this idea is puzzling. A beginner who has not entered the industry competition, the biggest capital is to have enough time to calm down and learn the basic things, and learn why rather than how. Modern technology is often easy to master, and it is getting easier to master, which is driven by commercial interests, in order to minimize the cost of software development. But this is the reality in the IT field. The easier it is to master, the more people will learn and the faster it will be eliminated. Every time a new technology comes out, there are many novices to follow up. These beginners spend a lot of time in the follow-up process because they lack the necessary foundation. When he learns, this technology will soon be eliminated. Basic courses, such as data structure and working system principle. , can significantly reduce the slope of the learning curve when you learn new technologies, although you can't realize a linux immediately (which is why many people laugh at the uselessness of theoretical courses). Even for many key technologies (such as Win32 SDK programming and DDK programming), it is indispensable. A living example is me and one of my classmates. When I was a freshman, I couldn't find the start button. He could already write some simple assemblers. I spent all my time studying assembly, computer architecture, data structure, working system principle, etc. in Grade Two, and he began to learn HTML and VB, catching up with the trend of ASP. When I was a junior, I began to learn the programming principles of Windows * and SDK. It took a long time, and then I can develop a decent application with VC. I was annoyed because my classmate's program was running and I was still learning how to create a dialog box. I didn't realize how correct my choice was until I graduated. The company I negotiated with offered him more than twice his salary. Here is an inappropriate example: suppose it takes 4 months to learn VB programming, and it takes 1 year to learn basic courses and VC programming. So if you learn VB first and then learn the latter, the time will not be reduced, or 1 year. Conversely, if you learn the latter first and then learn VB, you may only need 1 week to learn very skillfully. Several important basic courses if you are a student, or you have enough time. I suggest you master the following knowledge seriously. My suggestion is aimed at beginners who want to make achievements in IT technology. At the same time, I also listed some bibliographies, which should be available in bookstores. To be honest, when I read other people's articles, my greatest wish is that the author make a list of books. College English.-Don't be ridiculous. I strongly recommend this course, because reading without professional literature is unthinkable. Chinese versions are often published in the Year of the Monkey, and now many publishing houses simply print electronic texts directly. The way to learn is to force yourself to read the original textbook. You won't understand it at first, but if you use it too much, you will naturally become skilled. Eating hard and doing hard is definitely a quality that any industry needs. Computer architecture and assembly language-books about architecture are everywhere, and they are similar, but assembly has a very good book. Course of 80x86 Assembly Language Programming (Tsinghua University Press, black cover, by Yang Jiwen). You need to focus on the programming of post-386 protection mode. Otherwise, when you study the bottom of modern production system, you will feel that you are reading a gobbledygook. Principles of Computer Operating System-Our development is always carried out on a specific operating system. If not, there is only one possibility: you are implementing an operating system yourself. In any case, Principles of Working System is a must-read. This is just like when we make a peripheral for a chip, we must understand the basic working sequence of the chip. There are many books in this category, and I haven't found out which one is outstanding. I just think that if I have time after reading these books, I should read Insider of Windows 2000 (Microsoft Press, I read the E version, and the Chinese title must be Insider of Windows 2000 technology). Another article about ZDNET has discussed the necessity of learning it. Data Structure and Algorithm-This course can determine a person's programming level and is the core course. My first choice is the Tsinghua version (Zhu, Liu). Many people like to buy the C++ version, but I don't think it is necessary. The syntax of C++ makes the algorithm implementation process much more complicated, and many teachers like to use modules to make the algorithm more complicated. After learning the C version, you'd better browse the C++ version. Software Engineering-This course becomes more and more important as it goes on, although it is as unintelligible as looking at philosophy at the beginning. My suggestion is to study Practical Software Engineering (Huang, Tsinghua). Don't spend too much time remembering the rules and regulations. If you don't understand them, just jump over. Every time you complete a software design task (whether it is an internship or a job), you will look back and look back, and you will gain something every time. Windows Programming-Peking University Press, Petzold I suggest that anyone who attempts to design a Windows program should finish it carefully before learning VC. Moreover, the books in Windows 2000 in front are better at the back of this book. In this book, there is no C++, no GUI and no controls. Some are how to use the original C language to complete Windows programming. After learning, you will find that VC is actually very studious. Never learn VC without reading this book. You'd better not touch it. Many famous schools I know even use it as teaching materials. Obviously, it is very important. I think the above courses are necessary (if you want to be a Windows programmer). Other courses have such a simple choice: if you are a computer major, please learn all your professional basic courses well. If not, please refer to the curriculum of Computer Department. If you find that you can't read a book, please turn to the end of the book, look at its references, find them and learn them, and then look back at the book. If there is the word "principle" in the title of the book, don't memorize the details. You should master the essentials at a speed of at least 50 pages a day. Try to practice a theory or algorithm on the computer. You can also read many book reviews about CSDN. These book reviews can help you decide what kind of books to read. Reading too many books in three provinces every day is easy to get lost. Every night, you must think about what you have learned, what other related things need to be mastered, what you are most interested in, whether you have spent too much time on a book, and so on. At the same time, you should also think more about the most likely applications in the future, so that you can lead the technology trend instead of catching up with it. At the same time, try to make use of the technology and theory you have now to do something new. Persisting in doing this can make you really become a software "developer" rather than just a coder. Spending the most time on study is the last advice for beginners. Try to reduce the time of playing SC or CS every week, and it is best not to play. At the same time, if your ASP technology has been able to get money, and even a company invites you to prove that your talent can ensure that you can get better income after studying hard, you should do more complicated things. In the long run, it applies to everyone. I believe you have been able to decide whether to learn C # or when.