Re: [Django] #22769: transaction.automic is not working as expected with Oracle DB for raw sql

[Django]

#22769: transaction.automic is not working as expected with Oracle DB for raw 
sql
-+-
 Reporter:  manish_kumar9@…  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by manish_kumar9@…):

 we support multiple database but at a time only one will be available for
 single installation. self.cursor is class variable where we have this
 mentioned method.

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

Re: [Django] #22758: Makemigrations puts subclasses of abstract models in the wrong app

[Django]

#22758: Makemigrations puts subclasses of abstract models in the wrong app
-+--
 Reporter:  cdestigter   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  1.7-beta-2
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by cdestigter):

 > This only occurs with an explicit app_label declaration

 That wasn't my experience. I encountered the issue with django-typed-
 models, where the abstract model was located in the `typedmodels` app, and
 the concrete model was in some other app.

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

Re: [Django] #21430: Raise explicit error when unpickling Models and QuerySet from incompatible version

[Django]

#21430: Raise explicit error when unpickling Models and QuerySet from 
incompatible
version
-+-
 Reporter:  FunkyBob |Owner:
 Type:  New feature  |  anubhav9042
Component:  Database layer   |   Status:  assigned
  (models, ORM)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by loic84):

 * cc: loic84 (added)


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

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

Re: [Django] #21430: Raise explicit error when unpickling Models and QuerySet from incompatible version

[Django]

#21430: Raise explicit error when unpickling Models and QuerySet from 
incompatible
version
-+-
 Reporter:  FunkyBob |Owner:
 Type:  New feature  |  anubhav9042
Component:  Database layer   |   Status:  assigned
  (models, ORM)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by loic84):

 We discussed this on IRC with Anubhav and Simon.

 My understanding of the issue is that we can't detect if a pickle is
 really incompatible since unpickling gives us silently corrupted objects
 rather than hard failures.

 The proposed patch
 (https://github.com/coder9042/django/compare/gsoc_21430) raises an
 exception every time a pickle from another major version is detected,
 based on the premise that we "try" not to break pickle in minor version.
 While it's true that minor releases are less likely to break pickling, a
 security issue or a data-loss issue could easily require a change in the
 ORM that would break pickling.

 I proposed we used runtime warnings rather than exceptions when **any**
 version mismatch is detected, these can easily be ignored if you've never
 cared/encountered the problem, but when you are affected, you'll clearly
 get a pointer to the issue. Another option is to mix the two approaches,
 forbid pickles across major versions with exceptions, and only warn about
 pickles across minor version.

 Our "release checklist" documentation could also add a recommendation of
 clearing pickled objects when upgrading Django.

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

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

Re: [Django] #22436: migrations fail on custom upload_to on ImageField

[Django]

#22436: migrations fail on custom upload_to on ImageField
-+-
 Reporter:  David Binetti|Owner:
     |  andrewgodwin
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:
 Severity:  Release blocker  |  1.7-beta-2
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  1|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by andrewgodwin):

 You do need the upload_to attribute in migrations, as well as help text,
 as they can affect the usage of fields inside RunPython segments, or other
 field subclasses might use help_text for something that's not just
 display. South tried the whitelist and blacklist approaches here and both
 were flawed.

 I've consulted with people and there's literally no sane way to get a
 pointer to a function like that if it's reused directly from the class
 body; the fix is to move the function outside of the class body.

 The fix for this will be a check which makes sure the referenced function
 is importable and gives the above advice if it is not.

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

Re: [Django] #22470: Migrations fail with order_with_respect_to and ForeignKey to self

[Django]

#22470: Migrations fail with order_with_respect_to and ForeignKey to self
-+-
 Reporter:  Jonas|Owner:
 Type:  Bug  |  andrewgodwin
Component:  Migrations   |   Status:  assigned
 Severity:  Release blocker  |  Version:
 Keywords:  migrations   |  1.7-beta-1
  order_with_respect_to  |   Resolution:
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by andrewgodwin):

 Just noting that this will be fixed as part of the big autodetector
 rewrite.

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

Re: [Django] #22758: Makemigrations puts subclasses of abstract models in the wrong app

[Django]

#22758: Makemigrations puts subclasses of abstract models in the wrong app
-+--
 Reporter:  cdestigter   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  1.7-beta-2
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by andrewgodwin):

 Also worth noting: This only occurs with an explicit app_label
 declaration. It's fine if the models just normally live in the separate
 apps' model files.

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

Re: [Django] #22758: Makemigrations puts subclasses of abstract models in the wrong app

[Django]

#22758: Makemigrations puts subclasses of abstract models in the wrong app
-+--
 Reporter:  cdestigter   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  1.7-beta-2
 Severity:  Release blocker  |   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 andrewgodwin):

 * needs_better_patch:   => 0
 * component:  Migrations => Core (Other)
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 This looks to be a problem in app loading - I've confirmed that on 1.6
 it's fine, on 1.7 even get_models() puts it in the wrong app. Reassigning
 component, will come back around to fix after migrations if nobody else
 gets there.

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

[django/django] 45fa52: Implement Migration.run_before

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 45fa5201874df2883be003b7ed29ac14751431b8
  
https://github.com/django/django/commit/45fa5201874df2883be003b7ed29ac14751431b8
  Author: Chris Beaven 
  Date:   2014-05-29 (Thu, 29 May 2014)

  Changed paths:
M django/db/migrations/loader.py
M tests/migrations/test_loader.py
A tests/migrations/test_migrations_run_before/0001_initial.py
A tests/migrations/test_migrations_run_before/0002_second.py
A tests/migrations/test_migrations_run_before/0003_third.py
A tests/migrations/test_migrations_run_before/__init__.py

  Log Message:
  ---
  Implement Migration.run_before

This attribute (used for reverse dependencies) was previously declared
and mentioned in the code, but never actually used.


  Commit: 5826dc52827254f44833acf678f429af94b4d636
  
https://github.com/django/django/commit/5826dc52827254f44833acf678f429af94b4d636
  Author: Andrew Godwin 
  Date:   2014-06-05 (Thu, 05 Jun 2014)

  Changed paths:
M django/db/migrations/loader.py
M tests/migrations/test_loader.py
A tests/migrations/test_migrations_run_before/0001_initial.py
A tests/migrations/test_migrations_run_before/0002_second.py
A tests/migrations/test_migrations_run_before/0003_third.py
A tests/migrations/test_migrations_run_before/__init__.py

  Log Message:
  ---
  Merge pull request #2736 from SmileyChris/migration-run_before

Fixed #22725 - Migration.run_before does nothing


Compare: https://github.com/django/django/compare/e071f67b7fb1...5826dc528272

-- 
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/53913597eabdc_10cae2dd4412480%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22725: Migration.run_before does nothing

[Django]

#22725: Migration.run_before does nothing
-+-
 Reporter:  SmileyChris  |Owner:  Andrew
 Type:  Bug  |  Godwin 
Component:  Migrations   |   Status:  closed
 Severity:  Release blocker  |  Version:  master
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:
  Needs tests:  0|  Unreviewed
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Andrew Godwin ):

 * status:  new => closed
 * owner:   => Andrew Godwin 
 * resolution:   => fixed


Comment:

 In [changeset:"5826dc52827254f44833acf678f429af94b4d636"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5826dc52827254f44833acf678f429af94b4d636"
 Merge pull request #2736 from SmileyChris/migration-run_before

 Fixed #22725 - Migration.run_before does nothing
 }}}

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

Re: [Django] #22766: Model derivated fields

[Django]

#22766: Model derivated fields
-+-
 Reporter:  luismasuelli@…   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by russellm):

 * resolution:  wontfix => duplicate


Comment:

 This idea has been proposed a few times in the past, in one of two guises:

 1) A new field on the model that references other fields - much in the
 same way that a GenericForeignKey field does right now. I'm going to guess
 there's some details that need to be finessed, but the basic pieces of
 virtual fields are already in place. See #16508, #373

 2) A variation to annotation that doesn't also imply grouping. See #20930,
 #14030, #11305

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

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

Re: [Django] #22079: TestClient serialization of POST params with empty list as value

[Django]

#22079: TestClient serialization of POST params with empty list as value
-+-
 Reporter:   |Owner:  nobody
  code.djangoproject.com@…   |   Status:  new
 Type:  Bug  |  Version:  master
Component:  Testing framework|   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|
-+-
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/093.7e85497334919f88362d8d52031ab241%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #11211: Add GMarkerOptions: clickable, bouncy, dragCrossMove, bounceGravity, autoPan and hide

[Django]

#11211: Add GMarkerOptions: clickable, bouncy, dragCrossMove, bounceGravity,
autoPan and hide
-+-
 Reporter:  Travis Jeffery   |Owner:  nobody
     |   Status:  new
 Type:  New feature  |  Version:  master
Component:  GIS  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  google, maps,|  Needs documentation:  0
  gmarker, options   |  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/097.6361bbcbeb36661d775c9159e06531e7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #12952: Models history doesn't use verbose names

[Django]

#12952: Models history doesn't use verbose names
---+
 Reporter:  acangiano  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.2-beta
 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


Comment:

 Patch will need to be updated to apply cleanly.

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

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

Re: [Django] #17018: LayerMapping - entries skipped when ForeignKey field has related model missing and null = True

[Django]

#17018: LayerMapping - entries skipped when ForeignKey field has related model
missing and null = True
-+-
 Reporter:  grobertson   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  GIS  |  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:  geodjango,   | Triage Stage:  Accepted
  layermapping   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
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/068.b0cc42d3c9eeb03955e9ab6bfc8e0423%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #13841: Allow context processors access to current version of context

[Django]

#13841: Allow context processors access to current version of context
-+
 Reporter:  mitar|Owner:  copelco
 Type:  New feature  |   Status:  assigned
Component:  Template system  |  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:  0
-+
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/063.28b2971582bcc93d494318907f899df9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #16872: Add touch support to the geographic admin

[Django]

#16872: Add touch support to the geographic admin
-+
 Reporter:  jbronn   |Owner:  jbronn
 Type:  New feature  |   Status:  assigned
Component:  GIS  |  Version:
 Severity:  Normal   |   Resolution:
 Keywords:  gis admin touch  | 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):

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

Re: [Django] #12713: Fire 'onChange' event when adding a new option to a select box

[Django]

#12713: Fire 'onChange' event when adding a new option to a select box
---+
 Reporter:  mishaaq|Owner:  mishaaq
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  js admin onchange  | 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/065.a48722d4fa4038ca0a2b51cadd857c14%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #10191: Fix / Add support for radiobuttons after adding item with popup in Django Admin

[Django]

#10191: Fix / Add support for radiobuttons after adding item with popup in 
Django
Admin
-+-
 Reporter:  trbs |Owner:  bodiddlie
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin, radio,| Triage Stage:  Accepted
  radiolist, |  Needs documentation:  0
  dismissAddAnotherPopup, popup  |  Patch needs improvement:  1
Has patch:  1|UI/UX:  1
  Needs tests:  1|
Easy pickings:  0|
-+-
Changes (by timo):

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


Comment:

 Patch will need to be updated to apply cleanly + 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/062.044d34963d2d24af708a238b6bd3709f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #14483: Implement subqueries in geodjango spatial lookup

[Django]

#14483: Implement subqueries in geodjango spatial lookup
-+
 Reporter:  milosu   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  GIS  |  Version:  1.2
 Severity:  Normal   |   Resolution:
 Keywords:  geodjango, subquery  | 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):

 * needs_better_patch:  0 => 1


Comment:

 Patch will need to be updated to apply cleanly.

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

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

Re: [Django] #13910: Add generator version of Template.render(Context)

[Django]

#13910: Add generator version of Template.render(Context)
-+--
 Reporter:  rooney   |Owner:  mindsocket
 Type:  New feature  |   Status:  assigned
Component:  Template system  |  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:  0
-+--
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/064.bb2a7b39fcc2d70613dddbfe9b8d2cdf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21446: Add possibility to not perform redirect in set_language view

[Django]

#21446: Add possibility to not perform redirect in set_language view
--+
 Reporter:  KJ|Owner:  KJ
 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:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timo):

 * needs_better_patch:  0 => 1
 * easy:  1 => 0


Comment:

 I left comments for improvement on PR. Please uncheck "Patch needs
 improvement" when you update it, thanks.

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

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

Re: [Django] #21139: Document django.utils.functional

[Django]

#21139: Document django.utils.functional
--+
 Reporter:  EvilDMP   |Owner:  EvilDMP
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.5
 Severity:  Normal|   Resolution:  wontfix
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timo):

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


Comment:

 Doesn't seem like this idea has gotten much support.

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

Re: [Django] #21554: incorrect SQL generated when using multiple inheritance

[Django]

#21554: incorrect SQL generated when using multiple inheritance
-+-
 Reporter:  pegler   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  multiple-|  Needs documentation:  0
  inheritance|  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by timo):

 I left comments for improvement on PR. Please uncheck "Patch needs
 improvement" when you update it, thanks.

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

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

Re: [Django] #21696: Allow usage of objects with add_to_query() in filter() calls

[Django]

#21696: Allow usage of objects with add_to_query() in filter() calls
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (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|
-+-
Changes (by timo):

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

Re: [Django] #21461: Add pre_update and post_update signals

[Django]

#21461: Add pre_update and post_update signals
-+-
 Reporter:  loic84   |Owner:  loic84
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by bendavis78):

 * cc: bendavis78 (added)


Comment:

 Yeah, you're right, using the dict is a messy way to solve the problem. I
 guess idea was to put the onus of "type" handling on the pre_save &
 post_save. Ideally the update() method would be agnostic regarding the
 payloads being passed between the signals. I think you've got the right
 idea with using `sender`, though I don't think the API should be
 prescribing those types (ie pks vs querysets).

 Not sure what the right answer is at this point -- maybe someone will come
 up with a more elegant approach.

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

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

[Django]

#15910: show delete links for all admin inline formset rows
-+-
 Reporter:  Arthur de Jong   |Owner:  nobody
   |   Status:  new
 Type:  New feature  |  Version:  1.3
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  1
Easy pickings:  0|
-+-
Changes (by timo):

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


Comment:

 Current patch likely needs to be updated to apply clealy and also could
 use some selenium 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/089.371b1ececb1980db2e533baad04a9ac0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19869: Make changing the active language inside `LiveTestServerCase` possible

[Django]

#19869: Make changing the active language inside `LiveTestServerCase` possible
-+-
 Reporter:  void |Owner:
 Type:  New feature  |  unaizalakain
Component:  Testing framework|   Status:  assigned
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  1
 |UI/UX:  0
-+-
Changes (by timo):

 * needs_better_patch:  0 => 1


Comment:

 If the patch makes apollo13 run, I guess it needs 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/062.0904ebf872405c46ff60d28f6b808cb2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21392: changepassword option to read from stdin

[Django]

#21392: changepassword option to read from stdin
--+-
 Reporter:  pkasid|Owner:  AeroNotix
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-
Changes (by timo):

 * has_patch:  1 => 0


Comment:

 The ticket has "Has patch" set, but I don't see a patch or a link to a
 pull request?

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

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

Re: [Django] #18355: Add ordering mixin for class based generic views

[Django]

#18355: Add ordering mixin for class based generic views
---+-
 Reporter:  aaugustin  |Owner:  pjrharley
 Type:  New feature|   Status:  assigned
Component:  Generic views  |  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:  0
---+-
Changes (by timo):

 * needs_better_patch:  0 => 1


Comment:

 I left comments for improvement on PR. Please uncheck "Patch needs
 improvement" when you update it, thanks.

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

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

Re: [Django] #20296: django.utils.safestring.mark_safe forces evaluation of lazy objects

[Django]

#20296: django.utils.safestring.mark_safe forces evaluation of lazy objects
-+
 Reporter:  bmispelon|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Utilities|  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:  0
-+
Changes (by timo):

 * needs_better_patch:  0 => 1


Comment:

 The current PR does not merge cleanly.

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

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

Re: [Django] #17958: Add a capture_logging test util

[Django]

#17958: Add a capture_logging test util
---+
 Reporter:  claudep|Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  logging| 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):

 * needs_better_patch:  0 => 1


Comment:

 We resolved the linked ticket without this -- do we still want/need it?

 In any case, I'm sure it needs to be updated to apply cleanly.

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

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

Re: [Django] #22772: django.contrib.formtools test failures on Windows due to failure to delete file that is being used by another process

[Django]

#22772: django.contrib.formtools test failures on Windows due to failure to 
delete
file that is being used by another process
---+--
 Reporter:  manfre |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.formtools  |  Version:  1.7-beta-2
 Severity:  Release blocker|   Resolution:
 Keywords:  Windows| 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):

 * type:  Uncategorized => Bug
 * 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/064.32dab584f94c008426cc4556f968297e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #5419: Add a model fuzz testing method to the test framework

[Django]

#5419: Add a model fuzz testing method to the test framework
---+
 Reporter:  adrian |Owner:  kkubasik
 Type:  New feature|   Status:  closed
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:  wontfix
 Keywords:  feature| 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):

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


Comment:

 Agreed with Aymeric's comment from 19 months ago, it doesn't seem like
 this is something that Django needs to provide.

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

Re: [Django] #21255: Django doesn't closes connection when running from management command

[Django]

#21255: Django doesn't closes connection when running from management command
-+-
 Reporter:  kabakov.as@… |Owner:  tuxcanfly
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  connection postgres  |  Needs documentation:  0
  management |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

 * needs_better_patch:  0 => 1


Comment:

 Current PR has comments for improvement. Please uncheck "Patch needs
 improvement" when you update it, thanks.

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

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

Re: [Django] #22391: fallback to pymysql if MySQLdb not available

[Django]

#22391: fallback to pymysql if MySQLdb not available
-+-
 Reporter:  CollinAnderson   |Owner:  nobody
 Type:  New feature  |   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:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * needs_better_patch:  0 => 1


Comment:

 Maybe this needs discussion on the mailing list for a resolution. One
 question I have is how we are going to ensure that it doesn't break if we
 merge it to core. Do we need another MySQL build to the Jenkins matrix?

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

Re: [Django] #7599: add get_user_permissions method to ModelBackend

[Django]

#7599: add get_user_permissions method to ModelBackend
--+--
 Reporter:  gwilson   |Owner:  jorgecarleitao
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  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:  0
--+--
Changes (by timo):

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


Comment:

 Please uncheck "Patch needs improvement" when you update the PR, thanks.

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

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

Re: [Django] #21548: Add the ability to limit file extensions for ImageField and FileField

[Django]

#21548: Add the ability to limit file extensions for ImageField and FileField
-+
 Reporter:  timo |Owner:  jfilipe
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by timo):

 * needs_better_patch:  0 => 1
 * needs_docs:  0 => 1


Comment:

 Hi, I left a comment for improvement on the PR, although it's better to
 open a PR against Django itself instead of your fork.

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

Re: [Django] #21461: Add pre_update and post_update signals

[Django]

#21461: Add pre_update and post_update signals
-+-
 Reporter:  loic84   |Owner:  loic84
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
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/064.96ba14d3dee722432d9bd8568344e0df%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22774: collectstatic does not work with zipped (egg) packages

[Django]

#22774: collectstatic does not work with zipped (egg) packages
+
 Reporter:  minder  |  Owner:  nobody
 Type:  Uncategorized   | Status:  new
Component:  Core (Management commands)  |Version:  1.6
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 I installed django-select2 which worked perfectly in my test venvironment.
 But during deployment, when I ran ./manage.py collectstatic, required
 files were not copied. It turned out that the package was installed as
 egg.

 I couldn't find a topic about this problem except
 [https://github.com/jorgebastida/django-dajax/issues/53 this ticket on
 django-dajax]. This issue is present in currently stable Django (1.6.5).

 The only solution by now is to reinstall the package manually enforcing
 unzipped installation.

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

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

[django/django] 5c95a5: Checked can_introspect_null feature in a test.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 5c95a55330bc2531405700a399bfb555bfe80120
  
https://github.com/django/django/commit/5c95a55330bc2531405700a399bfb555bfe80120
  Author: Aymeric Augustin 
  Date:   2014-06-06 (Fri, 06 Jun 2014)

  Changed paths:
M tests/inspectdb/tests.py

  Log Message:
  ---
  Checked can_introspect_null feature in a test.

Forward-port of 1238f92c from stable/1.7.x.


  Commit: e071f67b7fb1aa171baf5fb1f57310007cc91ab4
  
https://github.com/django/django/commit/e071f67b7fb1aa171baf5fb1f57310007cc91ab4
  Author: Aymeric Augustin 
  Date:   2014-06-06 (Fri, 06 Jun 2014)

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

  Log Message:
  ---
  Replaced an explicit vendor check by a feature flag.

Forward-port of c9aedce0 from stable/1.7.x.


Compare: https://github.com/django/django/compare/484f3edf1e79...e071f67b7fb1

-- 
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/5390effbc5109_5e2e573d3498289%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 1238f9: Checked can_introspect_null feature in a test.

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 1238f92c649ccd4ba99da0ce70be7597c90515d4
  
https://github.com/django/django/commit/1238f92c649ccd4ba99da0ce70be7597c90515d4
  Author: Aymeric Augustin 
  Date:   2014-06-06 (Fri, 06 Jun 2014)

  Changed paths:
M tests/inspectdb/tests.py

  Log Message:
  ---
  Checked can_introspect_null feature in a test.


  Commit: c9aedce01ae54f26d612b070ded57d2cb3eb8483
  
https://github.com/django/django/commit/c9aedce01ae54f26d612b070ded57d2cb3eb8483
  Author: Aymeric Augustin 
  Date:   2014-06-06 (Fri, 06 Jun 2014)

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

  Log Message:
  ---
  Replaced an explicit vendor check by a feature flag.


Compare: https://github.com/django/django/compare/4ad299f287e6...c9aedce01ae5

-- 
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/5390efc1d3b5_637b4c9d34586ba%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22765: South to Migrations detail

[Django]

#22765: South to Migrations detail
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Migrations   |  1.7-beta-2
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  south, migrations| Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by mardini):

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


Comment:

 Hello craiglabenz,

 Please use [https://groups.google.com/forum/#!forum/django-users django-
 users mailing list] to ask questions about using Django. Tickets are only
 used to report bugs and suggest new features.

 Thanks.

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

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

Re: [Django] #20550: Add an option to preserve the database between test runs

[Django]

#20550: Add an option to preserve the database between test runs
---+
 Reporter:  aaugustin  |Owner:  gchp
 Type:  New feature|   Status:  assigned
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by gchp):

 Created a PR here: https://github.com/django/django/pull/2764

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

Re: [Django] #22766: Model derivated fields

[Django]

#22766: Model derivated fields
-+-
 Reporter:  luismasuelli@…   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by mardini):

 * status:  new => closed
 * version:  1.6 => master
 * resolution:   => wontfix


Comment:

 I personally don't think this is an important feature, since there are so
 many ways to do that (you're aware of at least some of them).

 Nevertheless, please first request the feature on the
 [https://groups.google.com/d/forum/django-developers django-developers
 mailing list]. It’ll get read more closely if it’s on the mailing list.
 This is even more important for big feature requests like this one (and
 pretty much every new feature in the ORM).

 Please re-open if the decision after discussion is to implement the
 feature.

 Thanks.

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

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

[Django] #22773: makemessages bug

[Django]

#22773: makemessages bug
+--
 Reporter:  anonymous   |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Core (Management commands)  |Version:  1.7-beta-2
 Severity:  Normal  |   Keywords:  makemessages
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+--
 If templatize return empty string, then raise exception on fp.write.

 django 1.7b4
 makemessages.py:97
 {{{
 content = templatize(src_data, orig_file[2:])  # return '' (str)
 with io.open(os.path.join(self.dirpath, thefile), "w", encoding='utf-8')
 as fp:
 fp.write(content)  # TypeError: must be unicode, not str
 }}}

 Tested in Windows7x64, Python 2.7.7x87

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

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

Re: [Django] #22772: django.contrib.formtools test failures on Windows due to failure to delete file that is being used by another process

[Django]

#22772: django.contrib.formtools test failures on Windows due to failure to 
delete
file that is being used by another process
---+--
 Reporter:  manfre |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  contrib.formtools  |  Version:  1.7-beta-2
 Severity:  Release blocker|   Resolution:
 Keywords:  Windows| Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by manfre):

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


Comment:

 Bisect:

 fa8b4735287c92b03d23823de8a4e1168d1951d9 is the first bad commit
 commit fa8b4735287c92b03d23823de8a4e1168d1951d9
 Author: Simon Charette 
 Date:   Fri Mar 21 03:38:25 2014 -0400

 Fixed #22299 -- Cleanup wizard temp files when possible.

 Thanks to @erikr for the review.

 :04 04 de97d643027f86341b993b19cf2b1896112a9ad5
 c488ebce1872f6fe8d51ec97e724d30e569c7ed0 M  django
 :04 04 232d71b4aad76a1a62b7e93015ac0863769a04e4
 bf1b2199bdd62a95f0666219607ce2a2a8a8a96f M  docs

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

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

