From Wikipedia, the free encyclopedia
  (Redirected from Pyjamas (software))
Jump to: navigation, search
New logo of the Pyjs project (aka Pyjamas), after forking off in 2012.
Original author(s) James Tauber, Google
Developer(s) Luke Leighton, Anthony C Risinger, Kees Bos
Initial release March 2007; 8 years ago (2007-03)
Stable release 0.8.1a / May 6, 2012; 3 years ago (2012-05-06)
Development status Stalled
Written in Python, JavaScript
Operating system Windows, OS X, Linux
Available in Python
Type Ajax framework, Desktop and Web Widget toolkit, Compiler, Widget set
License Apache License 2.0

Pyjs (formerly Pyjamas before May 2012[1]), is a rich Internet application framework for developing client-side web and desktop applications in Python. The resulting applications can be run in a web browser or as standalone desktop application.

It contains a stand-alone Python-to-JavaScript compiler, an Ajax framework and widget toolkit, and through use of these components, developers can write comprehensive applications, to run in all major web browsers, without writing any JavaScript. Pyjs is a port of Google Web Toolkit (GWT)[2] from Java to Python.


Using pyjs, developers can write web applications in Python instead of JavaScript. The application is compiled to JavaScript. Also included is an Ajax library and widget set[3] that provides access to the DOM model of modern JavaScript-capable web browsers. The Ajax library and the widget set library are a hybrid mix of Python and JavaScript. Just as with Google Web Toolkit, pyjs is not its libraries, and neither is it just another Ajax framework. Ajax frameworks are strictly limited to providing pre-prepared specific functionality, written almost exclusively in tailor-made JavaScript. Both GWT and pyjs, being JavaScript compilers, allow the developer to work in the language with which they are familiar (Java or Python, respectively), to write their own custom widgets, either entirely from scratch or based on the existing available widgets, yet still target the full range of modern browsers. So, far from presenting web developers with a fait-accompli Ajax framework, pyjs gives you the freedom to develop your own.


The pyjs compiler is written in the programming language Python, and uses it to compile its input into JavaScript, walking the abstract syntax tree of the program being compiled. Although the compiler is stand-alone, the primary use of pyjs is for web development, so there is additional infrastructure for building web applications.

The[4] model library is an abstraction layer - a thin layer of Python on top of JavaScript code snippets - use of which provides access to the full Document Object Model of the target browser platform. As with any compiler, the JavaScript snippets are treated as inline assembler.

Furthermore, on top of the model library is an additional abstraction layer,,[5] which provides the most useful layer to web developers: a full suite of widgets with which desktop application developers will be familiar. At present, the list of available widgets is a mixture of the complete set of widgets that were available in Google Web Toolkit 1.2, along with a few more that have been forward-ported from GWT 1.5.


The major Pyjs components include:

pyjs Python-to-JavaScript Compiler
Translates the programming language Python into JavaScript.
Python builtin and standard emulation library
JavaScript implementations of the commonly used modules, builtins and classes in the Python standard runtime library (such as strings, lists, dictionaries, tuples, sets, getattr, map, filter, range, etc.; basic exception handling, a basic datetime and a basic math module).
pyjs DOM library[4]
Modules for manipulating the browser DOM.
pyjs Web UI module[5]
A module for creating widgets as if the web browser was a desktop widget engine.
pyjs Desktop ports
Support for running pyjs apps as pure Python, under Trident (MSHTML), Gecko (XULRunner) or WebKit. Pyjs Desktop is conceptually close to GWT "Hosted" mode, except that the applications can be deployed live, under pyjs Desktop, rather than be used exclusively as a debugging tool.

pyjs Desktop[edit]

The widget set library[3] that comes with pyjs is so similar to PyQt and PyGTK that a port of pyjs was made to run pyjs applications on the desktop, called pyjs Desktop (formerly PyjamasDesktop[6] before May 2012 and originally hosted separately prior to version 0.6[7]). The project uses Webkit, XULRunner or MSHTML as the underlying technology, and it is through these browser engines that pyjs manipulates the DOM model of the application. Together pyjs and pyjs Desktop allow writing cross-platform, cross-desktop, cross-browser and cross-widget applications that run on the web and on the desktop.[8][9]


Pyjamas was originally developed by James Tauber. The original code for the UI Widget Set and the DOM support libraries came from Google Web Toolkit, and was ported by James Tauber. James wrote the original pyjs compiler. Luke Leighton took over the project in 2008, and updated the UI Widget Set, improved the compiler and created the three pyjs Desktop runtimes. Bernd Dorn and his colleagues from Lovely Systems did some dramatic compiler improvements for 0.5. Kees Bos joined because he was not interested in learning JavaScript, but learn he definitely did. Kees is responsible for the majority of the vast improvements and the more esoteric Python interoperability in the compiler, such as "yield", long data type and much much more. C Anthony Risinger also joined as lead and administrator of the project.

