[Checkins] SVN: grok/branches/gotcha-configuration-actions/src/grok/tests/ Get more tests to pass

Philipp von Weitershausen philikon at philikon.de
Tue Oct 9 07:54:02 EDT 2007


Log message for revision 80738:
  Get more tests to pass
  

Changed:
  U   grok/branches/gotcha-configuration-actions/src/grok/tests/annotation/annotation.py
  U   grok/branches/gotcha-configuration-actions/src/grok/tests/annotation/implementsmany.py
  U   grok/branches/gotcha-configuration-actions/src/grok/tests/annotation/implementsnone.py
  U   grok/branches/gotcha-configuration-actions/src/grok/tests/annotation/name.py
  U   grok/branches/gotcha-configuration-actions/src/grok/tests/annotation/provides.py
  U   grok/branches/gotcha-configuration-actions/src/grok/tests/application/application.py
  U   grok/branches/gotcha-configuration-actions/src/grok/tests/baseclass/base.py
  U   grok/branches/gotcha-configuration-actions/src/grok/tests/baseclass/basecontext.py
  U   grok/branches/gotcha-configuration-actions/src/grok/tests/baseclass/basedirective.py
  U   grok/branches/gotcha-configuration-actions/src/grok/tests/catalog/indexes_no_app.py
  U   grok/branches/gotcha-configuration-actions/src/grok/tests/container/container.py
  U   grok/branches/gotcha-configuration-actions/src/grok/tests/container/container_model.py
  U   grok/branches/gotcha-configuration-actions/src/grok/tests/form/customautoform.py
  U   grok/branches/gotcha-configuration-actions/src/grok/tests/form/customform.py
  U   grok/branches/gotcha-configuration-actions/src/grok/tests/form/fields.py
  U   grok/branches/gotcha-configuration-actions/src/grok/tests/form/form.py
  U   grok/branches/gotcha-configuration-actions/src/grok/tests/form/norender.py
  U   grok/branches/gotcha-configuration-actions/src/grok/tests/form/norender2.py
  U   grok/branches/gotcha-configuration-actions/src/grok/tests/form/schemaform.py
  U   grok/branches/gotcha-configuration-actions/src/grok/tests/form/schemainherit.py
  U   grok/branches/gotcha-configuration-actions/src/grok/tests/grokker/continue_scanning.py
  U   grok/branches/gotcha-configuration-actions/src/grok/tests/grokker/grokcomponent.py
  U   grok/branches/gotcha-configuration-actions/src/grok/tests/grokker/onlyonce.py
  U   grok/branches/gotcha-configuration-actions/src/grok/tests/grokker/priority.py
  U   grok/branches/gotcha-configuration-actions/src/grok/tests/json/nocontext.py
  U   grok/branches/gotcha-configuration-actions/src/grok/tests/json/view_lookup.py
  U   grok/branches/gotcha-configuration-actions/src/grok/tests/site/site.py
  U   grok/branches/gotcha-configuration-actions/src/grok/tests/static/statichaspy.py
  U   grok/branches/gotcha-configuration-actions/src/grok/tests/static/staticispackage.py
  U   grok/branches/gotcha-configuration-actions/src/grok/tests/xmlrpc/nocontext.py

