date:20151119

Re: [Django] #25779: Redundant try block in WSGIHandler

2015-11-19 Thread Django

#25779: Redundant try block in WSGIHandler
--+
 Reporter:  Uran198   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  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 claudep):

 * stage:  Unreviewed => Accepted


Comment:

 The try block should probably have been removed during this commit:
 [e0fce8706d31f]

--
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.df962c306a33de91240e1df144fa8a9f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #25783: Site.objects.get_current() should use Django's cache framework

2015-11-19 Thread Django

#25783: Site.objects.get_current() should use Django's cache framework
--+
 Reporter:  patrys|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  contrib.sites |Version:  1.8
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Currently sites are cached using a module global. This solution makes it
 impossible to edit the site object in multiprocess environments as it's
 impossible to notify other processes that they need to invalidate local
 caches. Having to restart all servers/workers after a database operation
 is not intuitive.

--
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/049.728856aeb641d411fa409f9f07aaed1d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25746: Isolate inlined test models

2015-11-19 Thread Django

#25746: Isolate inlined test models
-+-
 Reporter:  charettes|Owner:  charettes
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Testing framework|  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 charettes):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/5687 PR]

--
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.9e8b0ce2ebbeef466076e8acbc4838e4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25551: makemigrations when adding a ForeignKey to a newly created model along with a unique_together constraint must create fields before the unique_together constraint

2015-11-19 Thread Django

#25551: makemigrations when adding a ForeignKey to a newly created model along 
with
a unique_together constraint must create fields before the unique_together
constraint
+---
 Reporter:  mssnlayam   |Owner:  avojnovicDk
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  1.8
 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 avojnovicDk):

 * needs_better_patch:  1 => 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/067.5fedb0dd0d99863b358c23df57625acd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25782: Discourage usage of cache_page decorator with UpdateCacheMiddleware (or make middleware ignore decorated views)

2015-11-19 Thread Django

#25782: Discourage usage of cache_page decorator with UpdateCacheMiddleware (or
make middleware ignore decorated views)
---+--
 Reporter:  int-ua |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  master
 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 carljm):

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


Comment:

 Any attempt to fix this should also take into account #15855 -- the
 `cache_page` decorator is already basically broken in terms of Vary
 headers. It shouldn't cache at all, it should mark the response for later
 caching by the middleware, or something.

--
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.c29c48ac291c9fc45a3951470d8ca3ce%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #10066: can per-site cache and per-view cache or some low level cache work together?

2015-11-19 Thread Django

#10066: can per-site cache and per-view cache or some low level cache work
together?
---+--
 Reporter:  ubestim|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.0
 Severity:  Normal |   Resolution:  invalid
 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 int-ua):

 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


Comment:

 I've tried to suggest ways to solve this in
 https://code.djangoproject.com/ticket/25782#ticket

--
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.cf90c59ff1d5f10e1589216516a95524%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #25782: Discourage usage of cache_page decorator with UpdateCacheMiddleware (or make middleware ignore decorated views)

2015-11-19 Thread Django

#25782: Discourage usage of cache_page decorator with UpdateCacheMiddleware (or
make middleware ignore decorated views)
---+
Reporter: int-ua | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation |Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
---+
If django.middleware.cache.UpdateCacheMiddleware is active and some view
is decorated with the cache_page that overrides cache alias, this view
will be cached in both caches, first time by cache_page and then by the
middleware. Well, at least it will try. And fail if the default cache is
memcached and the view response is bigger than its' maximum entry size.
While filebased cache will work and even create the cache entry. This way
first user to visit when there are no entry in cache will get error
instead of data.
So, I guess there should be some warning about this in the docs.
Ideally, middleware should ignore views with overridden cache alias, maybe
by means of checking headers like in case of the cache_control decorator.

--
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/049.9fb04254eadc19b9dbe52311386a33d8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #15910: show delete links for all admin inline formset rows

2015-11-19 Thread Django

#15910: show delete links for all admin inline formset rows
-+-
 Reporter:  Arthur de Jong   |Owner:  nobody
   |
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  1.3
 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
-+-
Changes (by timgraham):

 * needs_better_patch:  0 => 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/089.fcf6707d15b4bacf3d49182082a49828%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25764: Support serialization of enum.Enum instances in migrations

2015-11-19 Thread Django

#25764: Support serialization of enum.Enum instances in migrations
-+-
 Reporter:  andreif  |Owner:  andreif
 Type:  New feature  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  migrations,  | Triage Stage:  Accepted
  serialization, enum|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"998894e1b9f5a8715f4cac5f6201b5e9ac80510c" 998894e]:
 {{{
 #!CommitTicketReference repository=""
 revision="998894e1b9f5a8715f4cac5f6201b5e9ac80510c"
 Fixed #25764 -- Added support for serialization of enum.Enum in
 migrations.

 Thanks Tim Graham for the 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/065.07047b8d0a7700527ab4bc42c7fad3e3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #12233: Redirect logged in user

2015-11-19 Thread Django

#12233: Redirect logged in user
-+-
 Reporter:  dmathieu |Owner:
 |  aaronbassett
 Type:  New feature  |   Status:  assigned
Component:  contrib.auth |  Version:
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  authentication,login   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Left a few more comments for improvement. Please bump back to RFC when
 updated.

--
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.e14390eaa2b0401bfd982b6b7d695ea0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25779: Redundant try block in WSGIHandler

2015-11-19 Thread Django

#25779: Redundant try block in WSGIHandler
-+-
 Reporter:  Uran198  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Other) |  Version:  master
 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
-+-

Comment (by charettes):

 It looks like this change predates the use of context managers in Django.

--
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.64398e5849248abd0f250c2056dee2dd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25677: compilemessages throws an exception and does not report msgformat errors correctly

2015-11-19 Thread Django

#25677: compilemessages throws an exception and does not report msgformat errors
correctly
-+-
 Reporter:  gavinwahl|Owner:  Claude
 |  Paroz 
 Type:  Bug  |   Status:  closed
Component:   |  Version:  master
  Internationalization   |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"db8763fb239137e9f750d26df221483a8ae5c97c" db8763fb]:
 {{{
 #!CommitTicketReference repository=""
 revision="db8763fb239137e9f750d26df221483a8ae5c97c"
 Refs #25677 -- Fixed Python 2 i18n test failure on non-ASCII path.
 }}}

--
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.046e327a8fdee5f34c8115706ad7ad19%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24782: Add TestCase.assertFormValid

2015-11-19 Thread Django

#24782: Add TestCase.assertFormValid
---+
 Reporter:  mjtamlyn   |Owner:  jvzammit
 Type:  New feature|   Status:  assigned
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  forms  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timgraham):

 * needs_better_patch:  0 => 1


Comment:

 Left comments for improvement.

--
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.35041c2e6a88e6087e40678e5e1e5ab2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #7975: Admin inlines incorrectly report "this field is required" if inline model has field with default value

2015-11-19 Thread Django

#7975: Admin inlines incorrectly report "this field is required" if inline model
has field with default value
---+
Reporter: russellm |Owner: brosner
Type: Uncategorized | Status: closed
Component: contrib.admin | Version: master
Severity: Normal | Resolution: fixed
Keywords: 1.0-blocker| Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 |UI/UX: 0
---+
Changes (by mlissner):

* ui_ux: => 0
* type: => Uncategorized
* severity: => Normal
* easy: => 0

Comment:

This is an old bug, and I worry that my test case isn't right somehow, but
I'm fairly certain I'm hitting the same issue. I have an inline model that
has default drop down values, and I can't save the parent model without
the inline throwing a big error about required fields that aren't filled
in.

My models are more complex than we want in a bug report, but I figured I'd
pipe up in case others are encountering this on Django 1.8.2 as well.

--
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.bb66fd33f787889c4aad6607a08ea920%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19361: Link to object in message after creating/updating object in django admin

2015-11-19 Thread Django

#19361: Link to object in message after creating/updating object in django admin
-+-
 Reporter:  anonymous|Owner:  bak1an
 Type:  New feature  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  admin, messages, | Triage Stage:  Accepted
  update_object, create_object   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"80bcbecd4a394f67c1679b077ba79a797c4a57d7" 80bcbecd]:
 {{{
 #!CommitTicketReference repository=""
 revision="80bcbecd4a394f67c1679b077ba79a797c4a57d7"
 Fixed #19361 -- Added link to object's change form in admin's post-save
 message.

 Thanks Roel Kramer for tests.
 }}}

--
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.16464adfd1017192a8b1f608738b7714%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #25781: admin_views tests should mostly use client.force_login()

2015-11-19 Thread Django

#25781: admin_views tests should mostly use client.force_login()
+
   Reporter:  timgraham |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Testing framework |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  1
  UI/UX:  0 |
+
 Some `admin_views` tests that aren't testing the login view use something
 like `self.client.post(reverse('admin:login'), self.changeuser_login)`.
 Since it's not important to test the admin view in these cases, it will be
 fine to use `self.client.force_login(user)`. Some also have unnecessary
 calls `self.client.get(self.index_url)`.

--
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.37bc1a290dd2b0d182a1801bb55bf41c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25779: Redundant try block in WSGIHandler (was: Redundant try block)

2015-11-19 Thread Django

#25779: Redundant try block in WSGIHandler
-+-
 Reporter:  Uran198  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Other) |  Version:  master
 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 timgraham):

 * cc: andrewgodwin (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Andrew, I tracked that addition to the patch you committed in #11193
 [ba585a2c6d]. Any insight?

--
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.bbee2edba73416997d58973e7993fcd6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #25780: Remove redundant response.status_code assertions in tests

2015-11-19 Thread Django

#25780: Remove redundant response.status_code assertions in tests
+
   Reporter:  timgraham |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Testing framework |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  1
  UI/UX:  0 |
+
 `self.assertContains(response, '...')` also checks the response's status
 code. There are a lot of places (in the `admin_views` tests is the place I
 noticed it) where there's a redundant assertion that verifies
 `self.assertEqual(response.status_code, 200)`.

--
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.2929e2a4bbdc9a49a8381ea05bae80d8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #25779: Redundant try block

2015-11-19 Thread Django

#25779: Redundant try block
--+
 Reporter:  Uran198   |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Core (Other)  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 In this
 
code(https://github.com/django/django/blob/master/django/core/handlers/wsgi.py#L158-L165):
 {{{#!python
 try:
 # Check that middleware is still uninitialized.
 if self._request_middleware is None:
 self.load_middleware()
 except Exception:
 # Unload whatever middleware we got
 self._request_middleware = None
 raise
 }}}

 It seems there is no need for this try block, because
 `self._request_middleware` is being used as a flag of successful
 initialization completion.
 Here where it gets
 
assigned(https://github.com/django/django/blob/master/django/core/handlers/base.py#L73-L75):
 {{{#!python
 # We only assign to this when initialization is complete as it is
 used
 # as a flag for initialization being complete.
 self._request_middleware = request_middleware
 }}}
 Maybe, there are some thread safety issues that I'm missing, in which
 case, I'm sorry for bothering.

--
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/050.7a44c1c11cc47a53a9f4446debfe9fcc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25639: Cascade deleting cause deadlock

2015-11-19 Thread Django

#25639: Cascade deleting cause deadlock
-+-
 Reporter:  shellfly |Owner:  shellfly
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  db deadlock  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_better_patch:  0 => 1


Comment:

 The pull request has failing tests. Please uncheck "Patch needs
 improvement" when they are fixed.

--
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.c546d6871591d518bc21a6e5fa73b22a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #11313: list_editable fields don't support 'save' in multiuser environment

2015-11-19 Thread Django

#11313: list_editable fields don't support 'save' in multiuser environment
+
 Reporter:  margieroginski  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  contrib.admin   |  Version:  1.1-beta
 Severity:  Normal  |   Resolution:
 Keywords:  model formsets  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  1
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by benred42):

 While I still have not been able to reproduce the issue exactly as stated
 on the ticket, I have found a potentially related issue:

 1) User1 opens an admin changelist for a model with list-editable fields
 2)  User2 edits object "Foo" of that same model such that it moves to
 another page in the pagination order and saves
 3) User1 edits object "Foo" and saves
 4)  The edit made by User1 does not get applied to object "Foo" but
 instead are used to create a new object

 I have attempted to address this issue in PR 5686
 https://github.com/django/django/pull/5686

