Anyone who can't see past Python's indentation-based syntax is a person who doesn't understand Python.<p>(Both literally and figuratively!)<p>When "significant whitespace" is at the top of someone's complaints about Python, I'm immediately done hearing about their superficial criticism of the language.
> I built this to learn more about python/interpreter language syntax in general, but not interested in pursuing this further.<p>Good job trying something new out! There is always room for experimentation, if any reason to try to learn something new.
Sorry, I have to ask...<p>Does it support also braces? :)<p>IIUC the source is writen as a long heresting and then executed.<p>Does it have the same speed than normal Python?<p>Does it suppont numpy, numba and other similar packages that use jit?<p>Can a function inside the modified code call a function outside? (It may be helpful for porting conde one function at a time.)<p>Is it possible to do something similar with a decorator instead of a herestring?
I used to code in Python for everything in the late aughts and loved meaningful whitespace. Whenever I used a language with braces like JavaScript, for instance, I felt like I was still indenting code meaningfully but now I had the extra hurdle of also caring about the braces. It felt unnecessary and stone-agey.<p>But back then I was just using vim with a nicely configured .vimrc. Linters weren't really a thing, or at least not neatly integrated into my editing experience.<p>Nowadays I write Rust in vscode and I love braces. Rustfmt just formats my code every time anyway, so I don't have to care about indentation and braces are placed where they should be. I spend zero time caring about code formatting, outside of configuring rustfmt.toml once per project or the occasional #[rustfmt::skip] for codeblocks which I really want to format in a specific way outside of the linter's configured rules. I also have the benefit of the compiler screaming at me if I forget a brace, pointing to the exact error including telling me when indentation is suggesting a brace is missing! :O<p>Moreover, I'm much more proficient in vim, and the single hotkey % is reason enough to want to favor braces. Coupled with how often I paste code into Claude, V$%,y has become muscle memory (visually select this whole line, go to the end of the line, then expand the selection to the line matching the closing delimiter under the cursor, then yank everything into the system clipboard with <leader>y)...<p>On occasion, I go back to Python for some side project and the whole experience feels... weird. If braces before LSPs and linters was the stone age, then Python feels like the iron age and I'm living in the future with a compiler that is incredibly talkative and helpful. I'm never going back.
Please make the corner/base cases more prominent. For instance, the question obviously arises: can we have this:<p><pre><code> def function(x) do
end
</code></pre>
without writing "pass"?