← Back to team overview

launchpad-dev team mailing list archive

Re: New coding standard for formatting imports

 

On Fri, Aug 20, 2010 at 3:19 AM, Francis J. Lacoste
<francis.lacoste@xxxxxxxxxxxxx> wrote:
> Hi Henning,
>
> That output only means there was a problem building Mailman. When there are no
> errors, that step is silent. Most of it are useless warnings.
>
> The bit that is failing is:

>    from canonical.launchpad.webapp.interfaces import (
>  File "/var/launchpad/test/lib/canonical/launchpad/webapp/__init__.py", line
> 48, in <module>
>    from canonical.launchpad.webapp.launchpadform import (
> ImportError: cannot import name action
>
> That should point you in the right direction. (Probably something created by
> your formatter.)
>
> Running make clean and trying to build locally should reproduce the failure.

Oh dear. I suspect there might be more work involved than that. In
some cases, imports are in an explicit order to avoid circular import
issues.


-- 
Stuart Bishop <stuart@xxxxxxxxxxxxxxxx>
http://www.stuartbishop.net/



Follow ups

References