[06:45:21] <niko>	 no bugs, but make it sentient could help :)
[14:11:15] <Texas>	 heh
[14:11:20] <Texas>	 yes it would :P
[14:11:31] <RhinosF1>	 Hi Texas
[14:11:38] <Texas>	 hey RhinosF1
[14:12:24] <Texas>	 RhinosF1: Have we had any trolls come today?
[14:12:47] <RhinosF1>	 Texas: no, I'm hopefully going to fix the 3.7 issues tonight on zppixbot so we can roll to 3.7 Sunday
[14:12:56] <Texas>	 ah nice
[14:13:10] * Texas will probably keep working on the Sygnal engine
[14:13:26] <Texas>	 RhinosF1: Also, why can't we reload ZppixBot?
[14:13:33] <Texas>	 it seems to work fine on my sopel
[14:13:40] <RhinosF1>	 Texas: because the function is way too risky
[14:13:51] <Texas>	 why is it risky though?
[14:13:58] <RhinosF1>	 It's prone if you do it too often to behaving weirdly
[14:14:12] <Texas>	 ah
[14:14:13] <RhinosF1>	 As it doesn't always unload/load properly
[14:14:19] <Texas>	 interesting
[14:15:54] <RhinosF1>	 Texas: python doesn't like doing it and isnt built to. So if you have enough modules and do it enough, the chance of it failing is highet
[14:16:47] <RhinosF1>	 Also, if the deploy breaks anything, it can simply crash the bot or refuse to load module and wont pick up a fix
[14:17:20] <Texas>	 RhinosF1: Yeah I have experienced the last part before
[14:17:28] <RhinosF1>	 So it's simpler to just reboot it, which as long as you git pull before is guarnteed to update everything
[14:18:05] <RhinosF1>	 You should be logged in anyway when deploying