| | |
| | | Pyramid Provides Too Few "Rails" |
| | | -------------------------------- |
| | | |
| | | By design, :mod:`pyramid` is not a particularly "opinionated" web |
| | | framework. It has a relatively parsimonious feature set. It contains |
| | | no built in ORM nor any particular database bindings. It contains no |
| | | form generation framework. It does not contain a sessioning library. |
| | | It has no administrative web user interface. It has no built in text |
| | | indexing. It does not dictate how you arrange your code. |
| | | By design, :mod:`pyramid` is not a particularly "opinionated" web framework. |
| | | It has a relatively parsimonious feature set. It contains no built in ORM |
| | | nor any particular database bindings. It contains no form generation |
| | | framework. It has no administrative web user interface. It has no built in |
| | | text indexing. It does not dictate how you arrange your code. |
| | | |
| | | Such opinionated functionality exists in applications and frameworks |
| | | built *on top* of :mod:`pyramid`. It's intended that higher-level |
| | | systems emerge built using :mod:`pyramid` as a base. See also |
| | | :ref:`apps_are_extensible`. |
| | | Such opinionated functionality exists in applications and frameworks built |
| | | *on top* of :mod:`pyramid`. It's intended that higher-level systems emerge |
| | | built using :mod:`pyramid` as a base. See also :ref:`apps_are_extensible`. |
| | | |
| | | Pyramid Provides Too Many "Rails" |
| | | --------------------------------- |