Note that it has been quite some time since I wrote that hack. So, I may have
forgotten some details..
On Monday 18 January 2010, you wrote:
> i know it's been merged, I don't know about right, but from what I've read
> the situation with addons hitting directly in tools.config['addons_path']
> as a path is basically ignored isn't it?
I remember that no module should be using the tools.config['addons_path']
value, but instead call the find_module() or sth like that.
> > From my conf (all this time):
> > addons_path = /home/panos/build/openerp/addons/,
> > /home/panos/build/openerp/addons/etl/lib/,
> > /home/panos/build/openerp/client- kde/server-modules
> >
> > See, it takes a comma and a space (did I trim that?) .. Feel free to
> > improve.
>
> As I said, I'm floating a spec among the colleagues to solve the issue in a
> cleaner (and more extensible) way in the future, I can send you the link
> if you'd like (though I don't know if it'll end up folded in trunk in the
> end).
Yes, a single line in the config is not the best way, but was easy to code at
that time.
>
> Also, I think we should use the platform's os.pathsep to split paths.
pathsep has to do with directories notation, doesn't it? The delimiter we
could use in a string, such as the comma, colon or semicolon (like in $PATH)
is another thing to decide.
Note that it has been quite some time since I wrote that hack. So, I may have
forgotten some details..
On Monday 18 January 2010, you wrote:
> i know it's been merged, I don't know about right, but from what I've read 'addons_ path'] 'addons_ path']
> the situation with addons hitting directly in tools.config[
> as a path is basically ignored isn't it?
I remember that no module should be using the tools.config[
value, but instead call the find_module() or sth like that.
> > From my conf (all this time): build/openerp/ addons/ , build/openerp/ addons/ etl/lib/ , build/openerp/ client- kde/server-modules
> > addons_path = /home/panos/
> > /home/panos/
> > /home/panos/
> >
> > See, it takes a comma and a space (did I trim that?) .. Feel free to
> > improve.
>
> As I said, I'm floating a spec among the colleagues to solve the issue in a
> cleaner (and more extensible) way in the future, I can send you the link
> if you'd like (though I don't know if it'll end up folded in trunk in the
> end).
Yes, a single line in the config is not the best way, but was easy to code at
that time.
>
> Also, I think we should use the platform's os.pathsep to split paths.
pathsep has to do with directories notation, doesn't it? The delimiter we
could use in a string, such as the comma, colon or semicolon (like in $PATH)
is another thing to decide.