Hey fun fact I just learned: the correct way to exec a file and make the functions it defines part of your module's exports is: exec(code_goes_here, globals()) I presume this works in py2 as well, but the jank-ass way I was doing it doesn't work in py3.
1
I want to see the jank ass py2 version please!
1
github.com/tabatkins/bikeshe…

bikeshed/bikeshed/extensions.py at main · speced/bikeshed

:bike: A preprocessor for anyone writing specifications that converts source files into actual specs. - bikeshed/bikeshed/extensions.py at main · speced/bikeshed

github.com
1
NICE
1
Look I was just slamming plausible-looking code down until it worked then I STEPPED AWAY
1
1
browsers: held together by chewing gum and baling wire, but that's okay because there are SPECS specs: lol also held together by chewing gum and baling wire spec authoring tools: also held together by chewing gum and baling wire, apparently turtles all the way down
2
1
9
Replying to @ManishEarth @tabatkins @blelbach
If you're using Respec, it's just an infinite loop, but if you're using bikeshed, you at least fall through to python (which I'm sure has its own chewing gum and bailing wire).

Mar 14, 2020 · 5:27 AM UTC
3