From 522c236157016f416c122060f52efda275a38a5d Mon Sep 17 00:00:00 2001 From: michr Date: Mon, 24 Jan 2011 21:06:44 -0800 Subject: =?UTF-8?q?fixed=20typo:=20"reqest"=20->=20request=20in=20"Pyramid?= =?UTF-8?q?=20Views=20Do=20Not=20Accept=20Arbitrary=20Keyword=20Arguments"?= =?UTF-8?q?=20section=20of=20"Defending=20Pyramid=E2=80=99s=20Design"?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/designdefense.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs') diff --git a/docs/designdefense.rst b/docs/designdefense.rst index 740313486..c37ae61ce 100644 --- a/docs/designdefense.rst +++ b/docs/designdefense.rst @@ -599,7 +599,7 @@ the method is called (if possible) with its argument list filled with values mentioned therein. TurboGears and Pylons 1.X operate similarly. Out of the box, :app:`Pyramid` is configured to have none of these features. -By default, :mod:`pyramid` view callables always accept only ``reqest`` and +By default, :mod:`pyramid` view callables always accept only ``request`` and no other arguments. The rationale: this argument specification matching done aggressively can be costly, and :app:`Pyramid` has performance as one of its main goals, so we've decided to make people, by default, obtain information -- cgit v1.2.3