Skip to content
This repository was archived by the owner on Mar 12, 2023. It is now read-only.
This repository was archived by the owner on Mar 12, 2023. It is now read-only.

Code and directory structure #31

@gausie

Description

@gausie

Questions to answer:

  • We can't keep putting classes in libkol/... can we? Where do they go that would be familiar to a normal python developer
  • How do we want to support content-based functionality? My current thoughts are a content directory, and you could do something like from libkol.content import KremlinsGreatestBriefcase or something to start using that
  • Is passing the session around like this good? At the moment we aren't really getting the benefit of either approach because we use a singleton for the Models but pass it around everywhere else. Passing it around is great for the possibility of running multiple concurrent bots from a single script, which wouldn't really be possible. Singleton is good for ease of use.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions