Re: [Twisted-Python] Coding standard question: flowing long imports with parens

2009-12-22 Thread Robert Kern
On 2009-12-21 18:55 PM, Glyph Lefkowitz wrote: > This is handy, and a bit more reliable than an unstructured import, but what > I *really* want is the ability to say "what depends on this", where "this" is > a fully-qualified dotted name in Python. The weakness of grinimports seems > to be tha

Re: [Twisted-Python] Coding standard question: flowing long imports with parens

2009-12-21 Thread Glyph Lefkowitz
On Dec 21, 2009, at 12:27 PM, Robert Kern wrote: > On 2009-12-21 10:10 AM, Glyph Lefkowitz wrote: >> >> On Dec 21, 2009, at 10:20 AM, James Y Knight wrote: >>> On Dec 21, 2009, at 12:03 AM, Jonathan Lange wrote: Now that we no longer support Python 2.3, may we also allow imports in the

Re: [Twisted-Python] Coding standard question: flowing long imports with parens

2009-12-21 Thread Robert Kern
On 2009-12-21 10:10 AM, Glyph Lefkowitz wrote: > > On Dec 21, 2009, at 10:20 AM, James Y Knight wrote: > >> On Dec 21, 2009, at 12:03 AM, Jonathan Lange wrote: >>> Now that we no longer support Python 2.3, may we also allow imports in >>> the following style? >>> >>> from very.long.package import (

Re: [Twisted-Python] Coding standard question: flowing long imports with parens

2009-12-21 Thread Glyph Lefkowitz
On Dec 21, 2009, at 10:20 AM, James Y Knight wrote: > On Dec 21, 2009, at 12:03 AM, Jonathan Lange wrote: >> Now that we no longer support Python 2.3, may we also allow imports in >> the following style? >> >> from very.long.package import ( >> bar, >> foo, >> ) > > > Separating "from X

Re: [Twisted-Python] Coding standard question: flowing long imports with parens

2009-12-21 Thread James Y Knight
On Dec 21, 2009, at 12:03 AM, Jonathan Lange wrote: > Now that we no longer support Python 2.3, may we also allow imports in > the following style? > > from very.long.package import ( >bar, >foo, >) Separating "from X import" and "Y" over a newline totally breaks grepping for impor