def get_db_prep_save ( self, value, connection ). def get_prep_lookup ( self, lookup_type, value ). Included with Django’s and is no longer hosted separately at .Ĭlass CustomModelField ( models. The GDAL interface now allows the user to set aįinally, GeoDjango’s documentation is now The GEOS interface was updated to use thread-safe C library functions when The force_rhr(), reverse_geom(), and geohash() GeoQuerySet Support for 3D geometry fields was added, and may be enabledĪnd extent3d() GeoQuerySet method were added as a part of this feature. With non-point geometries on geographic coordinate systems. New features include support for the geography type GeoDjango now supports the rich capabilities added in the PostGIS 1.5 release. In 1.2 is support for multiple spatial databases. The most significant new feature for GeoDjango There is a description of theĪPI these loader classes must implement in the template API reference and youĬan also examine the source code of the loaders shipped with Django. Porting them to a class-based implementation because the code for backwardsĬompatibility with function-based loaders starts its deprecation process inĭjango 1.2 and will be removed in Django 1.4. If you have developed your own custom template loaders we suggest to consider Untouched up to and including the Django 1.3 release. Setting in existing projects, things will keep working if you leave it Third party) so there is no immediate need to modify your TEMPLATE_LOADERS The template core machinery still accepts function-based loaders (builtin or Opposed to functions, the only method available until Django 1.1.Īll the template loaders shipped with Django haveīeen ported to the new API but they still implement the function-based API and To use template loading mechanisms that are encapsulated in Python classes as Transition to Python 3.x, is currently being developed, and will beĪnnounced prior to the release of Django 1.3.Īs part of the changes made to introduce Template caching and followingĪ general trend in Django, the template loaders API has been modified You’ll need to stick to Django 1.1 until you can upgrade perĬontinue to receive security support until the release of Django 1.3.Ī roadmap for Django’s overall 2.x Python support, and eventual If you’re still using Python 2.3, however, Operating-system vendors today are shipping Python 2.4 or newer as This change should affect only a small number of Django users, as most Supported on Python 2.4, 2.5 and 2.6, and will be supported on the Version required for Django is now 2.4, and Django is tested and Previous Django releases were testedĪnd supported on 2.x Python versions from 2.3 up Django 1.2, however,ĭrops official support for Python 2.3. Introduces the first shift in our Python compatibility policy sinceĭjango’s initial public debut. While not a new feature, it’s important to note that Django 1.2 The complete list of backwards-incompatible changes and the list of deprecated Upgrading from previous versions of Django are heavily encouraged to consult There’s a simple one-line fix detailed below.Īgain, these are just the big features that will affect the most users. Should ensure that their code follows the new rules for stateful templateįrom only apply to functions and no longer Template tags that need to store state (e.g. The internals of template tags have changed somewhat authors of custom Under get_db_prep_*() methods on Field, below. Important backwards-incompatible changes, detailed in CSRF Protection,Īuthors of custom Field subclasses should beĪware that a number of methods have had a change in prototype, detailed However, upgrading to the new CSRF protection framework requires a few Users of the old system will not be affected until The new CSRF protection framework is not backwards-compatible with However, a handful of features have changed in ways that, for some users, will beīackwards-incompatible. Manner per our API stability policy policy. Wherever possible these features have been introduced in a backwards-compatible Django Advent covered the release of Django 1.2 with a series ofĪrticles and tutorials that cover some of the new features in depth.
0 Comments
Leave a Reply. |