Contributors welcome conda, Release 25.1.2.dev1 • performance tuning (#4104) • add additional fields to dist object serialization (#4102) Bug Fixes • fix a noarch install bug on windows (#4071) • input parameter: a list of PrefixSetup objects, which are just namedtuple objects with the following fields. These are populated by Solver.solve_for_transaction after running Solver.solve_for_diff: • target_prefix: concrete package tarball and its contents. They follow specific naming conventions and expose several fields. Inspect them directly in the class code. • MatchSpec objects are essentially a query language to

Contributors welcome conda, Release 24.11.3.dev2 • performance tuning (#4104) • add additional fields to dist object serialization (#4102) Bug Fixes • fix a noarch install bug on windows (#4071) • input parameter: a list of PrefixSetup objects, which are just namedtuple objects with the following fields. These are populated by Solver.solve_for_transaction after running Solver.solve_for_diff: • target_prefix: concrete package tarball and its contents. They follow specific naming conventions and expose several fields. Inspect them directly in the class code. • MatchSpec objects are essentially a query language to

Contributors welcome conda, Release 24.9.3.dev1 • performance tuning (#4104) • add additional fields to dist object serialization (#4102) Bug Fixes • fix a noarch install bug on windows (#4071) • input parameter: a list of PrefixSetup objects, which are just namedtuple objects with the followiing fields. These are populated by Solver.solve_for_transaction after running Solver.solve_for_diff: • target_prefix: concrete package tarball and its contents. They follow specific naming conventions and expose several fields. Inspect them directly in the class code. • MatchSpec objects are essentially a query language to

Contributors welcome conda, Release 24.1.2.dev2 • performance tuning (#4104) • add additional fields to dist object serialization (#4102) Bug Fixes • fix a noarch install bug on windows (#4071) • input parameter: a list of PrefixSetup objects, which are just namedtuple objects with the followiing fields. These are populated by Solver.solve_for_transaction after running Solver.solve_for_diff: • target_prefix: concrete package tarball and its contents. They follow specific naming conventions and expose several fields. Inspect them directly in the class code. • MatchSpec objects are essentially a query language to

Contributors welcome conda, Release 24.3.1.dev2 • performance tuning (#4104) • add additional fields to dist object serialization (#4102) Bug Fixes • fix a noarch install bug on windows (#4071) • input parameter: a list of PrefixSetup objects, which are just namedtuple objects with the followiing fields. These are populated by Solver.solve_for_transaction after running Solver.solve_for_diff: • target_prefix: concrete package tarball and its contents. They follow specific naming conventions and expose several fields. Inspect them directly in the class code. • MatchSpec objects are essentially a query language to

Contributors welcome conda, Release 24.3.1.dev7 • performance tuning (#4104) • add additional fields to dist object serialization (#4102) Bug Fixes • fix a noarch install bug on windows (#4071) • input parameter: a list of PrefixSetup objects, which are just namedtuple objects with the followiing fields. These are populated by Solver.solve_for_transaction after running Solver.solve_for_diff: • target_prefix: concrete package tarball and its contents. They follow specific naming conventions and expose several fields. Inspect them directly in the class code. • MatchSpec objects are essentially a query language to

Contributors welcome conda, Release 24.5.1.dev1 • performance tuning (#4104) • add additional fields to dist object serialization (#4102) Bug Fixes • fix a noarch install bug on windows (#4071) • input parameter: a list of PrefixSetup objects, which are just namedtuple objects with the followiing fields. These are populated by Solver.solve_for_transaction after running Solver.solve_for_diff: • target_prefix: concrete package tarball and its contents. They follow specific naming conventions and expose several fields. Inspect them directly in the class code. • MatchSpec objects are essentially a query language to

(#4094) 4.4. Release notes 281 conda, Release 24.7.1 • performance tuning (#4104) • add additional fields to dist object serialization (#4102) Bug Fixes • fix a noarch install bug on windows (#4071) • input parameter: a list of PrefixSetup objects, which are just namedtuple objects with the followiing fields. These are populated by Solver.solve_for_transaction after running Solver.solve_for_diff: • target_prefix: concrete package tarball and its contents. They follow specific naming conventions and expose several fields. Inspect them directly in the class code. • MatchSpec objects are essentially a query language to

4. Release notes 259 conda, Release 23.10.1.dev3 • performance tuning (#4104) • add additional fields to dist object serialization (#4102) Bug Fixes • fix a noarch install bug on windows (#4071) • input parameter: a list of PrefixSetup objects, which are just namedtuple objects with the followiing fields. These are populated by Solver.solve_for_transaction after running Solver.solve_for_diff: • target_prefix: concrete package tarball and its contents. They follow specific naming conventions and expose several fields. Inspect them directly in the class code. • MatchSpec objects are essentially a query language to

input parameter: a list of PrefixSetup objects, which are just namedtuple objects with the followiing fields. These are populated by Solver.solve_for_transaction after running Solver.solve_for_diff: • target_prefix: concrete package tarball and its contents. They follow specific naming conventions and expose several fields. Inspect them directly in the class code. • MatchSpec objects are essentially a query language to of this class. This query language has its own syntax and rules, detailed here. The most important fields of a MatchSpec object are: – name: the name of the package (e.g. pytorch); always expected. – version: