Yeah, I don't think we'd try to do anything like that in our actual Django
patch... the THREADLOCALS thing has worked well for us but I realize that's
a pretty big shift to impose on others. If anything I think the patch might
simply modify the existing CursorDebugWrapper to add the traceback-ba
On 25 loka, 17:52, Marty Woodlee wrote:
> Yeah, I don't think we'd try to do anything like that in our actual Django
> patch... the THREADLOCALS thing has worked well for us but I realize that's
> a pretty big shift to impose on others. If anything I think the patch might
> simply modify the exist
Good point, and I agree, allowing the user to use their own cursor wrappers
is probably the best solution. At least, it would allow us to avoid the
monkeypatching we're having to use here. From there, this particular
wrapping could just turn into a django-snippet. I'll try to work on
something
Our first milestone on the road to Django 1.5 came today, with the
release of the first alpha package.
Blog post about it is here:
https://www.djangoproject.com/weblog/2012/oct/25/15-alpha-1/
Release notes are here:
https://docs.djangoproject.com/en/dev/releases/1.5-alpha-1/
And you can get th
Hey folks --
One thing about 1.5 that's of particular note to -developers: this
marks the beginning of our "master is always open" policy. That is,
we're *not* freezing the master branch until 1.5 is released; new
features can continue to go into master as soon as they're ready.
This is a pretty
