channels as package sources”. The details are complicated, but in essence, the Solver will: 1. Express the requested packages, command line options and prefix state as MatchSpec objects 2. Query the only covered these three steps: The details are complicated, but in essence, the solver will: 1. Express the requested packages, command line options and prefix state as MatchSpec objects 2. Query the NamesFilter(set(['alice', 'bob'])).filter(['alice', 'bob', 'carol']) ['alice', 'bob'] What if we want to just express "let all the names through"? We could try to enumerate all of the expected names: ��NamesFilter({'alice'

channels as package sources”. The details are complicated, but in essence, the Solver will: 1. Express the requested packages, command line options and prefix state as MatchSpec objects 2. Query the only covered these three steps: The details are complicated, but in essence, the solver will: 1. Express the requested packages, command line options and prefix state as MatchSpec objects 2. Query the NamesFilter(set(['alice', 'bob'])).filter(['alice', 'bob', 'carol']) ['alice', 'bob'] What if we want to just express "let all the names through"? We could try to enumerate all of the expected names: ��NamesFilter({'alice'

channels as package sources”. The details are complicated, but in essence, the Solver will: 1. Express the requested packages, command line options and prefix state as MatchSpec objects 2. Query the only covered these three steps: The details are complicated, but in essence, the solver will: 1. Express the requested packages, command line options and prefix state as MatchSpec objects 2. Query the NamesFilter(set(['alice', 'bob'])).filter(['alice', 'bob', 'carol']) ['alice', 'bob'] What if we want to just express "let all the names through"? We could try to enumerate all of the expected names: ��NamesFilter({'alice'

channels as package sources”. The details are complicated, but in essence, the Solver will: 1. Express the requested packages, command line options and prefix state as MatchSpec objects 2. Query the only covered these three steps: The details are complicated, but in essence, the solver will: 1. Express the requested packages, command line options and prefix state as MatchSpec objects 2. Query the NamesFilter(set(['alice', 'bob'])).filter(['alice', 'bob', 'carol']) ['alice', 'bob'] What if we want to just express "let all the names through"? We could try to enumerate all of the expected names: ��NamesFilter({'alice'

channels as package sources”. The details are complicated, but in essence, the Solver will: 1. Express the requested packages, command line options and prefix state as MatchSpec objects 2. Query the only covered these three steps: The details are complicated, but in essence, the solver will: 1. Express the requested packages, command line options and prefix state as MatchSpec objects 2. Query the NamesFilter(set(['alice', 'bob'])).filter(['alice', 'bob', 'carol']) ['alice', 'bob'] What if we want to just express "let all the names through"? We could try to enumerate all of the expected names: ��NamesFilter({'alice'

channels as package sources”. The details are complicated, but in essence, the Solver will: 1. Express the requested packages, command line options and prefix state as MatchSpec objects 2. Query the only covered these three steps: The details are complicated, but in essence, the solver will: 1. Express the requested packages, command line options and prefix state as MatchSpec objects 2. Query the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under

channels as package sources”. The details are complicated, but in essence, the Solver will: 1. Express the requested packages, command line options and prefix state as MatchSpec objects 2. Query the only covered these three steps: The details are complicated, but in essence, the solver will: 1. Express the requested packages, command line options and prefix state as MatchSpec objects 2. Query the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under

channels as package sources”. The details are complicated, but in essence, the Solver will: 1. Express the requested packages, command line options and prefix state as MatchSpec objects 2. Query the only covered these three steps: The details are complicated, but in essence, the solver will: 1. Express the requested packages, command line options and prefix state as MatchSpec objects 2. Query the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under

channels as package sources”. The details are complicated, but in essence, the Solver will: 1. Express the requested packages, command line options and prefix state as MatchSpec objects 2. Query the only covered these three steps: The details are complicated, but in essence, the solver will: 1. Express the requested packages, command line options and prefix state as MatchSpec objects 2. Query the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under

channels as package sources”. The details are complicated, but in essence, the Solver will: 1. Express the requested packages, command line options and prefix state as MatchSpec objects 2. Query the only covered these three steps: The details are complicated, but in essence, the solver will: 1. Express the requested packages, command line options and prefix state as MatchSpec objects 2. Query the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under