| Thread Previous • Date Previous • Date Next • Thread Next |
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?
Of course it would create a few problems. We'd want to use __all__ consistently (then again, we would like that anyway). Sometimes we'd have to write foo.go() instead of go() because there's also a bar.go(). We'd need a systematic approach to circular imports (possibly useful in and of itself). And sometimes we may just want substitutable names, à la "from cStringIO import StringIO." But if it saves us from maintaining all that boilerplate I'm sure there are palatable workarounds.
Jeroen
| Thread Previous • Date Previous • Date Next • Thread Next |
