openerp-india team mailing list archive

["Olivier Dony \(OpenERP\)" <1004539@xxxxxxxxxxxxxxxxxx>]

Hi Xavier,

Unfortunately it is impossible to avoid conflicts with all the current (and future) modules of the Python ecosystem in the "root" namespace. Renaming our modules just to avoid one such conflict (even with an official module) will only fix one case, it will cause a lot of backwards-incompatible and otherwise useless changes, *and* will not prevent future conflicts.
For example our "web" module contains the new OpenERP web client/framework, and it is in direct conflict with a popular Python web framework module: "web.py". This is as annoying as a conflict with Python's 'resource' package.
We prefer to find a global solution that will completely prevent this: a proper openerp namespace.

For the moment if you encounter such a conflict you will have to find a
workaround such as pre-loading your module before OpenERP's resource
module is loaded (via the --load server parameter), or altering yourself
the sys.path when you need it.

For the future we will implement a clean solution: we'll move all the
openerp modules under a clean namespace: "openerp.addons". So our
"resource" module will exclusively be available under
"openerp.addons.resource". This is a big change that has to be foreseen
over several releases because we'll have to eventually break backwards-
compatibility, so it will probably be done after release 7.0.

Thanks

** Changed in: openobject-addons
   Importance: Undecided => Wishlist

** Changed in: openobject-addons
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Addons.
https://bugs.launchpad.net/bugs/1004539

Title:
  resource addons/module

Status in OpenERP Addons (modules):
  Won't Fix

Bug description:
  resource is an OFFICIAL python module:
  http://docs.python.org/library/resource.html

  It would be nice to rename the openerp resource addons to something
  else to prevent this name conflict...

  "import resource" will import openerp python addons in most of the
  cases, since the addons path is added to sys.path.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/1004539/+subscriptions