date:20130524

Re: [Django] #20470: Querying crashes with RuntimeError (dictionary changed size during iteration)

2013-05-24 Thread Django

#20470: Querying crashes with RuntimeError (dictionary changed size during
iteration)
-+-
 Reporter:  jpaalasm |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by jpaalasm):

 * status:  closed => new
 * resolution:  needsinfo =>


Comment:

 Here's more information about the issue.

 This crash occurs in about 0.3% of all requests, in a view that gets some
 hundreds of requests per minute.

 I think that installing the development version is not currently possible,
 because we seem to be using some removed functionality (e.g. importing
 django.conf.urls.defaults fails).

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.9ed76345f40a5497b238b63342dc5f94%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20496: job section spams at community page

2013-05-24 Thread Django

#20496: job section spams at community page
---+
 Reporter:  john   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 https://www.djangoproject.com/community/

 job section occupied by spam posts
 all brings 404 error page

 odUBgviffJwdrPEBb 2013-05-24 12:30:59
 May 24th, 2013 at 12:31 p.m. by Django Jobs

 ldbQlEDgji 2013-05-24 12:30:59
 May 24th, 2013 at 12:31 p.m. by Django Jobs

 fEqCRXbFQvdQVTfZ 2013-05-24 12:31:00
 May 24th, 2013 at 12:31 p.m. by Django Jobs

 oetQsGjLgqvRaknQEXj 2013-05-24 12:31:00
 May 24th, 2013 at 12:31 p.m. by Django Jobs

 hRJTjdHcJQNcsuBFoNb 2013-05-24 12:31:01
 May 24th, 2013 at 12:31 p.m. by Django Jobs

 Thanks

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/047.336be3644a826c1fc57efb7dab3e8e08%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20244: PermissionsMixin should define related name of groups and user_permissions related name

2013-05-24 Thread Django

Comment (by ptone):

Looking at how this might possibly work, and haven't found any great
options.

I think this will have to happen at the level of the app_cache, after all
models are loaded. It can traverse the loaded models, looking for those
that are 'swappable' then checking for the appropriate setting, then
setting a 'swapped_for' attribute on swapped in model. {{{swapped_for}}}
as a term is already used in _swapped where I probably would have used
{{{swapped_with}}}, but given this is all private API, we can change at
will if it makes sense.

There isn't really any way I can see to discover this at Model creation
time.

@russelm if you get some time in a bit to look at this and get a start, or
at least a plan of attack, I can probably help finish up and/or review in
the AM my time.

--
Ticket URL:
Django
The Web framework for perfectionists with deadlines.

--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.84146e075a19e73ccf005096132a93c0%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19793: global name 'timezone' is not defined

2013-05-24 Thread Django

#19793: global name 'timezone' is not defined
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Documentation|  1.5-alpha-1
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  global name  | Triage Stage:
  'timezone' is not defined  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by nilu214):

 class Poll(models.Model):
 # ...
 def was_published_recently(self):
 return self.pub_date >= (timezone.now() -
 datetime.timedelta(days=1))

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.4423cc2cecb00cd3d7ce9e77e23ce89f%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20495: add login failure events to django.security logger

2013-05-24 Thread Django

#20495: add login failure events to django.security logger
+
   Reporter:  ptone |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  contrib.auth  |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 #18616 added a signal for failed login attempts - a primary use-case for
 this was monitoring.

 With #19866 we have the introduction of a django.security logger, and it
 would make more sense to log these events there.

 I'd be +0 on also deprecating the signal, they are brand new, and probably
 don't have much traction. There may be non-monitoring uses of said signal
 though that I'm not thinking of.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/048.adae1b801b9ffc0e17165f33d8d41f56%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20228: Admin interface doesn't prevent duplicates with unique_for_date

2013-05-24 Thread Django

#20228: Admin interface doesn't prevent duplicates with unique_for_date
---+
 Reporter:  monuszko   |Owner:  iapain
 Type:  Bug|   Status:  assigned
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by iapain):

 * has_patch:  0 => 1
 * component:  Database layer (models, ORM) => Documentation


Comment:

 https://github.com/django/django/pull/1215

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.1d71ffcad917f9d9a67ff40ba125a803%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20494: New reference for /wiki/Tutorials = Testing = suggestion

2013-05-24 Thread Django

#20494: New reference for /wiki/Tutorials = Testing = suggestion
-+-
 Reporter:  Maarten@…|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  *.djangoproject.com  |  Version:  1.4
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  Reference on | Triage Stage:
  Tutorial pages |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by carljm):

 * status:  new => closed
 * needs_docs:   => 0
 * resolution:   => invalid
 * needs_tests:   => 0
 * needs_better_patch:   => 0


Comment:

 Hi! Thanks for the suggestion.

 As you probably already know, we don't generally maintain links to
 resources like this in the official Django documentation, since it's just
 too much work to keep up with new resources and cull broken/outdated
 links. The Tutorials wiki page is a great place for it, and the wiki is
 open to anyone to edit, so if you'd like to help keep the Tutorials page
 up to date, no need to open a ticket, you can just go right ahead and do
 it! (You may need to register for a djangoproject.com account; that helps
 us avoid spam.)

 I'm closing this as "invalid" because that's the issue-tracker status we
 use for things that don't need to be on the issue tracker, but please
 don't take offense at the name - your suggestion is perfectly valid, it
 just doesn't need to be tracked here!

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/076.e085828ec0cbf48ae8457e8a975a1f76%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20494: New reference for /wiki/Tutorials = Testing = suggestion

2013-05-24 Thread Django

#20494: New reference for /wiki/Tutorials = Testing = suggestion
-+-
 Reporter:  Maarten@…|  Owner:  nobody
 Type:  Uncategorized| Status:  new
Component:   |Version:  1.4
  *.djangoproject.com|   Keywords:  Reference on Tutorial pages
 Severity:  Normal   |  Has patch:  0
 Triage Stage:  Unreviewed   |  UI/UX:  0
Easy pickings:  0|
-+-
 Just watched Python Django tutorial 18 - "Basic unit testing" by Mike
 Hibbert on YouTube, http://youtu.be/AcE4KTTBknc, I thought it was very
 good. Is it an idea to include the link in the wiki/Tutorials?

 Is tickets the right tool to use for this suggestion? Apologies if it is
 not.

 Kind Regards.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/061.fe13b51716674c0e08d97d44bc59e06a%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20493: HttpResponse objects cached with cache_page don't unpickle across Django version leading to strange errors

2013-05-24 Thread Django

#20493: HttpResponse objects cached with cache_page don't unpickle across Django
version leading to strange errors
---+
Reporter: cataliniacob |Owner: nobody
Type: Bug| Status: new
Component: Documentation | Version: 1.5
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 |UI/UX: 0
---+
Changes (by carljm):

* component: Core (Cache system) => Documentation
* stage: Unreviewed => Accepted

Comment:

I think you're right that a requirement of cross-version unpicklability is
more than we want to commit to. We do have an "upgrading Django" page in
the docs now (https://docs.djangoproject.com/en/1.5/howto/upgrade-
version/); seems like it would make a lot of sense to add this as a note
there.

On a more long-term note, it might be worth considering whether the
caching middleware should cache a very simple "body, headers" data
structure instead of a full pickled `HttpResponse`. This would probably
break all kinds of code, though, since it means anything else tacked on to
the `HttpResponse` (and perhaps used by middlewares further down the
chain) would be missing.

--
Ticket URL:
Django
The Web framework for perfectionists with deadlines.

--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.d7e2f0c207f8ba6be8ed7318e00263cd%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20493: HttpResponse objects cached with cache_page don't unpickle across Django version leading to strange errors

2013-05-24 Thread Django

#20493: HttpResponse objects cached with cache_page don't unpickle across Django
version leading to strange errors
-+-
 Reporter:  cataliniacob |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Cache system)  |  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by cataliniacob):

 * cc: iacobcatalin@… (added)
 * needs_docs:   => 0
 * needs_tests:   => 0
 * needs_better_patch:   => 0


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.441de434176c8907ef8f6d8aa8910f23%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] fd48d2: [1.5.x] Rotate CSRF token on login

2013-05-24 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: fd48d2d438ed6f58b9bae08b8866dd6e50dd673d
  
https://github.com/django/django/commit/fd48d2d438ed6f58b9bae08b8866dd6e50dd673d
  Author: Andrew Godwin 
  Date:   2013-05-24 (Fri, 24 May 2013)

  Changed paths:
M django/contrib/auth/__init__.py
M django/contrib/auth/tests/views.py
M django/middleware/csrf.py

  Log Message:
  ---
  [1.5.x] Rotate CSRF token on login

Backport of 1514f17aa60772f48839130f9a5071b9ffe15213 from master



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/519fd9c45f972_1ffccf5ddc71710%40hookshot-fe5-pe1-prd.aws.github.net.mail?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20493: HttpResponse objects cached with cache_page don't unpickle across Django version leading to strange errors

2013-05-24 Thread Django

