On 13 June 2012 08:51, Raphaël Badin <[email protected]> wrote: >> Gavin and I are thinking about reorganising the python packages >> structure a bit. The main goal or this reorganisation to stop the >> proliferation of python packages in src/. Instead of having top-level >> python packages 'maasserver', 'metadataserver', etc. we would have only >> one top-level python package (named 'maas') which would contain >> 'maasserver', 'metadataserver', etc. (i.e 'from metadataserver.models >> import NodeKey' → 'from maas.metadataserver.models import NodeKey'). >> [...] >> > > I forgot to say that the goal of this email is to gather feedback about > this code reorganisation. I think this will ease the packaging work a > bit but I'd be particularly interested to hear from the packaging guys > if they think there is any problem with the proposed reorg.
I'm losing enthusiasm for a big move, now that it's apparent that South imposes some restrictions on us. I /now/ think we should leave things as they are, except to move apiclient to maas.apiclient or something like that. Sorry for flip-flopping on this. Some other thoughts: 1. Waiting until we decide how to split the packages might make the decision of how to name things a no-brainer. 2. We may discover a workaround for the South restrictions before we get around to moving anything. 3. Do Python packagers like/mind namespace packages? -- Mailing list: https://launchpad.net/~maas-devel Post to : [email protected] Unsubscribe : https://launchpad.net/~maas-devel More help : https://help.launchpad.net/ListHelp
