repodata.json is always growing, which presents a problem both for the download itself and the solver engine. To reduce download times and bandwidth usage, repodata.json is also served as a BZIP2 compressed The Resolve class exposes the solving logic, but when it comes to interacting with the SAT solver engine, that’s done through the Clauses object tree. And we say “tree” because the actual engines are wrapped subscribes to the _SatSolver API is used. However, if the reason is choosing a better performing engine, consider the following: • The wrapped SAT solvers are already using compiled languages. • Generating

repodata.json is always growing, which presents a problem both for the download itself and the solver engine. To reduce download times and bandwidth usage, repodata.json is also served as a BZIP2 compressed The Resolve class exposes the solving logic, but when it comes to interacting with the SAT solver engine, that’s done through the Clauses object tree. And we say “tree” because the actual engines are wrapped subscribes to the _SatSolver API is used. However, if the reason is choosing a better performing engine, consider the following: • The wrapped SAT solvers are already using compiled languages. • Generating

repodata.json is always growing, which presents a problem both for the download itself and the solver engine. To reduce download times and bandwidth usage, repodata.json is also served as a BZIP2 compressed The Resolve class exposes the solving logic, but when it comes to interacting with the SAT solver engine, that’s done through the Clauses object tree. And we say “tree” because the actual engines are wrapped subscribes to the _SatSolver API is used. However, if the reason is choosing a better performing engine, consider the following: • The wrapped SAT solvers are already using compiled languages. • Generating

tremendous amount of flexibility via configuration. For more information, The Conda Config- uration Engine for Power Users blog post is a good resource. 114 Chapter 5. Release notes conda Documentation in bin to shell directory (#3186) 5.76 2016-07-28 4.2.0 5.76.1 New Features • New Configuration Engine: Configuration and “operating context” are the foundation of conda’s functionality. Conda now has configuration. Full documentation updates pending. (#2537, #3160, #3178) • New Exception Handling Engine: Previous releases followed a pattern of premature exiting (with hard calls to sys.exit()) when exceptional

tremendous amount of flexibility via configuration. For more information, The Conda Config- uration Engine for Power Users blog post is a good resource. 114 Chapter 5. Release notes conda Documentation in bin to shell directory (#3186) 5.76 2016-07-28 4.2.0 5.76.1 New Features • New Configuration Engine: Configuration and “operating context” are the foundation of conda’s functionality. Conda now has configuration. Full documentation updates pending. (#2537, #3160, #3178) • New Exception Handling Engine: Previous releases followed a pattern of premature exiting (with hard calls to sys.exit()) when exceptional

tremendous amount of flexibility via configuration. For more information, The Conda Config- uration Engine for Power Users blog post is a good resource. Deprecations/Breaking Changes • the conda ‘root’ shell directory (#3186) 4.4.140 4.2.0 (2016-07-28) Configuration New Features • New Configuration Engine: Configuration and “operating context” are the foundation of conda’s functionality. Conda now has configuration. Full documentation updates pending. (#2537, #3160, #3178) • New Exception Handling Engine: Previous releases followed a pattern of premature exiting (with hard calls to sys.exit() when exceptional

tremendous amount of flexibility via configuration. For more information, The Conda Config- uration Engine for Power Users blog post is a good resource. Deprecations/Breaking Changes • the conda ‘root’ shell directory (#3186) 4.4.141 4.2.0 (2016-07-28) Configuration New Features • New Configuration Engine: Configuration and “operating context” are the foundation of conda’s functionality. Conda now has configuration. Full documentation updates pending. (#2537, #3160, #3178) • New Exception Handling Engine: Previous releases followed a pattern of premature exiting (with hard calls to sys.exit() when exceptional

tremendous amount of flexibility via configuration. For more information, The Conda Config- uration Engine for Power Users blog post is a good resource. Deprecations/Breaking Changes • the conda ‘root’ shell directory (#3186) 4.4.144 4.2.0 (2016-07-28) Configuration New Features • New Configuration Engine: Configuration and “operating context” are the foundation of conda’s functionality. Conda now has configuration. Full documentation updates pending. (#2537, #3160, #3178) • New Exception Handling Engine: Previous releases followed a pattern of premature exiting (with hard calls to sys.exit() when exceptional

tremendous amount of flexibility via configuration. For more information, The Conda Config- uration Engine for Power Users blog post is a good resource. Deprecations/Breaking Changes • the conda ‘root’ shell directory (#3186) 4.4.145 4.2.0 (2016-07-28) Configuration New Features • New Configuration Engine: Configuration and “operating context” are the foundation of conda’s functionality. Conda now has configuration. Full documentation updates pending. (#2537, #3160, #3178) • New Exception Handling Engine: Previous releases followed a pattern of premature exiting (with hard calls to sys.exit() when exceptional

tremendous amount of flexibility via configuration. For more information, The Conda Config- uration Engine for Power Users blog post is a good resource. Deprecations/Breaking Changes • the conda ‘root’ shell directory (#3186) 4.4.146 4.2.0 (2016-07-28) Configuration New Features • New Configuration Engine: Configuration and “operating context” are the foundation of conda’s functionality. Conda now has configuration. Full documentation updates pending. (#2537, #3160, #3178) • New Exception Handling Engine: Previous releases followed a pattern of premature exiting (with hard calls to sys.exit() when exceptional