#20493: HttpResponse objects cached with cache_page don't unpickle across Django
version leading to strange errors
-+
 Reporter:  cataliniacob |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Core (Cache system)  |Version:  1.5
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 I just upgraded from 1.4 to 1.5 and this took a while to track.

 If one has a cache that persists across a Django version change
 (filesystem cache, memcached that is not restarted), when executing any
 view decorated with @cache_page unpickling the HttpResponse from the cache
 leads to strange errors. For example, when upgrading from 1.4 to 1.5 I
 get:

 {{{
 [24/May/2013 15:53:42] "GET / HTTP/1.1" 200 5
 Traceback (most recent call last):
   File "/usr/lib64/python2.7/wsgiref/handlers.py", line 86, in run
 self.finish_response()
   File "/usr/lib64/python2.7/wsgiref/handlers.py", line 129, in
 finish_response
 self.close()
   File "/usr/lib64/python2.7/wsgiref/simple_server.py", line 36, in close
 SimpleHandler.close(self)
   File "/usr/lib64/python2.7/wsgiref/handlers.py", line 257, in close
 self.result.close()
   File "/home/catalin/hacking/envs/cached-httpresponse-across-
 versions/lib/python2.7/site-packages/django/http/response.py", line 231,
 in close
 for closable in self._closable_objects:
 AttributeError: 'HttpResponse' object has no attribute '_closable_objects'
 [24/May/2013 15:53:42] "GET / HTTP/1.1" 500 59
 
 Exception happened during processing of request from ('127.0.0.1', 49852)
 Traceback (most recent call last):
   File "/usr/lib64/python2.7/SocketServer.py", line 582, in
 process_request_thread
 self.finish_request(request, client_address)
   File "/usr/lib64/python2.7/SocketServer.py", line 323, in finish_request
 self.RequestHandlerClass(request, client_address, self)
   File "/home/catalin/hacking/envs/cached-httpresponse-across-
 versions/lib/python2.7/site-packages/django/core/servers/basehttp.py",
 line 150, in __init__
 super(WSGIRequestHandler, self).__init__(*args, **kwargs)
   File "/usr/lib64/python2.7/SocketServer.py", line 638, in __init__
 self.handle()
   File "/usr/lib64/python2.7/wsgiref/simple_server.py", line 124, in
 handle
 handler.run(self.server.get_app())
   File "/usr/lib64/python2.7/wsgiref/handlers.py", line 89, in run
 self.handle_error()
   File "/usr/lib64/python2.7/wsgiref/handlers.py", line 304, in
 handle_error
 self.finish_response()
   File "/usr/lib64/python2.7/wsgiref/handlers.py", line 127, in
 finish_response
 self.write(data)
   File "/usr/lib64/python2.7/wsgiref/handlers.py", line 210, in write
 self.send_headers()
   File "/usr/lib64/python2.7/wsgiref/handlers.py", line 267, in
 send_headers
 if not self.origin_server or self.client_is_modern():
   File "/usr/lib64/python2.7/wsgiref/handlers.py", line 280, in
 client_is_modern
 return self.environ['SERVER_PROTOCOL'].upper() != 'HTTP/0.9'
 TypeError: 'NoneType' object has no attribute '__getitem__'
 
 }}}

 This was at first quite perplexing because I checked response.py and
 {{{self._closable_objects}}} gets assigned in
 {{{HttpResponseBase.__init__}}} which gets called by
 {{{HttpResponse.__init__}}} so it seemed impossible for an HttpResponse
 instance not to have the attribute. Unpickling doesn't normally call
 {{{__init__}}} but this is not at all obvious or easy to track.

 There are similar issues but with a bit more clear stacktrace if
 downgrading from 1.5 to 1.4:
 {{{
 Traceback:
 File "/home/catalin/hacking/envs/cached-httpresponse-across-
 versions/lib/python2.7/site-packages/django/core/handlers/base.py" in
 get_response
   89. response = middleware_method(request)
 File "/home/catalin/hacking/envs/cached-httpresponse-across-
 versions/lib/python2.7/site-packages/django/middleware/cache.py" in
 process_request
   147. response = self.cache.get(cache_key, None)
 File "/home/catalin/hacking/envs/cached-httpresponse-across-
 versions/lib/python2.7/site-
 packages/django/core/cache/backends/filebased.py" in get
   41. return pickle.load(f)

 Exception Type: ImportError at /
 Exception Value: No module named response
 }}}

 I'm surprised nobody seems to have run into this so far, googling for
 AttributeError on _closable_objects and searching the other bugs didn't
 show anything. I would imagine it's reasonably common to upgrade without
 restarting memcached or to have a filesystem based cache on a development
 machine where you don't bother to install memcached. And this happens on
 '''every''' view with @cache_page.

 I don't know what a good

[django/django] 475d0b: Rotate CSRF token on login

2013-05-24 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 475d0b8c34943150130ea08c9e54c29d08ecb57e
  
https://github.com/django/django/commit/475d0b8c34943150130ea08c9e54c29d08ecb57e
  Author: Andrew Godwin 
  Date:   2013-05-24 (Fri, 24 May 2013)

  Changed paths:
M django/contrib/auth/__init__.py
M django/contrib/auth/tests/views.py
M django/middleware/csrf.py

  Log Message:
  ---
  Rotate CSRF token on login

Backport of 1514f17aa60772f48839130f9a5071b9ffe15213 from master



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/519fd9a2af370_28b1eabdd41019dc%40hookshot-fe4-pe1-prd.aws.github.net.mail?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 1514f1: Rotate CSRF token on login

2013-05-24 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 1514f17aa60772f48839130f9a5071b9ffe15213
  
https://github.com/django/django/commit/1514f17aa60772f48839130f9a5071b9ffe15213
  Author: Andrew Godwin 
  Date:   2013-05-24 (Fri, 24 May 2013)

  Changed paths:
M django/contrib/auth/__init__.py
M django/contrib/auth/tests/test_views.py
M django/middleware/csrf.py

  Log Message:
  ---
  Rotate CSRF token on login



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/519fd88edc20_d54e37de488425%40hookshot-fe3-pe1-prd.aws.github.net.mail?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16137: .get behaviour is inconsistent with .get_or_create when no kwargs are given

2013-05-24 Thread Django

#16137: .get behaviour is inconsistent with .get_or_create when no kwargs are 
given
-+-
 Reporter:  wilfred@…|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.3
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

 * cc: timograham@… (added)


Comment:

 Updated patch to apply cleanly to master.
 https://github.com/django/django/pull/1214

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/082.dfb627b65fe772cd00fd1c03905229d6%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 7e95d7: Fixed a regression in router initialization

2013-05-24 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 7e95d7a93088675f984d1079e4e3c3ddc1723b0f
  
https://github.com/django/django/commit/7e95d7a93088675f984d1079e4e3c3ddc1723b0f
  Author: Claude Paroz 
  Date:   2013-05-24 (Fri, 24 May 2013)

  Changed paths:
M django/db/utils.py
M tests/multiple_database/tests.py

  Log Message:
  ---
  Fixed a regression in router initialization

Regression was introduced in 6a6bb168b. Thanks Bas Peschier for the
report.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/519fb8df67bc7_2901c9bddc917c4%40hookshot-fe1-pe1-prd.aws.github.net.mail?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20205: PositiveIntegerfield does not handle empty values well

2013-05-24 Thread Django

#20205: PositiveIntegerfield does not handle empty values well
-+-
 Reporter:  anonymous|Owner:  AmiZya
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * cc: timograham@… (added)
 * needs_better_patch:  1 => 0


Comment:

 Updated pull request without unrelated changes and tweaked test.

 https://github.com/django/django/pull/1213

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.76b6ec0b22d1ba36016fb473a3ed2366%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19900: Upgrade admin buttons

2013-05-24 Thread Django

#19900: Upgrade admin buttons
-+-
 Reporter:  Pedro Mourelle   |Owner:  anonymous
  |   Status:  assigned
 Type:   |  Version:
  Cleanup/optimization   |   Resolution:
Component:  contrib.admin| Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  sprints-django-ar|  Patch needs improvement:  1
Has patch:  1|UI/UX:  1
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

 * needs_better_patch:  0 => 1
 * stage:  Ready for checkin => Accepted


Comment:

 The discussion suggests that this is not actually RFC.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/096.42421ab361813c2e447d1f4857965ed9%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17582: DoesNotExist ambiguous exception when accessed via foreign key

2013-05-24 Thread Django

#17582: DoesNotExist ambiguous exception when accessed via foreign key
-+-
 Reporter:  simon@…  |Owner:
 Type:   |  JordanPowell
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by timo):

 * cc: timograham@… (added)
 * needs_better_patch:  1 => 0
 * needs_tests:  1 => 0
 * needs_docs:  1 => 0
 * has_patch:  0 => 1
 * stage:  Ready for checkin => Accepted


Comment:

 In reviewing this, I found another instance of {{{raise DoesNotExist}}}
 without a message. Updated in the following pull request:
 https://github.com/django/django/pull/1212

 (moving back to accepted to get another review)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/083.f0a98d03fd4865e393f1e38e95697af6%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20492: Broken external link in ref/contrib/gis/geoip/

2013-05-24 Thread Django

#20492: Broken external link in ref/contrib/gis/geoip/
---+
 Reporter:  bmispelon  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by Tim Graham ):

 In [changeset:"1deeda5785d2f7a27ddf8df89640e96ecc9e3e88"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1deeda5785d2f7a27ddf8df89640e96ecc9e3e88"
 [1.5.x] Fixed #20492 - Removed a broken link in GIS docs.

 Backport of fbab3209fc from master
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.f6dd28b0bc1afd64877fbbfa6d2d7012%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 1deeda: [1.5.x] Fixed #20492 - Removed a broken link in GI...

2013-05-24 Thread GitHub

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: 1deeda5785d2f7a27ddf8df89640e96ecc9e3e88
  
https://github.com/django/django/commit/1deeda5785d2f7a27ddf8df89640e96ecc9e3e88
  Author: Tim Graham 
  Date:   2013-05-24 (Fri, 24 May 2013)

  Changed paths:
M docs/ref/contrib/gis/geoip.txt

  Log Message:
  ---
  [1.5.x] Fixed #20492 - Removed a broken link in GIS docs.

Backport of fbab3209fc from master



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/519f97161e933_9e77fbde042968%40hookshot-fe3-pe1-prd.aws.github.net.mail?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20492: Broken external link in ref/contrib/gis/geoip/

2013-05-24 Thread Django

#20492: Broken external link in ref/contrib/gis/geoip/
---+
 Reporter:  bmispelon  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by Tim Graham ):

 In [changeset:"82fc3ce41db298ae4b191d4a15bddfaf02ea11af"]:
 {{{
 #!CommitTicketReference repository=""
 revision="82fc3ce41db298ae4b191d4a15bddfaf02ea11af"
 [1.5.x] Fixed #20492 - Removed a broken link in GIS docs.

 Backport of fbab3209fc from master
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.94cfc6ed6925baec3b4ab6368e8be020%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 82fc3c: [1.5.x] Fixed #20492 - Removed a broken link in GI...

2013-05-24 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 82fc3ce41db298ae4b191d4a15bddfaf02ea11af
  
https://github.com/django/django/commit/82fc3ce41db298ae4b191d4a15bddfaf02ea11af
  Author: Tim Graham 
  Date:   2013-05-24 (Fri, 24 May 2013)

  Changed paths:
M docs/ref/contrib/gis/geoip.txt

  Log Message:
  ---
  [1.5.x] Fixed #20492 - Removed a broken link in GIS docs.

Backport of fbab3209fc from master



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/519f970813158_23e3569dd49239e%40hookshot-fe2-pe1-prd.aws.github.net.mail?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] fbab32: Fixed #20492 - Removed a broken link in GIS docs.

2013-05-24 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: fbab3209fc6b32752a71d012add57cd440adfc94
  
https://github.com/django/django/commit/fbab3209fc6b32752a71d012add57cd440adfc94
  Author: Tim Graham 
  Date:   2013-05-24 (Fri, 24 May 2013)

  Changed paths:
M docs/ref/contrib/gis/geoip.txt

  Log Message:
  ---
  Fixed #20492 - Removed a broken link in GIS docs.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/519f96f024b67_d54e37de4632ae%40hookshot-fe3-pe1-prd.aws.github.net.mail?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20492: Broken external link in ref/contrib/gis/geoip/

2013-05-24 Thread Django

#20492: Broken external link in ref/contrib/gis/geoip/
---+
 Reporter:  bmispelon  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by Tim Graham ):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"fbab3209fc6b32752a71d012add57cd440adfc94"]:
 {{{
 #!CommitTicketReference repository=""
 revision="fbab3209fc6b32752a71d012add57cd440adfc94"
 Fixed #20492 - Removed a broken link in GIS docs.
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.30f88a775d81d848621efd8fdbc1890f%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] e149d8: [1.4.x] Updated link to jQuery Cookie plugin site

2013-05-24 Thread GitHub

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: e149d8ebf04415fb0bab5b1dda16ef7d196ade7c
  
https://github.com/django/django/commit/e149d8ebf04415fb0bab5b1dda16ef7d196ade7c
  Author: Alasdair Nicol 
  Date:   2013-05-24 (Fri, 24 May 2013)

  Changed paths:
M docs/ref/contrib/csrf.txt

  Log Message:
  ---
  [1.4.x] Updated link to jQuery Cookie plugin site

Backport of 81f454a322 from master



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/519f94bfae961_2a65cebddc26296%40hookshot-fe1-pe1-prd.aws.github.net.mail?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] d6025d: [1.5.x] Updated link to jQuery Cookie plugin site

2013-05-24 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: d6025d790f3f5ecc11981cb43e1e14f85adcdb4d
  
https://github.com/django/django/commit/d6025d790f3f5ecc11981cb43e1e14f85adcdb4d
  Author: Alasdair Nicol 
  Date:   2013-05-24 (Fri, 24 May 2013)

  Changed paths:
M docs/ref/contrib/csrf.txt

  Log Message:
  ---
  [1.5.x] Updated link to jQuery Cookie plugin site

Backport of 81f454a322 from master



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/519f94a559d4f_23b8789de42259b%40hookshot-fe2-pe1-prd.aws.github.net.mail?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 81f454: Update link to jQuery Cookie plugin site

2013-05-24 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 81f454a32296ad27437eaf19acfcdad9a9c03fca
  
https://github.com/django/django/commit/81f454a32296ad27437eaf19acfcdad9a9c03fca
  Author: Alasdair Nicol 
  Date:   2013-05-24 (Fri, 24 May 2013)

  Changed paths:
M docs/ref/contrib/csrf.txt

  Log Message:
  ---
  Update link to jQuery Cookie plugin site


  Commit: 92c9052addb73b7e73ea349b4244bdd4f0087ca0
  
https://github.com/django/django/commit/92c9052addb73b7e73ea349b4244bdd4f0087ca0
  Author: Tim Graham 
  Date:   2013-05-24 (Fri, 24 May 2013)

  Changed paths:
M docs/ref/contrib/csrf.txt

  Log Message:
  ---
  Merge pull request #1210 from alasdairnicol/jquery_cookie_plugin_link

Updated link to jQuery Cookie plugin site


Compare: https://github.com/django/django/compare/c4fb8326ddfd...92c9052addb7

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/519f947958d8_24268f9ddc707e3%40hookshot-fe2-pe1-prd.aws.github.net.mail?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20099: Allow filtering 404 reports by user agent

2013-05-24 Thread Django

#20099: Allow filtering 404 reports by user agent
-+-
 Reporter:  coolRR   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  1
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by charettes):

 * cc: charettes (added)
 * stage:  Accepted => Ready for checkin


Comment:

 Left some minor comment on @claudep's PR. Apart from those the patch looks
 RFC.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.e24517d303928189c24fd9705f91f084%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20099: Allow filtering 404 reports by user agent