-=-
Modified: grok/branches/gotcha-configuration-actions/src/grok/tests/annotation/annotation.py
===================================================================
--- grok/branches/gotcha-configuration-actions/src/grok/tests/annotation/annotation.py	2007-10-09 11:48:59 UTC (rev 80737)
+++ grok/branches/gotcha-configuration-actions/src/grok/tests/annotation/annotation.py	2007-10-09 11:54:01 UTC (rev 80738)
@@ -1,5 +1,5 @@
 """
-  >>> grok.grok(__name__)
+  >>> grok.tests.grok(__name__)
   >>> from zope import component
   >>> from zope.annotation.attribute import AttributeAnnotations
   >>> component.provideAdapter(AttributeAnnotations)

Modified: grok/branches/gotcha-configuration-actions/src/grok/tests/annotation/implementsmany.py
===================================================================
--- grok/branches/gotcha-configuration-actions/src/grok/tests/annotation/implementsmany.py	2007-10-09 11:48:59 UTC (rev 80737)
+++ grok/branches/gotcha-configuration-actions/src/grok/tests/annotation/implementsmany.py	2007-10-09 11:54:01 UTC (rev 80738)
@@ -3,7 +3,7 @@
 it should cspecify which of the many implemented interfaces it should
 be registered for.  Ambiguities lead to errors:
 
-  >>> grok.grok(__name__)
+  >>> grok.tests.grok(__name__)
   Traceback (most recent call last):
   GrokError: <class
   'grok.tests.annotation.implementsmany.MammothAnnotations'> is

Modified: grok/branches/gotcha-configuration-actions/src/grok/tests/annotation/implementsnone.py
===================================================================
--- grok/branches/gotcha-configuration-actions/src/grok/tests/annotation/implementsnone.py	2007-10-09 11:48:59 UTC (rev 80737)
+++ grok/branches/gotcha-configuration-actions/src/grok/tests/annotation/implementsnone.py	2007-10-09 11:54:01 UTC (rev 80738)
@@ -3,7 +3,7 @@
 interface to indicate which annotation interface they provide and can
 be looked up with:
 
-  >>> grok.grok(__name__)
+  >>> grok.tests.grok(__name__)
   Traceback (most recent call last):
   GrokError: <class 'grok.tests.annotation.implementsnone.Branding'>
   must implement at least one interface (use grok.implements to

Modified: grok/branches/gotcha-configuration-actions/src/grok/tests/annotation/name.py
===================================================================
--- grok/branches/gotcha-configuration-actions/src/grok/tests/annotation/name.py	2007-10-09 11:48:59 UTC (rev 80737)
+++ grok/branches/gotcha-configuration-actions/src/grok/tests/annotation/name.py	2007-10-09 11:54:01 UTC (rev 80738)
@@ -1,5 +1,5 @@
 """
-  >>> grok.grok(__name__)
+  >>> grok.tests.grok(__name__)
   >>> from zope import component
   >>> from zope.annotation.attribute import AttributeAnnotations
   >>> component.provideAdapter(AttributeAnnotations)

Modified: grok/branches/gotcha-configuration-actions/src/grok/tests/annotation/provides.py
===================================================================
--- grok/branches/gotcha-configuration-actions/src/grok/tests/annotation/provides.py	2007-10-09 11:48:59 UTC (rev 80737)
+++ grok/branches/gotcha-configuration-actions/src/grok/tests/annotation/provides.py	2007-10-09 11:54:01 UTC (rev 80738)
@@ -1,5 +1,5 @@
 """
-  >>> grok.grok(__name__)
+  >>> grok.tests.grok(__name__)
   >>> from zope import component
   >>> from zope.annotation.attribute import AttributeAnnotations
   >>> component.provideAdapter(AttributeAnnotations)

Modified: grok/branches/gotcha-configuration-actions/src/grok/tests/application/application.py
===================================================================
--- grok/branches/gotcha-configuration-actions/src/grok/tests/application/application.py	2007-10-09 11:48:59 UTC (rev 80737)
+++ grok/branches/gotcha-configuration-actions/src/grok/tests/application/application.py	2007-10-09 11:54:01 UTC (rev 80738)
@@ -3,7 +3,7 @@
 After grokking a module that defines an application, the application factory is
 available as a utility::
 
-    >>> grok.grok(__name__)
+    >>> grok.tests.grok(__name__)
     >>> import zope.component
     >>> import grok.interfaces
     >>> calendar_app = zope.component.getUtility(grok.interfaces.IApplication,

Modified: grok/branches/gotcha-configuration-actions/src/grok/tests/baseclass/base.py
===================================================================
--- grok/branches/gotcha-configuration-actions/src/grok/tests/baseclass/base.py	2007-10-09 11:48:59 UTC (rev 80737)
+++ grok/branches/gotcha-configuration-actions/src/grok/tests/baseclass/base.py	2007-10-09 11:54:01 UTC (rev 80738)
@@ -5,7 +5,7 @@
 classname with 'Base'. Another way is to use the 'grok.baseclass' directive
 on the class itself.
 
-  >>> grok.grok(__name__)
+  >>> grok.tests.grok(__name__)
 
   >>> from zope.publisher.browser import TestRequest
   >>> request = TestRequest()

Modified: grok/branches/gotcha-configuration-actions/src/grok/tests/baseclass/basecontext.py
===================================================================
--- grok/branches/gotcha-configuration-actions/src/grok/tests/baseclass/basecontext.py	2007-10-09 11:48:59 UTC (rev 80737)
+++ grok/branches/gotcha-configuration-actions/src/grok/tests/baseclass/basecontext.py	2007-10-09 11:54:01 UTC (rev 80738)
@@ -3,7 +3,7 @@
 function as a module-level context, and thus can have views associated
 with it.
 
-  >>> grok.grok(__name__)
+  >>> grok.tests.grok(__name__)
 
   >>> from zope.publisher.browser import TestRequest
   >>> request = TestRequest()

Modified: grok/branches/gotcha-configuration-actions/src/grok/tests/baseclass/basedirective.py
===================================================================
--- grok/branches/gotcha-configuration-actions/src/grok/tests/baseclass/basedirective.py	2007-10-09 11:48:59 UTC (rev 80737)
+++ grok/branches/gotcha-configuration-actions/src/grok/tests/baseclass/basedirective.py	2007-10-09 11:54:01 UTC (rev 80738)
@@ -3,7 +3,7 @@
 subclasses shouldn't inherit this otherwise there is no way to turn them
 into non-base classes.
 
-  >>> grok.grok(__name__)
+  >>> grok.tests.grok(__name__)
 
   >>> from zope.publisher.browser import TestRequest
   >>> request = TestRequest()

Modified: grok/branches/gotcha-configuration-actions/src/grok/tests/catalog/indexes_no_app.py
===================================================================
--- grok/branches/gotcha-configuration-actions/src/grok/tests/catalog/indexes_no_app.py	2007-10-09 11:48:59 UTC (rev 80737)
+++ grok/branches/gotcha-configuration-actions/src/grok/tests/catalog/indexes_no_app.py	2007-10-09 11:54:01 UTC (rev 80738)
@@ -3,7 +3,7 @@
 special indexes declaration.  We do need to specify a site (such as
 the application) for the Indexes however, otherwise we get a GrokError:
 
-  >>> grok.grok(__name__)
+  >>> grok.tests.grok(__name__)
   Traceback (most recent call last):
     ...
   GrokError: No site specified for grok.Indexes subclass in module

Modified: grok/branches/gotcha-configuration-actions/src/grok/tests/container/container.py
===================================================================
--- grok/branches/gotcha-configuration-actions/src/grok/tests/container/container.py	2007-10-09 11:48:59 UTC (rev 80737)
+++ grok/branches/gotcha-configuration-actions/src/grok/tests/container/container.py	2007-10-09 11:54:01 UTC (rev 80738)
@@ -4,7 +4,7 @@
 dictionary API. It in fact stores its information in a BTree so
 you can store a lot of items in a scalable way.
 
-    >>> grok.grok(__name__)
+    >>> grok.tests.grok(__name__)
 
     >>> from zope.app.container.interfaces import IContainer
     >>> bag = BoneBag()

Modified: grok/branches/gotcha-configuration-actions/src/grok/tests/container/container_model.py
===================================================================
--- grok/branches/gotcha-configuration-actions/src/grok/tests/container/container_model.py	2007-10-09 11:48:59 UTC (rev 80737)
+++ grok/branches/gotcha-configuration-actions/src/grok/tests/container/container_model.py	2007-10-09 11:54:01 UTC (rev 80738)
@@ -3,7 +3,7 @@
 registered as the default context object:
 
 
-    >>> grok.grok(__name__)
+    >>> grok.tests.grok(__name__)
     >>> bag = BoneBag()
     >>> from zope import component
     >>> from zope.publisher.browser import TestRequest

Modified: grok/branches/gotcha-configuration-actions/src/grok/tests/form/customautoform.py
===================================================================
--- grok/branches/gotcha-configuration-actions/src/grok/tests/form/customautoform.py	2007-10-09 11:48:59 UTC (rev 80737)
+++ grok/branches/gotcha-configuration-actions/src/grok/tests/form/customautoform.py	2007-10-09 11:54:01 UTC (rev 80738)
@@ -2,7 +2,7 @@
 A form view can have a custom form_fields but reusing those fields that
 were deduced automatically, using grok.AutoFields:
 
-  >>> grok.grok(__name__)
+  >>> grok.tests.grok(__name__)
 
 We only expect a single field to be present in the form, as we omitted 'size':
 

Modified: grok/branches/gotcha-configuration-actions/src/grok/tests/form/customform.py
===================================================================
--- grok/branches/gotcha-configuration-actions/src/grok/tests/form/customform.py	2007-10-09 11:48:59 UTC (rev 80737)
+++ grok/branches/gotcha-configuration-actions/src/grok/tests/form/customform.py	2007-10-09 11:54:01 UTC (rev 80738)
@@ -2,7 +2,7 @@
 A form view can completely override which fields are displayed by setting
 form_fields manually:
 
-  >>> grok.grok(__name__)
+  >>> grok.tests.grok(__name__)
 
 We only expect a single field to be present in the form, as we omitted 'size':
 

Modified: grok/branches/gotcha-configuration-actions/src/grok/tests/form/fields.py
===================================================================
--- grok/branches/gotcha-configuration-actions/src/grok/tests/form/fields.py	2007-10-09 11:48:59 UTC (rev 80737)
+++ grok/branches/gotcha-configuration-actions/src/grok/tests/form/fields.py	2007-10-09 11:54:01 UTC (rev 80738)
@@ -2,7 +2,7 @@
 A grok.Fields can receive keyword parameters with schema fields. These
 should be avaible in the definition order.
 
-  >>> grok.grok(__name__)
+  >>> grok.tests.grok(__name__)
 
   >>> from zope import component
   >>> from zope.publisher.browser import TestRequest

Modified: grok/branches/gotcha-configuration-actions/src/grok/tests/form/form.py
===================================================================
--- grok/branches/gotcha-configuration-actions/src/grok/tests/form/form.py	2007-10-09 11:48:59 UTC (rev 80737)
+++ grok/branches/gotcha-configuration-actions/src/grok/tests/form/form.py	2007-10-09 11:54:01 UTC (rev 80738)
@@ -3,7 +3,7 @@
 
   >>> from zope import component
   >>> from zope.publisher.browser import TestRequest
-  >>> grok.grok(__name__)
+  >>> grok.tests.grok(__name__)
   >>> manfred = Mammoth()
 
   >>> request = TestRequest()

Modified: grok/branches/gotcha-configuration-actions/src/grok/tests/form/norender.py
===================================================================
--- grok/branches/gotcha-configuration-actions/src/grok/tests/form/norender.py	2007-10-09 11:48:59 UTC (rev 80737)
+++ grok/branches/gotcha-configuration-actions/src/grok/tests/form/norender.py	2007-10-09 11:54:01 UTC (rev 80738)
@@ -2,7 +2,7 @@
 Forms cannot define a render method. Here we show the case where the
 EditForm has an explicit template associate with it.
 
-  >>> grok.grok(__name__)
+  >>> grok.tests.grok(__name__)
   Traceback (most recent call last):
   ...
   GrokError: It is not allowed to specify a custom 'render' method for

Modified: grok/branches/gotcha-configuration-actions/src/grok/tests/form/norender2.py
===================================================================
--- grok/branches/gotcha-configuration-actions/src/grok/tests/form/norender2.py	2007-10-09 11:48:59 UTC (rev 80737)
+++ grok/branches/gotcha-configuration-actions/src/grok/tests/form/norender2.py	2007-10-09 11:54:01 UTC (rev 80738)
@@ -2,7 +2,7 @@
 Forms cannot define a render method. Here we show the case where the
 EditForm has no explicit template associated with it:
 
-  >>> grok.grok(__name__)
+  >>> grok.tests.grok(__name__)
   Traceback (most recent call last):
   ...
   GrokError: It is not allowed to specify a custom 'render' method for

Modified: grok/branches/gotcha-configuration-actions/src/grok/tests/form/schemaform.py
===================================================================
--- grok/branches/gotcha-configuration-actions/src/grok/tests/form/schemaform.py	2007-10-09 11:48:59 UTC (rev 80737)
+++ grok/branches/gotcha-configuration-actions/src/grok/tests/form/schemaform.py	2007-10-09 11:54:01 UTC (rev 80738)
@@ -1,7 +1,7 @@
 """
 A grok.Model may implement one or more interfaces that are schemas:
 
