-
Notifications
You must be signed in to change notification settings - Fork 158
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
Question: Is this being maintained anymore? #127
Comments
It's hard to find suitable fork with good support. Maybe it will be better to add maintainers for this project, who have time to review PRs and issues? @egrubbs Because there exists some PRs with very important features as Python 3 support. But without tests it's always risky to merge anything. Maybe we should write some tests (for basic scenarios, at least) and then start merge important PRs. |
@prokaktus, I don't have permission to add new maintainers. I became a maintainer by asking dcramer for access several months ago, but I have unfortunately not spent as much time on the project as I had hoped. |
@egrubbs oh, thanks for info! |
@dcramer do you want to add this project to jazzband? |
@jdejoode yeah I'm totally fine w/ that. I'm not sure its heavily used these days fwiw. We had gotten to a point where we were mostly using it for its improved runserver capabilities, but I think all of that might be in Django core now. |
I think the line and memory profiler integration are still lacking in django core, or am I mistaking? |
They're not in core, you're correct. I've just found them to be less useful over the years. |
I see some recent activity but no release to pypi or bump in version? @egrubbs ?
The text was updated successfully, but these errors were encountered: