"…mais ce serait peut-être l'une des plus grandes opportunités manquées de notre époque si le logiciel libre ne libérait rien d'autre que du code…"

Archive for juin 2009

AppScale: implémentation libre en python de google app engine (GAE)

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.’)

Voir:

Publicités

Posted in 2009, python | Tagué: , | Leave a Comment »

Quelques nouvelles de python: jython2.5 et Django, Python2.6 sur NaCl (Native Client), PyPy 1.1, Ironpython 2.6

Posted by patrick sur juin 21, 2009

    • 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
    • a voir:
      • 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é: , , | Leave a Comment »

      Web Python Framework : le retour de Bobo, le framework de Jim Fulton

      Posted by patrick sur juin 21, 2009

      Rapidement:

      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.
      « )

      A voir

      • http://pypi.python.org/pypi/bobo
      • 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[1] (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 »