GeoDjango compatibility

[dyve]

I did this:

• Inherit from NullBoolean for better compatibility
• add South support
• make GeoDjango manager, query set, model
• add objects and all_objects to models
• adjust tests to reflect change in models

[akshayjshah]

Awesome. Thanks for the PR, Dylan!

Is there a convenient way to test the South and GIS integrations?

[dyve]

South is quite simple.

For GIS you need a GIS DB, either PostGIS (I use this) or Spatialite (I don't use this). I have little experience with automated PostGIS testing (unit tests for my other projects don't require this). Best to ask around I think, or maybe try StackOverflow.

On 9 juli 2014 at 16:38:01, Akshay Shah (notifications@github.com) wrote:

Awesome. Thanks for the PR, Dylan!

Is there a convenient way to test the South and GIS integrations?

— Reply to this email directly or view it on GitHub.

[akshayjshah]

Hrm, you're right - from a quick look around, I don't see a great way to do an end-to-end test of GeoDjango stuff on Travis. Let's table that for now - it should be possible to get some unit tests running with the mock library, but we can come back to that.

If adding a few tests is simple for South, can you add them to this PR?

[dyve]

If you are OK with renaming, it's better to rename first and then add South compatibility, because South wants to know the naming scheme.

I can modify this PR with the new naming scheme (will make for a rather big change), or first get GeoDjango stuff in and rename & add South later.

[akshayjshah]

Let's get the GeoDjango stuff in, then rename, then add South. No sense holding up the GIS integration.

[dyve]

OK, I'll modify this PR, commenting out the South integration.

[akshayjshah]

Works for me.

[dyve]

Also removed the from __future__

[akshayjshah]

Thanks, @dyve! I'm working on the internal renaming now, so we should be able to move ahead with the South integration soon.

[dyve]

Great. I also have UndeleteView (class based view for undelete) ready when the file renaming is done.