2013-05-24 Thread Django

#20099: Allow filtering 404 reports by user agent
---+
 Reporter:  coolRR |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by claudep):

 Revisiting this issue after some time, here's an alternative approach:
 https://github.com/django/django/pull/1211

 We need a referee now :-)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.d163fd245299389aaaf9f40cfe578936%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] fb1d81: Link to active fork for ODBC backend

2013-05-24 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: fb1d8134846b468a6b972d3af1a23d7ee381b149
  
https://github.com/django/django/commit/fb1d8134846b468a6b972d3af1a23d7ee381b149
  Author: Paul Tax 
  Date:   2013-05-24 (Fri, 24 May 2013)

  Changed paths:
M docs/ref/databases.txt

  Log Message:
  ---
  Link to active fork for ODBC backend

It took me quite some time to find if and where the ODBC backend was maintained.
I found (on djangoproject.com):
http://code.google.com/p/django-pyodbc/ (last commit about 3 years ago)
then:
https://github.com/avidal/django-pyodbc avidal fork.
then:
https://github.com/aurorasoftware/django-pyodbc/ aurorasoftware version which 
has avidal improvements merged.

Avidals version now links to https://github.com/aurorasoftware/django-pyodbc/ 
which is also the version installed through PIP.


  Commit: c4fb8326ddfd71440768d646b6acd68cd3d4d249
  
https://github.com/django/django/commit/c4fb8326ddfd71440768d646b6acd68cd3d4d249
  Author: Preston Holmes 
  Date:   2013-05-24 (Fri, 24 May 2013)

  Changed paths:
M docs/ref/databases.txt

  Log Message:
  ---
  Merge pull request #1209 from tax/master

Updated link to active project for ODBC backend


Compare: https://github.com/django/django/compare/f3ba6495e29d...c4fb8326ddfd

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/519f8b7b40ad5_23cb5afdd41056b5%40hookshot-fe2-pe1-prd.aws.github.net.mail?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20488: Enhance the Storage class with new copy and move methods

2013-05-24 Thread Django

#20488: Enhance the Storage class with new copy and move methods
--+
 Reporter:  kux   |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  File uploads/storage  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

 * stage:  Unreviewed => Accepted


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/061.c22b7c0a25b5578feea6582f94201475%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20492: Broken external link in ref/contrib/gis/geoip/

2013-05-24 Thread Django

#20492: Broken external link in ref/contrib/gis/geoip/
---+
 Reporter:  bmispelon  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by claudep):

 * easy:  0 => 1


Comment:

 I'd suggest just removing the link, as it is mainly informational.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.4c0768cf78a2a17404018df22499841a%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20182: prepare_lookup_value should treat 0 as False for __isnull

2013-05-24 Thread Django

#20182: prepare_lookup_value should treat 0 as False for __isnull
-+-
 Reporter:  benjie@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by timo):

 * stage:  Accepted => Ready for checkin


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/077.baec623c27a46dcbc9dd997bda8aa8b7%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] f3ba64: Updated my bio

2013-05-24 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: f3ba6495e29d84f8d98a2acd390821ff0d23fd7a
  
https://github.com/django/django/commit/f3ba6495e29d84f8d98a2acd390821ff0d23fd7a
  Author: Brian Rosner 
  Date:   2013-05-24 (Fri, 24 May 2013)

  Changed paths:
M docs/internals/committers.txt

  Log Message:
  ---
  Updated my bio



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/519f77e26d39f_28a55d5de073037%40hookshot-fe4-pe1-prd.aws.github.net.mail?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #14051: Signals for transaction commit/rollback

2013-05-24 Thread Django

Comment (by kux):

I don't actually understand why this got closed.

Even though manual transaction management no longer exists in master, I
would still find it very useful to be able to register on_commit and
on_rollback hooks for the atomic block. You might be having django models
that also depend on external resources. In case of a rollback you might
want to run a clean-up action. Don't actually care about savepoints... I
just want to make sure I don't leave any junk behind :)

Take for example the admin's change_view. If an exception is being raised
while changing an object, the only way I can run any clean-up code is by
overriding change_view. This doesn't seem very elegant.

--
Ticket URL:
Django
The Web framework for perfectionists with deadlines.

--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/091.a4b3da3db2e67c6e13dab054a2608311%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #12728: loadata/flush issues given GenericRelation, model inheritance and postgres

2013-05-24 Thread Django

#12728: loadata/flush issues given GenericRelation, model inheritance and 
postgres
-+-
 Reporter:  pragmar  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  master
  contrib.contenttypes   |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
  psycopg2.ProgrammingError, |  Patch needs improvement:  1
  GenericRelation|UI/UX:  0
Has patch:  1|
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by timo):

 Confirmed the new test no longer fails as of
 97774429aeb54df4c09895c07cd1b09e70201f7d (#19385). I didn't investigate
 this further to see if the underlying issue is fixed or if this is still
 an issue and just needs a new test.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.4d574cc811a975c15a00dabec568807f%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20492: Broken external link in ref/contrib/gis/geoip/

2013-05-24 Thread Django

#20492: Broken external link in ref/contrib/gis/geoip/
---+
 Reporter:  bmispelon  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by erikr):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.40cbd65e1d107bde52a31674e975c54f%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20290: override_settings cannot be nested

