Posted by patrick sur juin 21, 2009
- https://launchpad.net/appscale (‘AppScale is an open-source implementation of the Google AppEngine (GAE) cloud computing interface from the RACELab at UC Santa Barbara. AppScale enables execution of GAE applications on virtualized cluster systems. In particular, AppScale enables users to execute GAE applications using their own clusters with greater scalability and reliability than the GAE SDK provides. Moreover, AppScale executes automatically and transparently over cloud infrastructures such as the Amazon Web Services (AWS) Elastic Compute Cloud (EC2) and Eucalyptus, the open-source implementation of the AWS interfaces.’)
Posted in 2009, python | Tagué: App sclale, google app engine | Leave a Comment »
Posted by patrick sur juin 21, 2009
- http://mail.python.org/pipermail/python-dev/2009-June/090038.html (‘I have been doing some work to extend Google’s Native Client  to support dynamic linking . For those who haven’t heard of it, Native Client is a sandboxing system for running a subset of x86 code. It is proposed as a way of running native code inside web apps. One of my aims has been to get CPython working in the web browser under Native Client without having to modify CPython. I recently got to the point where modules from the Python standard library are importable under Native Client, including (as a demonstration) the Sqlite extension module. Sqlite also requires no modification – it builds straight from the Debian package. I’ve written a simple REPL to demonstrate Python running in the browser. There are some screenshots on my blog . I haven’t implemented accessing the DOM from Python yet – that’s another project for later. 🙂 Mark)
- http://code.google.com/p/nativeclient/ (‘Native Client is an open-source research technology for running x86 native code in web applications, with the goal of maintaining the browser neutrality, OS portability, and safety that people expect from web apps. We’ve released this project at an early, research stage to get feedback from the security and broader open-source communities. We believe that Native Client technology will someday help web developers to create richer and more dynamic browser-based applications.‘)
- http://plash.beasts.org/wiki/NativeClient (‘Google Native Client (abbreviated as NaCl) is a sandboxing system for running a subset of Intel x86 native code using software-based fault isolation. It is proposed for safely running native code from a web browser, allowing web-based applications to run at near-native speeds…In order to make it easier to run GNU/Linux programs under NaCl, and to run programs that require dynamic linking, I am porting glibc to NaCl. The port is at the stage where it can run simple statically-linked and dynamically-linked programs, both from the command line and from the web browser. It can run Python 2.6; no changes to Python were required.’)
- http://nativeclient.googlecode.com/svn/trunk/nacl/googleclient/native_client/documentation/building.html (‘Thanks to SCons, you use the same basic commands to build on all platforms. …If you followed the instructions in Getting Started, you should already have the right version of Python. The summary: Use Python 2.4 or 2.5 (possibly 2.6), don’t use the Cygwin version of Python, and avoid spaces in the path to
python. For further details, see Get the software and the details page for your platform (Linux, Mac, or Windows’)
- http://fwierzbicki.blogspot.com/2009/06/jython-250-final-is-out.html (‘…On behalf of the Jython development team, I’m pleased to announce that Jython 2.5.0 final is available for download. See the installation instructions. Jython 2.5.0 brings us up to language level compatibility with the 2.5 version of CPython. This release has had a strong focus on CPython compatibility, and so this release of Jython can run more pure Python apps then any previous release. Please see the NEWS file for detailed release notes.
- I want to thank all of the amazing people who have contributed in large and small ways to this important Jython release. For the first time in a long time we have Jython that is a modern version of Python. Enjoy!…‘)
- http://codespeak.net/pipermail/pypy-dev/2009q2/005222.html (‘Welcome to the PyPy 1.1 release – the first release after the end of EU funding. This release focuses on making PyPy’s Python interpreter more compatible with CPython (currently CPython 2.5) and on making the interpreter more stable and bug-free. Through a large number of tweaks, performance has been improved by 10%-50% since the 1.0 release. The Python interpreter is now between 0.8-2x (and in some corner case 3-4x) slower than CPython. A large part of these speed-ups come from our new generational garbage collectors. Our Python interpreter now supports distutils as well as easy_install for pure-Python modules. – We have tested PyPy with a number of third-party libraries. PyPy can run now: Django, Pylons, BitTorrent, Twisted, SymPy, Pyglet, Nevow, Pinax… The « clr« module was greatly improved. This module is used to interface with .NET libraries when translating the Python interpreter to the CLI. PyPy’s Python interpreter can be translated to Java bytecode now to produce a pypy-jvm. At the moment there is no integration with Java libraries yet, so this is not really useful
- http://lists.ironpython.com/pipermail/users-ironpython.com/2009-May/010391.html (‘ Hello Python Community,We’re quite pleased to announce the release of « IronPython 2.6 CTP for .NET 4.0 Beta 1 ». This is our second preview of IronPython running under the Dynamic Language Runtime that is built directly into a .NET 4.0 release! As before, this release allows you to use IronPython objects and types as .NET 4.0 dynamic objects from within C# and Visual Basic code. While this release does share a bit in common with the upcoming IronPython 2.6 Beta 1 release (e.g., a number of MSI improvements), the core functionality is essentially that of IronPython 2.6 Alpha 1. Please also note that « IronPython 2.6 CTP for .NET 4.0 Beta 1 » will run only under .NET 4.0 Beta 1.
Posted in Implémentation python, logiciel libre, RIA | Tagué: jython2.5, Native client, scons | Leave a Comment »
Posted by patrick sur juin 21, 2009
– http://bobo.digicool.com/ (‘Bobo is a light-weight framework for creating WSGI web applications. It’s goal is to be easy to learn and remember.It provides 2 features:
- Mapping URLs to objects
- Calling objects to generate HTTP responses
It doesn’t have a templateing language, a database integration layer, or a number of other features that can be provided by WSGI middle-ware or application-specific libraries.Bobo builds on other frameworks, most notably WSGI and WebOb.‘)
http://mail.python.org/pipermail/web-sig/2009-June/003831.html (from Philip J.Eby: « …anybody who knows Python web development should know that Bobo was actually the first Python web framework ever developed, 12 years ago, and that it invented quite a lot of the things found in Python web frameworks today, not to mention being the forerunner of all things Zope.
It’s rather nice to see it back, reincarnated on today’s egg/WSGI infrastructure. The original Bobo was what convinced me to become a Python programmer 12 years ago. (…after I realized that a Bobo-equivalent framework could not be implemented in Perl without far greater wizardry than I was capable of managing, while in Python it was nearly trivial to do so. I left Perl and never looked back. « )
- http://pypi.python.org/pypi/WebOb/ (‘WSGI request and response object WebOb provides wrappers around the WSGI request environment, and an object to help create WSGI responses. The objects map much of the specified behavior of HTTP, including header parsing and accessors for other standard parts of the environment…The primary object in WebOb is webob.Request, a wrapper around a WSGI environment.’)
- http://en.wikipedia.org/wiki/Wsgi (…The Web Server Gateway Interface defines a simple and universal interface between web servers and web applications or frameworks for the Python programming language. The latest version 3.0 of Python, released in December 2008, is already supported by mod_wsgi (a module for the Apache Web server…Historically Python web application frameworks have been a problem for new Python users because, generally speaking, the choice of web framework would limit the choice of usable web servers, and vice versa. Python applications were often designed for either CGI, FastCGI, mod_python or even custom API interfaces of specific web-servers. WSGI (sometimes pronounced ‘whiskey’ or ‘wiz-gee’) was created as a low-level interface between web servers and web applications or frameworks to promote common ground for portable web application development. WSGI is based on the existing CGI standard…)
Posted in 2009, python, Python Web Frameworks, Web Frameworks | Leave a Comment »