--
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/072.5bf253808aab9bb4dd11ad99f59c1ef6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #14370: Adding support for Autocomplete in contrib.admin

2015-11-19 Thread Django

#14370: Adding support for Autocomplete in contrib.admin
-+-
 Reporter:  tyrion   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  autocomplete,| Triage Stage:  Accepted
  jquery, javascript, widgets,   |
  admin  |
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-
Changes (by jpic):

 * cc: jpic (added)


--
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.4688417b2fc47cc5dffb40286807642e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25774: Refactor of datetime expressions and better, official support for right-hand-side date part extraction

2015-11-19 Thread Django

Comment (by ryuusenshi):

Josh, I've actually tweaked `YearLookup` and `YearComparisonLookup`
already.

I've reversed the order of `process_lhs` and `process_rhs` to make
`process_rhs` occur first, and then based on the result of that
processing, specifically, based on whether there are any `rhs_params`
returned, the lhs processing branches to accommodate right hand side based
on both a parameter and a function.

--
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.a91c158b2a8ef787b79f69a6c4a74184%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25771: Serialization of natural foreign key in migration scripts does not work

2015-11-19 Thread Django

#25771: Serialization of natural foreign key in migration scripts does not work
-+-
 Reporter:  bowensong|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Uncategorized|  Version:  1.8
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  database migration   | Triage Stage:
  serialization  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 I thought about calling this out in the docs, but I'm not convinced that
 doing serialization in migrations is a common use case or something that
 we should promote (see #24778 for discussion).

--
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.cad58daf94d73ad617e5edd87ff89646%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25778: Update docs links to use https

2015-11-19 Thread Django

#25778: Update docs links to use https
-+-
 Reporter:  timgraham|Owner:
 Type:   |  andersonresende
  Cleanup/optimization   |   Status:  assigned
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 andersonresende):

 * owner:  nobody => andersonresende
 * status:  new => assigned


--
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.2262ba09db690807e9739ba324dced67%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25772: ArrayField: incorrent len lookup on empty arrays (was: ArrayField: incorrent len lookup)

2015-11-19 Thread Django

#25772: ArrayField: incorrent len lookup on empty arrays
--+
 Reporter:  mrAdm |Owner:
 Type:  Bug   |   Status:  new
Component:  contrib.postgres  |  Version:  1.8
 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 timgraham):

 * stage:  Unreviewed => Accepted


Comment:

 Regression test attached.

--
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/063.a69bf2bf201957b0835956c6b6a2649d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25639: Cascade deleting cause deadlock

2015-11-19 Thread Django

#25639: Cascade deleting cause deadlock
-+-
 Reporter:  shellfly |Owner:  shellfly
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  db deadlock  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_tests:  1 => 0


Comment:

 [https://github.com/django/django/pull/5513 PR]

--
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.c7bc5482cb6fe119cb7ed83ab2bcf26f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25772: ArrayField: incorrent len lookup on empty arrays

2015-11-19 Thread Django

#25772: ArrayField: incorrent len lookup on empty arrays
--+
 Reporter:  mrAdm |Owner:
 Type:  Bug   |   Status:  new
Component:  contrib.postgres  |  Version:  1.8
 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 timgraham):

 * Attachment "25772-test.diff" added.


--
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/063.6e9ac49cb803d0b77c5a3ec502bb7f2b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #15910: show delete links for all admin inline formset rows

2015-11-19 Thread Django

#15910: show delete links for all admin inline formset rows
-+-
 Reporter:  Arthur de Jong   |Owner:  nobody
   |
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  1.3
 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:  1
-+-
Changes (by timgraham):

 * needs_better_patch:  1 => 0
 * needs_tests:  1 => 0


Comment:

 [https://github.com/django/django/pull/5594 PR]

--
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/089.70cadc33b8f45eb3a186a23d731128df%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #25778: Update docs links to use https

2015-11-19 Thread Django

#25778: Update docs links to use https
+
   Reporter:  timgraham |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Documentation |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  1
  UI/UX:  0 |
+
 Search the docs for links using "http:" and update them to "https:" for
 all sites that support it.

--
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.f3ca8d0f019c0a23af9a213cda3e1b44%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25680: Add support for manage.py shell -e 'run_some_code_as_django()' (was: Feature request: support python manage.py shell -e 'run_some_code_as_django()')

2015-11-19 Thread Django

#25680: Add support for manage.py shell -e 'run_some_code_as_django()'
-+-
 Reporter:  hakanw   |Owner:
 |  nielsvanoch
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  1.8
  commands)  |
 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:  0
