-
-
Notifications
You must be signed in to change notification settings - Fork 337
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
Comments
Two issues I've found:
|
Gah! I see these are covered in PR #227 |
I received this error with version django-silk==1.0.0 installed from pip |
#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). |
I also see this error when executing
|
any update on when this will be pulled/next release tagged? |
@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. |
1.1.0 released but not yet deployed to pip. When can I use 1.1.0 with pip? |
@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. |
@avelis Do you have any reason not to have ETA? |
@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. |
@avelis ah... It's unfortunate. I hope it will be resolved. Thank you! |
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 |
I have this error after update:
The text was updated successfully, but these errors were encountered: