API for accessing the on-disk representation of a given addon
Registered by
Xavier (Open ERP)
API to interact with the "physical" representation of an OpenERP addon (its on-disk form and state, not its existence in the OpenERP database, though the API defined thereafter could be extended for such a task later on).
Blueprint information
- Status:
- Started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- xrg
- Direction:
- Needs approval
- Assignee:
- xrg
- Definition:
- Discussion
- Series goal:
- Accepted for trunk
- Implementation:
-
Started
- Milestone target:
- None
- Started by
- Xavier (Open ERP)
- Completed by
Related branches
Related bugs
| Bug #507973: [trunk] [rev 1975] startup option --addons-path can't handle more than one addons path | Fix Released |
Sprints
Whiteboard
xrg: Well written.
2011-06: There has been a little movement in this direction. After the initial "API docs" experiments, we've thought about documenting the ORM classes off-line. That is, be able to extract the structure (such as model inheritance, columns, views, features) of addons without loading them in a database. However, this would require an "ORM emulation" layer in order to introspect those python files. So, we're pending some decisions whether to allocate work for that, or not.
(?)
