mirror of
https://github.com/python/cpython.git
synced 2025-08-04 00:48:58 +00:00
Merged revisions 69846 via svnmerge from
svn+ssh://pythondev@svn.python.org/python/trunk ........ r69846 | mark.dickinson | 2009-02-21 20:27:01 +0000 (Sat, 21 Feb 2009) | 2 lines Issue #5341: Fix a variety of spelling errors. ........
This commit is contained in:
parent
91cf882b36
commit
934896dc09
48 changed files with 83 additions and 83 deletions
|
@ -426,7 +426,7 @@ MVC stands for three components:
|
|||
user. Typically this component is represented by the templates.
|
||||
* The *controller*. This is the layer between the user and the model. The
|
||||
controller reacts on user actions (like opening some specific URL) and tells
|
||||
the model to modify the data if neccessary.
|
||||
the model to modify the data if necessary.
|
||||
|
||||
While one might think that MVC is a complex design pattern, in fact it is not.
|
||||
It is used in Python because it has turned out to be useful for creating clean,
|
||||
|
@ -435,9 +435,9 @@ maintainable web sites.
|
|||
.. note::
|
||||
|
||||
While not all Python frameworks explicitly support MVC, it is often trivial
|
||||
to create a web site which uses the MVC pattern by seperating the data logic
|
||||
to create a web site which uses the MVC pattern by separating the data logic
|
||||
(the model) from the user interaction logic (the controller) and the
|
||||
templates (the view). That's why it is important not to write unneccessary
|
||||
templates (the view). That's why it is important not to write unnecessary
|
||||
Python code in the templates -- it is against MVC and creates more chaos.
|
||||
|
||||
.. seealso::
|
||||
|
@ -607,7 +607,7 @@ Some notable frameworks
|
|||
-----------------------
|
||||
|
||||
There is an incredible number of frameworks, so there is no way to describe them
|
||||
all. It is not even neccessary, as most of these frameworks are nothing special
|
||||
all. It is not even necessary, as most of these frameworks are nothing special
|
||||
and everything that can be done with these can also be done with one of the
|
||||
popular ones.
|
||||
|
||||
|
@ -679,7 +679,7 @@ project called `Grok <http://grok.zope.org/>`_ which makes it possible for
|
|||
Another framework that's already been mentioned is `Pylons`_. Pylons is much
|
||||
like TurboGears with ab even stronger emphasis on flexibility, which is bought
|
||||
at the cost of being more difficult to use. Nearly every component can be
|
||||
exchanged, which makes it neccessary to use the documentation of every single
|
||||
exchanged, which makes it necessary to use the documentation of every single
|
||||
component, because there are so many Pylons combinations possible that can
|
||||
satisfy every requirement. Pylons builds upon `Paste
|
||||
<http://pythonpaste.org/>`_, an extensive set of tools which are handy for WSGI.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue