date:20131007

Re: [Django] #21236: Migrations: error applying unique_together

2013-10-07 Thread Django

#21236: Migrations: error applying unique_together
-+-
 Reporter:  hjwp |Owner:  Tim
 Type:  Bug  |  Graham 
Component:  Migrations   |   Status:  closed
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by tuxcanfly):

 Thanks to hjwp for the detailed bug report and Tim Graham for reviewing
 and merging the patch!

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

Re: [Django] #21164: get_user_model() does not handle custom user models for testing purposes

2013-10-07 Thread Django

#21164: get_user_model() does not handle custom user models for testing purposes
---+---
 Reporter:  raymond.penners@…  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.auth   |  Version:  1.6-alpha-1
 Severity:  Release blocker|   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
---+---

Comment (by Russell Keith-Magee ):

 In [changeset:"1ab84b6c653c3169994064f7c1772a8e869c7282"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1ab84b6c653c3169994064f7c1772a8e869c7282"
 [1.6.x] Fixed #21164 -- Added documentation for issue with test users.

 The package renaming restores the older package names (which were also the
 documented package names). This doesn't affect test discovery because the
 module in question doesn't contain any tests.

 Thanks to Carl for the design discussion.

 Backport of ddb5385 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/084.4df5f73d1af6005d4e5f50498a09dc76%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 1ab84b: [1.6.x] Fixed #21164 -- Added documentation for is...

2013-10-07 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 1ab84b6c653c3169994064f7c1772a8e869c7282
  
https://github.com/django/django/commit/1ab84b6c653c3169994064f7c1772a8e869c7282
  Author: Russell Keith-Magee 
  Date:   2013-10-07 (Mon, 07 Oct 2013)

  Changed paths:
A django/contrib/auth/tests/custom_user.py
M django/contrib/auth/tests/test_auth_backends.py
M django/contrib/auth/tests/test_basic.py
R django/contrib/auth/tests/test_custom_user.py
M django/contrib/auth/tests/test_handlers.py
M django/contrib/auth/tests/test_management.py
M docs/releases/1.6.txt
M docs/topics/auth/customizing.txt

  Log Message:
  ---
  [1.6.x] Fixed #21164 -- Added documentation for issue with test users.

The package renaming restores the older package names (which were also the
documented package names). This doesn't affect test discovery because the
module in question doesn't contain any tests.

Thanks to Carl for the design discussion.

Backport of ddb5385 from master.



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

Re: [Django] #21164: get_user_model() does not handle custom user models for testing purposes

2013-10-07 Thread Django

#21164: get_user_model() does not handle custom user models for testing purposes
---+---
 Reporter:  raymond.penners@…  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.auth   |  Version:  1.6-alpha-1
 Severity:  Release blocker|   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 Russell Keith-Magee ):

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


Comment:

 In [changeset:"ddb53856b62506128a6d19184dfa80da73c77db8"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ddb53856b62506128a6d19184dfa80da73c77db8"
 Fixed #21164 -- Added documentation for issue with test users.

 The package renaming restores the older package names (which were also the
 documented package names). This doesn't affect test discovery because the
 module in question doesn't contain any tests.

 Thanks to Carl for the design 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/084.17e40a6fc3aa7800a518901c8f3256a8%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] ddb538: Fixed #21164 -- Added documentation for issue with...

2013-10-07 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ddb53856b62506128a6d19184dfa80da73c77db8
  
https://github.com/django/django/commit/ddb53856b62506128a6d19184dfa80da73c77db8
  Author: Russell Keith-Magee 
  Date:   2013-10-07 (Mon, 07 Oct 2013)

  Changed paths:
A django/contrib/auth/tests/custom_user.py
M django/contrib/auth/tests/test_auth_backends.py
M django/contrib/auth/tests/test_basic.py
R django/contrib/auth/tests/test_custom_user.py
M django/contrib/auth/tests/test_handlers.py
M django/contrib/auth/tests/test_management.py
M docs/releases/1.6.txt
M docs/topics/auth/customizing.txt

  Log Message:
  ---
  Fixed #21164 -- Added documentation for issue with test users.

The package renaming restores the older package names (which were also the
documented package names). This doesn't affect test discovery because the
module in question doesn't contain any tests.

Thanks to Carl for the design discussion.



-- 
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/52536f5eb505d_49c9114bd50853db%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21164: get_user_model() does not handle custom user models for testing purposes

2013-10-07 Thread Django

#21164: get_user_model() does not handle custom user models for testing purposes
---+---
Reporter: raymond.penners@… |Owner: nobody
Type: Bug| Status: new
Component: contrib.auth | Version: 1.6-alpha-1
Severity: Release blocker| 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 russellm):

@carljm -- I don't think the "models in test models" thing is documented,
but it's definitely in wide use -- Django's own test suite has a couple of
places where models are defined in the tests package -- (e.g., the
app_cache tests). In most cases it's a non-issue, because if you're
running the tests for a module, then you're probably importing everything
in that module anyway. This is an odd case because the auth tests won't be
run, but the models we want are stored in the auth tests.

Based on your feedback, I'll commit a patch to docs that clarifies the
need for an explicit import.

--
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/084.3ab7dad6d1c0932218c3d17e3ecbd1d7%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21197: 1.6 compatibility checks don't correctly validate TEST_RUNNER

2013-10-07 Thread Django

#21197: 1.6 compatibility checks don't correctly validate TEST_RUNNER
-+-
 Reporter:  russellm |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:
  commands)  |  1.6-alpha-1
 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 Russell Keith-Magee ):

 In [changeset:"7f0fdffd07df71409fc44a3a039c25bf01ca1310"]:
 {{{
 #!CommitTicketReference repository=""
 revision="7f0fdffd07df71409fc44a3a039c25bf01ca1310"
 [1.6.x] Refs #21197 -- Clarified upgrade check message.

 Thanks to Carl and Shai for the discussion.

 Backport of 8ff4303 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/066.f3dc2dccd44dde88a5364396a7fe1c27%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21197: 1.6 compatibility checks don't correctly validate TEST_RUNNER

2013-10-07 Thread Django

#21197: 1.6 compatibility checks don't correctly validate TEST_RUNNER
-+-
 Reporter:  russellm |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:
  commands)  |  1.6-alpha-1
 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 Russell Keith-Magee ):

 In [changeset:"8ff43039466f5e3c78d3587fdbe229ed44c4e1aa"]:
 {{{
 #!CommitTicketReference repository=""
 revision="8ff43039466f5e3c78d3587fdbe229ed44c4e1aa"
 Refs #21197 -- Clarified upgrade check message.

 Thanks to Carl and Shai for the 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/066.b378121ef9c1c03c3d6474af1f8e2385%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 8ff430: Refs #21197 -- Clarified upgrade check message.

2013-10-07 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 8ff43039466f5e3c78d3587fdbe229ed44c4e1aa
  
https://github.com/django/django/commit/8ff43039466f5e3c78d3587fdbe229ed44c4e1aa
  Author: Russell Keith-Magee 
  Date:   2013-10-07 (Mon, 07 Oct 2013)

  Changed paths:
M django/core/checks/compatibility/django_1_6_0.py
M tests/check/tests.py

  Log Message:
  ---
  Refs #21197 -- Clarified upgrade check message.

Thanks to Carl and Shai for the discussion.



-- 
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/525367d6a5758_764d9f7d4c809e%40hookshot-fe5-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 7f0fdf: [1.6.x] Refs #21197 -- Clarified upgrade check mes...

2013-10-07 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 7f0fdffd07df71409fc44a3a039c25bf01ca1310
  
https://github.com/django/django/commit/7f0fdffd07df71409fc44a3a039c25bf01ca1310
  Author: Russell Keith-Magee 
  Date:   2013-10-07 (Mon, 07 Oct 2013)

  Changed paths:
M django/core/checks/compatibility/django_1_6_0.py
M tests/check/tests.py

  Log Message:
  ---
  [1.6.x] Refs #21197 -- Clarified upgrade check message.

Thanks to Carl and Shai for the discussion.

Backport of 8ff4303 from master.



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

Re: [Django] #21197: 1.6 compatibility checks don't correctly validate TEST_RUNNER

2013-10-07 Thread Django

* severity: Release blocker => Normal

Comment:

@carljm - On reflection, I think I agree that this isn't a release
blocker. There's definitely going to need to be some discussion for 1.7
(around landing the GSoC patch, and/or how the 1.6 warnings will manifest
on a 1.7 upgrade), but I don't think this needs to block 1.6.

That said, I think a minor change in the wording of the error message is
called for; as currently phrased, the message is misleading if you've
upgraded and *have* set TEST_RUNNER to point at the new test runner.

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

Re: [Django] #21197: 1.6 compatibility checks don't correctly validate TEST_RUNNER

2013-10-07 Thread Django

Comment (by carljm):

We already have that page in the docs:
https://docs.djangoproject.com/en/1.5/howto/upgrade-version/

If people read that page in the docs and followed its advice (which
prominently includes reading the release notes for every major version
upgrading across), we wouldn't be having this discussion at all :-) What
we're talking about here is automated help for people who try to upgrade
without reading the relevant docs.

I'm not really sure this ticket should be a 1.6 blocker at all. The
current upgrade-help situation isn't ideal, but we've made backwards-
incompatible changes before using our current documentation, without
automated help, and the ecosystem has lived through it just fine. I think
the upcoming system of automated checks will be a great help, but I'm not
convinced we should be blocking 1.6 on further preparing for it. The
current check in the "check" command is not perfect, but I also don't
think it's broken; given the context of when and how it would be run
(probably not very much), I don't think it's a problem for 1.6 as-is.

--
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.41a81f9d55dfe1b68beb511518d460e8%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21164: get_user_model() does not handle custom user models for testing purposes

2013-10-07 Thread Django

#21164: get_user_model() does not handle custom user models for testing purposes
---+---
 Reporter:  raymond.penners@…  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.auth   |  Version:  1.6-alpha-1
 Severity:  Release blocker|   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 carljm):

 @russellm That approach doesn't depend on the auth tests being run, but it
 does still depend on the previously-undocumented "models in test files are
 installed during test runs" behavior. I'm not sure that's behavior that we
 really want to solidify with a backwards-compatibility guarantee, but
 pragmatically given that the testing-custom-users docs already rely on it,
 I'm ok with your suggestion.

-- 
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/084.4842190e464e94e7e89624c99a7f1b8f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #5405: Support restructured text in model docstrings

2013-10-07 Thread Django

#5405: Support restructured text in model docstrings
-+-
 Reporter:  mattmcc  |Owner:  gokmen
 Type:  New feature  |   Status:  assigned
Component:  contrib.admindocs|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  nfa-someday  | Triage Stage:  Accepted
  sprint2013 |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * easy:  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/065.f2dc40e66fda0dec95cd154b13869c76%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19496: truncatechars_html

2013-10-07 Thread Django

#19496: truncatechars_html
-+
 Reporter:  esevece  |Owner:  EvilDMP
 Type:  New feature  |   Status:  assigned
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  truncatchars | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by timo):

 * version:  1.4 => master
 * easy:  1 => 0


Comment:

 I've left some comments on the PR 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/065.8f6a1b92bf64b9c3fea82689c666ea01%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21172: have LiveServerThread follow the semantics of threading.Thread.join()

2013-10-07 Thread Django

#21172: have LiveServerThread follow the semantics of threading.Thread.join()
-+-
 Reporter:  ldd  |Owner:
 Type:  Bug  |  unaizalakain
Component:  Testing framework|   Status:  assigned
 Severity:  Normal   |  Version:  master
 Keywords:  live server, test|   Resolution:
  server, live wsgi  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

 * easy:  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/061.34f761866aebccbc03751ffac134a267%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #13245: manually set db_table should not validate if it needs to be truncated

2013-10-07 Thread Django

#13245: manually set db_table should not validate if it needs to be truncated
-+-
 Reporter:  skoom|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by timo):

 * cc: timo (added)
 * needs_better_patch:  1 => 0
 * has_patch:  1 => 0
 * easy:  0 => 1
 * needs_tests:  1 => 0


Comment:

 The validation should be added in
 `django.core.management.validation.get_validation_errors()` with a test in
 `tests/invalid_models/invalid_models/models.py`. The validation and the
 test will have to be conditional on `connection.ops.max_name_length()` --
 there's already an example in `invalid_models/models.py` for
 `connection.features.interprets_empty_strings_as_nulls`.

-- 
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.1707d178a9329151c02de3f5b0ca83a0%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21126: Potential data corruption issue with Oracle and Mysql due to SQLCompiler.resolve_columns row, fields misalignment

2013-10-07 Thread Django

#21126: Potential data corruption issue with Oracle and Mysql due to
SQLCompiler.resolve_columns row, fields misalignment
-+-
 Reporter:  manfre   |Owner:  manfre
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by manfre):

 Can you write a test that reproduces the problem or at least provide more
 details about what specifically in your project is experiencing the error?
 If you're experiencing the problem with PostgresSQL, then it's probably
 also experienced by all of the other backends.

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

Re: [Django] #21126: Potential data corruption issue with Oracle and Mysql due to SQLCompiler.resolve_columns row, fields misalignment

2013-10-07 Thread Django

Comment (by radicalbiscuit ):

What would the process on that be? I'm entirely prepared to send in a pull
request, but I'm not sure whether to attach it to this issue, reference
the other recent patches, or whether it should really be accepted at all.
I know it fixes my problem, but I haven't been able to find the cause of
my misalignment since I'm using PostgreSQL and `resolve_columns` is
`False`.

Having said that, I don't see how it would break anything, but I'm not
intimately familiar with much of the Django core. And from what I've seen,
most patches require greater justification than "Fixed my problem."

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

Re: [Django] #21238: `ImageFieldFile.url` raises an AttributeError exception after retrieving it from cache

2013-10-07 Thread Django

#21238: `ImageFieldFile.url` raises an AttributeError exception after 
retrieving it
from cache
-+
 Reporter:  dulaccc  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Cache system)  |  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:  imagefield, cache| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by timo):

 * stage:  Unreviewed => Accepted


Comment:

 `ImageFieldFile` inherits from `ImageFile` and `FieldFile`. It looks like
 the problem is due to the fact that `FieldFile.__init__` isn't called when
 the object is retrieved from the cache.  I think the inheritance chain is
 broken because `ImageFile.__init__` (inheriting from
 `django.core.files.base.File`) doesn't call `super`.

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

Re: [Django] #21197: 1.6 compatibility checks don't correctly validate TEST_RUNNER

2013-10-07 Thread Django

#21197: 1.6 compatibility checks don't correctly validate TEST_RUNNER
-+-
 Reporter:  russellm |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:
  commands)  |  1.6-alpha-1
 Severity:  Release blocker  |   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 thepapermen):

 Maybe this could be relevant to the discussion: Ruby on Rails has a
 special "[http://edgeguides.rubyonrails.org/upgrading_ruby_on_rails.html
 #upgrading-from-rails-3-2-to-rails-4-0 Guide for Upgrading Ruby on Rails]"
 page, which has sections that are dedicated to guiding users on how they
 should upgrade the framework from one specific version to another specific
 version. Maybe a special page in the docs and a setting could be good
 enough?

-- 
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.443cbf7f97dad15c921279bdc5168ee0%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21126: Potential data corruption issue with Oracle and Mysql due to SQLCompiler.resolve_columns row, fields misalignment

2013-10-07 Thread Django

#21126: Potential data corruption issue with Oracle and Mysql due to
SQLCompiler.resolve_columns row, fields misalignment
-+-
 Reporter:  manfre   |Owner:  manfre
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by akaariai):

 As we have already backpatched other changes to that part of compiler, I
 can't see what we could possibly lose by backpatching a bit more.

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

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

Re: [Django] #21190: Fix broken ePub documentation by adding a proper theme for it

2013-10-07 Thread Django

* has_patch: 0 => 1

Comment:

I've looked a little. I have to say that I am not thrilled with having to
add epub specific things since this means another thing to think about
when adding new documentation features, but I agree the current version
had some issues that would benefit from this.

I don't get the broken behavior on epub readers that I've tried (Calibre
on Linux and Stanza on iOS). Some of the broken styles seem to be inserted
by the service that builds our epubs, readthedocs.org, so we may want to
coordinate with them to resolve some of these issues.

You could probably use symlinks for the documentation images to avoid
duplicating them.

If you could send a pull request with your branch, that will make
reviewing this easier.

--
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/073.0e9a23963bf2ff1fa0d2edf41aab024a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21173: Django DateTimeInput determines language/locale at startup time but this may change later, resulting in validation errors

2013-10-07 Thread Django

Comment (by claudep):

I think the basic issue is that `widget.is_localized` is False by default,
and contrib.auth forms doesn't set it. In your own forms, you can probably
activate `is_localized` and the `self.format` variable set in the
`__init__` method will not be used.

Personally, I'd vote for setting `is_localized` to the `settings.USE_L10N`
value by default. But this might be backwards incompatible.

A more contained fix would be to let `self.format` to None when it is not
specified in the widget constructor, and then getting the format only if
and when it is needed in `_format_value`.

--
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/087.6fd41f3768431884eafb39e4b7d16391%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21126: Potential data corruption issue with Oracle and Mysql due to SQLCompiler.resolve_columns row, fields misalignment

2013-10-07 Thread Django

#21126: Potential data corruption issue with Oracle and Mysql due to
SQLCompiler.resolve_columns row, fields misalignment
-+-
 Reporter:  manfre   |Owner:  manfre
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by anonymous):

 Whoops, forgot to complete a line:

 It should be noted that the backpatch to 1.5.x did ''not'' resolve my
 issue and, in fact, had no effect, which makes sense since
 `resolve_columns` is `False` in this 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/064.467a28c952ac3f395a7e04be58c7baa7%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21126: Potential data corruption issue with Oracle and Mysql due to SQLCompiler.resolve_columns row, fields misalignment

2013-10-07 Thread Django

Comment (by radicalbiscuit):

I'm experiencing this bug or something very similar on Django 1.5 and
here's the kicker: I'm using PostgreSQL.

I took a look at the patches, and using the

{{{#!python
loaded_fields = self.query.get_loaded_field_names().get(self.query.model,
set()) or self.query.select
}}}

line for determining `aggregate_start` completely fixes my issue. It
should be noted that the backpatch to 1.5.x did ''not'' resolve my issue
and, in fact, had no effect, which makes sense since our

The query that triggers this only does so while resolving the aggregates
as part of the template layer and includes deferred fields, related
fields, and of course, the aggregate.

Can you think of any reason to ''not'' included the `loaded_fields` code
in the 1.5 backpatch, and if not, can it be included? Let me know if you
need any further information. I'll be keeping an eye 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.a41982535e71479424d174cd5294c150%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21237: Add Australian English (en_AU) to locale conf

2013-10-07 Thread Django

#21237: Add Australian English (en_AU) to locale conf
--+
 Reporter:  anonymous |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Internationalization  |  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):

 * has_patch:  0 => 1
 * version:  1.5 => master
 * type:  Uncategorized => New feature
 * stage:  Unreviewed => Accepted


Comment:

 Do you plan to add some translations to django.po? Otherwise, I suggest to
 remove the file from the commit.

-- 
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.74fdb34d93a1ff584b18dd369a722bab%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21220: Improve admin user friendliness

2013-10-07 Thread Django

#21220: Improve admin user friendliness
--+
 Reporter:  ryangallen|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admin |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  1
--+

Comment (by Tim Graham ):

 In [changeset:"935001c4f1ab8660c76323854945e9e660514046"]:
 {{{
 #!CommitTicketReference repository=""
 revision="935001c4f1ab8660c76323854945e9e660514046"
 Cleaned up admin CSS for consistency.

 * header selected twice -merged
 * match indentation throughout
 * color names to hex

 refs #21220.
 }}}

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

[django/django] 935001: Cleaned up admin CSS for consistency.

2013-10-07 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 935001c4f1ab8660c76323854945e9e660514046
  
https://github.com/django/django/commit/935001c4f1ab8660c76323854945e9e660514046
  Author: Ryan Allen 
  Date:   2013-10-07 (Mon, 07 Oct 2013)

  Changed paths:
M django/contrib/admin/static/admin/css/base.css

  Log Message:
  ---
  Cleaned up admin CSS for consistency.

* header selected twice -merged
* match indentation throughout
* color names to hex

refs #21220.



-- 
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/5253024eacad6_7fa78d3d58598e6%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21190: Fix broken ePub documentation by adding a proper theme for it

2013-10-07 Thread Django

#21190: Fix broken ePub documentation by adding a proper theme for it
-+
 Reporter:  giuliettamasina  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Documentation|  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by giuliettamasina):

 Has anyone had time to look at this?

-- 
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/073.307931f83491f4d8026a7c580b9ea557%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 3eab22: Added min-width for date and time inputs in admin.

2013-10-07 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 3eab22a0452f976727ba21b4b6e25dabba85111e
  
