Changes between Initial Version and Version 1 of Ticket #30689, comment 2
- Timestamp:
- Aug 8, 2019, 4:06:16 AM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #30689, comment 2
initial v1 1 My problem was that the `fields` argument was not passed to the constructor of a class inheriting from `MultiValueField`. In Django 1.11 it worked, because empty tuple `()` was the default for this argument, just like in the class header in the documentation, and since Django 2.0 there is no default value. The exact code change is here: https://github.com/django/django/commit/8e752d84378c7169ef73a483ffffcba55a08c867.1 My problem was that the `fields` argument was not passed to the constructor of a class inheriting from `MultiValueField`. In Django 1.11 it worked, because empty tuple `()` was the default for this argument, just like in the class header in the documentation, and since Django 2.0 there is no default value. The exact code change is here: 8e752d84378c7169ef73a483ffffcba55a08c867. 2 2 3 3 I think this is a breaking change that should be documented in the release notes. This: