"…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 février 2008

Quelques nouvelles de Mono: passage de la version 1.2.6 à la version 1.9.0 Preview, Gendarme, MoMA

Posted by patrick sur février 13, 2008

– Source: http://lists.ximian.com/mailman/listinfo/mono-devel-list (« I can tell you that we jumped from 1.2.6 to 1.9 in preparation for our next release which will be Mono 2.0. See the road map for more details of what that entails ( http://mono-project.com/Roadmap#Mono_2.0 « ).

http://lists.ximian.com/mailman/listinfo/mono-devel-list (« de miguel@ximian.com : « Hey folks, Am assembling the release notes for Mono 1.9, please send me additions, edits, etc:http://www.go-mono.com/archive/1.9« )

http://mono-project.com/Gendarme(« Gendarme is an extensible rule-based tool to find problems in .NET applications and libraries. Gendarme inspects programs and libraries that contain code in ECMA CIL format (Mono and .NET) and looks for common problems with the code, problems that compiler do not typically check or have not historically checked.The current Gendarme framework, Gendarme.Framework.dll, is a work in progress. It will probably change a lot before 1.0 is released. It’s main goal is to make it easier to write and test rules. The current Gendarme framework, Gendarme.Framework.dll, is a work in progress. It’s main goal is to make it easier to write and test rules. It requires a C# 3 compliant compiler to compile properly (it works with Mono from SVN and with VS.NET 2008). At this stage we’re not committed to a final API, so things may still change a lot before version 1.0 is released…You can follow the Gendarme’s development discussions on it’s Google Group . This is also where you’ll find the roadmap  to the future versions, (wish)list of todo, rules  proposal and developer documentation. Gendarme’s developers are also IRC (#gendarme on GIMPnet). Source code is available from SVN  (tarball . Since Mono 1.9.0 Gendarme is part of mono-tools and is probably available for your distro (if recent) or from openSUSE Build Service . »)

http://mono-project.com/Moma (« The Mono Migration Analyzer (MoMA) tool helps you identify issues you may have when porting your .Net application to Mono. It helps pinpoint platform specific calls (P/Invoke) and areas that are not yet supported by the Mono project. »)

http://tirania.org/blog/archive/2008/Feb-03.html (« Shawn at CogmationMono is being used as the scripting engine for their robotFoundry application… has written us to notify us that We discovered Mono while we were evaluating 3D engines. Mono was successfully being used to develop video games and it was extremely fast. We performed a small test and compared the speed between Python and C# mono and were shocked at how fast mono was compared to python. In addition to the speed increase and portability, we now had the ability to allow our users to write scripts in any .Net language... »)


Posted in DotNet, mono | Tagué: , , , | Leave a Comment »

Quelques nouvelles de python: cobra, fusil, django

Posted by patrick sur février 12, 2008

http://www.blueskyonmars.com/2008/02/08/cobra-programming-language/ ( » So, we’ve got Jython and IronPython as Python language reimplementations. There’s also Boo, which is clearly heavily inspired by Python but has some interesting extensions (static typing, for example). I just came across Cobra (http://cobra-language.com/). Cobra, like Boo, is built on the .NET platform. The syntax is clearly inspired by Python, which I consider a good thing. In keeping line noise to a minimum, Cobra even ditches the “:” at the end of the line preceding a block of code. Chuck Esterbrook has also pulled inspiration from a number of other places. I recognize some D and Eiffel in there (it’s got design by contract and unit tests built right into the classes). There’s a comparison to Python available right on the Cobra site. »)

http://www.haypocalc.com/blog/index.php/2008/01/04/112-fusil-version-07 (« L’idée de Fusil est de simplifier l’écriture d’un projet de fuzzing. Il suffit de décrire le scénario pour préparer et surveiller l’environnement, sans avoir à s’occuper des détails techniques (rediriger la sortie du processus, détecter un plantage, etc)« )

http://www.voidspace.org.uk/python/weblog/arch_d7_2008_01_26.shtml#e930 (« This is an early announcement of a new project: Python-System, an implementation of the BCL and other .NET libraries in pure Python. Before you decide I’m completely mad, let me explain my motivation. Smile

The goal here is to provide libraries (the BCL and other .NET libraries) to aid the porting of IronPython code to run on CPython. Specifically, I would like to get Resolver One spreadsheets, exported as code, to run under CPython. I’m opening it up because it may also be useful to other people, and maybe you’ll help me. Laughing

I will be starting with partial implementations of Array, DateTime, Color, Point and friends (the ‘low hanging fruit’). The goal is for ‘compatible but not necessarily complete’ implementations of the classes (etc) that I need. Code that is useful for other people will happily be added of course.« )

http://blog.michaeltrier.com/2008/2/11/this-week-in-django-10-2008-02-10 (« This week we talk about a few source commits, a discussion about unicode usernames, Some cool projects from the community, the Tip of the Week, and a couple of questions from the IRC. »)

http://www.djangoproject.com/weblog/2007/dec/16/book/ («  The Django Book started shipping last week, and we’ve put the full text online for free. We put a draft of the book up about a year ago for comments, and were amazed by the quality (and quantity!) of responses. We read each of the comments (around 2500) as we revised the book towards a final print release. That print release has been available in stores for about a week, and we’ve put the text up for you to read for free. »)

http://www.holovaty.com/blog/archive/2007/12/12/1311 (« …Now that the Django Book is finally in the can, I’m mulling the idea of writing another book — this time, a book about online journalism. In the past two years, I’ve been to (way too) many journalism-related events and conferences trying to spread the good word about « journalism via computer programming, » and I’ve detected a strong, I daresay furious, demand, from journalists at all levels in the org chart, for information about this new form of journalism. Higher-ups want to know why they should employ programmers; middle managers want to know how to find them and how to treat them; and working journalists want to learn these skills and strategies. The problem is that I can’t point them anywhere for in-depth information. This book would attempt to solve that. I want to take a shot at writing a manual, a manifesto, a practical guidebook to this emerging discipline of database-driven Web journalism. It would be a combination of high-level strategy and low-level technique, probably split cleanly into two parts (one for the suits, one for the non-suits). »)

http://www.biologeek.com/journal/index.php/astuces-et-bonnes-pratiques-django (« Développant avec Django depuis maintenant près de deux ans (ça rajeunit pas tout ça…), je suis encore surpris de découvrir de nouvelles possibilités de temps en temps. Dans mon combat pour les bonnes pratiques, je pense qu’il y a quelques bases à avoir pour se lancer dans un projet d’envergure avec Django. Je vais essayer de lister les miennes, n’hésitez pas à ajouter les vôtres pour que ça devienne une ressource collaborative…)

Posted in DotNet, Ironpython, python, tests | Tagué: , , | Leave a Comment »

Django on the Java Virtual Machine : django on jython 2.5

Posted by patrick sur février 4, 2008

Source: http://www.infoq.com/news/2008/01/django_on_jython

Alors que jython semblait un peu marqué le pas depuis quelques années, on apprend que le développement de la version 2.5 est prévue pour cette année.


The Jython developers are working hard on producing Jython 2.5 which aims to align Jython with CPython 2.5 and provide a much cleaner and consistent code base.

A side goal of Jython 2.5 is to try to get some CPython frameworks working, especially the web frameworks, for example:

  • Django
  • Pylons
  • TurboGears
  • Twisted

InfoQ recently had the opportunity to interview Jim Baker, a python evangelist and contributor to Django on Jython (DoJ), to find out what is expected and when.

What is the expected release date for Django on Jython?

This year. It’s predicated on the next release of Jython. See #2 for that planning. Django in contrast just works, with only minor changes, thanks to a lot of work that many other people did in identifying (minor) Jython incompatibilities. Now most of the problems we have identified actually occur only in testing, where Django makes certain assumptions about Python should run that don’t apply to Jython. An example of such an assumption that the hash algorithm is the same for dictionary implementations; because we use Java’s (ConcurrentHashMap), this is not the case. However, that’s an artifact of the testing process, Django doesn’t really care about that. Still, we plan to certify this by passing all the tests (fixed as necessary).

What version of Jython is going to be required?

Jython 2.5 – equivalent to CPython 2.5 (or what is conventionally called Python!) is what we are targeting in the Jython project. This is actually moving very fast. We have a 2.5 compiler that’s available for experimental usage, but it’s getting more and more robust as we have additional people testing it. This « newcompiler » was initiated by a Google Summer of Code project that I mentored. (Bruce Eckel mentioned this in a blog post. We in fact hit that mid-September date!) At the Python Conference« A New Compiler for Jython » at PyCon. in mid-March, we will be setting the specific target based on where we are. Tobias and I will also be presenting our paper  « A New Compiler for Jython » at PyCon.

Is Django trying to be what Rails is for Ruby and Grails is becoming for Groovy?

Django offers comparable functionality to those web app frameworks, with ostensibly a more robust platform. So Django is written to be multithreaded, unlike RoR, which means we don’t have to go through a lot of tricks to make it work on the Java platform, such as using multiple classloaders. We currently have database support for PostgreSQL, with some work done also on MySQL. I helped write the Oracle backend for Django. We’re also planning to support Java DB (Derby).

Jim also expressed the usefulness of having a preconfigured stack available, to ease the experimentation of using Django on Jython (DoJ),

I’d like to see the following preconfigured stack available for Django on Jython (DoJ): Derby + Tomcat. This should be something that a developer can just access via a plugin from Eclipse or Netbeans or IDE of their choice, which means they can configure Derby and Tomcat directly from the IDE. It also provides an obvious migration path to other containers and databases. Perhaps more importantly, such a setup allows for easy DoJ experimentation, whether that’s for someone building a Django app, or also using tuple spaces, rules engines, PDF tools, or other parts of the heavy-lifting infrastructure available on the Java platform. This is where I think DoJ provides true compelling value.

For additional information try the following links:

———————————–8<—————————————- A voir:





http://www.jython.org/Project/index.html (« Jython is an implementation of the high-level, dynamic, object-oriented language Python written in 100% Pure Java, and seamlessly integrated with the Java platform. It thus allows you to run Python on any Java platform. »)


Posted in java, python, Web Frameworks | Tagué: , , | Leave a Comment »