openerp-india team mailing list archive

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

On 05/28/2012 03:43 PM, Raphaël Valyi - http://www.akretion.com wrote:
> Hello Olivier, while I think namespaces is the right solution, I don't
> understand that last statement. Why don't you do that change for version
> 7.0 ? Version 7.0 is a new major version as there is only every 12 or 18
> months at best. Isn't that the right timing to do those backward
> incompatible changes?

LTS != Major. Currently there's a major version planned every 6 months, so the
one after 7.0 will be 7.1, etc. This refactoring of module namespace is a
project of its own, and if it's ready and stable in time for 7.0 it will be in
it. Otherwise it will be in the next one, as it's not a release blocker.
That's what I meant by "probably after 7.0".

-- 
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