[13:52:07] The reason why the tests didn't pass was a weird tabs vs spaces error in Python code that didn't have any tabs. A warning saying "you have tabs in your code!" should be enough to fix such issues [13:52:07] Ideally, the Wikifunctions editor shouldn't insert tabs in Python code. I think it should treat the tab character as a command to insert a specific number of spaces, not as a hard tab, just like Ctrl-V doesn't insert a [[Synchronous idle]] character (re @Al: The implementation is fine, so I’ve reconnected it. Please bear T406784 in mind before [13:52:07] disconnecting implementations that have r...) [13:52:51] /delete [14:55:20] Yes, I didn’t see the Python implementation but that error persisted with your JavaScript alternative, and JavaScript doesn’t care. So we can be pretty certain the error was generated by the replaced Python code, which is ultimately a caching issue. [14:55:21] As for tabs in Python code, this is the effective default, because the auto-generated function header contains a tab at the start of the second line. If you replace that tab with spaces, the code editor will begin subsequent lines with spaces, but pressing return after a colon will indent with a tab after the spaces, which is a different kind of error ('Tabs not allowed [14:55:21] as part o [14:55:22] f indentation after spaces' as opposed to 'inconsistent use of tabs and spaces in indentation'). [14:55:24] So, yes… it can be more than a little frustrating at times, but consistent use of tabs turns out to be less inconvenient than the alternatives, in my experience. [22:52:55] I added the mulitlingual table of helpers to the NLG page : https://tools-static.wmflabs.org/bridgebot/e32ee8ba/file_76148.jpg [23:39:45] Why we got stuck? : https://tools-static.wmflabs.org/bridgebot/9faf5e19/file_76149.jpg