Wednesday, December 21, 2016

Re: django-report-tools replacement for Django 1.7 and higher

Quick followup, it looks like 3 of the 4 forks from HEAD on master have fixed it, take a look at the network graph

https://github.com/evanbrumley/django-report-tools/network

On Thursday, December 22, 2016 at 9:49:44 AM UTC+2, C. Kirby wrote:
It looks like github user daegun has the most up to date fork of it, but you will have to pip install from github instead of pypi

https://github.com/daegun/django-report-tools/commit/521cefa61103166c5aea40586549d95aadbc561d


On Wednesday, December 21, 2016 at 4:06:05 PM UTC+2, scha...@gmail.com wrote:
Hi all,
I took over a very old Django project and I like to upgrade it to the actual version.
I will do a step wise upgrade and from Django 1.6 to 1.7 I have the problem, that the used django-report-tools is no longer supported/compatible because the
django.utils.encoding.StrAndUnicode
has been removed.

Is there a replacement or what do you recommend for report generation in django 1.7 and higher.

Thanks
schaf

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/5e3039a5-c56a-43c1-b632-46df2f21e327%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment