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

• 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:

• bzr branch lp:~appscale-maintainers/appscale/appscale
• http://code.google.com/intl/fr-FR/appengine/
• http://linuxfr.org/2009/06/18/25613.html
  

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

• http://mail.python.org/pipermail/python-dev/2009-June/090038.html (’I have been doing some work to extend Google’s Native Client [1] to support dynamic linking [2]. 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 [3]. I haven’t implemented accessing the DOM from Python yet – that’s another project for later. Mark)
  • voir:
    • 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://docs.djangoproject.com/en/dev/howto/jython/ (’Jython is an implementation of Python that runs on the Java platform (JVM). Django runs cleanly on Jython version 2.5 or later, which means you can deploy Django on any Java platform….The django-jython project contains database backends and management commands for Django/Jython development. Note that the builtin Django backends won’t work on top of Jython.To install it, follow the installation instructions detailed on the project website. Also, read the database backends documentation there.‘)

• 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://morepypy.blogspot.com/2008/08/pypy-runs-unmodified-django-10-beta.html
    • http://morepypy.blogspot.com/2008/07/pypys-python-runs-pinax-django.html
    • http://morepypy.blogspot.com/2008/06/running-nevow-on-top-of-pypy.html
    • http://codespeak.net/pypy/dist/pypy/doc/clr-module.html
    • http://morepypy.blogspot.com/2008/01/pypynet-goes-windows-forms.html
    • http://morepypy.blogspot.com/2008/01/improve-net-integration.html

• 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.

• http://ironpython.codeplex.com/SourceControl/ListDownloadableCommits.aspx#DownloadLatest
• http://www.codeplex.com/Wiki/View.aspx?ProjectName=IronPython

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

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…)

Quelques nouvelles de python: python 3.1a2 release, switching to mercurial, pycon 2009

Gestion de versions: la gestion des sources de python passe de subversion à mercurial !.

• http://sayspy.blogspot.com/2009/03/why-python-is-switching-to-mercurial.html (’Starting at PyCon 2008 thanks to Barry Warsaw and the Bazaar team I started thinking about moving Python over to a distributed version control system (DVCS). While I wanted to get offline commits for the benefit of non-core developers along with easier merging from 2.6 to 3.0 (ah, the days when there are only three branches under development), I knew that would not necessarily be enough of a reason for others to switch…Based on the results of that survey where git was clearly the most disliked tool of the core developers, having the weakest Windows support, and not being implemented in Python, I decided to eliminate git from the running and announce its elimination at the first lightning talk at PyCon.When I arrived at PyCon pretty much everyone asked me about the DVCS PEP. People wanted to know how it was going, who was going to win, and giving me support/pity for what I was going through. Guido noticed this and decided to end my misery by saying he wanted to make a decision by the end of PyCon. I said I was fine with that as one was already about to be eliminated and I knew my personal preference at that exact moment aligned with Guido’s…So Monday morning came around and I walked into the sprint. I asked Guido if he was ready to make a decision. He said yes, we both said hg, and so Guido tweeted the decision before telling python-dev that we chose Mercurial…Obviously community preference as shown at PyCon played a role. No one wants to choose a DVCS that causes the community to not want to contribute to Python. And I would never choose a VCS that would cause Guido to not want to work on Python. Some people seem surprised that something non-technical played a role, but ignoring social issues is to ignore how much open source is a social phenomenon. And we are not the first project to take social preference into consideration: I know both GNOME and Pinax chose git because their developers preferred git. And there are technical reasons. Having hg being faster than bzr by 2x to 3x does matter to some extent. No one wants to cause someone to not contribute because they didn’t want to wait for a checkout. And having personally experienced long checkout times because of a subpar connection to a specific server I know this can occur. The performance margin between hg and bzr is within reason typically and is not a flat-out deal-breaker, but it doesn’t help either. Bazaar also has its short timespan of format stability working against it. The tool has changed its format at least three times based on what the man page says (1.0, 1.6, and 1.9). Mercurial, on the other hand, has been stable since I think it went public or near that time. They take great pride in the fact they have not changed it. And that stability more aligns with python-dev’s sensibilities regarding stability. Once again the Python community stands out as being friendly and understanding about stuff like this with no one really seeming to be upset that we made the decision we did.’)
• http://mail.python.org/pipermail/python-dev/2009-March/087931.html (’Dear Python developers,The decision is made! I’ve selected a DVCS to use for Python. We’re switching to Mercurial (Hg). The implementation and schedule is still up in the air — I am hoping that we can switch before the summer.’)

A voir

• http://code.python.org/hg/
• http://www.python.org/dev/peps/pep-0374/ (‘Migrating from svn to a distributed VCS‘)
• http://en.wikipedia.org/wiki/Mercurial_(software) (’ Mercurial is a cross-platform, distributed revision control tool for software developers. It is mainly implemented using the Python programming language, but includes a binary diff implementation written in C. Mercurial was initially written to run on Linux. It has been ported to Windows, Mac OS X, and most other Unix-like systems. Mercurial is primarily a command line program. All of Mercurial’s operations are invoked as keyword options to its driver program hg, a reference to the chemical symbol of the element mercury. Mercurial’s major design goals include high performance and scalability, decentralized, fully distributed collaborative development, robust handling of both plain text and binary files, and advanced branching and merging capabilities, while remaining conceptually simple ^[1]. It includes an integrated web interface.The creator and lead developer of Mercurial is Matt Mackall. The source code is available under the terms of the GNU General Public License version 2, qualifying Mercurial as free software.’)
  • http://en.wikipedia.org/wiki/Mercurial_(software)#Related_software
• http://pypi.python.org/pypi/hgview/ (mercurial interactive history viewer. Its purpose is similar to the hgk tool of mercurial, and it has been written with efficiency in mind when dealing with big repositories (it can happily be used to browse Linux kernel source code repository).)

Pycon 2009

• http://pycon.blogspot.com/2009/04/all-pycon-2009-videos-uploading.html (’The video team has pulled the trigger and all the video from the conference is being uploaded now. At the time of this post about 14 talks are now online. By the end of the day Friday, almost everything should be available (with a few minor exceptions). The videos are also integrated into the PyCon Schedule App as well, with a minor lag time. Just look for the tiny video icon: .
  Congratulations to the entire PyCon US 2009 volunteer video team for performing this Herculean task. In total 2.2TB of video, covering 168 hours of material, were collected, edited, transcoded, and uploaded. This is divided into 96 hours from the tutorials and 72 hours from the main conference.’)

A voir

• http://holdenweb.blogspot.com/2009/03/pycon-proves-its-worth.html (’Here’s a great quote from Catherine Devlin’s blog post Five Minutes at PyCon Changes Everything reporting the unexpected recruitment of a high-powered development team after giving a lightning talk:
  

  If I’d had $1 million of startup funding to hire a staff to work on sqlpython, I couldn’t have gotten a team that large or that talented. I figure that gives me better than a 1000-to-1 return on my PyCon investment. ‘)

• http://us.pycon.org/2009/conference/schedule/

Python 3.1a2 release

• http://mail.python.org/pipermail/python-dev/2009-April/088213.html (’ On behalf of the Python development team, I’m thrilled to announce the second alpha release of Python 3.1. Python 3.1 focuses on the stabilization and optimization of features and changes Python 3.0 introduced. For example, the new I/O system has been rewritten in C for speed. Other features include an ordered dictionary implementation and support for ttk Tile in Tkinter. For a more extensive list of changes in 3.1, see http://doc.python.org/dev/py3k/whatsnew/3.1.html or Misc/NEWS in the Python distribution.Please note that this is an alpha release, and as such is not suitable for production environments. We continue to strive for a high degree of quality ,but there are still some known problems and the feature sets have not been finalized. This alpha is being released to solicit feedback and hopefully discover bugs, as well as allowing you to determine how changes in 3.1 might impact you. If you find things broken or incorrect, please submit a bug report at  http://bugs.python.org. For more information and downloadable distributions, see the Python 3.1 website:
  • http://www.python.org/download/releases/3.1/.
  • http://www.python.org/dev/peps/pep-0375/‘)
• http://code.python.org/hg/branches/py3k/file/202c0c7f1c1d/Misc/NEWS
  

Systèmes de gestion de versions: subversion, bazaar

Beauccoup de mouvements encore autour des systèmes de gestion de versions distribuées git, mercurial et bazaar:

- http://arstechnica.com/open-source/news/2009/03/sourceforge-adds-support-for-new-version-control-systems.ars (’SourceForge has launched support for Git, Bazaar, and Mercurial, the three most popular distributed version control systems. The site has also added an impressive new hosted application feature which will allow users to run various open source project management and collaboration services—including Trac, Mantis, and phpBB—on SourceForge’s infrastructure. Although SourceForge was once the dominant collaboration service for open source software, its relevance declined sharply over the past few years as it stagnated and lost ground to emerging competitors. The trend towards distributed version control systems (DVCS) looked like it would be the final nail in the coffin, but now SourceForge is preparing to make a major comeback. The Web service has gained support for Git, Mercurial, and Bazaar, the three most popular distributed version control systems. This brings the site’s total number of supported source code management technologies to five, including its existing support for CVS and Subversion. DVCS is a major technical advancement in the area of source code management. The approach offers developers an unprecedented level of power and flexibility. The three major DVCS systems have all been used to build robust project management and code hosting services—such as GitHub, Launchpad, and BitBucket—which are rapidly displacing SourceForge. Here at Ars, our Web ninjas use GitHub extensively for managing the source code that powers our website. I personally use Launchpad for several of my own projects.’)

Passage de CVS à subversion pour la documentation Debian (il y a un an mais mieux vaut tard que jamais pour que le signale )

- http://www.ouaza.com/wp/2008/03/03/ddp-went-svn-webml-might-follow/ (’The topic of switching from CVS to something else regularly came forward but nobody did anything. The net result is that several documentation are now maintained outside of the debian-doc repository because their respective maintainers didn’t want to stay with CVS. After noticing that the developers-reference also switched to SVN, I decided to convert the whole debian-doc CVS repository and import it in the new “ddp” SVN repository on Alioth. This is now done. Hopefully, the Debian Documentation Project can now again become the central place for writing good documentation about Debian. New contributors can be easily added through the DDP Alioth project. Volunteers are welcome to review what’s in the SVN and move obsolete documentation aside. People who moved away are welcome back. ‘)

Passage de sourceforge à launchpad (https://code.launchpad.net/mailman)

- http://blog.launchpad.net/general/why-launchpad-for-mailman (’Over the last 18 months, I’ve moved GNU Mailman development from SourceForge to Launchpad.  The reasons are varied. Mailman was one of the first projects hosted on SourceForge ages ago.  I think our project id is a pride-inducing low 103, and we were even highlighted as its Project of the Month at one point.  Of course SF itself uses Mailman to serve its own mailing lists.  While the SF guys have always been great (including providing assistance during the migration to LP), I just became increasingly roadblocked by it.

The first major motivation for moving was Bazaar. This is of course the GPL’d distributed version control system developed by Canonical and used for code hosting on Launchpad.  Having come from decades of SCCS/RCS/CVS/SVN use, distributed version control systems in general and Bazaar in particular have been an enlightenment on the order of learning Python.  I mean, who’d have thunk a version control system could be fun?

After we moved code hosting to Bazaar on LP, evaluating the other benefits of Launchpad became easier.  Truth be told, there was (and still is) some resistance in the community to moving to LP because Mailman is a GNU project but LP is not open source.  That’s being fixed. The next service to migrate was the tracker, and thanks to the excellent assistance of my colleague Graham Binns, we were able to migrate the SF issues to LP.  For years, even before I joined Canonical, I let the Mailman tracker languish because I found it so difficult to use.  The simplicity and power of Launchpad’s tracker really shines for me here, especially with its ability to link across projects and artifacts (e.g. branches linked to bugs).’)

A voir:

- http://sourceforge.net/softwaremap/trove_list.php?form_cat=646

- http://en.wikipedia.org/wiki/Subversion_(software) (’Subversion (SVN) is a version control system initiated in 2000 by CollabNet Inc. It is used to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly-compatible successor to the widely used Concurrent Versions System (CVS). Subversion is well-known in the open source community and is used on many open source projects, including Apache Software Foundation, KDE, GNOME, Free Pascal, FreeBSD, GCC, Python, Django, Ruby, Mono, SourceForge.net, ExtJS and Tigris.org. Google Code also provides Subversion hosting for their open source projects. BountySource systems use it exclusively. Codeplex offers access to both subversion as well as other types of clients. Subversion is also being adopted in the corporate world. In a 2007 report by Forrester Research, Subversion was recognized as the sole leader in the Standalone Software Configuration Management (SCM) category and a strong performer in the Software Configuration and Change Management (SCCM) category.^[1] Subversion is released under the Apache License, making it free software. ‘)

- http://subversion.tigris.org/development.html (’ The best way to get involved in Subversion development is to submit a patch to fix a bug or add a new feature. If you don’t know what to write a patch for, have a look at the list of open issues. Subversion development discussion takes place on the mailing list dev@subversion.tigris.org. You don’t need to subscribe to the list just to submit a patch or two, but if you want to be involved with Subversion development on a regular basis, you should subscribe. It’s high-traffic, but threading tends to be fairly disciplined, so you can ignore conversations you aren’t interested in. For real-time chat, developers use the IRC channel irc.freenode.net/svn-dev (some also hang out in the user-support channel, irc.freenode.net/svn).’)

- http://svnbook.red-bean.com/ (’This is the online home of Version Control with Subversion, a free book about Subversion, a new version control system designed to supplant CVS. As you may have guessed from the layout of this page, this book is published by O’Reilly Media. This is a place to read HTML and PDF versions of the book (although you can certainly buy a copy if you’d like to). We’ll do our best to keep the site up-to-date. As Subversion development continues, the product will continue to grow new features, and we plan to continue documenting those changes.’)

- http://svn.collab.net/viewvc/svn/trunk/ (sources de subversion)

• - http://subversion.tigris.org/hacking.html
  • http://subversion.tigris.org/hacking.html#branch-based-development (’We prefer to have development performed on the trunk. Changes made to trunk have the highest visibility and get the greatest amount of exercise that can be expected from unreleased code. That said, trunk is expected at all times to be stable. It should build. It should work. Those policies, combined with our preference to see large changes broken up and committed in the smallest logical chunks feasible, and applied to particularly large changes (new features, sweeping code reorganizations, etc.), makes for set of rules that are almost impossible to keep. It is in those situations that you might consider using a custom branch dedicated to your development task. The following are some guidelines to make your branch-based development work go smoothly…

    Branch creation and management

    There’s nothing particularly complex about branch-based development. You make a branch from the trunk (or from whatever branch best serves as both source and destination for your work), and you do your work on it. Subversion’s merge tracking feature has greatly helped to reduce the sort of mental overhead required to work in this way, so making good use of that feature (by using Subversion 1.5 or newer clients, and by performing all merges to and from the roots of branches) is highly encouraged.’)

  •  svn co http://svn.collab.net/repos/svn/trunk  (intéressant, il y ade très nombreux scripts python)

  • à suivre…

