launchpad-dev team mailing list archive
-
launchpad-dev team
-
Mailing list archive
-
Message #04382
Re: New coding standard for formatting imports
On Thu, Aug 19, 2010 at 2:26 PM, Jeroen Vermeulen <jtv@xxxxxxxxxxxxx> wrote:
> On 2010-08-19 20:10, Jonathan Lange wrote:
>
>>> 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.
>
...
> The part I haven't thought about at all yet is how to avoid this being an
> extra step, or a noticeable delay, for the developer. But at any rate we
> may find a "make" before testing preferable over editing imports ourselves.
> I for one dislike that jump to the top of the file and back.
>
Easily avoided with a scriptable editor. IIRC, Edwin demonstrated a
vim script for this at the Epic.
jml
Follow ups
References