https://github.com/django/django/commit/3eab22a0452f976727ba21b4b6e25dabba85111e
  Author: Ryan Allen 
  Date:   2013-10-07 (Mon, 07 Oct 2013)

  Changed paths:
M django/contrib/admin/static/admin/css/forms.css

  Log Message:
  ---
  Added min-width for date and time inputs in admin.

refs #21220.



-- 
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/5252fe0044e_42a9c87d50152986%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21220: Improve admin user friendliness

2013-10-07 Thread Django

#21220: Improve admin user friendliness
--+
 Reporter:  ryangallen|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admin |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  1
--+

Comment (by Tim Graham ):

 In [changeset:"3eab22a0452f976727ba21b4b6e25dabba85111e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3eab22a0452f976727ba21b4b6e25dabba85111e"
 Added min-width for date and time inputs in admin.

 refs #21220.
 }}}

-- 
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.67a91067796b020d2c42975ab8891911%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21241: Optimize the query generated for admin changelist filters

2013-10-07 Thread Django

#21241: Optimize the query generated for admin changelist filters
-+-
 Reporter:  acdha|Owner:  charettes
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by charettes):

 @acdha can you confirm one of your `search_filters` reference a multi
 valued relationship?

-- 
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.4c545791667ea2f1cc5607f392b53fed%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21241: Optimize the query generated for admin changelist filters

2013-10-07 Thread Django

Comment (by akaariai):

For single valued relationships doing single .filter() call and multiple
chained .filter() calls should both result in a single join (if it doesn't
actually to that then it is a bug in the ORM). There might be a
performance change due to less cloning for single .filter() call, but that
shouldn't be anything dramatic in common cases.

Tests for current behaviour would of course be good. If there is some easy
way to allow users to choose just one filter() call that would be good,
too.

--
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.94829d69800ea093f5b5166a1214bc44%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] a8df8e: Revert "Fixed #21241 -- Avoid extraneous JOINs in ...

2013-10-07 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a8df8e34f9fc0219de73eabcb215d976e75a89ae
  
https://github.com/django/django/commit/a8df8e34f9fc0219de73eabcb215d976e75a89ae
  Author: Simon Charette 
  Date:   2013-10-07 (Mon, 07 Oct 2013)

  Changed paths:
M django/contrib/admin/options.py
M tests/admin_changelist/tests.py

  Log Message:
  ---
  Revert "Fixed #21241 -- Avoid extraneous JOINs in admin changelist search."

This reverts commit 698dd82eee1cb83f51d4cd39546461bf76976b5e.

The patch introduced a backward incompatible change.



-- 
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/5252f373861e1_7e17cffd501216c7%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21241: Optimize the query generated for admin changelist filters

2013-10-07 Thread Django

#21241: Optimize the query generated for admin changelist filters
-+-
 Reporter:  acdha|Owner:  charettes
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by charettes):

 * status:  closed => new
 * resolution:  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/063.646f35f445a4d8d6e0080ac317dab177%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21241: Optimize the query generated for admin changelist filters

2013-10-07 Thread Django

#21241: Optimize the query generated for admin changelist filters
-+-
 Reporter:  acdha|Owner:  charettes
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  contrib.admin|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Simon Charette ):

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


Comment:

 In [changeset:"a8df8e34f9fc0219de73eabcb215d976e75a89ae"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a8df8e34f9fc0219de73eabcb215d976e75a89ae"
 Revert "Fixed #21241 -- Avoid extraneous JOINs in admin changelist
 search."

 This reverts commit 698dd82eee1cb83f51d4cd39546461bf76976b5e.

 The patch introduced a backward incompatible change.
 }}}

-- 
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.463483ed74a8608f3c6b489786ee217e%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21241: Optimize the query generated for admin changelist filters

2013-10-07 Thread Django

#21241: Optimize the query generated for admin changelist filters
-+-
 Reporter:  acdha|Owner:  charettes
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by charettes):

 * status:  closed => new
 * resolution:  fixed =>
 * stage:  Ready for checkin => Accepted


Comment:

 Since this is backward incompatible and both use cases are valid I'll just
 revert this commit for now.

 Maybe we could use the proposed code path when there's no multi-valued
 relationships?

 Might be worth writing a regression test case to make sure we're not
 breaking the admin changelist behavior in the future.

-- 
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.1e1c997296964017731d33ff94f0adf9%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 259a6e: Added a link in admin branding block to admin inde...

2013-10-07 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 259a6ea82cfb8bf242449666e4b643a19e54a423
  
https://github.com/django/django/commit/259a6ea82cfb8bf242449666e4b643a19e54a423
  Author: Ryan Allen 
  Date:   2013-10-07 (Mon, 07 Oct 2013)

  Changed paths:
M django/contrib/admin/static/admin/css/base.css
M django/contrib/admin/templates/admin/base_site.html

  Log Message:
  ---
  Added a link in admin branding block to admin index.

Refs #13749 and #21220.



-- 
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/5252f1eaa20bc_4243937d5811132a%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21220: Improve admin user friendliness

2013-10-07 Thread Django

#21220: Improve admin user friendliness
--+
 Reporter:  ryangallen|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admin |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  1
--+

Comment (by Tim Graham ):

 In [changeset:"259a6ea82cfb8bf242449666e4b643a19e54a423"]:
 {{{
 #!CommitTicketReference repository=""
 revision="259a6ea82cfb8bf242449666e4b643a19e54a423"
 Added a link in admin branding block to admin index.

 Refs #13749 and #21220.
 }}}

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

Re: [Django] #13749: Link from admin-site to site

2013-10-07 Thread Django

#13749: Link from admin-site to site
+-
 Reporter:  romankrv|Owner:  joelklabo
 Type:  New feature |   Status:  new
Component:  contrib.admin   |  Version:  1.2
 Severity:  Normal  |   Resolution:
 Keywords:  admin url dceu2011  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  1
+-

Comment (by Tim Graham ):

 In [changeset:"259a6ea82cfb8bf242449666e4b643a19e54a423"]:
 {{{
 #!CommitTicketReference repository=""
 revision="259a6ea82cfb8bf242449666e4b643a19e54a423"
 Added a link in admin branding block to admin index.

 Refs #13749 and #21220.
 }}}

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

Re: [Django] #21241: Optimize the query generated for admin changelist filters

2013-10-07 Thread Django

#21241: Optimize the query generated for admin changelist filters
-+-
 Reporter:  acdha|Owner:  charettes
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  contrib.admin|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by akaariai):

 I am pretty sure the patch is bogus. For multivalued relation doing
 .filter(cond1).filter(cond2) isn't equivalent to .filter(cond1, cond2).
 The first one creates multiple joins on purpose. The reason for that is
 that if you have structure like:

 ||id||parent_id||intval1||intval2||
 ||1||null||10
 ||2||1||20||25||
 ||3||1||30||35||

 then doing
 `Tree.objects.filter(child__intval1=20).filter(child__intval2=35)` will
 result in a match - there is a children with intval1=20 and a children
 with intval2=35 (it could be the same children, in this case it isn't).
 But if you do `Tree.objects.filter(child__intval1=20, child__intval2=35)`
 then the interpretation is that there must be *single* children with
 intval1=20 and intval2=35 and that isn't true. (However,
 `Tree.objects.filter(child__intval1=20, child__intval2=25)` would match as
 there is single children with both values).

 On SQL level this single instance versus multiple instances is implemented
 as single join to childrens versus multiple joins to childrens. So, it is
 intentional that multiple .filter() calls chained together generates
 multiple joins, while pushing them all into single .filter() call
 generates just one join.

 This behaviour of the ORM API isn't easy to understand, and I guess most
 users do not actually know of this... But still, that is how it works, and
 changing how admin interprets the given filters in this case is a
 backwards incompatible change.

 The ORM API is documented in
 https://docs.djangoproject.com/en/dev/topics/db/queries/#spanning-multi-
 valued-relationships.

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

