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
Release to support Django 1.6 #405
Comments
+1. Why so much movement on this repo, but no PyPI releases for more than a year and a half? |
👍 |
1 similar comment
+1 |
Agree. The deprecation warning in 1.5 was already a bother to my team on version 1.5 (which has been out six months). These issues are already fixed, we just need a release. Are there any roadblocks? What's the missing piece of the puzzle here? |
+1 Strong on this one |
Thanks everyone for your encouragements. I've just been given commit access to the repository and I'm going to push towards a release compatible 1.6. In the meantime, since this ticket doesn't track any actionable items (such as a patch), I'm going to close it. I hope you understand. Call me out in three months if there hasn't been a release and I'll reopen it :) |
I didn't get it, you are closing the bug so that we have to remember to ask again in 3 months? Why not make a release now... we are all already using the repo directly it would make more sense to just release it. |
The list of issues is so long that maintenance has stalled. I'm removing from the list tickets without actionable items. That's all! Supporting Django 1.5 requires supporting Python 3. I plan to do that in the coming weeks. Then I'll ask someone with the keys to PyPI to push a release. |
@aaugustin Other than Python 3 support, are there any other issues blocking a new release on PyPi? |
I'm not aware of any other blockers. |
Is there somewhere that to support django >= 1.5 you need to support python 3? Because I don't think that is sane, it puts too much work on django extensions/apps. |
After porting about 60% Django itself to Python 3, I think I can handle porting the Debug Toolbar ;-) |
The error:
" ImproperlyConfigured: Error importing module debug_toolbar.middleware: "No module named defaults" "
was fixed in master, but there was no release since then, and django 1.6 is going to be rc in 2 weeks.
The text was updated successfully, but these errors were encountered: