Olivier Dony cf113c2316 [FIX] base: module sequence number removed from XML data, moved to individual module manifests ... Having the sequence number living outside the module itself causes various problems at initialization when modules are missing (e.g. if creating a database with `base` only). It is also cleaner to have the module sequence in the module manifest, like other module metadata. A corresponding commit in the addons project adds the `sequence` field in the manifest of all modules who have a non-default sequence (the main apps). bzr revid: odo@openerp.com-20120107041745-tik3iu1b2qs4ym85		2012-01-07 05:17:45 +01:00
..
__init__.py	[REF] renamed modules.__init__ to modules.loading.	2011-05-11 19:48:41 +02:00
db.py	[FIX] base: module sequence number removed from XML data, moved to individual module manifests	2012-01-07 05:17:45 +01:00
graph.py	[IMP] module loading: iterate on the module graph in deterministic order (by sorting modules for each level).	2011-12-22 10:01:56 +01:00
loading.py	[IMP] indicate tests in current thread, and prevent email sending during tests	2011-12-01 16:31:56 +01:00
migration.py	[REF] module code goes into openerp.modules.module.	2011-05-11 19:24:48 +02:00
module.py	[FIX] base: module sequence number removed from XML data, moved to individual module manifests	2012-01-07 05:17:45 +01:00
registry.py	[FIX] deadlock between crons scheduling and new registry initialization creation	2011-09-30 17:00:26 +02:00