Le nouveau cahier de l’administrateur Debian GNU/Linux “Lenny” de Raphaël Hertzog et Roland Mas est sorti

Debian GNU/Linux lenny administration

Références :

• Titre : Debian Lenny
• Auteurs : Raphaël Hertzog et Roland Mas
• ISBN13 : 978-2-212-12443-9
• Site web : chez Raphaël et chez Eyrolles

Sources:

- http://www.ouaza.com/livre/admin-debian/(’Ce livre a été rédigé par deux développeurs Debian de longue date (Raphaël contribue depuis 1997, Roland depuis 2000). Nous avons essayé de vous faire découvrir toutes les facettes de cette distribution fascinante, autant d’un point de vue technique qu’organisationnel. Jugez-en par vous même ! ‘)

- http://roland.entierement.nu/blog/2009/03/02/debian-lenny-le-livre-le-jeu.html (’Si vous n’avez pas passé les trois dernières semaines sous un caillou ou dans un monastère, vous savez déjà que la version 5.0 de Debian GNU/Linux, nom de code « Lenny », est sortie le 14 février dernier. Pour accompagner la publication de cette nouvelle version majeure de Debian, Raphaël Hertzog et moi-même avons également mis à jour le Cahier de l’admin Debian. L’édition portant sur Lenny est déjà disponible en version électronique sur Izibook, et la version papier sera chez les libraires le 19 mars. Elle ne constitue pas une révolution (on ne change pas une formule qui est devenue au fil des ans la référence en français), mais principalement une mise à jour, avec des ajouts pour combler quelques vides (par exemple, de nouvelles sections sur OpenVPN et les partitions chiffrées. Pour certaines des précédentes éditions, il avait été lancé un concours où les personnes faisant la meilleure promotion étaient récompensées par des exemplaires du livre. Pour cette édition, nous avons gardé l’idée, mais l’objet du concours est différent : il s’agit non plus de faire la promotion du livre, mais de participer à la communauté Debian. Pas besoin d’être un super-développeur, il suffit d’apporter une contribution qui va faire progresser Debian d’une manière ou d’une autre, à condition que ce soit tangible. Raphaël écrit une série d’articles sur le sujet, vous pouvez donc aller y piocher des idées. J’en ajouterai deux, complémentaires :

• Publier un blog qui donne une visibilité aux évolutions récentes, en cours ou prévues de Debian unstable et/ou testing, voire experimental. Quelques exemples de ce qu’on pourrait y voir serait l’arrivée d’une nouvelle version majeure du noyau ou de Gnome, la disparition d’un paquet au profit d’un autre, l’arrivée de nouveaux paquets intéressants, leur migration vers testing, etc. Pas une liste de tous les changements de chaque bibliothèque mineure, mais juste une vue macroscopique de ce qui se passe de visible pour les utilisateurs.
• Dans un registre un peu différent, il serait intéressant de publier (peut-être aussi sous forme de blog) un baromètre de l’état actuel d’unstable, avec les migrations en cours, les paquets importants connus pour être cassés, etc. Le but est de faciliter l’usage d’unstable par des utilisateurs courageux-mais-pas-téméraires. Un exemple de ce que j’y verrais bien est une mention du bug 511009, assorti d’une mention que c’est pas une bonne idée d’upgrader CUPS pour l’instant (ça m’aurait évité quelques heures d’interrogations) ; et un autre billet quand c’est résolu. Là encore, trop de débit ne servirait à rien, il suffirait d’une vision macroscopique de l’état des différents sous-systèmes.

Bien entendu, ce ne sont que des idées, et les plus originales seront peut-être les meilleures, puisqu’elles seront celles que nous n’aurons pas prévues et apporteront donc une réelle nouveauté.’  voir http://www.ouaza.com/wp/2009/03/02/contribuer-a-debian-gagner-un-livre/ )

- http://www.eyrolles.com/Informatique/Livre/debian-lenny-9782212124439 (‘Debian GNU/Linux, distribution Linux non commerciale extrêmement populaire, est réputée pour sa fiabilité et sa richesse. Créée et maintenue par un impressionnant réseau de plusieurs milliers de développeurs dans le monde, elle a pour principes l’engagement vis-à-vis de ses utilisateurs et la qualité. Ses technologies concernent un nombre toujours croissant d’administrateurs, notamment par le biais de la distribution dérivée Ubuntu.

Ce cahier de l’Admin entièrement revu pour Debian Lenny perpétue le succès des premières éditions : accessible à tous, il fournit les connaissances indispensables pour qui souhaite devenir un administrateur Debian GNU/Linux efficace et indépendant. Il traite des méthodes que tout administrateur Linux compétent maîtrise, depuis l’installation et la mise à jour du système jusqu’à la création de paquetages et la compilation d’un noyau Linux, en passant par la supervision, la sauvegarde et les migrations, sans oublier des techniques avancées telles que la mise en place de SELinux pour sécuriser des services, l’automatisation des installations ou encore la virtualisation avec Xen.

Au sommaire

• Le projet GNU/Debian
• Présentation de l’étude de cas
• Prise en compte de l’existant et migration
• Installation
• Système de paquetage, outils et principes fondamentaux
• Maintenance et mise à jour : les outils APT
• Résolution de problèmes et sources d’information
• Configuration de base : réseau, comptes, impression
• Services Unix
• Infrastructure réseau
• Services réseau : Postfix, Apache, NFS, Samba, Squid, LDAP
• Administration avancée
• Station de travail
• Sécurité
• Conception d’un paquet Debian
• Conclusion : l’avenir de Debian

• A. Distributions dérivées
• B. Petit cours de rattrapage

Extraits du livre

• Table des matières – Fichier PDF (248.8 Ko)
• Avant-propos – Fichier PDF (255 Ko), “Linux commence à bénéficier d’une couverture médiatique non négligeable, profitant essentiellement aux distributions commerciales (RedHat, SuSE, Mandriva…). Debian, souvent placée par les sondages dans le trio de tête des distributions les plus populaires, est pourtant loin d’être marginale, surtout si l’on y inclut les distributions dérivées dont certaines — comme Ubuntu — connaissent un succès très important.
  Ce n’est pas un hasard si Hewlett-Packard a vu ses ventes de matériel augmenter de 25 millions de dollars en 2006 après avoir proposé du sup-
  port pour Debian. Ce livre a ainsi pour vocation de faire découvrir cette distribution. Nous espérons vous faire profiter de toute l’expérience acquise depuis que nous avons rejoint le projet en tant que développeurs-contributeurs, en 1998 pour Raphaël et en 2000 pour Roland. Peut-être parviendrons-nous à
  vous communiquer notre enthousiasme, et vous donner l’envie de rejoindre nos rangs d’ici quelque temps, qui sait...”
