ntrary voice here, but I don't dig explicit relative imports, it's just
> adds an extra decision point for no real benefit.
>
> Personally I always recommend full absolute imports, ordered strictly
> alphabetically - there's then never any room for confusion or decision
> making a
recommend against any relative imports from
parent packages. It should be limited to siblings only.
Cheers.
Tai.
On Friday, 14 November 2014 00:57:15 UTC+11, Tom Christie wrote:
>
> Contrary voice here, but I don't dig explicit relative imports, it's just
> adds an extra decis
block at the end of the
imports which further show what is "within" a component, rather than it
being buried within a large block.
In any case, explicit relative imports are greatly preferable to implicit
ones.
Marc
On 13 Nov 2014 13:57, "Tom Christie" <christie@gmail.
Contrary voice here, but I don't dig explicit relative imports, it's just
adds an extra decision point for no real benefit.
Personally I always recommend full absolute imports, ordered strictly
alphabetically - there's then never any room for confusion or decision
making around how the imports
> On 11 Nov 2014, at 22:51, Aymeric Augustin
> <aymeric.augus...@polytechnique.org> wrote:
>
> Hello,
>
> We’ve started using explicit relative imports in newer parts of the Django
> source tree. They’re short and readable. That’s good.
>
> I would lik
mport AppConfig # NOQAfrom .registry import apps # NOQA
>
> from https://github.com/django/django/blob/master/django/apps/__init__.py
>
> On Tuesday, November 11, 2014 1:51:19 PM UTC-8, Aymeric Augustin wrote:
>>
>> Hello,
>>
>> We’ve started using explicit rela
>
> Hello,
>
> We’ve started using explicit relative imports in newer parts of the Django
> source tree. They’re short and readable. That’s good.
>
> I would like to add guidelines about imports in the coding style guide in
> order to improve consistency.
>
> My inclinatio
I agree wholeheartedly. (Sorry, not much else to say...)
On 11 November 2014 21:51, Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
> Hello,
>
> We’ve started using explicit relative imports in newer parts of the Django
> source tree. They’re short and readable.
Hello,
We’ve started using explicit relative imports in newer parts of the Django
source tree. They’re short and readable. That’s good.
I would like to add guidelines about imports in the coding style guide in order
to improve consistency.
My inclination would be to recommend relative imports
