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

Django 2.0 support #229

Closed
volodchenkov opened this issue Dec 3, 2017 · 13 comments · Fixed by #242
Closed

Django 2.0 support #229

volodchenkov opened this issue Dec 3, 2017 · 13 comments · Fixed by #242

Comments

@volodchenkov
Copy link

volodchenkov commented Dec 3, 2017

I have this error after update:

 File "/Users/izvr/Projects/bet/env/lib/python3.6/site-packages/silk/models.py", line 135, in Response
    request = OneToOneField(Request, related_name='response', db_index=True)
TypeError: __init__() missing 1 required positional argument: 'on_delete'
@jkeyes
Copy link

jkeyes commented Dec 3, 2017

Two issues I've found:

  • adding on_delete to ForeignKey and OneToOneField declarations (models.py)
  • MIDDLEWARE_CLASSES is no longer available from settings (profiler.py)

@jkeyes
Copy link

jkeyes commented Dec 3, 2017

Gah! I see these are covered in PR #227

@volodchenkov
Copy link
Author

volodchenkov commented Dec 3, 2017

I received this error with version django-silk==1.0.0 installed from pip

@albertyw
Copy link
Member

albertyw commented Dec 5, 2017

#227 has been landed and I'm running a small django 2 site with that PR now.

If you want to get django 2 support now, you can pip install directly from github (maybe pin to the current master commit). Otherwise, I'm going to work on #187 and make a new release (maybe v1.1.0 but I need to check the commit history for semantic versioning).

@physicalattraction
Copy link

I also see this error when executing runserver from the projects directory:

    include('silk.urls', namespace='silk', app_name='silk')
TypeError: include() got an unexpected keyword argument 'app_name'

@yousifa
Copy link

yousifa commented Dec 15, 2017

any update on when this will be pulled/next release tagged?

@albertyw
Copy link
Member

@yousifa I'm working through getting django 2 tests working in #233. It's quite slow going because I can't replicate the test environment locally. I'm hoping to fix the issues and make a new release within a week.

@physicalattraction there's a patch for your error in #233. Technically, that doesn't block the next release of silk because the projects directory is only used in tests.

@sebatyler
Copy link

1.1.0 released but not yet deployed to pip.
https://pypi.python.org/pypi/django-silk

When can I use 1.1.0 with pip?

@avelis
Copy link
Collaborator

avelis commented Dec 27, 2017

@sebatyler I don't have an ETA at the moment on the publish to PyPi. For now I suggest a way to reference the release directly in any requirements files you may use.

@sebatyler
Copy link

@avelis Do you have any reason not to have ETA?
I just wonder.

@avelis
Copy link
Collaborator

avelis commented Dec 27, 2017

@sebatyler I am unsure if Jazzband has the right privileges to publish releases to Django-Silk's Pypi account. I don't have access to verify this. I could also be missing a couple other steps to ensure proper state as a Jazzband project.

@sebatyler
Copy link

@avelis ah... It's unfortunate. I hope it will be resolved. Thank you!

@albertyw
Copy link
Member

Since this is more a discussion of releases rather than django 2 support (master should fully support django 2 now), I moved the discussion to #187 and jazzband/help#82

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 a pull request may close this issue.

7 participants