derp...this has nothing to do with parser. I just realized locally for me neither case works (I had put my puts between the two). Now for the twist! 126.96.36.199 the first case works???? In both cases these are strings so this is strange. Too strange to ignore for 188.8.131.52
Ok it took me longer to write my two comments then to actually figure this out. We were using a type check method which expects an exact match on warn argument being a String versus a kind-of String. Verifying something about protocol conversion before committing a fix.
Circling back on why the first case stopped working since 184.108.40.206...@kares had recently added some kwargs support to warn and what changed happened to change both into hitting the same incorrect typeconverter type check (I believe it from no newline strings performing a strDup which made first call work but it is enough for me to know I fixed both with my commit).