• Préface – Fichier PDF (169.2 Ko)
• Chapitre 1 : Le projet Debian – Fichier PDF (599.3 Ko)
• Chapitre 6 : Maintenance et mise à jour : les outils APT – Fichier PDF (553.9 Ko), (”Ce qui rend Debian si populaire auprès des administrateurs,
  c’est la facilité avec laquelle il est possible d’y installer des logiciels et de mettre à jour le système complet. Cet avantage unique est dû en grande partie au programme APT, outil dont les administrateurs de Falcot SA se sont empressés d’étudier les possibilités.”)

Voir aussi:

• http://www.debian.org/News/2009/20090214 (’Le projet Debian est heureux d’annoncer la publication officielle de la version 5.0 de Debian GNU/Linux, surnommée Lenny, après 22 mois de développement constant. Debian GNU/Linux est un système d’exploitation libre qui prend en charge au total douze architectures de processeurs et contient les environnements de bureau KDE, GNOME, Xfce et LXDE. C’est un système compatible avec la version 2.3 du FHS (« Filesystem Hierarchy Standard », ou standard sur l’organisation des systèmes de fichiers) et les logiciels développés pour la version 3.2 de la LSB (« Linux Standard Base », ou base standard de Linux). Debian GNU/Linux fonctionne sur de nombreux ordinateurs, depuis les assistants personnels (« palmtops ») jusqu’aux superordinateurs y compris quasiment tous les systèmes intermédiaires. Au total, douze architectures sont prises en charge : Sun SPARC (sparc), HP Alpha (alpha), Motorola/IBM PowerPC (powerpc), Intel IA-32 (i386) et IA-64 (ia64), HP PA-RISC (hppa), MIPS (mips, mipsel), ARM (arm, armel), IBM S/390 (s390) et AMD64 et Intel EM64T (amd64). Debian GNU/Linux 5.0 Lenny gère également la plateforme Orion de Marvell qui est utilisée dans de nombreux équipements de stockage, parmi lesquels on trouve la série QNAP Turbo Station, HP Media Vault mv2120, et Buffalo Kurobox Pro. De plus, Lenny gère maintenant plusieurs ordinateurs ultra-portables comme le Eee PC d’Asus. Debian GNU/Linux 5.0 Lenny inclut aussi les outils de construction pour Emdebian, qui permet de construire et les paquets source de Debian sur une autre architecture et de les réduire afin qu’ils conviennent aux systèmes embarqués ARM. Debian GNU/Linux 5.0 Lenny comporte le nouveau portage ARM EABI, Armel qui utilise plus efficacement les processeurs ARM actuels. L’ancien portage d’ARM (arm) est maintenant déconseillé.’)
• http://fr.wikipedia.org/wiki/Debian (”Debian est un système d’exploitation reposant sur les principes du logiciel libre et développé de façon bénévole par l’intermédiaire d’Internet. Ce système permet un mode d’unification des nombreux éléments pouvant être développés indépendamment les uns des autres. Ils sont associés sous forme de « paquets » modulables en fonction des besoins (on en dénombre plus de 23 000 en 2009). On l’assimile généralement à Debian GNU/Linux (la distribution GNU/Linux de Debian), car c’est la seule branche parfaitement fonctionnelle. Toutefois, d’autres versions du système Debian sont possibles comme le prouve le projet Debian GNU/Hurd^[1] ou Debian GNU/kFreeBSD^[2]. Debian a été utilisée comme base de nombreuses autres distributions comme Knoppix ou Ubuntu qui rencontrent un grand succès..”)
• http://en.wikipedia.org/wiki/Debian#Debian_releases (” As of February 2009, the latest stable release is version 5.0, code name lenny.^[41] When a new version is released, the previous stable is labeled oldstable; currently, this is version 4.0, code name etch. In addition, a stable release gets minor updates (called point releases). The numbering scheme up for the point releases to Debian 4.0 was to include the letter r (for release) after the main version number (eg 4.0) and then the number of the point release; for example, the latest point release of version 4.0 (etch) as of 15 February 2009 is 4.0r7.^[42] From Debian 5.0 (lenny) and the numbering scheme of point releases has been changed and conforms to the GNU version numbering standard; so, for example, the first point release of Debian 5.0 is going to be 5.0.1 (instead of 5.0r1).^[43].“)
• http://fr.wikipedia.org/wiki/Debian#Historique_des_versions (”Les différentes versions de la distribution empruntent leurs noms aux personnages du film d’animation Toy Story des studios Pixar “)
• http://fr.wikipedia.org/wiki/Logiciel_libre (”Un logiciel libre est un logiciel dont la licence dite libre donne à chacun le droit d’utiliser, d’étudier, de modifier, de dupliquer, de donner et de vendre le logiciel. Richard Stallman a formalisé la notion de logiciel libre dans la première moitié des années 1980 puis l’a popularisée avec le projet GNU et la Free Software Foundation (FSF). Depuis la fin des années 1990, le succès des logiciels libres, notamment de Linux, suscite un vif intérêt dans l’industrie informatique et les médias. Les logiciels libres constituent une option face à ceux qui ne le sont pas, qualifiés de « propriétaires ». La notion de logiciel libre ne se confond ni avec celle de logiciel gratuit (freewares), ni avec celle de sharewares, ni avec celle de domaine public. De même, les libertés définies par un logiciel libre sont beaucoup plus étendues que le simple accès aux sources, ce qu’on appelle souvent logiciel Open Source telle qu’elle est définie par l’Open source initiative. Toutefois, la notion formelle de logiciel Open Source est reconnue comme techniquement comparable au logiciel libre.“)
• Flux RSS:
  • http://planet-fr.debian.net/users/rss20.xml
  • http://feeds2.feedburner.com/debianadmin
  • http://www.debian-administration.org/atom.xml

- http://pvergain.wordpress.com/2007/11/29/un-nouveau-livre-sur-ladministration-systeme-sous-debian-gnulinux-debian-etch-de-raphael-hertzog-et-roland-mas/

Contre “HADOPI ? “Création et Internet” ? ” cinq gus dans un garage…

Deux images illustrent ce projet de loi ridicule:

Les arguments contre:

• http://www.april.org/hadopi (’ L’April a publié le 5 mars 2009 un communiqué de presse L’HADOPI filtrera aussi le Logiciel Libre, l’April condamne, ainsi qu’un argumentaire, intitulé Hadopi : sécurisation ou contrôle d’usage ? sur la partie technique du projet de loi, pour sensibiliser les députés autant que le public.Pour la partie juridique et une critique de la loi dans son ensemble, consulter la note de François Pellegrini et le dossier de la Quadrature du Net. ‘)

• http://www.april.org/fr/lhadopi-filtrera-aussi-le-logiciel-libre-lapril-condamne (’ L’April a pris connaissance du rapport communiqué par le Conseil Général des Télécommunications (CGTI) au ministère de la Culture.1 Elle constate que ce rapport clarifie l’interprétation du projet de loi HADOPI en énonçant clairement qu’une des finalités est d’imposer des logiciels propriétaires de filtrage sur le poste client. L’April note que ce rapport a été présenté par Jean Berbinau, actuel secrétaire général de l’inutile ARMT2 qui se rêve en secrétaire général de la liberticide HADOPI. Pour accéder à cette promotion, ce dernier n’hésite pas à proposer ce que demandent depuis des années les producteurs de disques et de films : l’obligation pour les internautes désireux de garantir leur sécurité juridique d’installer des logiciels propriétaires filtrant leurs communications. Ce qui avait pu être évité dans la loi DADVSI revient donc au travers du projet HADOPI. Logiciel Libre et dispositifs de contrôle d’usage, de surveillance et de filtrage fermés sont ontologiquement incompatibles. Comme cela a été maintes fois expliqué lors des débats sur la loi DADVSI, sur un système libre, l’utilisateur a le contrôle de sa machine et peut neutraliser tout mécanisme visant à le contrôler ou à le surveiller. En résumé, tout comme il n’est pas possible d’empêcher un utilisateur de logiciels libres de faire des copies privées, il n’est pas possible de lui coller ouvertement un mouchard filtrant. Dès lors, avec l’HADOPI, les utilisateurs de systèmes libres se retrouveront dans une insécurité juridique discriminatoire intolérable.’)