[Django] #22772: django.contrib.formtools test failures on Windows due to failure to delete file that is being used by another process

[Django]

#22772: django.contrib.formtools test failures on Windows due to failure to 
delete
file that is being used by another process
---+
 Reporter:  manfre |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  contrib.formtools  |Version:  1.7-beta-2
 Severity:  Release blocker|   Keywords:  Windows
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 One of many similar errors with Windows, Python 2.7, Django stable/1.7.x,
 and sqlite.

 {{{
 ==
 ERROR: test_form_refresh
 (django.contrib.formtools.tests.wizard.wizardtests.tests.CookieWizardTests)
 --
 Traceback (most recent call last):
   File
 
"C:\projects\django\django\django\contrib\formtools\tests\wizard\wizardtests\tests.py",
 line 49, in tearDown
 temp_storage.delete(file)
   File "C:\projects\django\django\django\core\files\storage.py", line 262,
 in delete
 os.remove(name)
 WindowsError: [Error 32] The process cannot access the file because it is
 being used by another process:
 u'c:\\users\\manfre\\appdata\\local\\temp\\django_sqv5du\\tmpruqopl\\tests.py'
 }}}

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

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

Re: [Django] #22760: Add a system check for context processors which trigger database queries

[Django]

#22760: Add a system check for context processors which trigger database queries
-+-
 Reporter:  Keryn Knight |Owner:  nobody
   |   Status:  closed
 Type:  New feature  |  Version:  master
Component:  Template system  |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Keryn Knight ):

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


Comment:

 Ah, that's fair enough. I'll close as an invalid use of the check
 framework, then.

 Should the system checks usage ever shift towards providing guidelines and
 hints to developers, and this ticket becomes useful, a quickly whipped
 together implementation of the check I was suggesting is
 [https://github.com/kezabelle/django-
 morechecks/blob/master/morechecks/checks.py 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/095.7e2eca43a7a11208da7616c582a74569%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #18400: Unexpected {% if %} behavior

[Django]

#18400: Unexpected {% if %} behavior
--+
 Reporter:  apollo13  |Owner:  susan
 Type:  Bug   |   Status:  closed
Component:  Template system   |  Version:  1.4
 Severity:  Normal|   Resolution:  fixed
 Keywords:  template, if, length  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"484f3edf1e79388f73dcb07e39d79d0c5029ae9e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="484f3edf1e79388f73dcb07e39d79d0c5029ae9e"
 Fixed #18400 -- Modified length template filter to return 0 for unknown
 variables.

 Thanks Florian for the bug report, luyikei for the initial code patch, and
 Bouke for the code review feedback.
 }}}

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

[django/django] 484f3e: Fixed #18400 -- Modified length template filter to...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 484f3edf1e79388f73dcb07e39d79d0c5029ae9e
  
https://github.com/django/django/commit/484f3edf1e79388f73dcb07e39d79d0c5029ae9e
  Author: Susan Tan 
  Date:   2014-06-05 (Thu, 05 Jun 2014)

  Changed paths:
M django/template/defaultfilters.py
M docs/ref/templates/builtins.txt
M docs/releases/1.8.txt
M tests/template_tests/filters.py

  Log Message:
  ---
  Fixed #18400 -- Modified length template filter to return 0 for unknown 
variables.

Thanks Florian for the bug report, luyikei for the initial code patch, and
Bouke for the code review feedback.


-- 
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/5390c857be6ba_5784cefd38721a2%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] f5b6b2: [1.6.x] Fix missing highlighting in some code exam...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: f5b6b25c5f9acbb336d87d1ef87722caca5c1d3e
  
https://github.com/django/django/commit/f5b6b25c5f9acbb336d87d1ef87722caca5c1d3e
  Author: Éric Araujo 
  Date:   2014-06-05 (Thu, 05 Jun 2014)

  Changed paths:
M docs/topics/db/queries.txt

  Log Message:
  ---
  [1.6.x] Fix missing highlighting in some code examples

Backport of 84cafc2b35 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/5390c1a11b7e2_1230fb1d3c7509f%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 4ad299: [1.7.x] Fix missing highlighting in some code exam...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 4ad299f287e6b8bc4ccd0ecbbfd1efcf4aca8251
  
https://github.com/django/django/commit/4ad299f287e6b8bc4ccd0ecbbfd1efcf4aca8251
  Author: Éric Araujo 
  Date:   2014-06-05 (Thu, 05 Jun 2014)

  Changed paths:
M docs/topics/db/queries.txt

  Log Message:
  ---
  [1.7.x] Fix missing highlighting in some code examples

Backport of 84cafc2b35 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/5390c1a3957ec_578b617d44991ba%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 84cafc: Fix missing highlighting in some code examples

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 84cafc2b3575fe1040c5ed98d3f82d3b42d606f7
  
https://github.com/django/django/commit/84cafc2b3575fe1040c5ed98d3f82d3b42d606f7
  Author: Éric Araujo 
  Date:   2014-06-05 (Thu, 05 Jun 2014)

  Changed paths:
M docs/topics/db/queries.txt

  Log Message:
  ---
  Fix missing highlighting in some code examples


-- 
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/5390c17d16ef7_636c1229d4470012%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22769: transaction.automic is not working as expected with Oracle DB for raw sql

[Django]

#22769: transaction.automic is not working as expected with Oracle DB for raw 
sql
-+-
 Reporter:  manish_kumar9@…  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 A few questions...

 - When you're testing on MySQL, are you using the MyISAM or the InnoDB
 storage engine? (Since MyISAM doesn't support transactions, that would
 make the comparison irrelevant.)
 - Where is `self.cursor` coming from in your example?
 - Are you using more than one 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/084.718c19e30dd8e3b20244cdaaae5aac49%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #20550: Add an option to preserve the database between test runs

[Django]

#20550: Add an option to preserve the database between test runs
---+
 Reporter:  aaugustin  |Owner:  gchp
 Type:  New feature|   Status:  assigned
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by manfre):

 * cc: mmanfre@… (added)


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

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

[Django] #22771: TestCase.client.logout fails when using custom authentication backend not based on AUTH_USER_MODEL

[Django]

#22771: TestCase.client.logout fails when using custom authentication backend 
not
based on AUTH_USER_MODEL
-+-
 Reporter:  xafer|  Owner:  nobody
 Type:  Uncategorized| Status:  new
