| === falcojr9 is now known as falcojr1 | |
| === Guest93 is now known as skull-skrimp | |
| === falcojr is now known as falcojr[m] | |
| === falcojr1 is now known as falcojr | |
| [17:05] <meena> falcojr: you think this https://gist.github.com/5824e72b26ecbde9f50f9459edb489f3 is better than before? | |
| === Guest93 is now known as skull-skrimp | |
| [18:34] <falcojr> meena: is there a reason for the change? I usually prefer dealing with exit/error codes as text output will often change and be subject to internationalization...though...that doesn't really seem relevant here, so I think it's fine...but not sure why'd we prefer this over the previous version | |
| [20:16] <meena> falcojr: i dunno, hence the question. is it better to compare an error string, or rip thru the stack with an exception, catch it and then continue like nothing happened | |
| [20:17] <meena> it feels strange… not very performant, but maybe I just don't understand python well enough | |
| [20:17] <meena> maybe throwing and immediately catching an exception is more akin to returning from a function for the optimiser | |