Re: [Django] #20974: Adding test for mysql-specific model validation checks

2013-10-07 Thread Django

#20974: Adding test for mysql-specific model validation checks
-+-
 Reporter:  chrismedrela |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.5
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  checks   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

 * easy:  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/070.de9978ec7426a93a1103f89bf943a34c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #6681: `admindocs` breaks compatibility with `docutils` when rendering reStructuredText

2013-10-07 Thread Django

#6681: `admindocs` breaks compatibility with `docutils` when rendering
reStructuredText
-+-
 Reporter:  mtredinnick  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admindocs|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  restructuredtext | Triage Stage:  Accepted
  docutils   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

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


Comment:

 This causes docutils to throw an error when running the full test suite
 (or just the `webdesign` + `admin_views` tests. I'm not sure the best way
 to fix it.

 {{{
 $ ./runtests.py django.contrib.webdesign admin_views

 :2: (ERROR/3) Error in "default-role" directive:
 no content permitted.

 .. default-role:: cmsreference

 * ``{% lorem %}`` will output the common "lorem ipsum" paragraph
 * ``{% lorem 3 p %}`` will output the common "lorem ipsum" paragraph
   and two random paragraphs each wrapped in HTML  tags
 * ``{% lorem 2 w random %}`` will output two random latin words
 }}}

 The "Example:" bit in the docstring for
 django.contrib.webdesign.templatetags.webdesign.lorem is parsed as
 metadata so the bullet list is then interpreted as a new block and
 unexpectedly indented under the `.. default-role` directive. Possibly we
 can fix this particular docstring to avoid the problem, but I'm wondering
 if other users will encounter the problem with their own docstrings.

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

Re: [Django] #21241: Optimize the query generated for admin changelist filters

2013-10-07 Thread Django

#21241: Optimize the query generated for admin changelist filters
-+-
 Reporter:  acdha|Owner:  charettes
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  contrib.admin|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette ):

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


Comment:

 In [changeset:"698dd82eee1cb83f51d4cd39546461bf76976b5e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="698dd82eee1cb83f51d4cd39546461bf76976b5e"
 Fixed #21241 -- Avoid extraneous JOINs in admin changelist search.
 }}}

-- 
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.78ca622dd2bca391c566565e23a18d6c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 698dd8: Fixed #21241 -- Avoid extraneous JOINs in admin ch...

2013-10-07 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 698dd82eee1cb83f51d4cd39546461bf76976b5e
  
https://github.com/django/django/commit/698dd82eee1cb83f51d4cd39546461bf76976b5e
  Author: Chris Adams 
  Date:   2013-10-07 (Mon, 07 Oct 2013)

  Changed paths:
M django/contrib/admin/options.py
M tests/admin_changelist/tests.py

  Log Message:
  ---
  Fixed #21241 -- Avoid extraneous JOINs in admin changelist search.



-- 
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/5252eb2bb1419_42a9c87d5014092e%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21241: Optimize the query generated for admin changelist filters

2013-10-07 Thread Django

#21241: Optimize the query generated for admin changelist filters
-+-
 Reporter:  acdha|Owner:  charettes
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #21241: Optimize the query generated for admin changelist filters

2013-10-07 Thread Django

#21241: Optimize the query generated for admin changelist filters
-+-
 Reporter:  acdha|Owner:  charettes
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by charettes):

 * status:  new => assigned
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * owner:  nobody => charettes
 * needs_docs:   => 0
 * stage:  Unreviewed => Accepted


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

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

[Django] #21241: Optimize the query generated for admin changelist filters

2013-10-07 Thread Django

#21241: Optimize the query generated for admin changelist filters
--+
 Reporter:  acdha |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  contrib.admin |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+
 The admin changelist search implementation currently calls
 queryset.filter() for each whitespace-separated term. This can cause the
 ORM to generate repeated JOINs of the same table which is both a potential
 performance problem and will actually cause MySQL to return an error once
 you hit a system limit (~60 on the example I encountered).

 The patch at https://github.com/django/django/pull/881 changes the logic
 to combine the terms into a single filter() call and adds some 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/048.03a05c38cf7acfa3b051a3a880622d91%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 617ace: Fixed #18263 -- Corrrected handling of hidden fiel...

2013-10-07 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 617aceb1b4ec97b4d70f9b3071cb46a645f69f87
  
https://github.com/django/django/commit/617aceb1b4ec97b4d70f9b3071cb46a645f69f87
  Author: Tim Graham 
  Date:   2013-10-07 (Mon, 07 Oct 2013)

  Changed paths:
M django/contrib/admin/templates/admin/edit_inline/tabular.html
M tests/admin_inlines/admin.py
M tests/admin_inlines/models.py
M tests/admin_inlines/tests.py

  Log Message:
  ---
  Fixed #18263 -- Corrrected handling of hidden fields in tabular admin inlines.

Thanks hvdklauw for the report and patch.



-- 
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/5252e1e523a3a_421ccd3d54110729%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18263: admin/edit_inline/tabular.html only handles hidden fields correctly in the header

2013-10-07 Thread Django

#18263: admin/edit_inline/tabular.html only handles hidden fields correctly in 
the
header
---+
 Reporter:  hvdklauw   |Owner:  hvdklauw
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.4
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  1  |UI/UX:  0
---+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"617aceb1b4ec97b4d70f9b3071cb46a645f69f87"]:
 {{{
 #!CommitTicketReference repository=""
 revision="617aceb1b4ec97b4d70f9b3071cb46a645f69f87"
 Fixed #18263 -- Corrrected handling of hidden fields in tabular admin
 inlines.

 Thanks hvdklauw for the report and patch.
 }}}

-- 
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.7983827e0e04c381fe8e2d927604cbf2%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16027: Include app_label in ContentType.unicode

2013-10-07 Thread Django

#16027: Include app_label in ContentType.__unicode__
-+-
 Reporter:  jakub|Owner:
 Type:   |  djangsters
  Cleanup/optimization   |   Status:  assigned
Component:   |  Version:  master
  contrib.contenttypes   |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * easy:  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/063.b358d983f865425d24251fb5d5fc%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21240: Breaking change regarding select_related+OneToOneField missing from release notes

2013-10-07 Thread Django

#21240: Breaking change regarding select_related+OneToOneField missing from 
release
notes
-+--
 Reporter:  marcin@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:  breaking change  | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by marcin@…):

 I just realized I made a serious faux pas in the testcase when pasting
 code around (inadvertently re-using the local "nut"), it still works fine
 though. If someone could edit and change the loop variable name, that'd be
 lovely, wouldn't want to clutter the ticket with another half-a-screen of
 nearly identical code.

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

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