Component:  Testing  |Version:  1.6
  framework  |   Keywords:  logout test AUTH_USER_MODEL
 Severity:  Normal   |  Has patch:  0
 Triage Stage:  Unreviewed   |  UI/UX:  0
Easy pickings:  0|
-+-
 Hello !

 I'm not sure if it's a bug or a new feature:

 TestCase.client.login calls django.contrib.auth.login(request, user)
 which stores the user id and its backend in the request's session:
 request.session[SESSION_KEY] = user.pk
 request.session[BACKEND_SESSION_KEY] = user.backend

 But in TestCase.client.logout calls, Django tries to get the authenticated
 user with:
 uid = self.session.get(SESSION_KEY)
 request.user = UserModel._default_manager.get(pk=uid)

 assuming user is a AUTH_USER_MODEL and without checking its
 BACKEND_SESSION_KEY...

 It would seem cleaner to actually rly on django.contrib.auth.get_user to
 find the correct user (whatever its type) and allow the concurrent use of
 multiple user models (typically user model and customer model...).

 See https://github.com/xavfernandez/django_test_client_bugreport for a
 failing example.

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

[django/django] 5643a3: Fixed #10811 -- Made assigning unsaved objects to ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 5643a3b51be338196d0b292d5626ad43648448d3
  
https://github.com/django/django/commit/5643a3b51be338196d0b292d5626ad43648448d3
  Author: Anubhav Joshi 
  Date:   2014-06-05 (Thu, 05 Jun 2014)

  Changed paths:
M django/contrib/contenttypes/fields.py
M django/db/models/fields/related.py
M docs/releases/1.8.txt
M docs/topics/db/examples/many_to_one.txt
M docs/topics/db/examples/one_to_one.txt
M tests/admin_util/tests.py
M tests/contenttypes_tests/tests.py
M tests/many_to_one_regress/tests.py
M tests/multiple_database/tests.py
M tests/one_to_one/models.py
M tests/one_to_one/tests.py
M tests/one_to_one_regress/tests.py

  Log Message:
  ---
  Fixed #10811 -- Made assigning unsaved objects to FK, O2O, and GFK raise 
ValueError.

This prevents silent data loss.

Thanks Aymeric Augustin for the initial patch and Loic Bistuer for the review.


-- 
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/5390a5138bca3_116c1389d38118758%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #10811: Assigning unsaved model to a ForeignKey leads to silent failures

[Django]

#10811: Assigning unsaved model to a ForeignKey leads to silent failures
-+-
 Reporter:  Glenn|Owner:
 Type:  Bug  |  anubhav9042
Component:  Database layer   |   Status:  closed
  (models, ORM)  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"5643a3b51be338196d0b292d5626ad43648448d3"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5643a3b51be338196d0b292d5626ad43648448d3"
 Fixed #10811 -- Made assigning unsaved objects to FK, O2O, and GFK raise
 ValueError.

 This prevents silent data loss.

 Thanks Aymeric Augustin for the initial patch and Loic Bistuer for the
 review.
 }}}

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

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

Re: [Django] #22769: transaction.automic is not working as expected with Oracle DB for raw sql

[Django]

#22769: transaction.automic is not working as expected with Oracle DB for raw 
sql
-+-
 Reporter:  manish_kumar9@…  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by manish_kumar9@…):

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


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

Re: [Django] #22769: transaction.automic is not working as expected with Oracle DB for raw sql

[Django]

#22769: transaction.automic is not working as expected with Oracle DB for raw 
sql
-+-
 Reporter:  manish_kumar9@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  needsinfo
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by manish_kumar9@…):

 Added code sample which is failing. Note : Instead of using
 @transaction.atomic if we put explicit commit i.e.
 self.connection.commit(), everything works fine.

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

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

Re: [Django] #22601: Migrations don't recognize fields added by mixins

[Django]

#22601: Migrations don't recognize fields added by mixins
---+--
 Reporter:  semenov|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.7-beta-2
 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 EvilDMP):

 I have had trouble in the past when trying to create mixins for models
 that had fields, but inherited from `object` rather than from `Model`.

 I can't remember what these problems were; sorry to be vague.

 On the other hand I have had no problems whatsoever creating numerous
 abstract model mixin classes, and building models using multiple mixins.
 It shouldn't be a 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/065.8344f8240c7711f30a6882977e6f9d84%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 4f72e5: Fixed #21773 -- made daemon threads default in the...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 4f72e5f03ae803fd9faa1445245c1050ca004526
  
https://github.com/django/django/commit/4f72e5f03ae803fd9faa1445245c1050ca004526
  Author: Moayad Mardini 
  Date:   2014-06-05 (Thu, 05 Jun 2014)

  Changed paths:
M django/core/servers/basehttp.py
M docs/releases/1.8.txt

  Log Message:
  ---
  Fixed #21773 -- made daemon threads default in the development server.

Thanks clime 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/53909a4cd928e_8131163d3861751%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21773: development server sometimes takes a long time to restart after source has been changed

[Django]

#21773: development server sometimes takes a long time to restart after source 
has
been changed
-+-
 Reporter:  clime|Owner:  mardini
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |   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 Tim Graham ):

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


Comment:

 In [changeset:"4f72e5f03ae803fd9faa1445245c1050ca004526"]:
 {{{
 #!CommitTicketReference repository=""
 revision="4f72e5f03ae803fd9faa1445245c1050ca004526"
 Fixed #21773 -- made daemon threads default in the development server.

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

Re: [Django] #20550: Add an option to preserve the database between test runs

[Django]

#20550: Add an option to preserve the database between test runs
---+-
 Reporter:  aaugustin  |Owner:  aaugustin
 Type:  New feature|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by gchp):

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


Comment:

 Re-opening this per a discussion on IRC where it was highlighted that
 `BaseDatabaseCreation.create_test_db` receives the new `keepdb` option,
 but `BaseDatabaseCreation.destroy_test_db` (and subclasses) do not, which
 leaves a strange asymmetry.

 I'm putting together a patch for this now.

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

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

Re: [Django] #20550: Add an option to preserve the database between test runs

[Django]

#20550: Add an option to preserve the database between test runs
---+
 Reporter:  aaugustin  |Owner:  gchp
 Type:  New feature|   Status:  assigned
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by gchp):

 * owner:  aaugustin => gchp
 * status:  new => assigned


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

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

Re: [Django] #22601: Migrations don't recognize fields added by mixins

[Django]

#22601: Migrations don't recognize fields added by mixins
---+--
 Reporter:  semenov|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.7-beta-2
 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 semenov):

 I am disappointed by the fix. The inconsistency in the behaviour is still
 there. Non-Model-derived mixins that have Fields are still fully supported
 by all Django modules except the migrations. In the example above, syncdb
 '''will''' create the `tux` field in the database, QuerySets '''will'''
 fetch it, and object instances '''will''' have the `tux` property. Only
 the migrations module will silently ignore it.

 If for some reason the migrations module can not be fixed to support non-
 Model-derived mixins (really? how come everything else works then?), they
 should be '''forbidden''' to use by the model meta class. The current
 implementation leaves a place for silent and hard to find mistakes, which
 is a ''bad thing''. Having a clause in the documentation is not an excuse
 for leaving such pitfalls.

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

[django/django] e56055: Fixed #22746 -- Removed background property from p...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e560558ecb3a727c8f3f23e3a036413f8d8679eb
  
https://github.com/django/django/commit/e560558ecb3a727c8f3f23e3a036413f8d8679eb
  Author: Konstantin Koroviev 
  Date:   2014-06-05 (Thu, 05 Jun 2014)

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

  Log Message:
  ---
  Fixed #22746 -- Removed background property from pre/code in admin CSS.


-- 
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/539094cfa92da_46a825d3479147%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22746: CSS glitch in the admin interface.

[Django]

#22746: CSS glitch in the admin interface.
---+---
 Reporter:  kkoroviev@…|Owner:  kkoroviev@…
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.6
 Severity:  Normal |   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"e560558ecb3a727c8f3f23e3a036413f8d8679eb"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e560558ecb3a727c8f3f23e3a036413f8d8679eb"
 Fixed #22746 -- Removed background property from pre/code in admin CSS.
 }}}

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

[django/django] 342b25: [1.7.x] Added a flag for the ability to introspect...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 342b25449d800ce29ae56ff8285869cbc3133a75
  
https://github.com/django/django/commit/342b25449d800ce29ae56ff8285869cbc3133a75
  Author: Aymeric Augustin 
  Date:   2014-06-05 (Thu, 05 Jun 2014)

  Changed paths:
M django/db/backends/__init__.py
M django/db/backends/oracle/base.py
M tests/introspection/tests.py

  Log Message:
  ---
  [1.7.x] Added a flag for the ability to introspect nullable fields.

Previously this was conflated with another Oracle-specific behavior.

Backport of a03d38d 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/53909389d0502_58ab13efd40558fb%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] a03d38: Added a flag for the ability to introspect nullabl...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a03d38ddd43957a402b64caddf74a73df72140fb
  
https://github.com/django/django/commit/a03d38ddd43957a402b64caddf74a73df72140fb
  Author: Aymeric Augustin 
  Date:   2014-06-05 (Thu, 05 Jun 2014)

  Changed paths:
M django/db/backends/__init__.py
M django/db/backends/oracle/base.py
M tests/introspection/tests.py

  Log Message:
  ---
  Added a flag for the ability to introspect nullable fields.

Previously this was conflated with another Oracle-specific behavior.


-- 
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/5390936fc2c80_601377dd3c711c%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 237c22: Avoided using BinaryField unecessarily in tests.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 237c229b91ae852ac5f4f0a52b37de3e243ee61f
  
https://github.com/django/django/commit/237c229b91ae852ac5f4f0a52b37de3e243ee61f
  Author: Aymeric Augustin 
  Date:   2014-06-05 (Thu, 05 Jun 2014)

  Changed paths:
M tests/backends/models.py
M tests/backends/tests.py

  Log Message:
  ---
  Avoided using BinaryField unecessarily in tests.

Several database backends struggle with binary data. This change
minimizes the risk of unrelated tests failures when binary fields
trigger errors.

Forward-port of 2e4bcb9b from stable/1.7.x.


-- 
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/5390889a620e5_116c1389d38111569%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 2e4bcb: Avoided using BinaryField unecessarily in tests.

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 2e4bcb9b0265ceb0ef0eae6da2a91f89d037d05f
  
https://github.com/django/django/commit/2e4bcb9b0265ceb0ef0eae6da2a91f89d037d05f
  Author: Aymeric Augustin 
  Date:   2014-06-05 (Thu, 05 Jun 2014)

  Changed paths:
M tests/backends/models.py
M tests/backends/tests.py

  Log Message:
  ---
  Avoided using BinaryField unecessarily in tests.

Several database backends struggle with binary data. This change
minimizes the risk of unrelated tests failures when binary fields
trigger errors.


-- 
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/539088815b5b5_10cae2dd441026b9%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 4fb50a: Reordered setUp code in prefetch_related tests.

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 4fb50a9a82a15134a72c4c77fe57e641002b7340
  
https://github.com/django/django/commit/4fb50a9a82a15134a72c4c77fe57e641002b7340
  Author: Aymeric Augustin 
  Date:   2014-06-05 (Thu, 05 Jun 2014)

  Changed paths:
M tests/prefetch_related/tests.py

  Log Message:
  ---
  Reordered setUp code in prefetch_related tests.

This allows these tests to run on databases that reject duplicate NULL
values in unique fields e.g. SQL Server.


-- 
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/53907f8d76f62_6664df3d3831759%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] ae3fe6: Reordered setUp code in prefetch_related tests.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ae3fe6ccbb925236aa3cfc9173d2d307634fded4
  
https://github.com/django/django/commit/ae3fe6ccbb925236aa3cfc9173d2d307634fded4
  Author: Aymeric Augustin 
  Date:   2014-06-05 (Thu, 05 Jun 2014)

  Changed paths:
M tests/prefetch_related/tests.py

  Log Message:
  ---
  Reordered setUp code in prefetch_related tests.

This allows these tests to run on databases that reject duplicate NULL
values in unique fields e.g. SQL Server.

Forward port of 4fb50a9a from stable/1.7.x.


-- 
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/53907fabe037a_57f5f79d3865029%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22690: 'Proxy model contains model fields' error

[Django]

#22690: 'Proxy model contains model fields' error
-+-
 Reporter:  cdestigter   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |  1.7-beta-2
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  0|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by CollinAnderson):

 * cc: cmawebsite@… (added)


