On Sat, Aug 12, 2017 at 6:31 AM, Alberto Berti <albe...@metapensiero.it> wrote:
> It's not really so confusing, most code I wrote with it it's perfectly
> understandable Python code. For me, one thing is the language, one other
> thing are the libraries or the builtin classes it's usually shipped
> with.
> The tool reads valid Python and writes valid ES6 JavaScript. As the
> documentation states, it allows you to retain most of Python language
> semantics (like for example you can have a working
> try...except...finally statement, instead of what vanilla JS gives you)
> and some of the library semantics. nothing more, nothing less.

Hold on. Make up your mind:

> As of now, I do nothing. As I said, the goal of the tool is not to
> shield you from JS, for this reason it's not meant for beginners (in
> both JS or Python). You always manipulate JS objects, but allows you to
> to be naive on all that plethora of JS idiosyncrasies (from a Python pow
> at least) that you have to think about when you frequently switch from
> python to js.

Do you "retain most of Python language semantics", or do you "always
manipulate JS objects"? As shown in a previous post, there are some
subtle and very dangerous semantic differences between the languages.
You can't have it both ways.

Python-ideas mailing list
Code of Conduct: http://python.org/psf/codeofconduct/

Reply via email to