Re: Explicit relative imports

> On 11 Nov 2014, at 22:51, Aymeric Augustin > 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 like to add guidelines about imports in the coding style guide in > order to im

Re: Creating data in TestCase.setUpClass() (proposed refactoring)

Thanks for your feedback. I updated my pull request (https://github.com/django/django/pull/3464) following Anssi suggestion: subclasses of TestCase can define a class method "setupTestData" to create some data once for the whole TestCase. If the database backend does not support transaction (e.

Re: Explicit relative imports

Hi Zach, django/apps/registry.py is a better example. It has relative imports from django/apps/config.py and absolute imports from other parts of Django. -- Aymeric. 2014-11-12 17:37 GMT+01:00 Zach Borboa : > Aymeric, is this the example? > > from .config import AppConfig # NOQAfrom .registry

Re: Explicit relative imports

Aymeric, is this the example? from .config import 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 relat

Re: Are rasters on the GeoDjango roadmap?

Hi Daniel, I've answered on the GeoDjango list. Please avoid cross-posting, thanks. Claude Le mercredi 12 novembre 2014 12:34:34 UTC+1, Daniel Wiesmann a écrit : > > Hi All > > I am wondering if integration of Raster data is on the roadmap of > GeoDjango. > > I am asking because I have started

Are rasters on the GeoDjango roadmap?

Hi All I am wondering if integration of Raster data is on the roadmap of GeoDjango. I am asking because I have started to work on a package to include Rasters into Django (see link below). This is still very early stage, but I already use the package in a Django project I am working on. For tha

Re: Explicit relative imports

Parent imports inside the sub-framework could make sense, otherwise the mixture of imports might look odd. As long as it stops at ".." and doesn't include more it's relatively fine imo. Cheers, Florian On Tuesday, November 11, 2014 10:51:19 PM UTC+1, Aymeric Augustin wrote: > > Hello, > > We’v