-  >>> grok.grok(__name__)
+  >>> grok.tests.grok(__name__)
   >>> manfred = Mammoth()
   >>> print manfred.name
   None

Modified: grok/branches/gotcha-configuration-actions/src/grok/tests/form/schemainherit.py
===================================================================
--- grok/branches/gotcha-configuration-actions/src/grok/tests/form/schemainherit.py	2007-10-09 11:48:59 UTC (rev 80737)
+++ grok/branches/gotcha-configuration-actions/src/grok/tests/form/schemainherit.py	2007-10-09 11:54:01 UTC (rev 80738)
@@ -1,7 +1,7 @@
 """
 A grok.Model may implement a schema that inherits from another one:
 
-  >>> grok.grok(__name__)
+  >>> grok.tests.grok(__name__)
   >>> manfred = Mammoth()
 
   >>> from zope import component

Modified: grok/branches/gotcha-configuration-actions/src/grok/tests/grokker/continue_scanning.py
===================================================================
--- grok/branches/gotcha-configuration-actions/src/grok/tests/grokker/continue_scanning.py	2007-10-09 11:48:59 UTC (rev 80737)
+++ grok/branches/gotcha-configuration-actions/src/grok/tests/grokker/continue_scanning.py	2007-10-09 11:54:01 UTC (rev 80738)
@@ -5,12 +5,12 @@
 Here we define AlphaGrokker which has higher priority than BetaGrokker but does
 not block BetaGrokker from picking up the same component::
 
-    >>> grok.grok(__name__)
+    >>> grok.tests.grok(__name__)
 
 In the fixture there is AlphaBetaSub that inherits from both Alpha and Beta.
 Thus, both Grokkers are executed, with AlphaGrokker coming before BetaGrokker::
 
-    >>> grok.grok('grok.tests.grokker.continue_scanning_fixture')
+    >>> grok.tests.grok('grok.tests.grokker.continue_scanning_fixture')
     alpha
     beta
 

Modified: grok/branches/gotcha-configuration-actions/src/grok/tests/grokker/grokcomponent.py
===================================================================
--- grok/branches/gotcha-configuration-actions/src/grok/tests/grokker/grokcomponent.py	2007-10-09 11:48:59 UTC (rev 80737)
+++ grok/branches/gotcha-configuration-actions/src/grok/tests/grokker/grokcomponent.py	2007-10-09 11:54:01 UTC (rev 80738)
@@ -3,7 +3,7 @@
 Let's first grok the meta module to define some basic grokkers::
 
   >>> import grok
-  >>> grok.grok('grok.meta')
+  >>> grok.tests.grok('grok.meta')
   
 It is possible to grok an individual component. Let's define an adapter::
 
@@ -18,7 +18,7 @@
 
 To grok this adapter, you can simply write this::
 
-  >>> grok.grok_component('MyAdapter', MyAdapter)
+  >>> grok.tests.grok_component('MyAdapter', MyAdapter)
   True
 
 We can now use the adapter::
@@ -40,14 +40,14 @@
 This adapter does not supply its own context. Trying to do what we did
 before will therefore fail::
 
-  >>> grok.grok_component('SecondAdapter', SecondAdapter)
+  >>> grok.tests.grok_component('SecondAdapter', SecondAdapter)
   Traceback (most recent call last):
     ...
   GrokError: No module-level context for <class 'grok.tests.grokker.grokcomponent.SecondAdapter'>, please use grok.context.
 
 So we need to supply the context ourselves::
 
-  >>> grok.grok_component('SecondAdapter', SecondAdapter, context=SomeClass)
+  >>> grok.tests.grok_component('SecondAdapter', SecondAdapter, context=SomeClass)
   True
 
 Now we can use the SecondAdapter as well::

Modified: grok/branches/gotcha-configuration-actions/src/grok/tests/grokker/onlyonce.py
===================================================================
--- grok/branches/gotcha-configuration-actions/src/grok/tests/grokker/onlyonce.py	2007-10-09 11:48:59 UTC (rev 80737)
+++ grok/branches/gotcha-configuration-actions/src/grok/tests/grokker/onlyonce.py	2007-10-09 11:54:01 UTC (rev 80738)
@@ -9,7 +9,7 @@
 We do it manually now::
 
   >>> import grok
-  >>> grok.grok('grok.tests.grokker.onlyonce_fixture._meta')
+  >>> grok.tests.grok('grok.tests.grokker.onlyonce_fixture._meta')
 
 This _meta.py module then will be grokked again during 'normal' grok time. Grok
 will not re-register the grokkers as this could have unwanted side-effects. It
@@ -21,7 +21,7 @@
 
 To simulate this, we grok the whole package::
 
-  >>> grok.grok('grok.tests.grokker.onlyonce_fixture')
+  >>> grok.tests.grok('grok.tests.grokker.onlyonce_fixture')
   alpha
 
 """

