1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
|
Source: quixote1
Section: web
Priority: optional
Maintainer: Debian Python Modules Team <python-modules-team@lists.alioth.debian.org>
Uploaders: Santiago Ruano Rincón <santiago@debian.org>
Build-Depends: debhelper (>= 7), python (>= 2.5.4-1~), python-all-dev (>= 2.5.4-1~), dh-python
Standards-Version: 3.9.2
Vcs-Svn: svn://anonscm.debian.org/python-modules/packages/quixote1/trunk/
Vcs-Browser: http://anonscm.debian.org/viewvc/python-modules/packages/quixote1/trunk/
Homepage: http://www.mems-exchange.org/software/quixote/
Package: python-quixote1
Section: python
Architecture: any
Depends: ${python:Depends}, ${shlibs:Depends}, ${misc:Depends}
Conflicts: quixote1, quixote, python-quixote
Replaces: quixote1, quixote, python-quixote
Provides: ${python:Provides}
Description: highly Pythonic Web application framework
Quixote is yet another framework for developing Web applications in
Python. The design goals were:
.
1) To allow easy development of Web applications where the
emphasis is more on complicated programming logic than
complicated templating.
.
2) To make the templating language as similar to Python as possible,
in both syntax and semantics. The aim is to make as many of the
skills and structural techniques used in writing regular Python
code applicable to Web applications built using Quixote.
.
3) No magic. When it's not obvious what to do in
a certain case, Quixote refuses to guess.
.
If you view a web site as a program, and web pages as subroutines,
Quixote just might be the tool for you. If you view a web site as a
graphic design showcase, and each web page as an individual work of
art, Quixote is probably not what you're looking for.
Package: quixote1-doc
Section: doc
Architecture: all
Depends: python-quixote1, ${misc:Depends}
Description: Quixote web application framework documentation
Contains the documentation and examples for Quixote-1.2.
|
