In many of the examples, there is a section for "Dependencies" which is hard-coded, stating each Bonsai package dependency necessary to run the example. This is not ideal for several reasons. The information is redundant with the Bonsai bootstrapper, which for the latest Bonsai 2.9 now automatically searches for and bootstraps the Bonsai environment. Additionally, updating these packages by hand is quite laborious, error-prone, and can lead to some confusing mismatches between the versions stated as dependencies and the versions used by the workflow/environment.
For these reasons, I think it is best to remove these sections from the documentation and rely solely on the Bonsai config files for knowing which package dependencies are required.
In many of the examples, there is a section for "Dependencies" which is hard-coded, stating each Bonsai package dependency necessary to run the example. This is not ideal for several reasons. The information is redundant with the Bonsai bootstrapper, which for the latest Bonsai 2.9 now automatically searches for and bootstraps the Bonsai environment. Additionally, updating these packages by hand is quite laborious, error-prone, and can lead to some confusing mismatches between the versions stated as dependencies and the versions used by the workflow/environment.
For these reasons, I think it is best to remove these sections from the documentation and rely solely on the Bonsai config files for knowing which package dependencies are required.