Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drop support for Django < 1.11 and remove workarounds #266

Merged
merged 1 commit into from
Jan 29, 2018
Merged

Drop support for Django < 1.11 and remove workarounds #266

merged 1 commit into from
Jan 29, 2018

Conversation

jdufresne
Copy link
Member

Per Django's recommendation, as django-silk supports 2.0, it should drop support for Django < 1.11 to ease maintenance and compatibility across Django versions. So long as no deprecation warnings are produced, django-silk should remain forward compatible with the next Django
version.

For more details, see the Django docs:

https://docs.djangoproject.com/en/2.0/releases/2.0/#third-party-library-support-for-older-version-of-django

Third-party library support for older version of Django

Following the release of Django 2.0, we suggest that third-party app authors drop support for all versions of Django prior to 1.11. At that time, you should be able to run your package’s tests using python -Wd so that deprecation warnings do appear. After making the deprecation warning fixes, your app should be compatible with Django 2.0.

Those wishing to continue using an older Django can pin the version django-silk.

Should significantly reduce testing resources as the test matrix is much smaller.

Per Django's recommendation, as django-silk supports 2.0, it should drop
support for Django < 1.11 to ease maintenance and compatibility across
Django versions. So long as no deprecation warnings are produced,
django-silk should remain forward compatible with the next Django
version.

For more details, see the Django docs:

https://docs.djangoproject.com/en/2.0/releases/2.0/#third-party-library-support-for-older-version-of-django

> Third-party library support for older version of Django
>
> Following the release of Django 2.0, we suggest that third-party app authors
> drop support for all versions of Django prior to 1.11. At that time, you
> should be able to run your package’s tests using python -Wd so that
> deprecation warnings do appear. After making the deprecation warning fixes,
> your app should be compatible with Django 2.0.

Those wishing to continue using an older Django can pin the version
django-silk.

Should significantly reduce testing resources as the test matrix is much
smaller.
Copy link
Member

@albertyw albertyw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me

@albertyw albertyw requested a review from avelis January 28, 2018 22:45
@avelis avelis merged commit fa1f542 into jazzband:master Jan 29, 2018
@avelis
Copy link
Collaborator

avelis commented Jan 29, 2018

@jdufresne Thank you for cleaning up this library and improving django-silks compatibility for Django 2.0 onward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants