Citrine

In this release of Citrine Python, we are shipping internal improvements to both enable further development and allow for smoother debugging in the future. As always, we are constantly improving Citrine Python to be more reliable and flexible to meet your needs.

Improvements
* Additional fields added to predictor reports to support future feature delivery. 778

Fixes
* Introduce `BATCH_SIZE` as a package constant that to control how many objects are registered to the platform at one time. This constant can be extended to debug issues in data service timeouts. 779

**Full Changelog**: https://github.com/CitrineInformatics/citrine-python/compare/v1.36.6...v1.37.1

In this release of Citrine Python, we are providing minor fixes and improvements to keep our users running smoothly and building confidently. We've improved our documentation for contributions and included fixes to some of our deprecation warnings brought about by the Teams migration.

Improvements
* Improved documentation for contributions. 775

Fixes
* Correct deprecation warning on `find_or_create_project` and `projects.register` to trigger only when used incorrectly in the Teams context. 774, 777
* Internal fix to default design space creation. 776

**Full Changelog**: https://github.com/CitrineInformatics/citrine-python/compare/v1.36.2...v1.36.6

In this release of Citrine Python, we are adding more functionality for the upcoming migration to Teams, including the ability to quickly access user permissions and resources available to a project at the Team level. We've also improved our search functionality around files and performed some additional under-the-hood work to fix bugs and improve performance.

What's New
* New endpoints to allow quick access of a user's permissions on a given Team. Using `team.me()` will allow you to check your permissions within a team with one call! 770
* Added functionality to list the IDs of accessible resources at a Team level. This allows you to see what assets are available to use in their project that have been published from other projects in your team. 769

Improvements
* Improved the way we search for files on our platform by using filters. 772

Fixes
* Minor improvements and bug fixes. 771, 773

**Full Changelog**: https://github.com/CitrineInformatics/citrine-python/compare/v1.34.0...v1.36.2

In this release of Citrine Python, we are happy to announce additional configurability of Design Spaces that are created via the `create_default` method. The method, which creates a new Design Space based on a given Predictor configuration, now takes three optional flags: one each to constrain the design space ingredient amounts, label amounts, or ingredient-counts-per-label based on the shape of the training data.

This lets you build your default design space in a number of ways: you can start similar to your training data and expand, or start with a big design space and constrain smaller. All these flags are optional; omitting them will default to "False" resulting in an unconstrained design space. As always, we are also shipping minor bug fixes to keep you running smoothly.

What's New
* Add configurability flags to the `create_default` Design Space method. 767

Fixes
* Minor bug fixes and improvements. https://github.com/CitrineInformatics/citrine-python/pull/766

**Full Changelog**: https://github.com/CitrineInformatics/citrine-python/compare/v1.33.2...v1.34.0

This release is a quick fix to some formatting issues with our deprecation warnings around project and user management methods affected by the migration to Teams for access control. The fixes should increase the readability of the warnings and make it easier to know where and how to prepare your code for migration. There is no change to what methods will be deprecated or replaced in the migration.

Fixes
* Formatting fix to deprecation warnings around project and user management. https://github.com/CitrineInformatics/citrine-python/pull/765

**Full Changelog**: https://github.com/CitrineInformatics/citrine-python/compare/v1.33.1...v1.33.2

In this release of Citrine Python, we've made one small, but important addition, to our warning system. Any methods around project and user management that will be deprecated with the migration to Teams for access control are now accompanied by a readable deprecation warning pointing you to the post-migration equivalent. This will allow you to test your code before migration and point you to the new methods to support your workflow once migration has been completed.

What's New
* Added deprecation warnings for methods to be deprecated in the migration to Teams for access control. https://github.com/CitrineInformatics/citrine-python/pull/763

**Full Changelog**: https://github.com/CitrineInformatics/citrine-python/compare/v1.33.0...v1.33.1