FAQ

Why is Tryton written in Python?

Python runs on many operating systems and can be learned in a few days.

Its design philosophy emphasizes programmer productivity and code readability.

Why choosing Postgresql as DBMS?

PostgreSQL is a powerful, open source relational database system:

Why using Mercurial?

Mercurial is a distributed source management tool. It will allow anybody to easily modify, publish and provide patches to Tryton.

Why modularity is so important?

Lack of modularity is a long time criticism towards most of management softwares. Because there is as much organizational architectures as kind of activities, modularity is crucial to reach the best balance between functional coverage, simplicity of use and advanced customization.

Why starting from Tiny ERP?

Tiny ERP (now know as Open ERP from Tiny) has a good technological base, which provides the complete stack needed for an ERP: ORM layer, network services, client application, etc. Moreover, the platform provides ease of development and a great modularity.

So, why forking?

The goal behind Tryton is not to create a direct competitor but to provide a new way to tackle the problem of programming a business software. The idea is to favor a solid and consistent solution over more cutting edge features.

Practically this means that today (20 October 2008), compared to the version of Tiny ERP (4.2) that was the base of the fork:

Moreover, all the modules available in Tryton have been completely rewritten, which represent nearly 20000 lines of code. All this work was necessary from our point of view because most of the fundamental modules in Tiny ERP where written when some of the most advanced technical features were still missing. The result is a better harmonization between base modules, an optimized modularity and amore powerful platform for custom developments.

Here is list of improvements made on Tryton compared to OpenERP.