PyPy.js: A fast, compliant Python implementation for the web • Hacker News Board

Re: PyPy.js: A fast, compliant Python implementation for the web

#141

Post by techdragon » Fri, May 08, 2015, 3:07 AM UTC

dlitz wrote: post #42

Is there a Python 3 version of this?

I was talking with some contributors at PyCon last month and there was a consensus that Python 3 is actually preferable. There's issues to be resolved that are more important than switching the version to 3 so the work is focused on these for now.

It boils down to the argument that "if there is no existing Python code relying on Python 2 semantics, why even bother making a Python 2 version, why not skip straight to Python 3 and not introduce the switching problem later?" There's a small matter of the Python 3 version not being the prime target of PyPy but they are updating it and progressing it forward so it's not any kind of roadblock just a little less than perfect.

Re: PyPy.js: A fast, compliant Python implementation for the web

#142

Post by dulvac » Fri, May 08, 2015, 2:45 PM UTC

I can imagine a way to include language extensions in the browser and have them loaded up lazily in a sandbox. And a checkbox that says "Allow websites to run code" or something. Then you could develop an extension for your favourite language and either install them manually or have some popular ones bundled with the browser.

If we're going to run everything in the browser, why use javascript as the low-level language that stuff compiles to?

I know portability and existing standards are a limitation, but those can be influenced by the 3 (?) major browsers if needed.

I think asm.js is an awesome cute little thing, but the fact that it's taken seriously is worrisome to me.

Am I completely crazy here?

Re: PyPy.js: A fast, compliant Python implementation for the web

#143

Post by bootload » Sat, May 09, 2015, 11:30 PM UTC

techdragon wrote: post #140

bootload wrote: post #138

Earlier quoted context omitted.

ages ago @zo1, I do see similar problems now if I shift from *nux/vim toolchain to win/idle which by default uses 'Python standard: 4 spaces!' but still throws random format error parsing on default code edits. I don't like the fact python code stops working randomly if I write it in one environment then touch (edit) in another. Never have this problem with C or JS.

I have only ever had issues like that when I worked on an actual Python checker where I had to keep BAD code in my tests to ensure the checks worked. I've never ( read 99.999% of the time I've performed the task ) had issues with Python formatting that weren't my own fault, everyone makes mistakes after all. I routinely edit the same Python files in Vim, Nano, Sublime Text, Atom, and PyCharm, and even jumping between…

" I routinely edit the same Python files in Vim, Nano, Sublime Text, Atom, and PyCharm, and even jumping between all those editors, they have never "damaged" the formatting and created syntax errors in my code."

Do you routinely change OS?

Re: PyPy.js: A fast, compliant Python implementation for the web

#144

Post by lqdc13 » Sun, May 10, 2015, 1:40 PM UTC

bootload wrote: post #138

zo1 wrote: post #136

Earlier quoted context omitted.

One-off spacing errors? That doesn't sound right at all... Do you have an example?

ages ago @zo1, I do see similar problems now if I shift from *nux/vim toolchain to win/idle which by default uses 'Python standard: 4 spaces!' but still throws random format error parsing on default code edits. I don't like the fact python code stops working randomly if I write it in one environment then touch (edit) in another. Never have this problem with C or JS.

It is probably carriage returns