Modified: grok/branches/gotcha-configuration-actions/src/grok/tests/grokker/priority.py
===================================================================
--- grok/branches/gotcha-configuration-actions/src/grok/tests/grokker/priority.py	2007-10-09 11:48:59 UTC (rev 80737)
+++ grok/branches/gotcha-configuration-actions/src/grok/tests/grokker/priority.py	2007-10-09 11:54:01 UTC (rev 80738)
@@ -6,12 +6,12 @@
 - BetaGrokker with priority 1
 - GammaGrokker with priority -1
 
-    >>> grok.grok(__name__)
+    >>> grok.tests.grok(__name__)
 
 We grok a module that implements subclasses for Alpha, Beta, and Gamma and our
 grokkers get executed in the order of priority (highest first)::
 
-    >>> grok.grok('grok.tests.grokker.priority_fixture')
+    >>> grok.tests.grok('grok.tests.grokker.priority_fixture')
     beta
     alpha
     gamma

Modified: grok/branches/gotcha-configuration-actions/src/grok/tests/json/nocontext.py
===================================================================
--- grok/branches/gotcha-configuration-actions/src/grok/tests/json/nocontext.py	2007-10-09 11:48:59 UTC (rev 80737)
+++ grok/branches/gotcha-configuration-actions/src/grok/tests/json/nocontext.py	2007-10-09 11:54:01 UTC (rev 80738)
@@ -3,7 +3,7 @@
 Context-determination follows the same rules as for adapters. We just check
 whether it's hooked up at all:
 