Re: [Django] #21240: Breaking change regarding select_related+OneToOneField missing from release notes

2013-10-07 Thread Django

#21240: Breaking change regarding select_related+OneToOneField missing from 
release
notes
-+--
 Reporter:  marcin@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:  breaking change  | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by marcin@…):

 Models:
 {{{
 class Nut (models.Model):
 pass

 class Bolt (models.Model):
 nut = models.OneToOneField (Nut)
 }}}

 Relevant tests:
 {{{
 class FindingOrphanedNutsTestcase (TestCase):

 def test_old_behaviour__will_fail_on_1_5_and_later (self): # fails by
 letting DoesNotExist escape
 nut = Nut.objects.create ()
 nuts = [nut for nut in Nut.objects.all().select_related("bolt") if
 nut.bolt is None]
 self.assertListEqual (nuts, [nut])

 def test_new_behaviour__will_fail_on_1_4_and_earlier (self): # fails
 by producing an empty list
 nut = Nut.objects.create ()

 nuts = []
 for nut in Nut.objects.all().select_related("bolt"):
 try:
 nut.bolt
 except Bolt.DoesNotExist:
 nuts.append (nut)

 self.assertListEqual (nuts, [nut])
 }}}

 Now of course you could write that to accommodate both None and
 !DoesNotExist (or just with a .filter), but that's not the point, it's the
 fact that old code for many years and releases had to handle None, but
 didn't have to handle !DoesNotExist. And with 1.5 it suddenly has to
 handle !DoesNotExist and can disregard None.

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

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

Re: [Django] #18098: order_with_respect_to should construct set_RELATED_order() method name from related_name

2013-10-07 Thread Django

#18098: order_with_respect_to should construct set_RELATED_order() method name 
from
related_name
-+-
 Reporter:  pressureman  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * needs_better_patch:  0 => 1
 * needs_tests:  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/069.e751f1884934c9a48e8c1dd875a53c93%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #3591: add support for custom app_label and verbose_name

2013-10-07 Thread Django

#3591: add support for custom app_label and verbose_name
--+
 Reporter:  jkocherhans   |Owner:  adrian
 Type:  New feature   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  1
--+
Changes (by timo):

 * 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/069.3e728fb5b7db6e1895025be17e431922%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19259: Annotations generating inefficient SQL on PostgreSQL

2013-10-07 Thread Django

#19259: Annotations generating inefficient SQL on PostgreSQL
-+-
 Reporter:  hcarvalhoalves   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.4
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-
Changes (by timo):

 * needs_better_patch:  0 => 1
 * needs_tests:  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/072.4a3eb09e4731383ba0522d4ffac8b8f1%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21173: Django DateTimeInput determines language/locale at startup time but this may change later, resulting in validation errors

2013-10-07 Thread Django

#21173: Django DateTimeInput determines language/locale at startup time but this
may change later, resulting in validation errors
-+-
 Reporter:  django-locale-   |Owner:  nobody
  issue@…|   Status:  new
 Type:  Bug  |  Version:  1.4
Component:  Forms|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
  forms,widgets,locale   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by django-locale-issue@…):

 Form initialization kicks in at startup / import time, LocaleMiddleWare
 doesn't happen until the first request.
 LocaleMiddleware may activate a different language than the widget was
 initialized with.

-- 
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/087.cbf475dee61c3f014e0066d059696b98%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21236: Migrations: error applying unique_together

2013-10-07 Thread Django

#21236: Migrations: error applying unique_together
-+-
 Reporter:  hjwp |Owner:  Tim
 Type:  Bug  |  Graham 
Component:  Migrations   |   Status:  closed
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by anonymous):

 I'm bloody impressed with the turnaround!  Nice one gang.

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

[django/django] 4dbd95: Fixed #21236 -- Allowed migrations to work with un...

2013-10-07 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 4dbd95ad65fa3fc86af7391b28a759b401f530d1
  
https://github.com/django/django/commit/4dbd95ad65fa3fc86af7391b28a759b401f530d1
  Author: Javed Khan 
  Date:   2013-10-07 (Mon, 07 Oct 2013)

  Changed paths:
M django/db/migrations/operations/models.py
M django/db/models/options.py
M tests/migrations/test_operations.py

  Log Message:
  ---
  Fixed #21236 -- Allowed migrations to work with unique_together tuples.

Thanks hjwp for the report.



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

Re: [Django] #21240: Breaking change regarding select_related+OneToOneField missing from release notes

2013-10-07 Thread Django

#21240: Breaking change regarding select_related+OneToOneField missing from 
release
notes
-+--
 Reporter:  marcin@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:  breaking change  | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by akaariai):

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


Comment:

 Could you add an example of what breaks and how? This should include
 example models, query and how the query behaves in 1.4 compared to 1.5.

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

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

Re: [Django] #21236: Migrations: error applying unique_together

2013-10-07 Thread Django

#21236: Migrations: error applying unique_together
-+-
 Reporter:  hjwp |Owner:  Tim
 Type:  Bug  |  Graham 
Component:  Migrations   |   Status:  closed
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Tim Graham ):

 * owner:   => Tim Graham 
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"4dbd95ad65fa3fc86af7391b28a759b401f530d1"]:
 {{{
 #!CommitTicketReference repository=""
 revision="4dbd95ad65fa3fc86af7391b28a759b401f530d1"
 Fixed #21236 -- Allowed migrations to work with unique_together tuples.

 Thanks hjwp for the report.
 }}}

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

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

[Django] #21240: Breaking change regarding select_related+OneToOneField missing from release notes

2013-10-07 Thread Django

#21240: Breaking change regarding select_related+OneToOneField missing from 
release
notes
---+-
 Reporter:  marcin@…   |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Documentation  |Version:  1.5
 Severity:  Normal |   Keywords:  breaking change
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+-
 Django 1.5 made changes to the way select_related interacts with
 OneToOneField reverse relations:
 https://code.djangoproject.com/ticket/13839

 This is a breaking change and was not included in the release notes.

 The behaviour of this interaction was previously undocumented (and had an
 open bug), but since it is core ORM functionality, I don't think you can
 fault people for relying on it.

 Please document it in 1.5's release notes, preferably with its own
 paragraph.

-- 
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.676f5c7fe10b673c54c25a961b757474%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21239: Closing connection inside atomic block breaks atomicity

2013-10-07 Thread Django

#21239: Closing connection inside atomic block breaks atomicity
-+-
 Reporter:  marcin@… |Owner:  aaugustin
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:  atomic close |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by akaariai):

 Can you skip the test on sqlite? It seems good enough that CI will catch
 errors here.

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

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

Re: [Django] #21239: Closing connection inside atomic block breaks atomicity

2013-10-07 Thread Django

#21239: Closing connection inside atomic block breaks atomicity
-+-
 Reporter:  marcin@… |Owner:  aaugustin
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:  atomic close |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by aaugustin):

 I can't include a test to validate this behavior, because the test suite
 needs a constantly open connection when running with an in-memory SQLite
 database.

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

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

