[Python-es] Fwd: [IPython-dev] IScala: a Scala-language backend for IPython

Julio S.G. julio.sg en mundo-r.com
Dom Sep 8 22:13:08 CEST 2013


Puede ser, pero Scala, me encanta todo sea dicho, tiene que liberarse de 
la JVM. Después hablamos


El 08/09/2013 21:58, Juan Luis Cano escribió:
> Esto le interesará a los amantes de Scala y Python ;)
>
>
> -------- Original Message --------
> Subject: 	[IPython-dev] IScala: a Scala-language backend for IPython
> Date: 	Sun, 8 Sep 2013 21:54:14 +0200
> From: 	Mateusz Paprocki <mattpap en gmail.com>
> Reply-To: 	IPython developers list <ipython-dev en scipy.org>
> To: 	IPython developers list <ipython-dev en scipy.org>
>
>
>
> Hi,
>
> I would like to announce IScala: a Scala-language backend for IPython,
> see [1]. Scala is general purpose, object-functional, statically typed
> programming language for JVM. IScala is an early work in progress, but
> it's already fairly usable. All three types of frontends are
> supported. Required dependencies are IPython 1.0+ and Java Runtime
> Environment 1.6+. See README.md for installation and usage details.
>
> Motivation for this project came when I saw IJulia announcement. The
> hard part - actually "interpreting" Scala - was done in Scala REPL by
> Scala developers. Scala is a compiled language, so interpreting it
> means that source code is compiled (with some fancy wrappers),
> resulting class files loaded into JVM and code run via Java
> reflection. Interpreted code behaves exactly the same as compiled code
> and it runs at full speed. There are a few issues with this, however.
> Scala is a pure object-oriented language, so at top level you can put
> only packages, traits, classes and singleton objects. No expressions
> and other types of statements are allowed. Interpreter removes this
> restriction, by wrapping source code in singleton objects, so that you
> can simply write e.g. `val x = 1` to define a value, which is
> otherwise illegal.
>
> During development of IScala I also created a set of notebooks with
> Scala code, see [2]. Those are based on a subset of Twitter's Scala
> lessons [3]. I didn't encode notebooks directly in the JSON-based
> format, but I invented an adhoc format based on Markdown with support
> for cells. There is a simple converter that allows to generate
> IPython-compatible notebooks.
>
> [1]https://github.com/mattpap/IScala
> [2]https://github.com/mattpap/scala_school_notebooks
> [3]https://github.com/twitter/scala_school
>
> Mateusz
> _______________________________________________
> IPython-dev mailing list
> IPython-dev en scipy.org
> http://mail.scipy.org/mailman/listinfo/ipython-dev
>
>
>
>
> _______________________________________________
> Python-es mailing list
> Python-es en python.org
> https://mail.python.org/mailman/listinfo/python-es
> FAQ: http://python-es-faq.wikidot.com/

------------ próxima parte ------------
Se ha borrado un adjunto en formato HTML...
URL: <http://mail.python.org/pipermail/python-es/attachments/20130908/06658c6d/attachment.html>


Más información sobre la lista de distribución Python-es