BioBricks aims to distribute a variety of assets beyond just parquet files. Given this goal, managing dependencies, especially those related to data loading like 'arrow', becomes crucial. We should handle such dependencies in a soft manner to ensure that BioBricks doesn't accumulate a large number of them, optimizing both functionality and ease of installation.
Objective: Broaden the asset format support, enhancing the versatility of BioBricks.
Considerations:
How to implement soft dependencies to streamline installation and reduce potential conflicts.
Designing a mechanism to easily incorporate and manage various data asset formats.
Feedback and suggestions regarding this enhancement are highly appreciated.
BioBricks aims to distribute a variety of assets beyond just parquet files. Given this goal, managing dependencies, especially those related to data loading like 'arrow', becomes crucial. We should handle such dependencies in a soft manner to ensure that BioBricks doesn't accumulate a large number of them, optimizing both functionality and ease of installation.
Feedback and suggestions regarding this enhancement are highly appreciated.