The strela package works seamlessly with tessa and its
Symbol class and financial information access functionality.
At the same time, care was taken to make strela open and flexible enough to be used with
other packages and/or your own code.
Still, many or most people will end up using strela together with tessa so it's worth
discussing whether strela should be incorporated into tessa.
I decided to keep strela separate from tessa because strela has a distinctly different
character: a) it is not purely a library but needs some script to be built on top and
then called as a CLI tool / cronjob, b) it tends to rely on external files such as a
list of symbols to be loaded, c) it needs a place to store the alert state (and will
fail if that place doesn't exist, which seems to be unacceptable behavior for a pure
library such as tessa).
But I would like to have your thoughts on this. Should strela and tessa be separate
packages or better both in one? Add your thoughts to the respective issue.
The strela package works seamlessly with tessa and its
Symbol class and financial information access functionality.
At the same time, care was taken to make strela open and flexible enough to be used with
other packages and/or your own code.
Still, many or most people will end up using strela together with tessa so it's worth
discussing whether strela should be incorporated into tessa.
I decided to keep strela separate from tessa because strela has a distinctly different
character: a) it is not purely a library but needs some script to be built on top and
then called as a CLI tool / cronjob, b) it tends to rely on external files such as a
list of symbols to be loaded, c) it needs a place to store the alert state (and will
fail if that place doesn't exist, which seems to be unacceptable behavior for a pure
library such as tessa).
But I would like to have your thoughts on this. Should strela and tessa be separate
packages or better both in one? Add your thoughts to the respective issue.