-  >>> grok.grok(__name__)
+  >>> grok.tests.grok(__name__)
   Traceback (most recent call last):
     ...
   GrokError: No module-level context for

Modified: grok/branches/gotcha-configuration-actions/src/grok/tests/json/view_lookup.py
===================================================================
--- grok/branches/gotcha-configuration-actions/src/grok/tests/json/view_lookup.py	2007-10-09 11:48:59 UTC (rev 80737)
+++ grok/branches/gotcha-configuration-actions/src/grok/tests/json/view_lookup.py	2007-10-09 11:54:01 UTC (rev 80738)
@@ -3,7 +3,7 @@
 The JSON grokker registers a view for each method of the JSON class.
 So we should be able to search for view by method name.
 
-  >>> grok.grok(__name__)
+  >>> grok.tests.grok(__name__)
   >>> mammoth = Mammoth()
   >>> from zope.publisher.browser import TestRequest
   >>> request = TestRequest()

Modified: grok/branches/gotcha-configuration-actions/src/grok/tests/site/site.py
===================================================================
--- grok/branches/gotcha-configuration-actions/src/grok/tests/site/site.py	2007-10-09 11:48:59 UTC (rev 80737)
+++ grok/branches/gotcha-configuration-actions/src/grok/tests/site/site.py	2007-10-09 11:54:01 UTC (rev 80738)
@@ -2,7 +2,7 @@
 A site can be created by mixing in grok.Site into a grok.Model or
 grok.Container.
 
