Could we selectively set the numberasstring property per query if there are any
decimal fields for that particular query? I guess this could help in the
interim until/if cx_oracle can fix the problem and that particular version of
cx oracle becomes the minimum version django supports.
--
You
Report for week ending May 16, 2015:
I also tested Django with Python 2.7.10rc1 and found a backwards
incompatible change which has been reverted.
https://bugs.python.org/issue24134
Triaged
---
https://code.djangoproject.com/ticket/24779 - django-1.8.1 fails test with
pypy - FAIL: test
Hi Marten,
I am a little less acquainted with the internals of resolving and reversing
than the people above, and I must say that I have a hard time understanding
your new syntax when looking at the example gist. That might also have to
do with the indentation style. Would the (blog_detail, blog_i
One important thing to keep in mind is reverse() performance.
While it isn't important that the prototype is fast, making sure the API
doesn't limit performance for the most important operations must be checked.
At least my experience is that URL resolving performance isn't that
important, but ha
Hi Marten,
I had a look at your proposal today. You've done good work there.
My comments revolve around making the API obvious, simplifying it until
someone who discovers it understands immediately what the moving pieces are,
what they do, and how they relate to one another.
Here are my two main