2013-05-24 Thread Django

#20290: override_settings cannot be nested
---+
 Reporter:  obeattie   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by obeattie):

 It appears there
 
[[https://github.com/obeattie/django/blob/248b92e2de936266b6039333291c653fd39870b5/tests/settings_tests/tests.py#L12|are
 already tests]] that check this. I have beefed them up slightly from what
 they were to check that things are applying in the correct precedence
 order for sure, but they weren't insufficient before.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.ed243f0b785a9f899be7f493a77c11d9%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19607: prefetch_related crash

2013-05-24 Thread Django

#19607: prefetch_related crash
-+-
 Reporter:  av@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:  prefetch |  Unreviewed
  prefetch_related   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Luke Plant ):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"4fd94969d859eb25680a5a52ed482c8f22e5ee15"]:
 {{{
 #!CommitTicketReference repository=""
 revision="4fd94969d859eb25680a5a52ed482c8f22e5ee15"
 Fixed #19607 - prefetch_related crash

 Thanks to a...@rdf.ru and flarn...@yahoo.de for the report.
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.9814e5fdb7765a5604ec5e423cffe2bc%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 4fd949: Fixed #19607 - prefetch_related crash

2013-05-24 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 4fd94969d859eb25680a5a52ed482c8f22e5ee15
  
https://github.com/django/django/commit/4fd94969d859eb25680a5a52ed482c8f22e5ee15
  Author: Luke Plant 
  Date:   2013-05-24 (Fri, 24 May 2013)

  Changed paths:
M django/db/models/query.py
M tests/prefetch_related/models.py
M tests/prefetch_related/tests.py

  Log Message:
  ---
  Fixed #19607 - prefetch_related crash

Thanks to a...@rdf.ru and flarn...@yahoo.de for the report.


  Commit: 17559e6eb0422aa6ec7bd9b7f1345b97a2a454a6
  
https://github.com/django/django/commit/17559e6eb0422aa6ec7bd9b7f1345b97a2a454a6
  Author: Luke Plant 
  Date:   2013-05-24 (Fri, 24 May 2013)

  Changed paths:
M django/db/models/query.py

  Log Message:
  ---
  Optimisation in prefetch_related_objects


Compare: https://github.com/django/django/compare/48424adaba74...17559e6eb042

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/519f3f72682b4_497adbdddc7518%40hookshot-fe1-pe1-prd.aws.github.net.mail?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20393: django.db.models.query.QuerySet.repr should not have side-effects

2013-05-24 Thread Django

#20393: django.db.models.query.QuerySet.__repr__ should not have side-effects
-+-
 Reporter:  justin@… |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:  QuerySet, repr,  |  Unreviewed
  side-effect|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by patrys):

 What if we changed `__repr__` to be safe (only print query params) and
 allowed a slice with `Ellipsis` to return a list of first N elements,
 possibly executing the query if not evaluated earlier?

 Example:

 {{{
 >>> x = Foo.objects.filter(age__gte=5)
 
 >>> x[...]
 [, , , , '11 more...']
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/079.76ced1481e2b594e73584104f8bb83fc%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20492: Broken external link in ref/contrib/gis/geoip/

2013-05-24 Thread Django

#20492: Broken external link in ref/contrib/gis/geoip/
---+
 Reporter:  bmispelon  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Documentation  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 In the first paragraph of
 https://docs.djangoproject.com/en/dev/ref/contrib/gis/geoip/, the link
 pointing to `http://www.maxmind.com/en/python` (the GPL-licensed library)
 gives a 404.

 It seems that this particular library is not supported anymore.

 I is still referenced on that page (note the "legacy" part of the URL):
 http://dev.maxmind.com/geoip/legacy/downloadable#Python-10 but the link
 there is just for a tarball, there doesn't seem to be a dedicated page for
 it anymore.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.37aac56d8a404436167d94f40d2a2fb2%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20483: Reduce the set of apps seen by individual tests

2013-05-24 Thread Django

Comment (by akaariai):

Patch updated (force-pushed to
https://github.com/akaariai/django/compare/isolated_apps). Here is the
commit message:
{{{
Any django.test.testcases.TransactionTestCase subclass can include
app_mask. The app_mask tells the subset of INSTALLED_APPS the test
requires. Any model outside the app_mask can not be queried. The
currently tested app is always included in the app_mask.

The intended use case is to make Django's test suite faster. By
masking applications the non-masked applications do not need to
flushed, nor is there need to install contenttypes or permissions for
masked applications. For example SQLite tests run in about 210s vs
560s, and PostgreSQL tests run in 4500s vs 300s.

The change does not alter behaviour of tests when the app_mask is not
set, unless DJANGO_ALWAYS_MASK_APPS[_TX] environment variable is set.
The _TX variant controls transactional test cases, while plain variant
controls other test cases. runtests.py contains set of the _TX
variable. If set, app_mask is set to current tested app unless the
test case contains its own app_mask.
}}}

The code might be a little rough, but it seems to work on both SQLite and
PostgreSQL. Please review, I would like to get this committed soon. This
should cut our CI cycle time by order of magnitude.

--
Ticket URL:
Django
The Web framework for perfectionists with deadlines.

--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.a7e8100e593b33d1c922c24c6f9e5c49%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19607: prefetch_related crash

2013-05-24 Thread Django

#19607: prefetch_related crash
-+-
 Reporter:  av@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  prefetch |  Unreviewed
  prefetch_related   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by lukeplant):

 Thank you kenn, that's brilliant! I have at last been able to reproduce
 the bug in test case form using this data, and I'll hopefully get it fixed
 soon.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.d3358a930e4294ea98faee59c6fea4f2%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20491: jobs section spam posts

2013-05-24 Thread Django

#20491: jobs section spam posts
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  *.djangoproject.com  |  Version:  1.4
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by jezdez):

 * component:  Uncategorized => *.djangoproject.com


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.a673b14857f3af2dab21a5365d8f6a7d%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20491: jobs section spam posts

2013-05-24 Thread Django

#20491: jobs section spam posts
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.4
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by jezdez):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 I've removed the offending feed item. If this happens again with
 djangojobs.org I'll remove the feed completely.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.ced545bde38fcc2d2da2e30198cdd01e%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #9025: Nested Inline Support in Admin

2013-05-24 Thread Django

#9025: Nested Inline Support in Admin
---+
 Reporter:  pixelcort  |Owner:
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  1
---+

Comment (by anonymous):

 +1

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.75526d2002908f0861719ca8b1491911%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20304: Does not work the feed of the kate editor

2013-05-24 Thread Django

#20304: Does not work the feed of the kate editor
-+
 Reporter:  pmartin  |Owner:  jezdez
 Type:  Bug  |   Status:  new
Component:  *.djangoproject.com  |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by jezdez):

 * stage:  Unreviewed => Accepted


Comment:

 I checked in Superfeedr's debugging console (the PubSubHubbub provider we
 use) and it seems to fetch the feed successfully, but doesn't get further
 than starting to parse it. Not sure, I've reached out to Superfeedr here:
 https://twitter.com/jezdez/status/337836072216186880

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.608df6c4edcdcf9d1d6b7f2b5cab9f2e%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20491: jobs section spam posts

2013-05-24 Thread Django

#20491: jobs section spam posts
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by anonymous):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Replying to [ticket:20491 anonymous]:
 > http://www.djangojobs.org/developers/bmikxkophmlabuf/
 >
 > community page spammed by this site

 https://www.djangoproject.com/community/

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.9408449dc04258a4127d82bb54348a7c%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20491: jobs section spam posts