-  >>> grok.grok(__name__)
+  >>> grok.tests.grok(__name__)
 
   >>> from zope import interface
   >>> from zope.app.component.interfaces import IPossibleSite, ISite

Modified: grok/branches/gotcha-configuration-actions/src/grok/tests/static/statichaspy.py
===================================================================
--- grok/branches/gotcha-configuration-actions/src/grok/tests/static/statichaspy.py	2007-10-09 11:48:59 UTC (rev 80737)
+++ grok/branches/gotcha-configuration-actions/src/grok/tests/static/statichaspy.py	2007-10-09 11:54:01 UTC (rev 80738)
@@ -3,7 +3,7 @@
 a module called 'static.py':
 
   >>> import grok
-  >>> grok.grok('grok.tests.static.statichaspy_fixture')
+  >>> grok.tests.grok('grok.tests.static.statichaspy_fixture')
   Traceback (most recent call last):
     ...
   GrokError: A package can not contain both a 'static' resource directory

Modified: grok/branches/gotcha-configuration-actions/src/grok/tests/static/staticispackage.py
===================================================================
--- grok/branches/gotcha-configuration-actions/src/grok/tests/static/staticispackage.py	2007-10-09 11:48:59 UTC (rev 80737)
+++ grok/branches/gotcha-configuration-actions/src/grok/tests/static/staticispackage.py	2007-10-09 11:54:01 UTC (rev 80738)
@@ -2,7 +2,7 @@
 It is an error for the 'static' directory to be a python package:
 
   >>> import grok
-  >>> grok.grok('grok.tests.static.staticispackage_fixture')
+  >>> grok.tests.grok('grok.tests.static.staticispackage_fixture')
   Traceback (most recent call last):
     ...
   GrokError: The 'static' resource directory must not be a python package.

Modified: grok/branches/gotcha-configuration-actions/src/grok/tests/xmlrpc/nocontext.py
===================================================================
--- grok/branches/gotcha-configuration-actions/src/grok/tests/xmlrpc/nocontext.py	2007-10-09 11:48:59 UTC (rev 80737)
+++ grok/branches/gotcha-configuration-actions/src/grok/tests/xmlrpc/nocontext.py	2007-10-09 11:54:01 UTC (rev 80738)
@@ -3,7 +3,7 @@
 Context-determination follows the same rules as for adapters. We just check
 whether it's hooked up at all:
 
-  >>> grok.grok(__name__)
+  >>> grok.tests.grok(__name__)
   Traceback (most recent call last):
     ...
   GrokError: No module-level context for



More information about the Checkins mailing list