| .. |
|
bug639
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
cache
|
Fixed #4845 -- Fixed some problems with Unicode usage and caching. Thanks,
|
2007-07-16 09:36:10 +00:00 |
|
datastructures
|
…
|
|
|
datatypes
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
dateformat
|
…
|
|
|
db_typecasts
|
…
|
|
|
defaultfilters
|
…
|
|
|
dispatch
|
Fixed #4040 -- Changed uses of has_key() to "in". Slight performance
|
2007-04-26 13:30:48 +00:00 |
|
fixtures_regress
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
forms
|
Fixed #4228 -- Removed hardcoding of `RadioFieldRenderer` in the `RadioSelect` Widget so that the display of `RadioSelect`s can be more easily customized. `BoundField.__unicode__` also no longer special cases `RadioSelect` since `RadioSelect.render()` now returns a string like every other Widget.
|
2007-08-01 05:41:32 +00:00 |
|
httpwrappers
|
Merged Unicode branch into trunk (r4952:5608). This should be fully
|
2007-07-04 12:11:04 +00:00 |
|
humanize
|
…
|
|
|
i18n
|
Merged Unicode branch into trunk (r4952:5608). This should be fully
|
2007-07-04 12:11:04 +00:00 |
|
initial_sql_regress
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
invalid_admin_options
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
many_to_one_regress
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
maxlength
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
model_fields
|
…
|
|
|
model_regress
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
null_queries
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
one_to_one_regress
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
serializers_regress
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
string_lookup
|
Fixed #2101 -- Renamed `maxlength` argument to `max_length` for oldforms `FormField`s and db model `Field`s. This is fully backwards compatible at the moment since the legacy `maxlength` argument is still supported. Using `maxlength` will, however, issue a `PendingDeprecationWarning` when used.
|
2007-08-05 05:14:46 +00:00 |
|
templates
|
…
|
|
|
test_client_regress
|
…
|
|
|
text
|
Merged Unicode branch into trunk (r4952:5608). This should be fully
|
2007-07-04 12:11:04 +00:00 |
|
urlpatterns_reverse
|
…
|
|
|
utils
|
Fixed #4310 -- Fixed a regular expression bug in `strip_entities` function and added tests for several `django.utils.html` functions. Based on patch from Brian Harring.
|
2007-07-15 05:03:28 +00:00 |
|
__init__.py
|
Added regressions tests to ensure that one-to-one and many-to-many fields
|
2006-06-20 05:29:19 +00:00 |
212ee65be7