Skip to content

Classify dependencies and introduce optional extras/constraints #77

Description

@Tim55667757

Parent Feature: #40
Parent roadmap: #28

Scope

Separate core runtime, rendering, indicators, docs, test and release dependencies.

Acceptance criteria

  • unused runtime dependencies are removed or justified;
  • obsolete bkcharts is removed from modern runtime path;
  • Bokeh/Jinja/pandas-ta are optional where architecture permits;
  • dependency declarations are consistent across packaging/dev workflows;
  • reproducible constraints/lock strategy is documented.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions