cf113c2316
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 |
||
---|---|---|
addons | ||
bin | ||
debian | ||
doc | ||
history | ||
install | ||
openerp | ||
win32 | ||
.bzrignore | ||
LICENSE | ||
LICENSE.web | ||
MANIFEST.in | ||
Makefile | ||
README | ||
README.web | ||
babel.cfg | ||
gen_translations.sh | ||
gunicorn.conf.py | ||
logging.json | ||
npybabel.py | ||
openerp-server | ||
openerp-web | ||
openerp-web.cfg | ||
setup.cfg | ||
setup.nsi | ||
setup.py | ||
setup_rpm.sh |
README
pydot - Python interface to Graphviz's Dot language Ero Carrera (c) 2004-2007 ero@dkbza.org This code is distributed under the MIT license. Requirements: ------------- pyparsing: pydot requires the pyparsing module in order to be able to load DOT files. GraphViz: is needed in order to render the graphs into any of the plethora of output formats supported. Installation: ------------- Should suffice with doing: python setup.py install Needless to say, no installation is needed just to use the module. A mere: import pydot should do it, provided that the directory containing the modules is on Python module search path.