an other idea could be to allow to pass config file as parameter like this
python goxtool.py --configpath/to/goxtool.ini
so it will be possible to have a screen with BTCUSD and an other one with BTCEUR
**but** if your strategies are writing files it could be a problem because 2 differents goxtools
are writing on same file...
Let's say that you are implementing a trailing stop strategy...
you will store stop loss price in a file (because you want not to lose value if goxtool is
stopped and started)
let's call sl.txt this file (ini, json or yaml file)
maybe you should add a "name" parameter in goxtool.ini
[gox]
name = MyGox1
currency = USD
use_ssl = True
use_plain_old_websocket = False
use_http_api = False
load_fulldepth = True
load_history = True
history_timeframe = 15
secret_key =
secret_secret =
[goxtool]
set_xterm_title = True
and strategy that writes files (to store data such as last stop price) will store data as
MyGox1_sl.txt
so differents goxtool could work together
(english is not my mother tongue... so please excuse me if it's not very clear)
Adding config parameter is quite easy to do
in goxtool.py file
argp.add_argument('--config', action="store", default="goxtool.ini",
help="name of config file, default=goxtool.ini")
args = argp.parse_args()
config = goxapi.GoxConfig(args.config)
So you can now have a goxtoolBTCEUR.ini with
[gox]
currency = EUR
use_ssl = True
use_plain_old_websocket = False
use_http_api = False
load_fulldepth = True
load_history = True
history_timeframe = 15
secret_key =
secret_secret =
[goxtool]
set_xterm_title = True
and call goxtool with this config file as parameter using
python goxtool.py --config goxtoolBTCUSD.ini
or with my Raspberry Pi running my Bitcoin/Litecoin softwares in GNU Screen
screen -t goxtoolBTCUSD 50 pythonhome/pi/src/goxtool/goxtool.py --confighome/pi/src/goxtool/goxtoolBTCUSD.ini
screen -t goxtoolBTCEUR 51 pythonhome/pi/src/goxtool/goxtool.py --confighome/pi/src/goxtool/goxtoolBTCEUR.ini