Closed stugots closed 10 years ago
Hey John,
Great to hear you're still using the app!
I am getting absolutely crushed right now, and don't have any available time to install the project and get things going right now. If you have time to wrap up a pull request, that would be awesome -- I think the problem can likely be taken care of doing: (1) a conditional (try/catch) import to be pre/post Django 1.5 compatible, or (2) a Django 1.5+ only change. I don't mind either way, and I'm fine with the next version of the app being 1.5+ compatible only.
If not, I'll see when I can get some time to look into things, or hopefully some other kind soul might contribute a pull request.
Best, Ryan
roger that, i'll try today, it'll depend on how today goes. it's already shaping up to be "one of those days".
On Apr 4, 2013, at 7:55 PM, Ryan Roemer notifications@github.com wrote:
Hey John,
Great to hear you're still using the app!
I am getting absolutely crushed right now, and don't have any available time to install the project and get things going right now. If you have time to wrap up a pull request, that would be awesome -- I think the problem can likely be taken care of doing: (1) a conditional (try/catch) import to be pre/post Django 1.5 compatible, or (2) a Django 1.5+ only change. I don't mind either way, and I'm fine with the next version of the app being 1.5+ compatible only.
If not, I'll see when I can get some time to look into things, or hopefully some other kind soul might contribute a pull request.
Best, Ryan
— Reply to this email directly or view it on GitHub.
Still haven't dug out from under the fire drills…..
On Apr 4, 2013, at 7:55 PM, Ryan Roemer notifications@github.com wrote:
Hey John,
Great to hear you're still using the app!
I am getting absolutely crushed right now, and don't have any available time to install the project and get things going right now. If you have time to wrap up a pull request, that would be awesome -- I think the problem can likely be taken care of doing: (1) a conditional (try/catch) import to be pre/post Django 1.5 compatible, or (2) a Django 1.5+ only change. I don't mind either way, and I'm fine with the next version of the app being 1.5+ compatible only.
If not, I'll see when I can get some time to look into things, or hopefully some other kind soul might contribute a pull request.
Best, Ryan
— Reply to this email directly or view it on GitHub.
Hey John!
A year and change later and it's fixed via #6! (And not by me ;)
That's some speedy service there...
In urls_admin.py, there's a
...which doesn't exist in Django 1.5.1. See https://docs.djangoproject.com/en/1.4/topics/generic-views-migration/, etc....