Home | Trees | Indices | Help |
|
---|
|
object --+ | Solver
Chooses a set of implementations to satisfy the requirements of a program and its user. Typical use:
Instance Methods | |||
|
|||
|
|||
|
|||
architecture.Architecture |
|
||
Inherited from |
Instance Variables | |
{str: [(Implementation, comment)]} |
details extra information, if record_details mode was used |
set(str) |
feeds_used the feeds which contributed to the choice in selections |
{Interface: [(Implementation, str)]} |
record_details whether to record information about unselected implementations |
{model.Interface: [model.Dependency]} |
requires the selected dependencies for each chosen version |
selections.Selections |
selections the chosen implementation of each interface |
Properties | |
Inherited from |
Method Details |
x.__init__(...) initializes x; see help(type(x)) for signature
|
Solve for given requirements.
Postcondition: self.ready, self.selections and self.feeds_used are updated Since: 1.8 |
Get the best implementation of root_interface and all of its dependencies.
Postcondition: self.ready, self.selections and self.feeds_used are updated |
Return the Architecture we would use when solving for this interface. Normally, this architecture is constructed from the OS and CPU type in the requirements, using the host platform's settings if these are not given. If interface is the root, then we wrap this in a SourceArchitecture if looking for source code and (for backwards compatibility) we enable use="testing" dependencies if the command is "test".
Since: 1.9 |
Home | Trees | Indices | Help |
|
---|
Generated by Epydoc 3.0.1 on Tue Mar 26 18:14:07 2013 | http://epydoc.sourceforge.net |