From discussions with people using this project (and my own workflow), I realize run is the core functionality most people care about (and that's a bad name - it really should be called optimize).
This would be exposed in a pip module if I ever ship one. Ideally, this library could be easily added to whatever scripts people have for their DFS workflow and it could be extended to any game that has positions, players and salaries. So if a new website or DFS game pops up, it would be easy to do something like:
The reason this isn't possible now is that run takes a Namespace object from argparser. This interface doesn't make sense and needs to be changed. While I still want to maintain the CLI - I often find it useful for experimenting with different strategies - there can be a layer between the CLI and the pip module so they can speak to each other. Said another way, the CLI should be independent from the library exposed by pip.
This also should remove run / optimize's dependency on passing CSV file paths to it.
From discussions with people using this project (and my own workflow), I realize
run
is the core functionality most people care about (and that's a bad name - it really should be calledoptimize
).This would be exposed in a pip module if I ever ship one. Ideally, this library could be easily added to whatever scripts people have for their DFS workflow and it could be extended to any game that has positions, players and salaries. So if a new website or DFS game pops up, it would be easy to do something like:
The reason this isn't possible now is that
run
takes aNamespace
object fromargparser
. This interface doesn't make sense and needs to be changed. While I still want to maintain the CLI - I often find it useful for experimenting with different strategies - there can be a layer between the CLI and the pip module so they can speak to each other. Said another way, the CLI should be independent from the library exposed by pip.This also should remove
run
/optimize
's dependency on passing CSV file paths to it.