Comment:

 I also am using model fields on proxy models and I'll add overriding
 _check_model to my hacky code. (How else do you get virtual, non-database
 fields to show up both on the model _and_ in the admin?)

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

[Django] #22770: Remove create_superuser from post_migrate signals

[Django]

#22770: Remove create_superuser from post_migrate signals
+
   Reporter:  timo  |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  contrib.auth  |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 In IRC, Loic and I were in agreement that the prompt to create a superuser
 every time after you run `migrate` can be annoying. Running
 `createsuperuser` manually is not much of a burden if you do need it. I
 think we could make the change without a deprecation as it's not clear to
 me that doing so would offer any benefits.

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

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

Re: [Django] #22563: Migration of admin.LogEntry.user fails.

[Django]

#22563: Migration of admin.LogEntry.user fails.
-+
 Reporter:  efrinut@…|Owner:  andrewgodwin
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-beta-2
 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
-+
Changes (by segfault):

 * cc: segfault (added)


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

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

Re: [Django] #22767: Unexpected value for an unset variable with length filter in templates

[Django]

#22767: Unexpected value for an unset variable with length filter in templates
-+--
 Reporter:  Walkman  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.6
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by timo):

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


Comment:

 Duplicate of #18400.

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

Re: [Django] #22767: Unexpected value for an unset variable with length filter in templates

[Django]

#22767: Unexpected value for an unset variable with length filter in templates
-+--
 Reporter:  Walkman  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by gchp):

 Saying that, I would still expect the `length` filter to return `0` unless
 the length is indeed something other than that. From taking a quick look,
 it seems to return an empty string if the value given does not support
 `len()`. I changed this to instead return `0` and it does indeed fix the
 issue, though it makes a ton of tests fail. Perhaps someone with a little
 more experience with filters can provide some insight as to why it
 currently returns a string?

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

Re: [Django] #22767: Unexpected value for an unset variable with length filter in templates

[Django]

#22767: Unexpected value for an unset variable with length filter in templates
-+--
 Reporter:  Walkman  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.6
 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 gchp):

 * cc: gregchapple1@… (added)


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

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

Re: [Django] #22767: Unexpected value for an unset variable with length filter in templates

[Django]

#22767: Unexpected value for an unset variable with length filter in templates
-+--
 Reporter:  Walkman  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.6
 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 gchp):

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


Comment:

 I agree that this is somewhat unexpected, though I don't know if it's a
 bug. If you were to do the same in Python, and tried to get the length of
 something which is None, you would get a TypeError. To get around that you
 would either use a try/except block, or first check if the variable is not
 None. I think it's reasonable to do the same in your templates. ie:

 {{{
 {% if groups %}
 {% if groups|length > 0 %}
groups!
 {% else %}
no groups :(
 {% endif %}
 {% else %}
 groups not defined
 {% end %}
 }}}

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

Re: [Django] #22769: transaction.automic is not working as expected with Oracle DB for raw sql

[Django]

#22769: transaction.automic is not working as expected with Oracle DB for raw 
sql
-+-
 Reporter:  manish_kumar9@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  needsinfo
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by shai):

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


Comment:

 Hi,

 We'd appreciate a little more details about this. A code sample that works
 with !MySql and fails with Oracle will be nice.

 When adding more details, please reopen the bug.

 Thanks,
 Shai.

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

[Django] #22769: transaction.automic is not working as expected with Oracle DB for raw sql

[Django]

#22769: transaction.automic is not working as expected with Oracle DB for raw 
sql
--+
 Reporter:  manish_kumar9@…   |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.6
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 We have an usecase to store Blob data to DB. We are using raw sql to do
 that. We are wrapping method having this code with transaction.atomic
 decorator. The scenario work fine for MySQL database, but it fails with
 oracle DB. It works fine if we use self.connection.commit() explicit
 inside the method.

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

[Django] #22768: CreateUpdateView view class

[Django]

#22768: CreateUpdateView view class
-+-
 Reporter:   |  Owner:  nobody
  adi.andreias@… | Status:  new
 Type:  New  |Version:  master
  feature|   Keywords:  CBV class based view update create
Component:  Generic  |  CreateUpdateView
  views  |  Has patch:  0
 Severity:  Normal   |  UI/UX:  0
 Triage Stage:   |
  Unreviewed |
Easy pickings:  1|
-+-
 I think it makes sense to have a Class-based view for both updating and
 creating model objects.

 BaseUpdateView and BaseCreateView differ by just two lines, one in get()
 and one in post():
 https://github.com/django/django/blob/1.7b4/django/views/generic/edit.py#L218
 https://github.com/django/django/blob/1.7b4/django/views/generic/edit.py#L195

 A CreateUpdateView view would distinguish between create and update based
 on a slug, pk or similar (configurable?) parameter in url.

 There are situations where the view class contains a lot of code logic
 (like a secondary formset, ajax requests handled along with regular
 requests, etc.) and having separate classes for create and update would
 result in duplicate code.

 I also think this is a common pattern and deserves to be added to Django
 core.

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

[django/django] 52d952: Fixed RST syntax in 1.8 release docs.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 52d9521354daa7a2d3a335be971459a7310dd29f
  
https://github.com/django/django/commit/52d9521354daa7a2d3a335be971459a7310dd29f
  Author: Zbigniew Siciarz 
  Date:   2014-06-05 (Thu, 05 Jun 2014)

  Changed paths:
M docs/releases/1.8.txt

  Log Message:
  ---
  Fixed RST syntax in 1.8 release docs.


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

Re: [Django] #13956: Indefinite args for simpletags and inclusion tags

[Django]

#13956: Indefinite args for simpletags and inclusion tags
-+-
 Reporter:  melinath |Owner:  julien
 Type:  New feature  |   Status:  closed
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  simple_tag,  | Triage Stage:  Ready for
  simpletag  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by pczerkas@…):

 I think that one piece is still missing. How about allowing to pass
 args/kwargs to templatetags:
 {{{
 {% some_tag named_args *args **kwargs %}
 }}}
 where args is a list, kwargs is a dict?

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

Re: [Django] #22563: Migration of admin.LogEntry.user fails.

[Django]

#22563: Migration of admin.LogEntry.user fails.
-+
 Reporter:  efrinut@…|Owner:  andrewgodwin
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-beta-2
 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 melinath):

 FTR, I'm getting this with the app containing the {{{AUTH_USER_MODEL}}}
 coming ''before'' {{{django.contrib.admin}}}

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