• http://www.cinqgusdansungarage.org/

• http://www.01net.com/editorial/404166/richard-stallman-la-loi-creation-et-internet-est-cruelle-/ (’…
  Le créateur de la licence GNU et inspirateur du Copyleft s’est montré très véhément contre la loi qui doit être discutée à l’Assemblée nationale à partir du 4 mars prochain. « Si cette loi était votée, il ne faudra pas changer vos comportements quotidiens par peur d’être déconnecté, sinon ils auraient gagné, a exhorté l’apôtre du logiciel libre dans un français très correct. C’est une loi injuste et cruelle…Richard Stallman déplore que les gouvernements, agissant contre l’intérêt des citoyens, ne cessent d’étendre le droit d’auteur à la fois dans la durée et dans l’utilisation de l’oeuvre avec le pay per view (paiement à l’acte, sans téléchargement définitif). Autre appel à la résistance : « Il ne faut pas acheter des produits qui ont des verrous numériques comme les DVD, sauf si tu as le programme pour les casser. ». Richard Stallman avance plusieurs pistes pour concilier partage et respect des auteurs et artistes. « Je propose un droit d’auteur d’une durée de 10 ans à partir de la publication. Pour les oeuvres d’opinion, d’art et de divertissement, je propose la liberté de diffuser les oeuvres exactes non commercialement. » En effet, la liberté de modifier une autobiographie ou un roman lui semble saugrenue.Pour financer les artistes, Richard Stallman suggère un impôt sur les oeuvres vendues et le paiement volontaire. « Si tu avais un bouton pour envoyer un euro très facilement à l’artiste, tu le ferais. »Et de citer l’exemple de la chanteuse canadienne Jane Siberry qui reçoit en moyenne plus d’un dollar par morceau téléchargé. « C’est plus que les 99 cents demandés par les maisons de disques », conclut Richard Stallman. Preuve qu’il faut arrêter de traiter les internautes comme des voleurs.’)

• http://standblog.org/blog/post/2009/03/10/Le-Post-et-Hadopi
  
• http://standblog.org/blog/post/2009/02/26/Hadopi-%3A-Blackout-du-Net-fran%C3%A7ais
  

• http://www.laquadrature.net/files/LaQuadratureduNet-20090207_Riposte-Graduee_inefficace-inapplicable-dangereuse_2pages.pdf
• http://www.laquadrature.net/files/LaQuadratureduNet-Riposte-Graduee_reponse-inefficace-inapplicable-dangereuse-a-un-faux-probleme.pdf

• http://www.korben.info/richard-stallman-il-ne-faut-pas-avoir-peur-dhadopi-sinon-letat-policier-a-gagne.html

• http://www.ddmdllt.org/weblog/posts/2009/03/07/betisier-hadopi-definition-telechargement/ (’…Il convient de rappeler qu’il ne faut pas confondre téléchargement et téléchargement illicite (erreur critique facile à commettre sous l’effet de la propagande). Il convient aussi de rappeler qu’au sens strict il y a forcément téléchargement pour consulter la moindre page sur internet...’)

• http://bluetouff.com/2009/03/09/hadopi-albanel-gus-garage/ (’…Nous partîmes 5 gus, et par un prompt renfort , nous nous vîmes des dizaines des milliers en arrivant au garage… C’est surprenant Internet des fois. Pour rappel, le projet de loi Création et Internet introduit beaucoup de “fausses nouveautés” peu souhaitables dans notre démocratie : filtrage des réseaux, abandon du principe de la neutralité du transporteur, inversion de la charge de la preuve, sanction sans l’accès à un procès équitable, double peine .’)

• http://www.framablog.org/index.php/post/2009/03/08/nous-sommes-tous-des-gus-dans-un-garage (’…« Nous sommes tous des juifs allemands » est l’une des citations célèbres de mai 68, proclamée par la jeunesse en signe de solidarité à Daniel Cohn-Bendit, alors interdit de séjour en France. Ce soir, la Quadrature du Net peut compter sur « un gus de plus dans son garage », suite à la rocambolesque affaire de la dépêche AFP modifiée que nous relate le site PC INpact…’)

• http://www.mumblyworld.info/?p=257 (’Je tiens à vous rappeler par ailleurs qu’à ce jour, aucune étude scientifique n’a réussi à prouver que le partage de fichiers protégés par le droit d’auteur, ait le moindre impact sur la vente de disques ou de DVD. Bien au contraire, de nombreuses études tendent à prouver l’inverse. Quant à la rémunération des auteurs, d’autres études montrent, quant à elles, la corrélation entre le partage de fichiers et l’explosion récente des arts vivants, offrant une rémunération à un nombre bien plus large d’artistes que n’en offraient jadis les ventes de disques.‘)

• http://www.site-sans-nom.org/rc2/vrac/rsl_2009-03-02_rejetHADOPI.html (’…Il est interessant de constater que des études récentes menées en Bretagne, au Canada et aux Pays bas démontrent que le téléchargement illégal d´oeuvres protégées par le droit d´auteur a un impact nul voire positif sur la vente légale des oeuvres. Etrangement, ces études ont été passées sous silence par le ministère de la culture et les ayant-droit français….Lors qu´une atteinte aux droits d´auteurs sera signalée par les ayant-droit, l´HADOPI pourra envoyer deux messages d´avertissement (sans obligation de présenter le moindre accusé de réception) à l´internaute visé avant de procéder à la suspension voire à la résiliation pure et simple de son accès Internet. Le parlement européen s´est clairement opposé à ces pratiques dangereuses en avril 2008 en votant une résolution qui invite la Commission et les Etats membres à éviter de prendre des mesures qui entrent en contradiction avec les libertés civiques et les droits de l´homme et avec les principes de proportionnalité, d´efficacité et de dissuasion, telles que l´interruption de l´accès à l´Internet. Cette mise en garde ne semble pas avoir calmé les ardeurs du gouvernement français, lequel a fait pression sur le Conseil européen jusqu´au retrait de l´amendement 138 au Paquet Télécoms, pourtant voté par une large majorité des députés européens et soutenu par la commission européenne.…Cette volonté de limiter Internet à un sous-ensemble de sites conformes à la vision gouvernementale de la bienséance relative aux échanges électroniques se retrouve d´ailleurs explicitement dans la proposition de loi «Internet et Création». En effet, un document du Conseil Général des Technologies de l´Information prévoit d´une part de mettre en place une instance ayant autorité à définir et garder actif des portails blancs où se retrouveraient les sites utiles à la vie économique, culturelle et sociale du pays et d´autre part de restreindre à ces portails les accès Wi-Fi à l´Internet que proposent à titre gratuit des entités publiques (municipalités, leurs écoles, les hôpitaux ou les universités) , voire des personnes morales privées (Mac Donald, ..)).. La volonté d´atteinte à la liberté d´expression sur Internet est donc manifeste…’)

