Re: [Django] #24514: Unused import on some auto generated migrations

[Django]

#24514: Unused import on some auto generated migrations
-+-
 Reporter:  hugotacito   |Owner:  chrisjluc
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Migrations   |  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  unused import| Triage Stage:  Accepted
  migrations |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by chrisjluc):

 * owner:  nobody => chrisjluc
 * 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/068.38b8cef6f220a378f23bada4338f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24281: Improve docs for auto_now & auto_now_add and timezone handling

[Django]

#24281: Improve docs for auto_now & auto_now_add and timezone handling
-+-
 Reporter:  djbug|Owner:  chrisjluc
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  timezone | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by chrisjluc):

 * owner:  nobody => chrisjluc
 * 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/063.d20a2a666c45c02f26c1b560792b05f9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24244: Document contrib.admin.models.LogEntry

[Django]

#24244: Document contrib.admin.models.LogEntry
--+
 Reporter:  timgraham |Owner:  varun
 Type:  New feature   |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by varun):

 * has_patch:  0 => 1


Comment:

 PR: https://github.com/django/django/pull/4363

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

Re: [Django] #24244: Document contrib.admin.models.LogEntry

[Django]

#24244: Document contrib.admin.models.LogEntry
--+
 Reporter:  timgraham |Owner:  varun
 Type:  New feature   |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by varun):

 * Attachment "ticket_24244.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/067.292bb949cf167d4a0218a98e21cac36d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #18586: Rewrite unit tests migrated from doctests

[Django]

#18586: Rewrite unit tests migrated from doctests
-+-
 Reporter:  konk |Owner:
 Type:   |  alainivars
  Cleanup/optimization   |   Status:  assigned
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  unit tests   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by alainivars):

 * owner:   => alainivars
 * 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/066.4597fe2d82f30c0b14a8f84afc26e70c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24361: The doc is not right w.r.t. LOGGING overwriting.

[Django]

#24361: The doc is not right w.r.t. LOGGING overwriting.
---+
 Reporter:  Tuttle |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  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
---+

Comment (by timgraham):

 I lightly edited your patch and
 [https://github.com/django/django/pull/4362 created a pull request] so
 others can offer their thoughts. I also [https://groups.google.com/d/topic
 /django-developers/no2IhnRty68/discussion posted to django-developers] to
 see if we can improve the state of logging in Django more generally.

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

Re: [Django] #24347: parameter 'widget' of BoundField.as_widget is ignored

[Django]

#24347: parameter 'widget' of BoundField.as_widget is ignored
-+-
 Reporter:  srkunze  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.8beta1
 Severity:  Normal   |   Resolution:
 Keywords:  BoundField,  | Triage Stage:  Accepted
  as_widget  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-

Comment (by srkunze):

 > Well, I guess we can accept the ticket, but even after spending time
 looking at it, I still don't have a good understanding of the problem(s)

 I actually hoped you would be the one telling me. :D

 > or what a solution might look like.

 After our conversation and looking at the test-cases, I am even unsure if
 my patch would touch the heart of the problem.

 That is, btw., why I asked about the relationship between data and value.
 However, as it seems the problem lies even deeper.

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

Re: [Django] #12400: column "X" named in key does not exist error when models.PointField used in unique_together

[Django]

#12400: column "X" named in key does not exist error when models.PointField 
used in
unique_together
+
 Reporter:  monkut  |Owner:  claudep
 Type:  Bug |   Status:  assigned
Component:  GIS |  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):

 * owner:  jbronn => claudep
 * status:  new => assigned
 * has_patch:  0 => 1


Comment:

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

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

[Django] #24519: Language mismatch (word: project) between tutorial01 and tutorial02

[Django]

#24519: Language mismatch (word: project) between tutorial01 and tutorial02
--+
 Reporter:  kevinconway   |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.7
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 Tutorial01 defines a project as "a collection of configuration and apps
 for a particular Web site" which specifically refers to the Python package
 generated by "{{{django-admin startproject }}}".

 In tutorial02, while modifying the look and feel of the admin page, the
 guide asks the user to create a "templates" directory within the project
 and add "{{{TEMPLATE_DIRS = [os.path.join(BASE_DIR, 'templates')]}}}" to
 the settings.py which is also within the project. However, the
 "{{{BASE_DIR}}}" value resolves to the directory containing the django
 project Python package rather than the Python package itself as the
 default value is "{{{os.path.dirname(os.path.dirname(__file__))}}}".

 The documentation should clarify in tutorial02 whether project refers to
 the django project or the containing directory.

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

Re: [Django] #11997: cache_control returns 200 OK response even page has not been changed.

[Django]

#11997: cache_control returns 200 OK response even page has not been changed.
-+-
 Reporter:  jtiai|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Cache system)  |  Version:  master
 Severity:  Normal   |   Resolution:  needsinfo
 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):

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


Comment:

 I think that the response of the server is strongly dependent of installed
 middlewares. Typically, the 304 response you expect would be produced by
 the `ConditionalGetMiddleware`.

 If you still suffer from this issue, the best step forward would be to
 setup a minimal project to reproduce the issue, so as we can debug cache
 and middleware interactions.

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