Re: [Django] #21239: Closing connection inside atomic block breaks atomicity

2013-10-07 Thread Django

#21239: Closing connection inside atomic block breaks atomicity
-+-
 Reporter:  marcin@… |Owner:  aaugustin
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:  atomic close |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * status:  new => assigned
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * owner:  nobody => aaugustin
 * needs_docs:   => 0
 * stage:  Unreviewed => Accepted


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

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

[Django] #21239: Closing connection inside atomic block breaks atomicity

2013-10-07 Thread Django

#21239: Closing connection inside atomic block breaks atomicity
--+--
 Reporter:  marcin@…  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Release blocker   |   Keywords:  atomic close
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+--
 Closing the connection inside an atomic block rolls back queries up to
 that point, but doesn't prevent subsequent queries from reconnecting and
 getting committed. An exception should be raised in this situation in one
 of three places:
 * connection.close()
 * or on the next reconnection attempt
 * or on the next query execution attempt

 Testcase (currently failing):
 {{{
 def test_connection_closed_inside_atomic (self):
 with self.assertRaises(transaction.TransactionManagementError):
 with transaction.atomic():
 Reporter.objects.create(first_name="Tom")
 connection.close()
 Reporter.objects.create(first_name="Jerry")
 # here Jerry exists but Tom doesn't
 }}}

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

Re: [Django] #21226: Simple index view test fails with error "'NoneType' object has no attribute 'converter'"

2013-10-07 Thread Django

#21226: Simple index view test fails with error "'NoneType' object has no 
attribute
'converter'"
-+-
 Reporter:  heraldhoi@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  1.5
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  mysql automated- | Triage Stage:
  tests connector index-view |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 [https://docs.djangoproject.com/en/dev/ref/databases/#mysqldb As
 documented]: "MySQLdb is the Python interface to MySQL. Version 1.2.1p2 or
 later is required for full MySQL support in Django."

 Perhaps we should support this connector someday, but that's a larger
 question for the django-developers mailing list.

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

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

Re: [Django] #21223: Add id_for_label in Django forms topic documentation (was: Add id_for_label in Django forms api documentation)

2013-10-07 Thread Django

#21223: Add id_for_label in Django forms topic documentation
--+
 Reporter:  ebertti@… |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:  form  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timo):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * easy:  0 => 1
 * needs_docs:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 It's already in the
 
[https://docs.djangoproject.com/en/dev/ref/forms/api/#django.forms.BoundField.id_for_label
 forms API docs], but yes, we could add it the topic doc as you've
 suggested.

-- 
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/078.fd121fe3437e77a19f25a8a0c081d4f5%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19299: Foreign keys using to_field and having legitimate empty string values fail with NULL errors

2013-10-07 Thread Django

#19299: Foreign keys using to_field and having legitimate empty string values 
fail
with NULL errors
-+-
 Reporter:  evan@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by timo):

 Closed #21194 as a duplicate of this - the patch there is slightly
 different and may be useful.

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

Re: [Django] #21234: DATABASES['other']['TEST_NAME'] is ignored is some situations.

2013-10-07 Thread Django

#21234: DATABASES['other']['TEST_NAME'] is ignored is some situations.
---+--
 Reporter:  vernondcole|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  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
---+--
Description changed by timo:

Old description:

> Attempting to test django using the following settings fails with an
> infinite wait.  It appears that 'TEST_NAME' is ignored, causing
> conflicting use of the (single) database.
>
> I have determined that if DATABASES['default']['NAME'] !=
> DATABASES['other']['NAME'] then 'TEST_NAME' works correctly.
> ---
>  DATABASES = {
>
> 'default': {
>
> 'ENGINE': 'django.db.backends.postgresql_psycopg2',
> 'NAME': 'adotest',
> 'USER': 'adotestuser',
> 'PASSWORD': '12345678',
> 'HOST': 'localhost',
> 'OPTIONS': {
>
> 'autocommit': True,
> },
>
> },
>
> 'other': {
>
> 'ENGINE': 'django.db.backends.postgresql_psycopg2',
> 'NAME': 'adotest',
> 'TEST_NAME': 'other_test',
> 'USER': 'adotestuser',
> 'PASSWORD': '12345678',
> 'HOST': 'localhost',
> 'OPTIONS': {
>
> 'autocommit': True,
> },
>
> }
>
> }

New description:

 Attempting to test django using the following settings fails with an
 infinite wait.  It appears that 'TEST_NAME' is ignored, causing
 conflicting use of the (single) database.

 I have determined that if `DATABASES['default']['NAME'] !=
 DATABASES['other']['NAME']` then 'TEST_NAME' works correctly.
 {{{
  DATABASES = {

 'default': {

 'ENGINE': 'django.db.backends.postgresql_psycopg2',
 'NAME': 'adotest',
 'USER': 'adotestuser',
 'PASSWORD': '12345678',
 'HOST': 'localhost',
 'OPTIONS': {

 'autocommit': True,
 },

 },

 'other': {

 'ENGINE': 'django.db.backends.postgresql_psycopg2',
 'NAME': 'adotest',
 'TEST_NAME': 'other_test',
 'USER': 'adotestuser',
 'PASSWORD': '12345678',
 'HOST': 'localhost',
 'OPTIONS': {

 'autocommit': True,
 },

 }

 }
 }}}

--

-- 
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.19f31a04e8643ead2376898b91221a1e%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21194: Foreign Keying To A Field With An Empty String Value Converts To Null Database Value

2013-10-07 Thread Django

#21194: Foreign Keying To A Field With An Empty String Value Converts To Null
Database Value
-+-
 Reporter:  albertyw@…   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

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


Comment:

 I believe this is a duplicate of #19299. That ticket has a slightly
 different patch, so maybe you could take a look there and see which
 approach you think is correct.

-- 
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/074.a845eb9b99cf3e5a813a41f52a42f44b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 563b5c: [1.6.x] Re-added link to SQLite notes from DB sect...

2013-10-07 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 563b5c20007b993c8ab8d88f9083ab5df4b3606a
  
https://github.com/django/django/commit/563b5c20007b993c8ab8d88f9083ab5df4b3606a
  Author: Ramiro Morales 
  Date:   2013-10-07 (Mon, 07 Oct 2013)

  Changed paths:
M docs/topics/install.txt

  Log Message:
  ---
  [1.6.x] Re-added link to SQLite notes from DB section of install doc.

67f5dffbec from master.



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

[django/django] 67f5df: Re-added link to SQLite notes from DB section of i...

2013-10-07 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 67f5dffbec366ed50264d32c25facd2681105258
  
https://github.com/django/django/commit/67f5dffbec366ed50264d32c25facd2681105258
  Author: Ramiro Morales 
  Date:   2013-10-07 (Mon, 07 Oct 2013)

  Changed paths:
M docs/topics/install.txt

  Log Message:
  ---
  Re-added link to SQLite notes from DB section of install doc.



-- 
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/52528fe030b93_418e1189d581165f9%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21238: `ImageFieldFile.url` raise an AttributeError after retrieving it from cache

