-
Notifications
You must be signed in to change notification settings - Fork 66
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
This updates Django to v1.11.10 and and all updates related supporting requirements and introduces some code changes required to keep things running smoothly - django-filters 1.x required updates to all API filter classes - Implemented new filter class for Attribute model API viewset, replacing `AttributeViewSet.filter_fields` with `.filter_class` - All existing `MethodFilter` fields had to be converted to typed fields that specified `method=` as an argument - All `.filter_foo()` methods had to have a new `name` argument added to their signature - Custom database model fields have been updated to include the new `.from_db_value()` method which differs only slightly from the `.to_python()` method for each custom field. - The `nsot-server upgrade` command no longer calls `syncdb` (which has been deprecated) underneath has been updated to call `migrate` instead. - All places where `django.utils.log.getLogger` was being called has been replaced with `logging.getLogger` - Calls to `django.core.handlers.wsgi.STATUS_CODE_TEXT` have been replaced with `httplib.responses` - django-macaddress required all MAC address objects to conform to EUIv48 format: `settings.INTERFACE_DEFAULT_MAC` has been explicitly set to use EUIv48 format - `nsot.validators.validate_mac_address()` no longer utilizes `macaddress.formfields.MacAddressField.clean()` as a validator and instead directly instantitates a `netaddr.EUI()` object to assert validity. - Because pytest-django had to be updated, so did pytest, and new test warnings were occuring when `tests.api_tests.fixtures.TestSite` was used. It has been renamed to `SiteHelper` to avoid the warnings.
- Loading branch information
Showing
22 changed files
with
187 additions
and
111 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.