c2c-oerpscenario team mailing list archive
-
c2c-oerpscenario team
-
Mailing list archive
-
Message #15814
[Bug 520006] Re: Incorrect organisation of the code
The OpenERP server has been recently reorganized in trunk to be a normal
python module, similarly to what has been discussed here. As a result,
it is now possible to "import openerp".
You can upgrade to the latest trunk version to test it (after revision
3354). You can also see this thread for more info:
https://lists.launchpad.net/openerp-expert-framework/threads.html#00503
** Changed in: openobject-server/trunk
Status: Confirmed => Fix Released
** Changed in: openobject-server/trunk
Milestone: None => 6.1
--
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/520006
Title:
Incorrect organisation of the code
Status in OpenERP Server:
Fix Released
Status in OpenERP Server trunk series:
Fix Released
Bug description:
I was trying to create a zc.buildout style project of deployement of
OpenERP. I created a customer python egg project which will act as a
kind of patch to customized our OpenERP installation.
By doing that I discovered that all the code of OpenObject lib is
located in the bin/ dir and cannot be used as an external library.
It's a very stange organisation of the code.
By example, of you take a look at the openobject-client-web project,
there's is a directory at the top named "openobject" containing all
the code. I can refer to this namespace in other project. But for the
server it's very impossible do doing that.
Maybe converting OpenObject as good python citizen would be a
important. no ? And if not, how can I import a module of OpenObject in
a project ?
I proposed the following architecture:
openobject.server/
setup.py
...
openobject/
__init__.py
server/
addons/
ir/
osv/
pychart/
report/
service/
ssl/
tools/
wizard/
workflow/
...