11 | | == applications - wtf? == |
12 | | No explanation what they're for |
| 14 | == Multiple versions == |
| 15 | |
| 16 | Some of us had previous installations in the standard location, site-packages/, and wanted to not touch them. |
| 17 | Can install (typically, check out latest from SVN) to a home directory (or C:\Temp, ugh!), and then symlink it in site-packages/, or hack PYTHON_PATH before invoking the "non-standard" installations. |
| 18 | (Examples?) |
| 19 | |
| 20 | == The official tutorial == |
| 21 | |
| 22 | * "Applications": WTF? No explanation what they're for. |
| 23 | |
| 24 | But see more [wiki:CurrentTutorialIdeas about the tutorial]. |
| 25 | |
| 26 | == Template handles "un/safe" text == |
| 27 | |
| 28 | HTML escaped automatically. Or not. ''But'', note that HTML uses ''several'' syntaxes/domains: content (ie, plain text) marked up with HTML must not contain <, >, or & -- these must be escaped. Then, element ''attributes'' must not contain " (double quotes). ''And'' <xmp> nodes must not contain the string "</xmp>", and have no concept of escapes. Ugh. |
| 29 | |
| 30 | So, does Django's templating support all this mess? |