[Zope3-checkins] SVN: Zope3/trunk/src/zope/app/copypastemove/__init__.py use True and False in the tests since that is what the code uses

Fred L. Drake, Jr. fdrake at gmail.com
Fri Jun 3 16:34:15 EDT 2005


Log message for revision 30630:
  use True and False in the tests since that is what the code uses

Changed:
  U   Zope3/trunk/src/zope/app/copypastemove/__init__.py

-=-
Modified: Zope3/trunk/src/zope/app/copypastemove/__init__.py
===================================================================
--- Zope3/trunk/src/zope/app/copypastemove/__init__.py	2005-06-03 19:35:23 UTC (rev 30629)
+++ Zope3/trunk/src/zope/app/copypastemove/__init__.py	2005-06-03 20:34:15 UTC (rev 30630)
@@ -59,7 +59,7 @@
     object is movable:
 
     >>> mover.moveable()
-    1
+    True
 
     which, at least for now, they always are.  A better question to
     ask is whether we can move to a particular container. Right now,
@@ -67,7 +67,7 @@
 
     >>> container2 = ExampleContainer()
     >>> mover.moveableTo(container2)
-    1
+    True
     >>> mover.moveableTo({})
     Traceback (most recent call last):
     ...
@@ -83,7 +83,7 @@
     >>> list(container2)
     [u'foo']
     >>> ob.__parent__ is container2
-    1
+    True
 
     We can also specify a name:
 
@@ -92,7 +92,7 @@
     >>> list(container2)
     [u'bar']
     >>> ob.__parent__ is container2
-    1
+    True
     >>> ob.__name__
     u'bar'
 
@@ -141,9 +141,9 @@
     >>> from zope.app.container.constraints import checkObject
     >>> container3 = C1()
     >>> mover.moveableTo(container3, 'ZDummy')
-    0
+    False
     >>> mover.moveableTo(container3, 'newName')
-    1
+    True
 
     And a test for constraints:
 
@@ -164,10 +164,10 @@
     >>> cO = constrainedObject()
     >>> mover2 = ObjectMover(cO)
     >>> mover2.moveableTo(container)
-    0
+    False
     >>> container.x = 1
     >>> mover2.moveableTo(container)
-    1
+    True
 
     """
 
@@ -240,7 +240,7 @@
     object is movable:
 
     >>> copier.copyable()
-    1
+    True
 
     which, at least for now, they always are.  A better question to
     ask is whether we can copy to a particular container. Right now,
@@ -248,7 +248,7 @@
 
     >>> container2 = ExampleContainer()
     >>> copier.copyableTo(container2)
-    1
+    True
     >>> copier.copyableTo({})
     Traceback (most recent call last):
     ...
@@ -264,11 +264,11 @@
     >>> list(container2)
     [u'foo']
     >>> ob.__parent__ is container
-    1
+    True
     >>> container2[u'foo'] is ob
-    0
+    False
     >>> container2[u'foo'].__parent__ is container2
-    1
+    True
     >>> container2[u'foo'].__name__
     u'foo'
 
@@ -282,11 +282,11 @@
     [u'bar', u'foo']
 
     >>> ob.__parent__ is container
-    1
+    True
     >>> container2[u'bar'] is ob
-    0
+    False
     >>> container2[u'bar'].__parent__ is container2
-    1
+    True
     >>> container2[u'bar'].__name__
     u'bar'
 
@@ -333,9 +333,9 @@
     >>> from zope.app.container.constraints import checkObject
     >>> container3 = C1()
     >>> copier.copyableTo(container3, 'ZDummy')
-    0
+    False
     >>> copier.copyableTo(container3, 'newName')
-    1
+    True
 
     And a test for constraints:
 
@@ -356,10 +356,10 @@
     >>> cO = constrainedObject()
     >>> copier2 = ObjectCopier(cO)
     >>> copier2.copyableTo(container)
-    0
+    False
     >>> container.x = 1
     >>> copier2.copyableTo(container)
-    1
+    True
 
     """
 
@@ -703,4 +703,4 @@
     if subs is not None:
         for sub in subs.sublocations():
             for ignored in zapi.subscribers((sub, event), None):
-                pass # They do work in the adapter fetch
\ No newline at end of file
+                pass # They do work in the adapter fetch



More information about the Zope3-Checkins mailing list