← Back to team overview

launchpad-dev team mailing list archive

Re: New coding standard for formatting imports

 

On Thu, 2010-08-19 at 14:10 +0100, Jonathan Lange wrote:
> On Thu, Aug 19, 2010 at 2:01 PM, Jeroen Vermeulen <jtv@xxxxxxxxxxxxx> wrote:
> > On 2010-08-19 18:38, Jonathan Lange wrote:
> >
> >> Neither annoys me. What annoys me is getting conflicts from Bazaar for
> >> changes where there is no *actual* conflict, or having to actually use
> >> my brain to handle something so mindnumbingly trivial as finding and
> >> adding imports. Computers should be able to do that for me.
> >
> > This came up over lunch today.  Stuart joked: why write imports at all?  We
> > could look them up automatically.
> >
> > But does that have to be a joke?  Couldn't we generate imports (well, those
> > from other Launchpad modules) automatically during branch build?
> ...
> 
> I would much rather use editor tools than a preprocessor. Once we
> introduce a mandatory preprocessing stage, we are no longer writing
> Python code. Editor tools provide much the same convenience, but leave
> us still writing standard Python.

We would also lose the ability to use in-editor pyflakes to find
undefined names. It's true we wouldn't need it for missing imports
anymore, but that's not the only source of undefined names.

-- 
Guilherme Salgado <https://launchpad.net/~salgado>

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


Follow ups

References