Re: [Django] #12139: forms.fields.DateTimeField and TimeField so not accept stringified datetimes

[Django]

#12139: forms.fields.DateTimeField and TimeField so not accept stringified
datetimes
-+-
 Reporter:  mattbennett  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  datetime, forms, | Triage Stage:  Accepted
  datetimefield, timefield   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

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


Comment:

 I don't think this is a problem any longer nowadays.
 See #9459/[dce278673a409a10c1f74f597035b737bbf6a017]
 and #19917 [384c180e414a982a6cc5ccabc675bcfb4fd80988]

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

Re: [Django] #24500: Django runtests - 3 tests fail on windows due to encoding troubles

[Django]

#24500: Django runtests - 3 tests fail on windows due to encoding troubles
-+-
 Reporter:  pakal|Owner:  nobody
 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:"dc2cff5fcbbff207dc99d262e9f13de954c7267e" dc2cff5]:
 {{{
 #!CommitTicketReference repository=""
 revision="dc2cff5fcbbff207dc99d262e9f13de954c7267e"
 [1.8.x] Fixed #24500 -- Fixed makemessages encoding problems retrieving
 gettext version.

 Backport of 53c2cf1e7b3f1c9a7794fcc5c4669145f351b2fa 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/063.4b7304f8958ddaa52ae551022e378229%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24500: Django runtests - 3 tests fail on windows due to encoding troubles

[Django]

#24500: Django runtests - 3 tests fail on windows due to encoding troubles
-+-
 Reporter:  pakal|Owner:  nobody
 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 Tim Graham ):

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


Comment:

 In [changeset:"53c2cf1e7b3f1c9a7794fcc5c4669145f351b2fa" 53c2cf1e]:
 {{{
 #!CommitTicketReference repository=""
 revision="53c2cf1e7b3f1c9a7794fcc5c4669145f351b2fa"
 Fixed #24500 -- Fixed makemessages encoding problems retrieving gettext
 version.
 }}}

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

Re: [Django] #24215: Refactor of lazy model operations

[Django]

#24215: Refactor of lazy model operations
-+-
 Reporter:  AlexHill |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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:

 PR #4122 is merged. I left some minor comments on #4130, but suggest we
 wait until #4241 to avoid creating more work for Anssi.

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

Re: [Django] #24500: Django runtests - 3 tests fail on windows due to encoding troubles

[Django]

#24500: Django runtests - 3 tests fail on windows due to encoding troubles
-+-
 Reporter:  pakal|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  master
  Internationalization   |
 Severity:  Normal   |   Resolution:
 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 claudep):

 Apart from a minor note on the PR, it's fine for me.

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

Re: [Django] #16362: Ignore, rather than disallow, negative lookahead assertions

[Django]

#16362: Ignore, rather than disallow, negative lookahead assertions
-+-
 Reporter:  charles@…|Owner:  bpeschier
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Core (URLs)  |  Version:  1.3
 Severity:  Normal   |   Resolution:
 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 timgraham):

 * stage:  Accepted => Ready for checkin


Comment:

 Looks good, pending some cosmetic comments.

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

Re: [Django] #24394: Running tests fails when DATABASES['default'] = {}

[Django]

#24394: Running tests fails when DATABASES['default'] = {}
---+
 Reporter:  trecouvr   |Owner:  akulakov
 Type:  Bug|   Status:  assigned
Component:  Testing framework  |  Version:  1.7
 Severity:  Normal |   Resolution:
 Keywords:  test   | 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_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/066.d20d7cf26bc5d48a54720ac6cd300b91%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #13525: Document how to reverse URL patterns with nested groups (was: URL Reverser chokes on nested groups)

[Django]

#13525: Document how to reverse URL patterns with nested groups
-+-
 Reporter:  nickretallack|Owner:  bpeschier
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.1
 Severity:  Normal   |   Resolution:
 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 timgraham):

 * stage:  Accepted => Ready for checkin


Comment:

 Looks good, pending some cosmetic comments.

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

Re: [Django] #15815: Support memcached binary protocol in PyLibMCCache

[Django]

#15815: Support memcached binary protocol in PyLibMCCache
-+
 Reporter:  mtigas   |Owner:
 Type:  New feature  |   Status:  new
Component:  Core (Cache system)  |  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:  sprint2013   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by bpeschier):

 * owner:  bpeschier =>
 * status:  assigned => new


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

Re: [Django] #24500: Django runtests - 3 tests fail on windows due to encoding troubles

[Django]

#24500: Django runtests - 3 tests fail on windows due to encoding troubles
-+-
 Reporter:  pakal|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  master
  Internationalization   |
 Severity:  Normal   |   Resolution:
 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 timgraham):

 * stage:  Accepted => Ready for checkin


