Shulou(Shulou.com)06/02 Report--

This article is about how to optimize Python development and configuration. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.

I. the compiler's return to the compiler

It can be called a waste of time when developers spend their time doing things that computers can do better. A typical example is that programmers spend their time looking for bug that can be more accurately located by automated tools.

Perhaps because of the nature of the Python dynamic language and the reason it was regarded as a "scripting" language in the early days, static code analysis tools and spell checkers are still rarely seen on Python.

However, such tools are very helpful, they can basically check out a specific type of bug and syntax errors and remind developers to avoid making these mistakes. For example, these tools can find functional bug identifiers that affect the normal compilation of code, such as misspelled identifiers, or find quality problems with code, such as unused variables and references.

Of course, static analysis tools are not a panacea, but at least they do help us reduce the time spent on debug and code review, as well as the time invested in the early stages of development. If you only want one, only one tool to improve the quality of your Python code without being disturbed by error corrections and verbose prompts, then it is recommended that you use Pyflakes. Pyflakes is an open source, free, and easy to install spell checker.

In order to get feedback faster and discover bug earlier, it is recommended that you integrate Pyflakes into your code editor and back-end server. Integrating the ability to automatically fix code errors into your entire development process will make it easier for you to work. However, make sure that all developers on your team are using the same configuration to avoid undetected alarms in passed programs.

Recommendation 1: use static code analysis tools like Pyflakes

Second, avoid meaningless code style discussions

Will your team conduct a code review during development? That's the best! Note, however, that a common mistake made by inexperienced code reviewers is to spend too much time feedback on what automated tools can do for them. Yes, I'm talking about the code style. It is very easy for development teams to fall into a situation where code style is discussed during code review, and most of the time they talk about things such as "there should be an extra space here" or "class naming should be named with a hump."

This is a typical example of the "bike shed effect", which prevents developers from focusing on issues that really deserve attention, which lead to more money and time spent on maintenance.

A quick way to solve these problems is to choose a Python code style guide that can be found online, such as PEP8 or Google's Python code style guide, and then use automation tools to ensure that the project code follows the style in the guide.

It is recommended that you use PEP8-based Pycodestyle or flake8 code style checking tools. They can effectively avoid most arguments about code style and make your team more focused on issues that should be of more concern.

Tip 2: choose a specific code style and use automation tools to ensure that the code follows that style.

Third, the collapse of a thousand-mile dike due to the influence of ant nest-Catton and crash

Usability studies have shown that site loading time has a big impact on whether users give up their original purpose: if people are tired and impatient of waiting for something to happen, they are much more likely to give up what they had planned.

As a software developer, waiting for a variety of tools to complete their tasks is a common part of the daily work process. After all, we often wait for the installation of a third-party package, the run of a test, or the completion of a code submission. Of course, we don't "give up" every time we have to wait for a particular tool to run for a few seconds or even tens of seconds, and it's part of our job to pay attention to what's going on.

However, maintaining this level of concentration is exhausting, and we may use too much mental energy to affect our work in other areas: for example, feeling tired faster in the afternoon, or having a tiny bug in the code we just submitted. Even small stutters or delays can snowball after accumulation. Switching files in a slow editor or switching applications on a slow computer can be annoying. We can even pay attention to details such as editor character input delays in an almost critical manner. Because these small delays can also have a snowballing impact, they affect our productivity and make people feel irritable.

Let's imagine that in the development process, you spend one second every ten seconds waiting for a task to be completed. The cumulative cost of this time is equivalent to you waiting for half a day in a week, or two full days in a month. Or a month has passed while waiting for a year of work. Maybe this estimate is a bit exaggerated, but on the other hand, is it worth trying to improve your tools that you spent an afternoon optimizing your development tools, resulting in an extra week of work for the whole year?

Tip 3: your development tools should be highly responsive. Simplicity is always good.

Don't work in an editing environment that makes you uncomfortable

Working with tools that make you uncomfortable will greatly affect your work efficiency. Some development tools are very difficult to use and they can completely drain your energy and enthusiasm. What tools do you think are the most important in your daily development process? That must be the code editor. For some developers, the answer may be their email client or team's chat app, but we still want to spend most of the day writing code.

This means that it is absolutely worthwhile to invest your time in a pleasant code editing environment, because the direct result is higher productivity and a happier mood! As Python developers, we have many editors or IDE tools to choose from, such as Vim, Emacs, PyCharm, Wing IDE, Atom, Eclipse PyDev, Sublime Text and so on. You need to find the tools that best suit you and meet your unique needs to work. So please find more editors to try to see which one you like best, which is good for your productivity.

Tip 4: find the right editor and make it look like you need it.

Don't be stingy when buying the tools you need

If you use a paid editor, but are not willing to spend money on the official version of the editor, instead of using a trial version of the editor to work with the official version. In this version, after you save the file, a pop-up window pops up every minute or two to remind you to buy the official version. Then you will see this pop-up window hundreds of times every day. You need to buy a full license to say goodbye to these pop-up windows, so don't be so frugal in this matter. It is foolish to be stingy and find ways to save money on the development tools you often use, and your loss in dealing with these pop-up windows and the resulting series of problems definitely exceeds the price of the development tools themselves.

If you are working for yourself, the cost of these licenses can be deducted from your taxes as business expenses. If you are working for a company, after you explain why you need these tools and they can effectively improve your productivity, the company's managers will be willing to pay for your investment in the tools. Compared with art designers or architects, programmers spend much less money on licenses for software development tools, and even some of the great tools and editors are free. It makes sense to invest your money in the right tools and your work will benefit from it.

Thank you for reading! This is the end of the article on "how to optimize the development and configuration of Python". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, you can share it for more people to see!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.