-+-
Changes (by timgraham):

 * needs_better_patch:  0 => 1


Comment:

 Left comments for improvement on the pull request.

--
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.c75992a5e15e5726b02c8def3514d710%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25769: Update utils.version.get_version() for new release candidate naming scheme

2015-11-19 Thread Django

#25769: Update utils.version.get_version() for new release candidate naming 
scheme
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Utilities |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"4921d4e59f06c8add15a347c8b97b72b8d9baa74" 4921d4e5]:
 {{{
 #!CommitTicketReference repository=""
 revision="4921d4e59f06c8add15a347c8b97b72b8d9baa74"
 Fixed #25769 -- Updated get_version() release candidate naming for PEP
 0440.
 }}}

--
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.7d2f0cdf1365f2aa43e299d599ff50c9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25438: Oracle GIS test failures for Django 1.9

2015-11-19 Thread Django

#25438: Oracle GIS test failures for Django 1.9
+
 Reporter:  timgraham   |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  GIS |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  oracle 1.9  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by timgraham):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/5684 PR]

--
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.bca79e2f1929e83dac11ba2c8abe8faa%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25438: Oracle GIS test failures for Django 1.9

2015-11-19 Thread Django

#25438: Oracle GIS test failures for Django 1.9
+
 Reporter:  timgraham   |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  GIS |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  oracle 1.9  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by timgraham):

 * status:  closed => new
 * has_patch:  1 => 0
 * resolution:  fixed =>


Comment:

 `test_difference` and `test_difference_mixed_srid` still fail on the 1.9
 branch.
 {{{
 ==
 FAIL [0.102s]: test_difference
 (gis_tests.geoapp.test_functions.GISFunctionsTests)
 --
 Traceback (most recent call last):
   File "/home/jenkins/workspace/django-
 
oracle-1.9/database/oragis12/label/trusty/python/python2.7/django/test/testcases.py",
 line 1093, in skip_wrapper
 return test_func(*args, **kwargs)
   File "/home/jenkins/workspace/django-
 
oracle-1.9/database/oragis12/label/trusty/python/python2.7/tests/gis_tests/geoapp/test_functions.py",
 line 180, in test_difference
 self.assertEqual(c.mpoly.difference(geom), c.diff)
 AssertionError:  != 

 ==
 FAIL [0.120s]: test_difference_mixed_srid
 (gis_tests.geoapp.test_functions.GISFunctionsTests)
 --
 Traceback (most recent call last):
   File "/home/jenkins/workspace/django-
 
oracle-1.9/database/oragis12/label/trusty/python/python2.7/django/test/testcases.py",
 line 1093, in skip_wrapper
 return test_func(*args, **kwargs)
   File "/home/jenkins/workspace/django-
 
oracle-1.9/database/oragis12/label/trusty/python/python2.7/tests/gis_tests/geoapp/test_functions.py",
 line 191, in test_difference_mixed_srid
 self.assertEqual(c.mpoly.difference(geom), c.difference)
 AssertionError:  != 
 }}}

--
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.12a46acf9519998b5391bb5a57db576c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25677: compilemessages throws an exception and does not report msgformat errors correctly

2015-11-19 Thread Django

#25677: compilemessages throws an exception and does not report msgformat errors
correctly
-+-
 Reporter:  gavinwahl|Owner:  Claude
 |  Paroz 
 Type:  Bug  |   Status:  closed
Component:   |  Version:  master
  Internationalization   |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz ):

 * status:  new => closed
 * owner:   => Claude Paroz 
 * resolution:   => fixed


