> 2) F() expressions have not been updated to work with GIS fields. > However, based on some initial discussions with Justin, it should be > possible to make these changes without affecting any public API. If > anyone with access and experience with contrib.GIS cares to help out > on this front, assistance would be gratefully accepted; otherwise, > we'll just have to wait until Justin surfaces from his Bar exams.
Currently, nothing is broken and all tests pass -- only that a TypeError is raised when one tries to use F() on a geographic field. I've got a preliminary patch that fixes F() expressions for GIS fields: http://code.djangoproject.com/ticket/10159 Hopefully some people can bang on it and create improvements for the patch, including maybe a test case or two. -Justin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