2013-05-24 Thread Django

#20491: jobs section spam posts
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 http://www.djangojobs.org/developers/bmikxkophmlabuf/

 community page spammed by this site

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.634b3d871fe8f06543d42e14150c6e7e%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #10070: Named parameters not working on raw sql queries with sqlite

2013-05-24 Thread Django

#10070: Named parameters not working on raw sql queries with sqlite
-+-
 Reporter:  msurdi   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.0
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by rupa108):

 I started a related discussion here
 https://groups.google.com/forum/#!topic/django-developers/ts14HX9Yz0I

 named parameters do currently work with some db interfaces but the code
 breaks on the __repr__() method of a RawQuerySet:

 param = dict(lname = 'Doe')
 qs = Person.objects.raw('SELECT * FROM myapp_person WHERE last_name =
 %(lname)s', param)
 repr(qs)

 /home/user/vpy/dev/lib/python2.7/site-packages/django/db/models/query.pyc
 in __repr__(self)
1530
1531 def __repr__(self):
 -> 1532 return "" % (self.raw_query %
 tuple(self.params))
1533
1534 def __getitem__(self, k):

 TypeError: format requires a mapping

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.3a6955579adc165b5cf63c8b4334fcb4%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20483: Reduce the set of apps seen by individual tests

2013-05-24 Thread Django

Comment (by akaariai):

I think I am going to do these changes & commit:
1. app_mask is used if the TestCase has it set. Otherwise all apps are
used. So, no need for _ALWAYS_INSTALLED_APPS hack.
2. add some way (environment variable?) to enable "warn on missing
app_mask" so that we can eventually have app_mask for every Django's test.
3. manually cascade the TRUNCATE for postgresql (travel all reverse
foreign keys, add found tables to the truncate command)

When all test cases have requirements marked, we could get rid of
runtests.py ALWAYS_INSTALLED_APPS and instead create tables for apps in
set(t.app_mask for t in testcases).

Some numbers from testing this on postgresql: 4500s unpatched, 300s with
this ticket's patch. The time doesn't include database creation, so the
full time is probably more like 4700s vs 500s. Still, order of magnitude
difference.

--
Ticket URL:
Django
The Web framework for perfectionists with deadlines.

--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.f0eadba2e1b118d02972507d1c4ec20c%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

53 matches

Mail list logo