Comment:

 In [changeset:"fa08d27fb714534670b431fde0cd04a17d637585" fa08d27f]:
 {{{
 #!CommitTicketReference repository=""
 revision="fa08d27fb714534670b431fde0cd04a17d637585"
 Fixed #25677 -- Prevented decoding errors in/after Popen calls

 Thanks Gavin Wahl for the report and Tim Graham for the 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/067.4de0562f758ab491ccbe62c323dbd47e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25438: Oracle GIS test failures for Django 1.9

2015-11-19 Thread Django

#25438: Oracle GIS test failures for Django 1.9
+
 Reporter:  timgraham   |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  GIS |  Version:  master
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  oracle 1.9  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by Tim Graham ):

 In [changeset:"ad0056567b611bad3422af6b99c935b4efce0316" ad005656]:
 {{{
 #!CommitTicketReference repository=""
 revision="ad0056567b611bad3422af6b99c935b4efce0316"
 [1.9.x] Fixed #25438 -- Fixed assorted Oracle GIS test failures.

 Backport of 58379d7e958fdf024f896b86f7df3415ce876200 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.4834466cd79e1c4bf8df6eeea949dfae%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25438: Oracle GIS test failures for Django 1.9

2015-11-19 Thread Django

#25438: Oracle GIS test failures for Django 1.9
+
 Reporter:  timgraham   |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  GIS |  Version:  master
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  oracle 1.9  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"58379d7e958fdf024f896b86f7df3415ce876200" 58379d7e]:
 {{{
 #!CommitTicketReference repository=""
 revision="58379d7e958fdf024f896b86f7df3415ce876200"
 Fixed #25438 -- Fixed assorted Oracle GIS test failures.
 }}}

--
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.528df8fb49f6cef95ed300188173181f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #18914: Add a way to add items to the admin's object tools using Python code

2015-11-19 Thread Django

#18914: Add a way to add items to the admin's object tools using Python code
+
 Reporter:  mcrute  |Owner:  auvipy
 Type:  New feature |   Status:  assigned
Component:  contrib.admin   |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  admin object-tools  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+

Comment (by auvipy):

 Replying to [comment:5 manelclos]:
 > Nice, also see this project solving the issue:
 https://github.com/praekelt/django-object-tools

 are you planning to work on this ticket?

--
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.985edcfd128c0757f31885f110222c1e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #18914: Add a way to add items to the admin's object tools using Python code

2015-11-19 Thread Django

#18914: Add a way to add items to the admin's object tools using Python code
+
 Reporter:  mcrute  |Owner:  auvipy
 Type:  New feature |   Status:  assigned
Component:  contrib.admin   |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  admin object-tools  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+

Comment (by manelclos):

 Nice, also see this project solving the issue: https://github.com/praekelt
 /django-object-tools

--
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.4312d1de4a997f279c19386384fc4c6f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #14370: Adding support for Autocomplete in contrib.admin

2015-11-19 Thread Django

#14370: Adding support for Autocomplete in contrib.admin
-+-
 Reporter:  tyrion   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  autocomplete,| Triage Stage:  Accepted
  jquery, javascript, widgets,   |
  admin  |
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-

Comment (by jpic):

 Since codingjoe told me a couple of days ago that he didn't know about
 django-autocomplete-light (which i maintain) before he took over on
 django-select2, it should be mentioned that django-autocomplete-light also
 has support for generic foreign key which we might want in django admin as
 well (and it supports django-generic-m2m too), supports add-another (even
 outside the admin) and so on. While django-select2 might be lucky enough
 that it gets its features inside contrib.admin, I'm affraid that DAL will
 still require maintainance even in future versions of django. Anyway,
 autocompletion is a really rich subject and I recommend to write the
 documentation before the implementation itself, which use cases do you
 want to support and so on.

--
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.a0cdbcc4cb2c17276f03c9496701cd47%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25777: Django admin/views don't expect forms to fail after validation

2015-11-19 Thread Django

#25777: Django admin/views don't expect forms to fail after validation
---+--
 Reporter:  vzima  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.8
 Severity:  Normal |   Resolution:  wontfix
 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 timgraham):

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


Comment:

 This would be a fundamental change in the design of Django and should
 first be discussed on the DevelopersMailingList to find a consensus.
 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/063.70e5876f543d75da659d5dc319aa7426%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #25777: Django admin/views don't expect forms to fail after validation

2015-11-19 Thread Django

#25777: Django admin/views don't expect forms to fail after validation
---+
 Reporter:  vzima  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.8
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Django assumes that all input data in forms can be validated by
 `Form.is_valid()` which is not true. Database contraints, e.g. unique, can
 fail even though they are checked. An application may require
 communication with other servers while processing data which can lead to
 errors.

 Both Django admin and generic form views should expect that `save` may
 fail despite the validation and provide a way to handle those errors
 easily, e.g. expect `ValidationError` can be raised by `Model.save` and
 `ModelForm.save` etc.

--
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.3b7b5cb558328c607465829fd9481057%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25776: Generic way in the admin to add tools to object-tools-items

2015-11-19 Thread Django

#25776: Generic way in the admin to add tools to object-tools-items
---+--
 Reporter:  manelclos  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  contrib.admin  |  Version:  1.8
 Severity:  Normal |   Resolution:  duplicate
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  1
---+--
Changes (by timgraham):

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


Comment:

 Duplicate of #18914

--
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.9b28a9592e8d84c2e3e972f4bb95ad21%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #18914: Add a way to add items to the admin's object tools using Python code (was: Object tools improvements)

2015-11-19 Thread Django

#18914: Add a way to add items to the admin's object tools using Python code
+
 Reporter:  mcrute  |Owner:  auvipy
 Type:  New feature |   Status:  assigned
Component:  contrib.admin   |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  admin object-tools  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+

Comment (by timgraham):

 #25776 is a duplicate.

--
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.fd8ad6e31c151afa77aa807e583fd102%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #11560: let proxy models multiple-inherit from the same concrete base model

2015-11-19 Thread Django

#11560: let proxy models multiple-inherit from the same concrete base model
-+-
 Reporter:  rfk  |Owner:  auvipy
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 I don't know of any work that would have resolved this ticket.

--
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.cfda56a012efed52ffae44e188aa83c3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25775: Method log_message in server.py uses sys.stderr.write, not logging

2015-11-19 Thread Django

#25775: Method log_message in server.py uses sys.stderr.write, not logging
-+-
 Reporter:  soar |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  HTTP handling|  Version:  1.8
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  log, logging,| Triage Stage:
  stdout |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Duplicate of #25684

--
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/062.bdd288473c53a35b1a1e2885a94eae21%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25774: Refactor of datetime expressions and better, official support for right-hand-side date part extraction

2015-11-19 Thread Django

* stage: Unreviewed => Accepted

Comment:

I think you're on the right track for most of these points. I'm not yet
convinced that adding `DateExtract` is necessary, but once the patch is
written I'll take another look then. I just worry that there'll be two
ways to extract a date part and that may lead to confusion.

Would like others opinions on ExtractX rather than XExtract. I think it
reads and sorts better.

YearLookup and YearComparisonLookup are going to be interesting. They'll
still need to work the same way when used on the left hand side. Perhaps
we can rename to YearLookupOptimised (for example, that's a bad name) and
register that as a lookup, but provide a different ExtractYear that does
what you'd expect on the right hand side. The optimised version would then
just be a hidden implementation detail that users shouldn't touch
themselves.

I'll have a look at the actual PR tomorrow. Great work so far.

--
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.8780ec1184a492b977da0f5812fadc56%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25734: Nodata value not excluded when computing GDALBand min/max values

2015-11-19 Thread Django

#25734: Nodata value not excluded when computing GDALBand min/max values
-+-
 Reporter:  yellowcap|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  GIS  |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  raster gdal gis  | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by yellowcap):

 That's right, I agree that its probably not critical. An alternative
 simple way of "backporting" this would be to change the 1.8 documentation
 on the min/max attributes. The documentation could state that the methods
 might not return the true value if they are not already stored internally
 in the raster or in a metatdata file. However I am not sure if that would
 be good practice either.

--
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.213e063ffb97318234ecd0438edbcc41%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25776: Generic way in the admin to add tools to object-tools-items

2015-11-19 Thread Django

#25776: Generic way in the admin to add tools to object-tools-items
---+--
 Reporter:  manelclos  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  contrib.admin  |  Version:  1.8
 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:  1
---+--
Changes (by manelclos):

 * needs_docs:   => 0
 * component:  Uncategorized => contrib.admin
 * 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/067.14e47e8702cb677f67560b04915688ef%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #25776: Generic way in the admin to add tools to object-tools-items

2015-11-19 Thread Django

#25776: Generic way in the admin to add tools to object-tools-items
---+
 Reporter:  manelclos  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.8
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  1
---+
 If you have two different apps that affect the admin, say django-reversion
 and django-import-export, depending on the Mixins order in your ModelAdmin
 definition you will get the tool button for one or the other. As this
 works by extending the "admin/change_list.html" template and extending the
 "object-tools-items" block, only the last one processed gets into the
 final template.

 If this was a ModelAdmin method like get_object_tools_items_html(), then
 it would be chainable.

--
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.fb7d9ad347d5719100ef752ee6d52dfc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #25775: Method log_message in server.py uses sys.stderr.write, not logging

2015-11-19 Thread Django

#25775: Method log_message in server.py uses sys.stderr.write, not logging
--+--
 Reporter:  soar  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  HTTP handling |Version:  1.8
 Severity:  Normal|   Keywords:  log, logging, stdout
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+--
 I try to capture all log output of my Django-based project, but logged
 requests like:

 {{{
 [19/Nov/2015 12:30:12] "GET / HTTP/1.1" 200 12898
 [19/Nov/2015 12:37:32] "GET /favicon.ico HTTP/1.1" 302 0
 }}}

 can't be catched, reformatted, etc. I found line, where this log caused:

 {{{#!python
 def log_message(self, format, *args):
 """Log an arbitrary message.

 This is used by all other logging functions.  Override
 it if you have specific logging wishes.

 The first argument, FORMAT, is a format string for the
 message to be logged.  If the format string contains
 any % escapes requiring parameters, they should be
 specified as subsequent arguments (it's just like
 printf!).

 The client ip and current date/time are prefixed to
 every message.

 """

 sys.stderr.write("%s - - [%s] %s\n" %
  (self.client_address[0],
   self.log_date_time_string(),
   format%args))
 }}}

 So, why you use `sys.stderr.write()`, not
 `logging.debug()/info()/warn()/etc`?

--
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.a2ac44856ff2104a9b652acd73b4e3a1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25741: Make 'request' available to syndication.Feed methods

2015-11-19 Thread Django

#25741: Make 'request' available to syndication.Feed methods
-+-
 Reporter:  RamezIssac   |Owner:
 Type:   |  alexmorozov
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.syndication  |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  syndication, | Triage Stage:  Accepted
  request|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by alexmorozov):

 * easy:  1 => 0


Comment:

 Clearing the 'Easy pickings' flag, as it is obviously not the case.

--
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.f9b4373a4582a761f53038e7ee1b7867%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25713: Create an alternative tutorial targeted at those familar with HTML/CSS rather than Python

2015-11-19 Thread Django

#25713: Create an alternative tutorial targeted at those familar with HTML/CSS
rather than Python
---+
 Reporter:  EvilDMP|Owner:  nobody
 Type:  New feature|   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
---+

Comment (by auvipy):

 Replying to [comment:2 timgraham]:
 > To avoid duplicating effort in the community, I'm attracted to the
 alternative of pointing to other tutorials (like
 [http://tutorial.djangogirls.org/ DjangoGirls]) that target non-
 programmers, but to help make a decision, I don't mind looking at what you
 prepare.

 +1 for your thought

--
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.5e2b3d8b9235a1ba4e41c64efd64eb62%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #11560: let proxy models multiple-inherit from the same concrete base model

2015-11-19 Thread Django

Comment (by auvipy):

Replying to [comment:10 timgraham]:
> The patch needs to be updated to apply cleanly. If you can update it and
send a pull request, that will help. Also a mention in the release notes
and a `.. versionchanged:: 1.8` annotation would be helpful. See our
[https://docs.djangoproject.com/en/dev/internals/contributing/writing-code
/submitting-patches/#patch-review-checklist patch review checklist].

Hi Tim,

Is this issue already resolved by other works ? or I should work on the
patch to implement it cleanly?

--
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.0cfdd6b8262fac7e1d02e8ee00c88268%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

54 matches

Mail list logo