launchpad-dev team mailing list archive

["Francis J. Lacoste" <francis.lacoste@xxxxxxxxxxxxx>]

Hi Marc,

lp isn't a namespace package in Launchpad. I guess that's what Robert is 
hinting at by the "no good story". It was meant to be, but it seems that we 
added .py directly in it, at some point. And it misses the namespace 
registration declaration. I've filed bug 669938 about this.

In the mean time, we could use a lpx namespace for applications building on 
top of Launchpad?

-- 
Francis J. Lacoste
francis.lacoste@xxxxxxxxxxxxx

On November 2, 2010, Marc Tardif wrote:
> * Sidnei da Silva <sidnei.da.silva@xxxxxxxxxxxxx> [2010-11-02 01:12 -0200]:
> > On Tue, Nov 2, 2010 at 1:09 AM, Robert Collins
> > 
> > <robert.collins@xxxxxxxxxxxxx> wrote:
> > > What do you mean by 'lp namespace'? If you mean the python code is
> > > lp.SOMETHING, then I would rather you don't do that - we don't have a
> > > good story for working with packages like that, and it would be much
> > > easier if your package was lpSOMETHING instead - for now.
> > 
> > There's a bunch of packages under the lazr.* namespace. Maybe that's
> > safer to use.
> 
> Thanks for the suggestion, I had considered that namespace too. However,
> my understanding was that the lazr.* namespace was for general purpose
> libraries whereas the lp.* namespace could eventually be for services
> which might be specifically branded as Launchpad. For example, if we
> were to extract Answers from Launchpad, should it be under the lp.* or
> lazr.* namespace? In the end, I simply want to be consistent with the
> direction Launchpad is most likely to take when extracting components
> as standalone services. And, if there is no good story for this as
> pointed out by Robert, I'd like to help build one.

Attachment: signature.asc
Description: This is a digitally signed message part.