2013-10-07 Thread Django

#21238: `ImageFieldFile.url` raise an AttributeError after retrieving it from 
cache
-+---
 Reporter:  dulaccc  |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Core (Cache system)  |Version:  1.5
 Severity:  Normal   |   Keywords:  imagefield, cache
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+---
 Hi everyone,

 To reproduce the exception, just cache an instance of `ImageFieldFile`
 then retrieve it and call the `url` property on this retrieved instance.

 Here is a minimal code to reproduce :

 {{{
 from django.core.cache import cache
 from django.db import models

 class A(models.Model):
 pictogram = models.ImageField(upload_to='images')
 class Meta:
 app_label = 'test'

 a = A()
 a.pictogram = 'fake/test/url.png'
 original_picto = a.pictogram

 cache_key = 'picto'
 cache.set(cache_key, original_picto, 60)
 cached_picto = cache.get(cache_key)

 print original_picto.url
 print cached_picto.url
 }}}

 and you get

 {{{
 AttributeError: 'ImageFieldFile' object has no attribute 'storage'
 }}}

 Didn't tried to fix it yet...

 Have a nice day,

 Pierre

-- 
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.6f992811785957f5412ca052859853f0%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21238: `ImageFieldFile.url` raises an AttributeError exception after retrieving it from cache (was: `ImageFieldFile.url` raises an AttributeError after retrieving it from cache)

2013-10-07 Thread Django

#21238: `ImageFieldFile.url` raises an AttributeError exception after 
retrieving it
from cache
-+-
 Reporter:  dulaccc  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Cache system)  |  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:  imagefield, cache| Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  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/065.8cfac278138618d9b83c364acc724f47%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21238: `ImageFieldFile.url` raises an AttributeError after retrieving it from cache (was: `ImageFieldFile.url` raise an AttributeError after retrieving it from cache)

2013-10-07 Thread Django

#21238: `ImageFieldFile.url` raises an AttributeError after retrieving it from
cache
-+-
 Reporter:  dulaccc  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Cache system)  |  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:  imagefield, cache| Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by dulaccc):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 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/065.2b6b56bab97055f29267cc491f8afa77%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21201: Let ClearableFileInput work with other fields

2013-10-07 Thread Django

#21201: Let ClearableFileInput work with other fields
-+
 Reporter:  vzima|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by EvilDMP):

 This patch does change the behaviour of the widget, so we will need to
 understand any backwards-compatibility implications of 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/063.e2a171dcf911e170206fbed3949c2ae0%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21201: Let ClearableFileInput work with other fields

2013-10-07 Thread Django

#21201: Let ClearableFileInput work with other fields
-+
 Reporter:  vzima|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by EvilDMP):

 docs/forms/ref/widgets.txt documents ClearableFileInput, but not the
 internals; I don't see any particular need to document internals of
 widgets. Perhaps an example of usage would be helpful.

-- 
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.13195b1af1d37532ced60df14e265d38%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21201: Let ClearableFileInput work with other fields

2013-10-07 Thread Django

#21201: Let ClearableFileInput work with other fields
-+
 Reporter:  vzima|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by vzima):

 Replying to [comment:2 EvilDMP]:
 Do you have in mind any particular changes in documentation beside note in
 changelog? Current documentation does not describe these internals of the
 widget.

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

Re: [Django] #21235: 1.6: Suggest installing standalone pysqlite2 on Windows when using Python 2.6

2013-10-07 Thread Django

#21235: 1.6: Suggest installing standalone pysqlite2 on Windows when using 
Python
2.6
---+--
 Reporter:  ramiro |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.6-beta-1
 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 Aymeric Augustin ):

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


Comment:

 In [changeset:"b42f0665a8cc25869c8dbc7bb71927b7ea61f81c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b42f0665a8cc25869c8dbc7bb71927b7ea61f81c"
 [1.6.x] Fixed #21235 -- Disabled savepoints for old versions of SQLite.

 Thanks Ramiro for the report.

 Backport of 91547772 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/064.9e446626ecca168b4fce06130eee2d46%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 915477: Fixed #21235 -- Disabled savepoints for old versio...

2013-10-07 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 91547772e04e456f45c7ef86e1f76d087821c89d
  
https://github.com/django/django/commit/91547772e04e456f45c7ef86e1f76d087821c89d
  Author: Aymeric Augustin 
  Date:   2013-10-07 (Mon, 07 Oct 2013)

  Changed paths:
M django/db/backends/sqlite3/base.py

  Log Message:
  ---
  Fixed #21235 -- Disabled savepoints for old versions of SQLite.

Thanks Ramiro for the report.



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

Re: [Django] #21235: 1.6: Suggest installing standalone pysqlite2 on Windows when using Python 2.6

2013-10-07 Thread Django

#21235: 1.6: Suggest installing standalone pysqlite2 on Windows when using 
Python
2.6
---+--
 Reporter:  ramiro |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.6-beta-1
 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
---+--

Comment (by Aymeric Augustin ):

 In [changeset:"91547772e04e456f45c7ef86e1f76d087821c89d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="91547772e04e456f45c7ef86e1f76d087821c89d"
 Fixed #21235 -- Disabled savepoints for old versions of SQLite.

 Thanks Ramiro for the report.
 }}}

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

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

[django/django] b42f06: [1.6.x] Fixed #21235 -- Disabled savepoints for ol...

2013-10-07 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: b42f0665a8cc25869c8dbc7bb71927b7ea61f81c
  
https://github.com/django/django/commit/b42f0665a8cc25869c8dbc7bb71927b7ea61f81c
  Author: Aymeric Augustin 
  Date:   2013-10-07 (Mon, 07 Oct 2013)

  Changed paths:
M django/db/backends/sqlite3/base.py

  Log Message:
  ---
  [1.6.x] Fixed #21235 -- Disabled savepoints for old versions of SQLite.

Thanks Ramiro for the report.

Backport of 91547772 from master.



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

Re: [Django] #21234: DATABASES['other']['TEST_NAME'] is ignored is some situations.

2013-10-07 Thread Django

#21234: DATABASES['other']['TEST_NAME'] is ignored is some situations.
---+--
 Reporter:  vernondcole|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  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 mjtamlyn):

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


Comment:

 Why would you have `DATABASES['default']['NAME'] ==
 DATABASES['other']['NAME']`? This seems illogical to 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/069.0839947e1bd8de3a793e1ead3f69a3d6%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21236: Migrations: error applying unique_together

2013-10-07 Thread Django

#21236: Migrations: error applying unique_together
+
 Reporter:  hjwp|Owner:
 Type:  Bug |   Status:  new
Component:  Migrations  |  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 tuxcanfly):

 * needs_tests:  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/062.bf63518c6c294f626c5fc0eac01c0ffa%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21236: Migrations: error applying unique_together

2013-10-07 Thread Django

#21236: Migrations: error applying unique_together
+
 Reporter:  hjwp|Owner:
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by tuxcanfly):

 * cc: tuxcanfly (added)
 * has_patch:  0 => 1
 * needs_tests:  0 => 1


Comment:

 Here's a patch that appears to fix the migration error.

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

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

87 matches

Mail list logo