On May 2, 2012 the leadership roles of the project came into question. This was a community driven open source project that was extensively developed by many contributors including the people mentioned above. Due to disagreements between members of the group on how to move forward with the infrastructure and direction of the software, some members decided to create their own fork of the pyjamas project. This fork was created by a team led by Anthony Risinger, one of the administrators of the project. This group included the person who owned the domain and he voluntarily decided to assign ownership of the domain to this new fork being created and hence became the new fork of the pyjamas project. Luke Leighton continued his work on his own fork through a new domain and continues to develop and maintain pyjamas on this fork.

This still left a controversy over the copying of the mailing list data from the old server to create the new mailing list of google groups. This was raised as a violation of the UK Data Protection Act by Luke Leighton. Whether this was actually a legal violation is not really clear and is open to interpretation. This was a community driven open source project. According to many in the community [weasel words], both Luke and Anthony were co-administrators of the project and co-leads to it. It was being forked by a team including Anthony, one of the administrators who had privileges for the server, which Luke Leighton owned. The mailing list was part of the domain. So the ownership of the mailing list data itself isn't very clear. Though Luke claims he personally owned the mailing list and that using it to create a new mailing list for the new fork of the project constituted stealing, many in the community [weasel words] feel differently. Many feel [weasel words] that this was an open source community project and Luke Leighton was a co-lead and co-administrator. Hence the mailing list was actually a community property of the community and not the personal property of Luke. Thus, though some disagree, in the opinion of many in the community [weasel words], using it to create the new google groups was legal.

Even though the ownership of the mailing list data is not entirely clear, when some members complained about being subscribed to the new google groups mailing list, immediate action was taken by the maintainers of the new fork to remove everyone from the new google groups and invited all the members to voluntarily join the new google groups. This being exactly the same approach that Luke Leighton took when he decided to move the pyjamas mailing list from google groups where it was originally created before Luke Leighton took over leadership of the project.

The current membership of the Google Groups owned and maintained by both forks of the original is now voluntary, created through invitation, and does not violate any privacy and data protection laws. There are no unresolved legal issues at this time nor any pending lawsuits with either forks of the pyjamas project.

Both forks are being actively developed and have formed their own community following.


There are now two forks of the Pyjamas/Pyjs project: one maintained by the new Pyjs team and another maintained by Luke Leighton.[edit]

The fork, available at, has gone through active development.

  • New GitHub based infrastructure
  • Travis CI based continuous integration for both build, install and automated testing
  • pip install and VirtualEnv based development environment
  • Separation of pyjs tools from pyjs GWT widgets to allow other widgets sets to be developed
  • Built-in Closure compiler integration
  • GI Introspection/WebKit-GTK based pyjs-desktop runner[edit], available at, continued to be maintained by Luke Leighton and was still active with bug fixes and new development. As of early 2015, however, the website is not available anymore.


Pyjamas has been criticized by heavy users for several aspects:[10]

  • Browser detection instead of feature detection
  • Bloat and boilerplate hell (Python feature coverage is favored over speed and size)
  • Debugging (perfect with Pyjs Desktop, but that is broken for more than 3 years)
  • Python is not Java, DOM is not a Desktop (the underlying GWT unnecessarily fakes a desktop GUI)

On the other hand, as a dynamically typed language Python is a specifically good fit for compiling code to JavaScript, actually a more natural fit than GWT's original Java-to-JavaScript approach.[11]


Most alternatives to Pyjamas are translators rather than frameworks.[12]

  • py2js
  • PyCow
  • Pyjaco
  • PyvaScript
  • RapydScript


  1. ^ Infrastructure, endpoint, process changes, clarification by Lex on pyjamas-dev mailing list (May 03, 2012)
  2. ^ pyjs README
  3. ^ a b The ui Module Class Hierarchy
  4. ^ a b DOM module
  5. ^ a b ui module
  6. ^ PyjamasDesktop history, Python Wiki
  7. ^ "Pyjamas Desktop". 
  8. ^ Pyjamas - Python Applications for Desktop and Web, Luke Kenneth Casson Leighton (August 30, 2008)
  9. ^ Coding in Pyjamas: Apps for Desktop and the Web Luke Kenneth Casson Leighton (November 7, 2008)
  10. ^ Why Pyjamas Isn't a Good Framework for Web Apps, Alexander Tsepkov (July 29, 2012)
  11. ^ Thinking alike, comment by user cananian (Nov 5, 2008)
  12. ^ Pyjamas Alternatives for Web Development, Alexander Tsepkov (September 17, 2012)

External links[edit]