| Home | Trees | Indices | Help |
|
|---|
|
|
Groups allow for performing a next() call on a specific
set of Generators allowing for more complex Fuzzing setups. This default
group object will iterate an infinit amount of times.
Group objects implement the iterator protocol.
|
|||
|
|||
| string |
|
||
|
|||
|
|||
|
|||
|
|||
| Array |
|
||
|
|||
|
|||
|
|||
|
|||
_name = None
|
|||
_generators = []
|
|||
_identity = ""
|
|||
|
|||
Create a new Group object.
|
Get current name of Group. Not currently used.
|
Set name of Group. Not currently used.
|
Add Generator to Group. This should almost never be called directly. Generators will call this when you set there Group. However, you can do some crazy stuff by adding a Generator into multiple Groups so they iterate themselves in strange ways.
|
Add Generators to Group. This should almost never be called directly. Generators will call this when you set there Group. However, you can do some crazy stuff by adding a Generator into multiple Groups so they iterate themselves in strange ways.
|
Remove Generator from Group.
|
Returns list of all generators in Group. This is a reference to our internal list so any changes will also affect the Group.
|
Iterate all Generators to next value. From Python docs on next(): The intention of the protocol is that once an iterator's next() method raises StopIteration, it will continue to do so on subsequent calls. Implementations that do not obey this property are deemed broken. (This constraint was added in Python 2.3; in Python 2.2, various iterators are broken according to this rule.) For Groups, please use the GroupCompleted exception instead of StopIteration (its a subclass). |
| Home | Trees | Indices | Help |
|
|---|
| Generated by Epydoc 3.0.1 on Sat Aug 16 12:17:14 2008 | http://epydoc.sourceforge.net |