• http://www.maitre-eolas.fr/2009/03/04/1333-hadopi-mon-amie-qui-es-tu

• Loi Hadopi: l’édito-vidéo (http://www.dailymotion.com/video/x8lptt_loi-hadopi-leditovideo_news)
• http://www.ca-va-couper.fr

Quelques nouvelles d’applications python: Open Object, OpenERP 5.0, Django + Python 2.6 Quick Reference de Richard Gruet

Quelques nouvelles intéressantes concernant le développement d’applications python:

- http://thisweekindjango.com/callcasts/episode/9/callcast-discussion-corey-oordt-and-opensource/ (’ A conversation with Corey Oordt discussing the new OpenSource Washington Times project and their forthcoming collection of reusable apps, along with greater goals for becoming a platform for Django newspaper/media applications. Oordt is the Deputy Internet Director for the Washington Times. His small team of Django developers soon plans to make a greater public position in the open source community with their latest opensource.washingtontimes.com project website and their soon to be releases project repository including django-suppertagging (Open Calais integration), django-massmedia, solango, a Django powered trac-like management application, django-clickpass, along with further aspirations for hosting Django sprints, projects, and ideally growing into a platform for hosting Django powered news applications. ‘)

- http://thedjangoforum.com/board/ (’A forum for anyone interested in Django or Python development. Find help for your Django related questions or share your knowledge with developers that are just getting started. Please come take a look’)

- http://rgruet.free.fr/#QuickRef (The Python 2.6 Quick Reference is available in HTML and PDF formats. This time I was helped by Josh Stone for the update. As usual, your feedback is welcome (pqr at rgruet.net. Source: http://groups.google.com/group/comp.lang.python.announce/browse_thread/thread/70f000802201af4a/ea354c557bf13bb0?show_docid=ea354c557bf13bb0&pli=1).

-http://groups.google.com/group/comp.lang.python.announce/browse_thread/thread/529f43330e4c5ac5 (’OpenERP 5.0 is out ! Why do I talk about OpenERP on this mailing list ? Because OpenERP is fully developed with Python. That major enhancement of Open ERP can now answer to all the needs of a business. Open ERP V5 not only provides management functions, but also all functionalities necessary to a SMB, like : a process management by modules, a wiki, a webmail, a Business Intelligence (Cube OLAP),  a Document Management System, an eCommerce, an idea box, etc.This new version comes with a full review of the web site giving access to more then 1500 pages of documentations on business management and a reorganization of the community sources build upon the Open Object framework. Free cycles of conferences are planned with the version 5.0 release of Open ERP.
Thanks to its huge community, Open Object produce more then 20 modules a month. The Open Object community it is more then 1000 contributors, 126 development branches in parallel, an average of 400 new functionalities or bugfix per month, one commit every 5 minutes and functional and technical  experts specialized by activity and working in teams.
The rise of Open Object and the diversity of the projects makes it an unmatched framework composed of more then 400 modules installable in a few clicks to cover all kinds of need or to simply start, with a simple module, to answer a simple need. Then, you can install other functionalities to come to a fully integrated and automatized system.
Open ERP v5 is characterized by the appearance of many functionalities far beyond the perimeter of traditional management. One can underline the following innovations:

* An integrated wiki.
* An integrated document management system.
* A Business Intelligence (BI) using a OLAP (Online analytical processing) database.
* An integrated BPM (management of process).
* A web portal for clients and suppliers.
* Improvement of translations (1 translation file by language and module).
* A touchscreen point of sale.
* A full Ajax webmail .
* A shared calendar.
* Plugins for Outlook, OpenOffice, ms. Office, Thunderbird.
* An integrated eCommerce, etc

This new release offers 3 user interfaces :
* the rich application client for a day to day advanced use,
* the web interface allowing a remote access and an easy deployment,
* the QT client that perfectly fits in a KDE environment.

….
The web version of Open ERP includes numerous functions to  modify or create your own application :
* an visual view editor,
* an object editor,
* a workflow (process) editor,
* an Open Office integrated report editor
* a statistics engine (BI cube),
* etc…
URL: http://www.openerp.com
URL: http://www.openobject.com
DOC: http://doc.openerp.com
Screencast: http://www.openerp.tv
LaunchPad Project: http://launchpad.net/openobject‘).

- http://freshmeat.net/projects/openerp/?branch_id=77761&release_id=293852 (’Open ERP is a complete ERP and CRM. The main features are accounting (analytic and financial), production management (MRP), stock management, sales and purchases management, task automation, marketing campaigns, help desk, POS, and more. Technical features include a distributed server, flexible workflows, an object database, a dynamic GUI, an XML-RPC interface, and customizable reports. ‘)

- https://launchpad.net/openobject (’OpenObject is a professional Rapid Application Development framework in Python that allows you to build your applications within a few minutes. This is the main project of all related projects around OpenObject: OpenERP (a complete enterprise management software), OpenObject Server, OpenObject Web Client (the web version of OpenObject applications), OpenObject Application Client, BI (a complete business intelligence application based on openobject), OpenObject Addons (about 300 modules available for OpenObject’s applications), .

• OpenERP (’This project contains all packaging scripts to allow you to download and customize openerp instances and create packages which are a selection of modules and projects. These scripts will download all different bazaar projects and link them to create an full openerp system.’)
  
  • Screenshots
  • External downloads
• OpenObject Addons
• OpenObject Business Intelligence (’OpenObject’s Business Intelligence allows you to build a full featured and flexible reporting environment in a few minutes. It plugs efficiently on OpenObject’s applications but also on most populare databases. You don’t need to waste time building complexe and inflexible shemas: due to his user friendly cube designer, it allows you to build or customize your cube on any application in a few minutes. The datawarehouse structure is then computed and feeded automatically based on an analysis of the queries made by the end-users. OpenObject is the first tool ever made that allows small companies to set up a complete Business Intelligence solution within a few hours. The following animations present you how to we built a complete schema on a new database in a few minutes.’)
  • Screenshots
• https://launchpad.net/openobject-client OpenObject Application Client (’OpenObject is an open source framework based on Python that lets you build your entreprise applications extremely fastly and easily. It includes an ORM, a Workflow engine, several report designers, a MDX engine, a dashboard designer, a module system, an automated migration engine, and much more… Get a web (Ajax) and a rich application with the same code and launch your SaaS offer within minutes thanks to our portal, our webservices interfaces and our 300+ available modules.’)
• https://launchpad.net/openobject-client-kde KDE OpenObject Client (’Cross-platform OpenObject Client based on Qt and KDE libraries.’)
  • Sourceforge project
  • Freshmeat record
• https://launchpad.net/openobject-client-web (OpenObject Web Client:  The Web client of OpenObject offers a high quality and ergonomy client for OpenObject and OpenERP. It is known to work with all major web browsers available today, including Firefox, IE6, IE7, Safari3 and Opera9. It uses extensively Ajax for a maximum of ergonomy and a minimum of communictation. It includes a calendar view, a workflow designer, a view editor, an object designer, eso.)
• https://launchpad.net/openobject-doc (Open Object Documentations : This is the project to manage .rst documentations on Open ERP and Open Object. Most documentations must be written in .rst, and we generate the final output using Sphinx.)
• https://launchpad.net/openobject-server (’OpenObject Server: ‘)

DaboDev: un framework python pour développer des applications 3-tiers portables sur GNU/Linux, Windows ou OSX

“Dabo is the easy to use, cross-platform, 3-tier, open source desktop database development framework.”

- http://dabodev.com/ (’ Desktop applications. That’s what Dabo does. It’s not YAWF (yet another web framework). There are plenty of excellent web frameworks out there, so if that’s what you are looking for, Dabo isn’t for you. But there are almost no desktop application frameworks out there, and if you want to create applications that run on Windows, OS X or Linux, Dabo is for you!

• Background
• 3-Tier Design
  • Database
  • Business Objects
  • User Interface
• Multi-Platform
• Community
• Screenshots
• License

Dabo is a 3-tier, cross-platform application development framework, written in Python atop the wxPython GUI toolkit. And while Dabo is designed to create database-centric apps, that is not a requirement. Lots of people are using Dabo for the GUI tools to create apps that have no need to connect to a database at all.’)