Comment:

 [https://github.com/django/django/pull/4359 PR]; tests seem fine on CI and
 my Windows setup. Claude does the code look fine?

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

Re: [Django] #16362: Ignore, rather than disallow, negative lookahead assertions

[Django]

#16362: Ignore, rather than disallow, negative lookahead assertions
-+-
 Reporter:  charles@…|Owner:  bpeschier
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Core (URLs)  |  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:  0
-+-
Changes (by bpeschier):

 * owner:  nobody => bpeschier
 * needs_docs:  1 => 0
 * status:  new => assigned
 * needs_tests:  1 => 0


Comment:

 It was never documented that it was not allowed except for the source
 comments above {{{normalize}}}. These assertions are part of a valid
 regular expression, so I only added a release note.

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

Re: [Django] #1919: filter truncatewords is inefficient and destroys white space

[Django]

#1919: filter truncatewords is inefficient and destroys white space
-+
 Reporter:  derelm   |Owner:  gcc
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  sprintsept14 | 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):

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


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

Re: [Django] #24479: Add a system check to prevent defining both ordering and order_with_respect_to

[Django]

#24479: Add a system check to prevent defining both ordering and
order_with_respect_to
-+-
 Reporter:  blueyed  |Owner:  Tim
 |  Graham 
 Type:  New feature  |   Status:  closed
Component:  Core (System |  Version:  master
  checks)|
 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
 * owner:   => Tim Graham 
 * resolution:   => fixed


Comment:

 In [changeset:"966a29c2b83fed2fc7c2b5b09de80cbebc94ac74" 966a29c]:
 {{{
 #!CommitTicketReference repository=""
 revision="966a29c2b83fed2fc7c2b5b09de80cbebc94ac74"
 Fixed #24479 -- Added system check to prevent both ordering and order_wrt.
 }}}

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

Re: [Django] #24515: Plural handling broken

[Django]

#24515: Plural handling broken
-+-
 Reporter:  claudep  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:   |  Version:  1.8rc1
  Internationalization   |
 Severity:  Release blocker  |   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 Claude Paroz ):

 In [changeset:"8e4b0d60109950c3dd0d500feb30d95fb716325c" 8e4b0d6]:
 {{{
 #!CommitTicketReference repository=""
 revision="8e4b0d60109950c3dd0d500feb30d95fb716325c"
 [1.8.x] Fixed #24515 -- Fixed DjangoTranslation plural handling

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

Re: [Django] #24515: Plural handling broken

[Django]

#24515: Plural handling broken
-+-
 Reporter:  claudep  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:   |  Version:  1.8rc1
  Internationalization   |
 Severity:  Release blocker  |   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
 * resolution:   => fixed


Comment:

 In [changeset:"9e83f30cd318693995decebdc68433853e93a6bb" 9e83f30]:
 {{{
 #!CommitTicketReference repository=""
 revision="9e83f30cd318693995decebdc68433853e93a6bb"
 Fixed #24515 -- Fixed DjangoTranslation plural handling
 }}}

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

Re: [Django] #24518: OptionParser verbosity not cast to int (Python3)

[Django]

#24518: OptionParser verbosity not cast to int (Python3)
-+-
 Reporter:  jthi3rry |Owner:  jthi3rry
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  1.8rc1
  commands)  |
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by claudep):

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


Comment:

 I'm not sure we want to change that. If you look at Django management
 commands in pre-1.8 versions, you'll read many `self.verbosity =
 int(options.get('verbosity'))` or `if int(options['verbosity']) > 0:`
 patterns. The future is definitely using `argparse`, so if for any reason
 you still want to keep using `optparse`, you should continue to cast the
 result of the `verbosity` option to `int`.
 Your proposed patch would remove the option list checking of `verbosity`,
 which would be slightly backwards incompatible.

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

Re: [Django] #6363: Bug with has_permission method of AdminSite class.

[Django]

#6363: Bug with has_permission method of AdminSite class.
---+--
 Reporter:  michelts   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  newforms-admin
 Severity:  Normal |   Resolution:
 Keywords:  nfa-someday| Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by claudep):

 The visual quirk about user tools is gone. But there is still a small
 difference in that the authentication simply refuse the login and
 redisplay the login form without any explanation (like it would have given
 if user is not staff or password is wrong).

 Tentative resolution:
 {{{
 #!diff
 diff --git a/django/contrib/admin/forms.py b/django/contrib/admin/forms.py
 index 2e482b9..f40b2fc 100644
 --- a/django/contrib/admin/forms.py
 +++ b/django/contrib/admin/forms.py
 @@ -17,7 +17,7 @@ class AdminAuthenticationForm(AuthenticationForm):
  required_css_class = 'required'

  def confirm_login_allowed(self, user):
 -if not user.is_active or not user.is_staff:
 +if not self.request.admin_site.has_permission(self.request):
  raise forms.ValidationError(
  self.error_messages['invalid_login'],
  code='invalid_login',
 diff --git a/django/contrib/admin/sites.py b/django/contrib/admin/sites.py
 index 4b5ee57..ff6767f 100644
 --- a/django/contrib/admin/sites.py
 +++ b/django/contrib/admin/sites.py
 @@ -392,6 +392,7 @@ class AdminSite(object):
  'authentication_form': self.login_form or
 AdminAuthenticationForm,
  'template_name': self.login_template or 'admin/login.html',
  }
 +request.admin_site = self
  return login(request, **defaults)

  @never_cache
 }}}

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