What are the good Web frameworks in Python?

When it comes to Web frameworks, Ruby's world Rails dominates the rivers and lakes, while Python is a world full of flowers, with countless micro-frameworks and frameworks.

PHP, another major scripting language, has many frameworks, but it is far less exaggerated than Python. It is precisely because there are too many Python Web Development Frameworks (hereinafter referred to as Python Frameworks) that there has always been a topic about which Python frameworks are better or worse in the Python community, and the time span of discussion is even as long as 3-5 years. ?

There are so many Python frameworks that few people can play them all. Frankly speaking, I have only used three of these development projects, and several of them have been touched slightly, so I can only talk about them here.

Django, Python framework is full of flowers, but there is one that is the biggest, and that is Django. To say that Django is the best in the Python framework, some people agree with it, and some people resolutely oppose it, but it is estimated that everyone has no opinion. Django has the most comprehensive documents, the highest market share and the most recruitment positions. Django was praised mainly for: Perfect documentation, Django's success, I think a large part is due to Django's almost perfect official documentation (including Django book). ?

A complete set of solutions, like Rails, Django provides a complete set of solutions (full stack framework+battery), basically everything (such as cache, session, feed, orm, geo, auth), and all of them are made by Django. Django, the tools for developing websites are basically ready for you. The development efficiency is self-evident, and it is easy to find problems. It is not in your code, but in Django's source code. ?

Powerful URL routing configuration, Django allows you to design very elegant URLs, and you can basically say goodbye to ugly GET parameters in Django. ? Self-help background management, admin interface is a striking contrib in Django, which allows you to have a complete background management interface without writing a line of code. ?

Django's shortcomings mainly come from Django's insistence on making all the wheels by himself, and the whole system is relatively closed. The most criticized thing about Django is that the system is closely coupled. If you think that one of Django's built-in functions is not very good, it is very difficult to replace it with your favorite third-party libraries, such as ORM and Template, which will be mentioned below.

It's almost impossible to use SQLAlchemy or Mako in Django, and even using some patches will make you feel very, very uncomfortable. ? Django's ORM is far less powerful than SQLAlchemy. Except in Django, SQLAlchemy is the de facto ORM standard in Python world, and all other frameworks support SQLAlchemy, but Django still sticks to its own set. Django developers also discussed and tried to support SQLAlchemy, but finally gave up, which is estimated to be too expensive and difficult to integrate with other modules of Django. ? Template function is weak, and Python code cannot be inserted. To write more complex logic, you need to implement Tag or Filter in Python. Although URL configuration is powerful, it must be handwritten, which is completely opposite to the conventional concept of Rails configuration. Experts and people who first met Django will have very different matching websites. ?

The tangled auth module, Django's auth is closely integrated with other modules, and its function is quite strong, but it is a bit too much. The user's database schema has been set for you, so the problem is coming. For example, many websites require a unique email address, but the value of this field in the schema is not unique, and entanglement is necessary. ?

Python files are used as configuration files instead of the more common forms such as ini, xml or yaml. This is not a problem in itself, but in theory, the value of the setting can be changed dynamically (although people will not do this), but this is not the embodiment of best practice. ? Generally speaking, Django does everything, and it is very good to develop some Web applications quickly with it. If you follow Django's design philosophy, you will find Django very easy to use, and the more you use it, the easier it is. On the contrary, if you can't integrate or accept Django's design concept, it will be very painful for you to use Django, so it's better to give up early.

So, in some people's eyes, Jiang Ge is no different from the elixir, but for some people, it is poison and highly toxic. ? Tower and. Turbine gear and parts company. Besides Django, another big head of reboze.bfg is Pylons, because TurboGears2.x is based on Pylons, and reboze.bfg has also been incorporated into the Pylons project, so we will not discuss TurboGears and reboze.bfg separately in the future. ?

The design concept of tower and Django is completely different. Pylons itself has only about 2000 lines of Python code, but it also comes with some third-party modules that are almost used by Pylons Royal. Hanger only provides one shelf and options. You can freely choose templates, ORM, forms, auth and other components according to your own preferences, and the system is highly customizable. We often say Python is a glue language, so we can say that Pylons is a glue framework designed in glue language. ? Choosing a tower is mainly about choosing its freedom. Choosing freedom also means that you have chosen nightmares. Learning nightmare, Hanger relies on many third-party libraries, not Hanger. You must learn how to use these libraries while learning the tower. The point is that sometimes you don't know what you want to learn.

The learning curve of Ta is much higher than that of Django, and the official documents of Ta have always been criticized. Fortunately, the book "The Authoritative Guide to the Tower" was published later, and this situation has changed. For this reason, Pylons was once considered as a Python framework only suitable for experts. ? Debugging nightmare, because there are many modules involved, it is difficult to locate the problem once something goes wrong.

Maybe the program you wrote is wrong, maybe Pylons is wrong, or SQLAlchemy is wrong, or there is a bug in formencode, which is a mess anyway. This problem can only be solved if it is used well. ? Upgrading nightmare, installing hanger * * * requires installing nearly 20 Python modules, each with its own version number. To upgrade the version of Pylons, any module may have incompatibility problems, and upgrading is basically very difficult. So far, reddit's hanger is still in the 0.9.6 version of Antique, and SQLAlchemy is still in the 0.5.3 version, which should be related to this article. ?

Finally, what is the misunderstanding about the framework selection? In the choice of framework, many people easily fall into the following two misunderstandings without knowing it:

1. Which framework is the best-there is no best framework in the world, only the one that suits you and your team best. So is the choice of programming language. Your team is familiar with Python, so use it. If you are familiar with Ruby, use Ruby. Programming languages and frameworks are just tools, so it's good to save as quickly as possible. 2. Pay too much attention to performance-in fact, most people don't need to pay too much attention to the performance of the framework, because the websites you develop are simply small stations, and there are not many websites that can visit 10000 IP, and even fewer websites visit 10000 IP. It doesn't make much sense to talk about performance before there is a certain traffic, because your CPU and memory are always idle. Moreover, language and framework are generally not performance bottlenecks, and performance problems most often appear in database access and file reading and writing. The Zend framework of PHP is notoriously slow, but the Zend framework also has big stations, such as: digg.com; Ruby and Rails, which are often said to have performance problems, can't develop twitter yet? In addition, the current hardware and bandwidth costs are actually very low. Especially with the cloud computing platform, the labor cost is the most expensive. There are not tens of thousands of IP, and you don't have to worry too much about performance issues. The traffic has gone up, so spend some money to buy some server space and solve the performance problem simply and quickly. ? Note: Some netizens questioned that it was not objective for me to say that Quora was developed with hangers. I want to make it clear that a website mentioned here is developed with B, which only means that A is mainly or partially developed with B, so let's not dwell on A or C any more.

Regarding python web, I suggest you learn more about the case of Great God. Extract the essence from it and absorb it. See the Python study guide code below.

Study? =? Enter ('Do? What about you? Want it? Where to? Study? Python？ Now (yes? Or? No):')

Answer? =? study

What if? Answer? ==? "yes":

Print ('QQ 1 129834903')

Otherwise:

Print ('Thank you! ! ')