Installation

• http://dabodev.com/download (”Download and decompress the file. It will create a folder named ‘dabo‘, which will contain 4 main things: the dabo module itself (in a subdirectory also named ‘dabo’), along with folders containing the visual tools (’ide’), the DaboDemo program (’demo’), and the code for running Dabo apps across the web (’daboserver’). First, we need to install the module. To do this, change to the main directory created when you decompressed the downloaded file, and issue:

  python setup.py install

  Of course, if your Python installation is in a protected location, you will need to run the above command as a user with admin rights.

  If you have trouble with setuptools, or you don’t want to install the Python Egg for any reason, you can instead extract Dabo anywhere you like, and then put a dabo.pth file in your Python site-packages directory pointing to the directory that contains the Dabo Readme file. This method has the advantage that you can keep the Dabo module in an unprivileged location, where you can keep it updated using the Web Update feature.

  After installing the module, you should then copy the ‘ide‘ and ‘demo‘ directories to whatever location you prefer, as these are applications written in Dabo, and do not need to be installed. If you plan on creating Dabo web applications, you need to create a Pylons app named ‘daboserver’ and replace its ‘daboserver’ subdirectory with the ‘daboserver’ directory you downloaded‘)

Quelques articles sur des frameworks Web Python : Django, Pylons, Web2py, Repoze.bfg, Pyxer

Sources:

• http://plope.com/whats_your_web_framework_doing (’It can be a bit useless to benchmark web application frameworks. When you’re commmitted to a particular framework, either it works or it doesn’t for your particular application; often raw speed is not really a concern. You’re probably not going to switch web frameworks in the middle of a project in order to get a 15% or even a 50% or 100% speed increase: you’ve got too much investment in the code that works under the framework to consider it. In my experience, very few people truly understand more than one web framework, and they tend to use that framework for everything even it it’s slightly less optimal for any specific task; this is because the “switching cost” to go to another one is so high. So benchmarks aren’t really all that interesting in the “real” web world; it all depends on context. But if you haven’t chosen a web framework yet (is there anyone?), or if you’re falling out of love with your current web framework and you’re considering using a different one, you might be able to learn something from profiling an application running under various frameworks nonetheless, even if you ignore the raw speed of the framework itself’Here are the results:
  • • repoze.bfg emitted 50 lines of profiler output ( (”Big Fine Gun”)
      
    • Django emitted 105 lines of profiler output
    • Pylons emitted 163 lines of profiler output
    • Grok emitted 834 lines of profiler output

• - http://compoundthinking.com/blog/index.php/2009/02/04/wsgi-and-cooperation/ (’…The point of all this is that the wider python web world is seeing a huge increase in cross-polination of ideas, of working together on projects, and sharing code across major frameworks from TurboGears to Zope, to Pylons. And at the core of all this is the WSGI specification. WSGI may not be pefect, but it’s still great, because it provides a defined way for web framework developers to work together. And, that coupled with the fact that we’re all pretty friendly people, and we all like each other and want to work together on things, has created a renasance of sorts in python web tools world…’)

• http://code.google.com/p/pyxer/ (’Yet another Python Framework! The goal of this project to make web development as easy as possible to enable the developer to start quickly with a new project. This project should be distributable via PasteDeploy for normal servers and for Google App Engine (GAE), without the need of using different technologies and approaches. The Pyxer Server is a very simple Python Web Framework that aims to makes starting a new project as easy as it can be. It still works respecting the MVC concept but the files can be mixed in one directory. For a high end solution you should maybe consider using Pylons, Django, TurboGears and similar. This work is inspired by http://pythonpaste.org/webob/do-it-yourself.html.  Technical background. The Google App Engine (GAE) in version 1.1 offers a very restricted Python environment and the developer as to ship arround a lot of limitations. Pyxer helps on this point by providing solutions that also work together with the WSGI Framework Paste by Ian Bicking. This way you get the best from both sides: GAE and Paste. To achieve this, some other common third party tools are used like WebOb and VirtualEnv also by Ian Bicking. The templating s based on Genshi. .‘)
• http://groups.google.com/group/comp.lang.python.announce/browse_thread/thread/09cfe8decd549127/1382cac331ce7805?show_docid=1382cac331ce7805 (’web2py 1.56 is out, including a new web site with better documentation http://www.web2py.com.
  • New features Include:
    =================
    - Authentication
    - Authorization (Role Based Access Controller)
    - CRUD
    - portable url fetch function
    - portable geocoding function
    - PEP8 compliant
    - Python 2.5 and Python 2.6 compliant
    - Runs on Jython (although without db drivers)
    - Runs on IronPython (although without CSV, db drivers and internal
    web-server)
    - DAL shortcuts
    - SQLFORM has default image preview
    - new generic.html view
    - more examples and documentation
    - always backward compatible ‘)
• http://kiznet.fr/blog/2008/11/21/django–python-cest-plus-fort-que-toi/ (’Aujourd”hui, je vais vous présenter Django, “Le framework web pour les perfectionnistes sous pression” ! Avouez que c”est déjà pas mal comme slogan. Je vais parler ici de mon expérience personnelle d’amateur qui pratique l”informatique sur son temps libre. Donc tout ce que je peux raconter ici peut apparaître totalement FAUX à un expert en la matière, mais bon, faut bien se lancer un jour hein …J’ai ensuite installé Django en lui même (ce qui se résume à télécharger la version en cours de développement puis créer 2-3 liens symboliques, du gâteau quoi), puis paramétrer mon httpd.conf (de même, processus très simple grâce à la très bonne documentation très bien traduite par David Larlet. Résultat, en partant de rien, un framework fonctionnel disponible en production en tout juste 5 petites minutes…Bienvenue dans le monde merveilleux de Django! Pour tes accents, vérifie que tu as bien créé ta base MySQL avec le bon encodage. Il y a en fait deux encodages qui interviennent: celui de la base et celui de la connexion client. Tu peux mettre les deux en UTF-8. L’encodage de la base détermine comment ton texte est stocké physiquement sur le disque; si tu mets un encodage non-universel, alors certains caractères ne pourront être stockés. L’encodage de la connexion client détermine comment ton texte est transféré physiquement entre le serveur SQL et ton applicatif. Là aussi, il est important que l’encodage choisi soit capable de gérer les caractères de ton texte, mais il est également très important que l’applicatif et le serveur SQL soient d’accord sur cet encodage (c’est une erreur que je vois trop souvent sur des sites PHP). Normalement Django pose tout seul les bons encodages sur la connexion client, donc de ce point de vue là ce n’est probablement pas un souci pour toi. Mais fais gaffe à l’encodage de la base. ‘)
• http://www.screeley.com/entries/2008/aug/21/enterprise-django/ (’…If there’s one thing I love about Alfresco it would be webscripts. They make it easy to retrieve, create and modify content from a repository RESTfully. Webscripts are also very technology agnostic, you can put just about anything on top. We looked at Symphony, Ruby on Rails and Django, but because I have a hammer and everything looks like a nail, we went with Django. This might have been short sighted. The developer working on this django-jython project only got Django running on Jython in TomCat 4 days ago. It also doesn’t help that the client asked if we misspelled banjo in our presentation. Needless to say there will be a few challenges going forward. Tech Stuff: If you have an existing Django project it takes less than an hour to make the conversion. Before you get started you will need three things: Java 6, Tomcat(I am using 5.5) and the Postgres JDBC. The initial install directions are here and to create the WAR the docs are here. The only issue I ran into was a Java class version issue, which is why you need Java 6. ‘)

