mirror of
https://github.com/kennethreitz/python-guide.git
synced 2026-06-05 23:00:18 +00:00
+1
-1
@@ -74,7 +74,7 @@ It has:
|
||||
- Virtual env support;
|
||||
- Search by python documentation and run python code;
|
||||
- More other things like auto pep8 error fixes;
|
||||
- Very customizable an documented as well;
|
||||
- Very customizable and documented as well;
|
||||
- Have all required libraries in self;
|
||||
|
||||
And more stuff.
|
||||
|
||||
@@ -164,7 +164,7 @@ support for Python 2.7 applications.
|
||||
Heroku allows you to run as many Python web applications as you like, 24/7 and
|
||||
free of charge. Heroku is best described as a horizontal scaling platform. They
|
||||
start to charge you once you "scale" you application to run on more than one
|
||||
Dyno (abstacted servers) at a time.
|
||||
Dyno (abstracted servers) at a time.
|
||||
|
||||
Heroku publishes `step-by-step instructions
|
||||
<http://devcenter.heroku.com/articles/python>`_ on how to set up your first
|
||||
@@ -212,7 +212,7 @@ Templating
|
||||
Most WSGI applications are responding to HTTP requests to serve
|
||||
content in HTML or other markup languages. Instead of generating directly
|
||||
textual content from Python, the concept of separation of concerns
|
||||
advise us to use templates. A template engine manage a suite of
|
||||
advises us to use templates. A template engine manage a suite of
|
||||
template files, with a system of hierarchy and inclusion to
|
||||
avoid unnecessary repetition, and is in charge of rendering
|
||||
(generating) the actual content, filling the static content
|
||||
@@ -220,10 +220,10 @@ of the templates with the dynamic content generated by the
|
||||
application.
|
||||
|
||||
As template files are
|
||||
sometime written by designers or front-end developpers,
|
||||
sometimes written by designers or front-end developers,
|
||||
it can be difficult to handle increasing complexity.
|
||||
|
||||
Some general good pratices apply to the part of the
|
||||
Some general good practices apply to the part of the
|
||||
application passing dynamic content to the template engine,
|
||||
and to the templates themselves.
|
||||
|
||||
@@ -233,7 +233,7 @@ and to the templates themselves.
|
||||
it is easier to add some missing variable when needed than to remove
|
||||
a likely unused variable later.
|
||||
|
||||
- Many template engine allow for complex statements
|
||||
- Many template engines allow for complex statements
|
||||
or assignments in the template itself, and many
|
||||
allow some Python code to be evaluated in the
|
||||
templates. This convenience can lead to uncontrolled
|
||||
|
||||
Reference in New Issue
Block a user