[Idle-dev] The Future of Python

[Bruce Sherwood]

At the moment I know very little about Brython, but I do note that in the
documentation at

http://www.brython.info/doc/en/index.html#

in the section "Syntax, keywords, and built-in functions" there is the
statement "Brython supports most keywords and functions of Python 3",
though I don't know whether this Python 3 orientation extends to the text
issue you reference. I know that there are Python -> JavaScript projects
that deviate from Python syntax, but I don't see this now in the Brython
documentation or examples. Searching around I found this statement from the
main Brython developer, making a comparison in a forum with another project
that in fact does not rigorously follow Python syntax: "All this doesn't
mean that Brython performance can't be improved, just that there is a price
to pay for compliance with the Python reference implementation."

Certainly there have to be mechanisms for interacting with the web page. At
www.brython.info if you right-click and view the page source, the code for
the analog clock looks like pretty ordinary Python to me, so maybe there
have been major changes in recent times.

Bruce


On Tue, Feb 11, 2014 at 7:06 AM, Terry Reedy <tjreedy at udel.edu> wrote:

> On 2/10/2014 11:34 PM, Guido van Rossum wrote:
>
>> You've convinced me that brython is interesting. I still think it would
>> require a miracle for it to become mainstream, but it has a better
>> change than pythonb.org <http://pythonb.org>. :-)
>>
>
> The Brython author posted to python-list for 'feedback' about a year or so
> ago, when Brython was in the 0.n (.8?) stage. *As I remember*, there were
> two problems, as least then, from a strict pythonista view.
>
> 1. It was (then, at least) intentionally not the same as Python. Moreover,
> the added syntax was distinctly not pythonic. As I remember, the non-Python
> syntax was not optional and ignorable, like Cython type hints, but pretty
> much required for interacting with the browser.
>
> 2. It was based on Py2 and its text model. To many of us, this seemed like
> a mistake for plugging in to unicode-based browsers and translation to a
> unicode-based javascript. Python 3's text=unicode model seems like a much
> better fit.
>
> The author did not seem interested in suggestions for changing these
> design decisions.
>
> --
> Terry Jan Reedy
>
>
> _______________________________________________
> IDLE-dev mailing list
> IDLE-dev at python.org
> https://mail.python.org/mailman/listinfo/idle-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/idle-dev/attachments/20140211/ec3a49a8/attachment.html>