A voir:

• http://wiki.python.org/moin/WebFrameworks
• http://mdp.cti.depaul.edu/ (’web2py^TM Enterprise Web Framework.Free and open source full-stack enterprise framework for agile development of fast, secure and portable database-driven web-based applications. Written and programmable in Python.Version 1.56.1 (2009-02-05 11:49:10) Created by Massimo Di Pierro. © 2007-2009. ‘)
• http://en.wikipedia.org/wiki/Django_(web_framework)
• http://www.django-fr.org/liens/ (’La documentation officielle est complète mais ne suffit parfois pas à certaines spécificités, les liens présents sur cette page sont là pour combler ce manque. ‘)
• http://plope.com/Members/chrism/repoze-bfg (’…So, for the last few weeks (at the expense of much else), with a lot of help from Paul Everitt and Tres Seaver, I’ve been working on a new web framework. This framework is named (provisionally) repoze.bfg (”Big Fine Gun“). It uses the Zope CA, and Zope interfaces, and a bunch of other Zope libraries, but doesn’t use the Z2 or Z3 publishers; it has its own publisher. It also does not use any form of Zope security; it implements its own security model. It has the same concept of views that Zope and Django have. Its development model is closer to Pylons’ or Django’s than it is to Zope’s. It uses the z3c.pt templating system, which is a reimplementation of ZPT, or you can also use XSL, or plug in whatever templating system you like really. It doesn’t assume any particular persistence mechanism; you provide your own (ZODB, relational, filesystem, etc); in a tip of the hat to Pylons, that’s considered an application decision. It depends heavily on a variety of Ian Bicking creations, including WebOb and Paste. It’s very small, currently clocking in at a little over 2000 lines of code, minus dependencies. That said, it does about what I want out of a web framework. It’s still in a pretty early stage, but it has definitely moved its way out of “toy” phase. We’ve managed to create several applications using the framework so far. The very first one was repoze.virginia , which is the application which serves up Repoze.org these days. It’s a simple file hierarchy publisher with slight dynamicism. The second one Paul wrote, and it’s named repoze.lxmlgraph , where he demonstrates how one might publish a website that was represented entirely by a single XML document. The third one is named repoze.cluegun , which is a port of Rocky Burt’s ClueBin application to repoze.bfg. That code runs the ClueGun website . Of the three, ClueGun is probably the most real-world app (albeit small). I’m sort of excited about it. It’s sort of like getting out of jail or something to be able to have your own web framework to write as you see fit. We’ll likely continue to develop applications using repoze.bfg, pushing features into the framework as we find them useful.’)
• http://en.wikipedia.org/wiki/Pylons_(web_framework)
• http://static.repoze.org/bfgdocs/ (’repoze.bfg is a Python web application framework. It is inspired by Zope, and uses Zope libraries to do much of its work. However, it is simpler than any released version of Zope. repoze.bfg uses the WSGI protocol to handle request and responses.’)
  • http://static.repoze.org/bfgdocs/narr/introduction.html#similarities-to-other-frameworks (’The repoze.bfg concept of traversal is inspired by Zope. Additionally, repoze.bfg uses the Zope Component Architecture (“CA”) internally, as do Zope 2, Zope 3, and Grok. Application repoze.bfg developers use either ZCML (an XML dialect, used in Zope) or decorators to perform various configuration tasks. The decorator support is provided by the Grok project. Like Pylons, repoze.bfg is mostly policy-free. It makes no assertions about which database you should use, and its built-in templating facilities are only for convenience. In essence, it only supplies a mechanism to map URLs to view code, along with a convention for calling those views. You are free to use third-party components in your application that fit your needs. Also like Pylons, repoze.bfg is heavily dependent on WSGI.The “Django docs state that Django is an “MTV” framework in their FAQ. This also happens to be true for repoze.bfg:‘)
  • http://static.repoze.org/bfgdocs/narr/introduction.html#differences-from-other-frameworks (’ Like Zope, the repoze.bfg framework imposes slightly more control inversion upon application developers than other Python frameworks such as Pylons. For example repoze.bfg assumes that you’re wiling to resolve a URL to a context object before passing it to a view. Pylons and other Python “MVC” frameworks have no such intermediate step; they resolve a URL directly to a controller. Another example: using the repoze.bfg security subsystem assumes that you’re willing to attach an ACL to a context object; the ACL is checked by the framework itself instead of by user code, and access is permitted or denied by the framework itself rather than by user code. Such a task would typically be performed by user-space decorators in other Python web frameworks. Unlike application development using Zope, application developers don’t interact with the Zope Component Architecture (“CA”) very much during repoze.bfg application development. Instead, the repoze.bfg framework tends to “hide” most interaction with the CA behind special-purpose API functions. Also unlike Zope and unlike other “full-featured” frameworks such as Django, repoze.bfg makes no assumptions about what persistence mechanisms you want to use to build an application. Zope applications are typically reliant on ZODB; repoze.bfg allows you to build ZODB applications, but it has no reliance on the ZODB package. Likewise, Django tends to make the assumption that you’re going to want to store your application’s data in a relational database. repoze.bfg makes no such assumption; it allows you to use a relational database but doesn’t enourage or discourage an application developer about such a decision.’)
• http://en.wikipedia.org/wiki/Grok_(web_framework) (’ Grok is a web framework based on Zope 3 technology. The project was started in 2006 by a number of Zope 3 developers.Grok has since then seen regular releases. Its core technologies (Martian, grokcore.component) are also finding uptake in other Zope 3 and Zope 2 based projects. The primary motive behind Grok is to make the powerful, but not quite easily approachable Zope 3 technology more accessible and easier to use for newcomers and, at the same time, speed up application development, in accordance with the agile programming paradigm.To achieve this, Grok gives up some Zope 3 principles. Instead of using a strictly explicit, XML based configuration language (ZCML) like Zope 3 does, Grok uses Python code for component configuration, and has many implicit defaults and conventions so that you don’t have to have so much configuration, in the hope that it is easier to learn than standard Zope 3. Grok aims to be more similar in feel to popular Python web frameworks like TurboGears, Pylons and Django, while at the same time it retains much of Zope 3’s codebase and its component approach to development. ‘)