Skip to content

packaging needs some work #2

Description

@7yl4r

the planned package/module organization is not as intuitive as envisioned during planning. A new organization strategy in which I can actually remember lines of code is needed.

  • Option#1: more strictly standardized module names so that we know what to expect for each sub-package. I.e., the sub-structure of 'PA', 'Interaction', and other sub-modules match as closely as possible.
  • Option#2: less rigid structure to reduce sub-packaging. Visualization modules get more descriptive names, and less effort to break out sub-packages is made. Thus we get something more like PAbarChart.plot() in place of PA.timeSeries.barChart.plot()

Eh, I'm not sure what to do.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions