date:20140611

[django/django] 631d0b: [1.6.x] Fixed #22813 -- Updated Pillow URL in docu...

2014-06-11 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 631d0bb2da28eee753c562d3a07f248495118823
  
https://github.com/django/django/commit/631d0bb2da28eee753c562d3a07f248495118823
  Author: Claude Paroz 
  Date:   2014-06-12 (Thu, 12 Jun 2014)

  Changed paths:
M docs/ref/forms/fields.txt
M docs/ref/models/fields.txt

  Log Message:
  ---
  [1.6.x] Fixed #22813 -- Updated Pillow URL in documentation

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

Re: [Django] #22813: Dead link to Pillow library website

2014-06-11 Thread Django

#22813: Dead link to Pillow library website
--+
 Reporter:  anonymous |Owner:  claudep
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Claude Paroz ):

 In [changeset:"1c0e6e9d9f97d4183d1a696911613f1730e9a887"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1c0e6e9d9f97d4183d1a696911613f1730e9a887"
 [1.7.x] Fixed #22813 -- Updated Pillow URL in documentation

 Backport of dfa3505ff1 from master.
 }}}

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

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

[django/django] 1c0e6e: [1.7.x] Fixed #22813 -- Updated Pillow URL in docu...

2014-06-11 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 1c0e6e9d9f97d4183d1a696911613f1730e9a887
  
https://github.com/django/django/commit/1c0e6e9d9f97d4183d1a696911613f1730e9a887
  Author: Claude Paroz 
  Date:   2014-06-12 (Thu, 12 Jun 2014)

  Changed paths:
M docs/ref/forms/fields.txt
M docs/ref/models/fields.txt

  Log Message:
  ---
  [1.7.x] Fixed #22813 -- Updated Pillow URL in documentation

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

Re: [Django] #22813: Dead link to Pillow library website

2014-06-11 Thread Django

#22813: Dead link to Pillow library website
--+
 Reporter:  anonymous |Owner:  claudep
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"dfa3505ff1edf8453645592f1ffc39be81927935"]:
 {{{
 #!CommitTicketReference repository=""
 revision="dfa3505ff1edf8453645592f1ffc39be81927935"
 Fixed #22813 -- Updated Pillow URL in documentation
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.006349d1efe28efdc057569a0331ee30%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] dfa350: Fixed #22813 -- Updated Pillow URL in documentatio...

2014-06-11 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: dfa3505ff1edf8453645592f1ffc39be81927935
  
https://github.com/django/django/commit/dfa3505ff1edf8453645592f1ffc39be81927935
  Author: Claude Paroz 
  Date:   2014-06-12 (Thu, 12 Jun 2014)

  Changed paths:
M docs/ref/forms/fields.txt
M docs/ref/models/fields.txt

  Log Message:
  ---
  Fixed #22813 -- Updated Pillow URL in documentation


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

Re: [Django] #22813: Dead link to Pillow library website

2014-06-11 Thread Django

#22813: Dead link to Pillow library website
--+
 Reporter:  anonymous |Owner:  claudep
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by claudep):

 * status:  new => assigned
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * owner:  nobody => claudep
 * needs_docs:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #7074: MySQL error/warning when 'gt' field lookup with a datetime field and fulltext search.

2014-06-11 Thread Django

#7074: MySQL error/warning when 'gt' field lookup with a datetime field and
fulltext search.
-+-
 Reporter:  anonymous|Owner:
 Type:  Bug  |  anubhav9042
Component:  Database layer   |   Status:  assigned
  (models, ORM)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  qsrf-cleanup mysql,  | Triage Stage:  Accepted
  fulltext search, gt|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by anubhav9042):

 Can someone help me in reproducing this now. Because `__gt, __gte` works
 for both `DateTimeField` as well as `DateField`. If that's not the only
 issue here, kindly point me to what I have been missing.

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

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

[django/django] 43372f: Prevented markup escape in 'Welcome to Django' pag...

2014-06-11 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 43372fc7aa50b52487f29fffdea3c597a0e8117f
  
https://github.com/django/django/commit/43372fc7aa50b52487f29fffdea3c597a0e8117f
  Author: Claude Paroz 
  Date:   2014-06-12 (Thu, 12 Jun 2014)

  Changed paths:
M django/views/debug.py

  Log Message:
  ---
  Prevented markup escape in 'Welcome to Django' page

Fixes a regression introduced in 5f24cf9705. Refs #22635.
Thanks A.J. May for spotting the regression.


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

[Django] #22816: Oracle test failure: Inspecting NullBooleanField

2014-06-11 Thread Django

#22816: Oracle test failure: Inspecting NullBooleanField
-+-
   Reporter:  shai   |  Owner:  shai
   Type:  Bug| Status:  new
  Component:  Database   |Version:  1.7-beta-2
  layer (models, ORM)|   Keywords:  oracle
   Severity:  Release|  Has patch:  0
  blocker|Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 {{{
 ==
 FAIL: test_number_field_types (inspectdb.tests.InspectDBTestCase)
 Test introspection of various Django field types
 --
 Traceback (most recent call last):
   File "<.../tests/inspectdb/tests.py",> line 95, in
 test_number_field_types
 assertFieldType('null_bool_field', "models.BooleanField()")
   File "<.../tests/inspectdb/tests.py",> line 38, in assertFieldType
 self.assertEqual(definition, out_def)
 AssertionError: u'models.BooleanField()' != 'models.NullBooleanField()'

 --
 Ran 7008 tests in 11909.588s

 FAILED (failures=1, skipped=333, expected failures=8)
 }}}

 The copied report was on master, but 1.7 has it too.
 It's probably some minor thing, I'll deal with it later today.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.e5b96847724ff935e09cc70700d2e232%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22635: Welcome page should be translatable

2014-06-11 Thread Django

#22635: Welcome page should be translatable
-+-
 Reporter:  hakanw   |Owner:
 Type:   |  giuliettamasina
  Cleanup/optimization   |   Status:  closed
Component:  Translations |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"43372fc7aa50b52487f29fffdea3c597a0e8117f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="43372fc7aa50b52487f29fffdea3c597a0e8117f"
 Prevented markup escape in 'Welcome to Django' page

 Fixes a regression introduced in 5f24cf9705. Refs #22635.
 Thanks A.J. May for spotting the regression.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.c2762d6c72d34f0c5122df92ab782041%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

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

2014-06-11 Thread Django

Comment (by bendavis78):

Yeah, so I realized the situation I described above would only happen in
the following case: I have three apps, `A`, `B`, and `C`. Apps `A` and `B`
have unapplied initial migrations, while `C` has no migrations yet. If `C`
has a FK to `B`, and you try to run migrate for `A`, that's when the
exception occurs. In my case I just forgot to make migrations for `C`, so
I'm not sure yet if this is something that needs fixing or just needs a
better error message. I suppose it needs fixing since C could
theoretically be faked in order for A to go through.

But, it did get me thinking about the issue with `admin.LogEntry`, and it
could be the same problem. Since `admin.LogEntry` has a FK to the
swappable model, if the app with swappable model has an initial unapplied
migration, and you're trying to apply the initial migration with a
different app, I imagine you could end up with the same situation. I'd
need to write out proper tests for both cases though.

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

--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.b6ba61705f41ad6c7ff5b5f972f57256%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22815: I am getting an error and msg for a "null" ( None) content in nome variable i think, but how to treat it?

2014-06-11 Thread Django

#22815: I am getting an error and msg for a "null" ( None) content in nome 
variable
i think, but how to treat it?
-+-
 Reporter:  marcus.dung@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:  None GET |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 Please see
 https://code.djangoproject.com/wiki/TicketClosingReasons/UseSupportChannels,
 thank you.

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

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

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

2014-06-11 Thread 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 andrewgodwin):

 Thanks for looking into this issue, though, bendavis78! If you do find a
 bug at the end of the (figurative) rainbow, then please file it!

 (That might be the issue left; there's so many error paths that end in
 errors like this it can be hard to tell. South had this with the infamous
 "string has no attribute _meta" bugs for about 5 years)

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.b87ec14f30f556d7f050d5bf3f01900d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22814: parse_datetime can't parse datetimes returned from postgresql

2014-06-11 Thread Django

#22814: parse_datetime can't parse datetimes returned from postgresql
---+--
 Reporter:  Naddiseo   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Utilities  |  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 aaugustin):

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


Comment:

 Where does Django call `parse_datetime` on a value returned by PostgreSQL?

 If it never does, I'd just document the expected format.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.2f8e3f481499d9ecfb361cb4989e8fc8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

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

2014-06-11 Thread 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 bendavis78):

 Ok, so I just realized the issue I was having is probably different from
 the above issue above, but it might be similar. I'm throwing in the towel
 for now, hopefully I didn't confuse things too much :-/

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.309f3476be25f25063f3ed7a4ee1133b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19353: Make it easier to extend UserCreationForm for custom user models

2014-06-11 Thread Django

#19353: Make it easier to extend UserCreationForm for custom user models
-+-
 Reporter:  bmispelon|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.auth |  Version:
 Severity:  Normal   |  1.5-alpha-1
 Keywords:  UserCreationForm |   Resolution:
  AUTH_USER_MODEL| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by maestrofjp):

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

Re: [Django] #22815: I am getting an error and msg for a "null" ( None) content in nome variable i think, but how to treat it?

2014-06-11 Thread Django

#22815: I am getting an error and msg for a "null" ( None) content in nome 
variable
i think, but how to treat it?
-+-
 Reporter:  marcus.dung@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  None GET |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by marcus.dung@…):

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


Comment:

 The models.py, where the bug occurs is entirely browsed on the attached
 file.
 On lines 226 and 227, i try tu return Null values to Django Model field
 self.variavel.nome...
 I have tried to treat this None returns in many ways but i couldn't.
 I would thank a lot for any help 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/079.31fd17388b388f63b120810ed5649aa1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22815: I am getting an error and msg for a "null" ( None) content in nome variable i think, but how to treat it?

2014-06-11 Thread Django

#22815: I am getting an error and msg for a "null" ( None) content in nome 
variable
i think, but how to treat it?
--+--
 Reporter:  marcus.dung@… |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.4
 Severity:  Normal|   Keywords:  None GET
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+--
 AttributeError at /admin/projeto_cineo_acerto/termo_ou_fraseologismo/3977/
 'NoneType' object has no attribute 'nome'
 Request Method: GET
 Request URL:
 
http://intranet.reconscientia.org/admin/projeto_cineo_acerto/termo_ou_fraseologismo/3977/
 Django Version: 1.4.1
 Exception Type: AttributeError
 Exception Value:
 'NoneType' object has no attribute 'nome'
 Exception Location:
 /home/recons/webapps/intranet/consmatic/projeto_cineo_acerto/models.py in
 __unicode__, line 227
 Python Executable:  /usr/local/bin/python
 Python Version: 2.7.5
 Python Path:
 ['/home/recons/webapps/intranet',
  '/home/recons/webapps/intranet/consmatic',
  '/home/recons/webapps/intranet/lib/python2.7',
  '/usr/local/lib/python27.zip',
  '/usr/local/lib/python2.7',
  '/usr/local/lib/python2.7/plat-linux2',
  '/usr/local/lib/python2.7/lib-tk',
  '/usr/local/lib/python2.7/lib-old',
  '/usr/local/lib/python2.7/lib-dynload',
  '/usr/local/lib/python2.7/site-packages',
  '/usr/local/lib/python2.7/site-packages/PIL']
 Server time:Thu, 12 Jun 2014 02:11:03 -0300

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.5da2b4bba0048832983cb33daf7ab8e9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

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

2014-06-11 Thread Django

Comment (by bendavis78):

I decided to dig in for a few hours and see if I could find the cause to
this. I've found what's causing this bug.

When `manage.py migrate` is called, during the
`MigrationExecutor.detect_soft_applied()` method, A new `ProjectState` is
created. This project state accepts a list of "real apps" to use for
creating a ''fake'' `AppConfig` registry (kind of like a mock for
`django.apps.apps`). In this case, it is passed a list of *unmigrated
apps* (apps that do not yet have migration modules).

The ProjectState then attempts to render all models in this list of apps.
If one of these has a ForeignKey to a model that has not yet been
rendered, the target model is put into a "pending_lookups" list so that it
can be resolved later on. Once `ProjectState` finishes rendering all of
the models in its `real_apps` list, it moves on the the "pending_lookups"
list so that it can call `do_pending_lookups` for those target models.

Now, here's the bug: If a model being rendered has a ForeignKey to a model
from a *migrated* app (ie, an app ''with'' a migrations module), the FK
lookup will fail because it doesn't exist in the ProjectState's fake
AppConfg instance. The FK Lookup is defferred until later, but ultimately
fails because the app is never added to the fake AppConfig.

I'm working on a test case right now and will attach it soon.

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

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

Re: [Django] #22680: I/O operation on closed file

2014-06-11 Thread Django

#22680: I/O operation on closed file
-+-
 Reporter:  shelinanton@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  File |  Version:
  uploads/storage|  1.7-beta-2
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Loic Bistuer ):

 In [changeset:"6e8d614acd1b65a1ae472da7db88a7b2751dc388"]:
 {{{
 #!CommitTicketReference repository=""
 revision="6e8d614acd1b65a1ae472da7db88a7b2751dc388"
 Made the vendored NamedTemporaryFile work as a context manager. Refs
 #22680.

 This fixes a regression on Windows introduced by b7de5f5.

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

[django/django] 6e8d61: Made the vendored NamedTemporaryFile work as a con...

2014-06-11 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 6e8d614acd1b65a1ae472da7db88a7b2751dc388
  
https://github.com/django/django/commit/6e8d614acd1b65a1ae472da7db88a7b2751dc388
  Author: Loic Bistuer 
  Date:   2014-06-12 (Thu, 12 Jun 2014)

  Changed paths:
M django/core/files/temp.py

  Log Message:
  ---
  Made the vendored NamedTemporaryFile work as a context manager. Refs #22680.

This fixes a regression on Windows introduced by b7de5f5.

Thanks Tim Graham for the report and 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/5398fd97a6eb1_1c35e93d38905c0%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[Django] #22814: parse_datetime can't parse datetimes returned from postgresql

2014-06-11 Thread Django

#22814: parse_datetime can't parse datetimes returned from postgresql
+
 Reporter:  Naddiseo|  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Utilities   |Version:  1.6
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 The datetime format returned by postgresql is "2014-06-11
 23:31:38.134266+00" which is failed to parsed because the offset is only
 two digits.

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

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

Re: [Django] #14030: Use F() objects in aggregates(), annotates() and values()

2014-06-11 Thread Django

#14030: Use F() objects in aggregates(), annotates() and values()
-+-
 Reporter:  delfick  |Owner:  smeatonj
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  aggregate, annotate  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by smeatonj):

 All of those scenarios in your gist will be covered, yes. There is going
 to be some overlap with the new Lookups/Transforms API and this patch, but
 I *think* we can also get them to work together, since they both support
 the Query Expression API. In particular, your datepart example could be:

 {{{
 .annotate(month=F('the_date__month'))
 # or
 .annotate(month=Extract('the_date', MONTH))
 }}}

 Of course this requires implementing the Extract() expression, and
 registering it with the DateField transform. Also, F() expressions don't
 yet support the __transform__lookup syntax, but that'd be the next thing
 I'd implement once (if) this patch is committed.

 The other scenarios you bring up are a lot simpler:

 {{{
 class Coalesce(Func):
 function = 'COALESCE'
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.595f0e89a2662bca6267a885f59af59a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22775: Management command sqlall should support unmanaged models

2014-06-11 Thread Django

Comment (by smeatonj):

I don't think either of those workarounds are particularly good. We
discussed setting managed=False as a temporary solution, but that can be
cumbersome, and has to be repeated by every dev (unless you copy the
output to a new script..). Your second solution also requires devs to have
direct access to the production database, and possibly one that has a lot
more in it then a single table that you just want to output sql for.

For my specific use-case I have materialised views and views in the
production database (managed=False), but want to create tables that match
the definition in the development database. These definitions may change
over time, so `inspectdb --sql` isn't really what I'm after. And with the
sql commands going away, I'm not sure how switching the managed setting
temporarily is going to work with migrations.

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

--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.1542b813cfcab883e13ee42882526539%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22813: Dead link to Pillow library website

2014-06-11 Thread Django

#22813: Dead link to Pillow library website
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 The [http://python-imaging.github.io/Pillow/ link] to the Pillow website
 in this
 [https://docs.djangoproject.com/en/1.6/ref/models/fields/#imagefield
 section] of the documentation appears to be dead, it might be replaced by
 [http://pillow.readthedocs.org/en/latest/ this one].

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.18b3cd21d83440a6f0c802845cf04b68%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] c6725d: [1.7.x] Fixed typo in docs/ref/forms/validation.tx...

2014-06-11 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: c6725d69a2b7f00653886f0aeae301b7ce0baf69
  
https://github.com/django/django/commit/c6725d69a2b7f00653886f0aeae301b7ce0baf69
  Author: Maxime Lorant 
  Date:   2014-06-11 (Wed, 11 Jun 2014)

  Changed paths:
M docs/ref/forms/validation.txt

  Log Message:
  ---
  [1.7.x] Fixed typo in docs/ref/forms/validation.txt.

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

[django/django] c30738: Fixed typo in docs/ref/forms/validation.txt.

2014-06-11 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c307383ec9d30cd59f858cfdad9621a4d5adf200
  
https://github.com/django/django/commit/c307383ec9d30cd59f858cfdad9621a4d5adf200
  Author: Maxime Lorant 
  Date:   2014-06-11 (Wed, 11 Jun 2014)

  Changed paths:
M docs/ref/forms/validation.txt

  Log Message:
  ---
  Fixed typo in docs/ref/forms/validation.txt.


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

Re: [Django] #9321: When overriding the widget for a manytomany field default help_text stays

2014-06-11 Thread Django

#9321: When overriding the widget for a manytomany field default help_text stays
-+-
 Reporter:  mrcai|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.4
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  manytomanyfield, | Triage Stage:  Accepted
  widget, related.py, admin  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  1
Easy pickings:  0|
-+-

Comment (by timo):

 Please look at the commits above for details. The Version field on the
 ticket merely indicates what the current version was when the ticket was
 reported.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.6d238059e78766345b516d8624f75975%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #14030: Use F() objects in aggregates(), annotates() and values()

2014-06-11 Thread Django

#14030: Use F() objects in aggregates(), annotates() and values()
-+-
 Reporter:  delfick  |Owner:  smeatonj
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  aggregate, annotate  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by bendavis78):

 I was about to post to django-dev about this when I discovered it was
 already being worked on. Very pleased about this. Having an API for
 commonly used SQL expressions, available anywhere in the query, will
 really open up the door for flexible queries. I think this could even pave
 the way to deprecating `.extra()` :-)

 I've posted some use cases that I'm hoping will be covered by this:
 https://gist.github.com/bendavis78/865611a9e36c0897cb00 . Would any of
 these be difficult to implement with the addition of this patch?

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

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

Re: [Django] #9321: When overriding the widget for a manytomany field default help_text stays

2014-06-11 Thread Django

#9321: When overriding the widget for a manytomany field default help_text stays
-+-
 Reporter:  mrcai|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.4
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  manytomanyfield, | Triage Stage:  Accepted
  widget, related.py, admin  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  1
Easy pickings:  0|
-+-

Comment (by anonymous):

 will this be implemented in 1.8? the ticket says 1.4 and the "press
 ctrl..."-help text is still appended to any custom text.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.74d42db40af8b716f54e99887f7d923e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22803: Move contains_aggregate from ExpressionNode to F

2014-06-11 Thread Django

#22803: Move contains_aggregate from ExpressionNode to F
-+-
 Reporter:  jorgecarleitao   |Owner:
 Type:   |  jorgecarleitao
  Cleanup/optimization   |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (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 timo):

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


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

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

[django/django] 2e4d66: Added note to alphabetize AUTHORS.

2014-06-11 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2e4d667ec1ebcc433353ee191f239e528a44c56f
  
https://github.com/django/django/commit/2e4d667ec1ebcc433353ee191f239e528a44c56f
  Author: Tim Graham 
  Date:   2014-06-11 (Wed, 11 Jun 2014)

  Changed paths:
M AUTHORS

  Log Message:
  ---
  Added note to alphabetize AUTHORS.


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

[django/django] 4123f5: Added link to data migrations in initial data depr...

2014-06-11 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 4123f55c3304eced289666e256fca1e8d5d7a69d
  
https://github.com/django/django/commit/4123f55c3304eced289666e256fca1e8d5d7a69d
  Author: Greg Chapple 
  Date:   2014-06-11 (Wed, 11 Jun 2014)

  Changed paths:
M docs/howto/initial-data.txt

  Log Message:
  ---
  Added link to data migrations in initial data deprecation note


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

[django/django] 8c20f4: [1.7.x] Added link to data migrations in initial d...

2014-06-11 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 8c20f4af12d1f0f4798467dfac33858d05bfc182
  
https://github.com/django/django/commit/8c20f4af12d1f0f4798467dfac33858d05bfc182
  Author: Greg Chapple 
  Date:   2014-06-11 (Wed, 11 Jun 2014)

  Changed paths:
M docs/howto/initial-data.txt

  Log Message:
  ---
  [1.7.x] Added link to data migrations in initial data deprecation note

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

Re: [Django] #22803: Move contains_aggregate from ExpressionNode to F

2014-06-11 Thread Django

#22803: Move contains_aggregate from ExpressionNode to F
-+-
 Reporter:  jorgecarleitao   |Owner:
 Type:   |  jorgecarleitao
  Cleanup/optimization   |   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 jorgecarleitao):

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


Comment:

 This will be fixed by Pull Request for #14030.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.56833fa7780ca9f6ae0e8828497d57b6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22811: Cannot create a settings file that uses both old and new TEST database settings

2014-06-11 Thread Django

#22811: Cannot create a settings file that uses both old and new TEST database
settings
-+-
 Reporter:  timo |Owner:  timo
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:
Component:  Testing framework|  1.7-beta-2
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  1|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by timo):

 * has_patch:  0 => 1


Comment:

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

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

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

Re: [Django] #22805: urlresolvers.get_callable() need to present the inner exception if any

2014-06-11 Thread Django

#22805: urlresolvers.get_callable() need to present the inner exception if any
-+-
 Reporter:  fangsboyfriend@… |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.6
Component:  Core (Other) |   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 mardini):

 I personally don't think the exception message (ViewDoesNotExist: Could
 not import ... View does not exist in module ...) is ambiguous. In fact,
 that particular exception is used to make the error more clear. What info
 from AttributeError did you find would make the error message better?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.456f477964a02a53e2853bc90a1cf4fe%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22778: Specify default value for a Model's RelatedFields related_name.

2014-06-11 Thread Django

#22778: Specify default value for a Model's RelatedFields related_name.
-+-
 Reporter:  renaud.parent@…  |Owner:  anonymous
 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:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by RenaudParent):

 Ok thanks, I just updated my commit.

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

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

Re: [Django] #22534: Checks fail on non-swappable ForeignKeys when the related model is swapped out

2014-06-11 Thread Django

#22534: Checks fail on non-swappable ForeignKeys when the related model is 
swapped
out
+
 Reporter:  bendavis78  |Owner:  andrewgodwin
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  1.7-beta-2
 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 andrewgodwin):

 Not quite; first of all, this is designed for FKs that point to models
 that might be the swap-in replacement - e.g. `myapp.User`, not
 `django.contrib.auth.User`.

 `swappable=True` means "if the other end of this foreignkey is currently
 the value of AUTH_USER_MODEL then make this FK point to
 `settings.AUTH_USER_MODEL`

 `swappable=False` means "even if the other end of this is the current
 value of AUTH_USER_MODEL, don't do a swappable link, do it directly, as I
 really want to always link to `myapp.User`, never to the generic user
 model". It's meant for companion models that are definitely only for a
 certain user model.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.8a1bbf88f832349dc7f6e68ec29c760a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22534: Checks fail on non-swappable ForeignKeys when the related model is swapped out

2014-06-11 Thread Django

#22534: Checks fail on non-swappable ForeignKeys when the related model is 
swapped
out
+
 Reporter:  bendavis78  |Owner:  andrewgodwin
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  1.7-beta-2
 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 bendavis78):

 Ah, so if I understand correctly, the meaning of `swappable=False` is
 "System check should fail if the referenced model is swapped out", and
 `swappable=True` (the default) means "Allow model to be swapped out". Is
 that correct?

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

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

Re: [Django] #22534: Checks fail on non-swappable ForeignKeys when the related model is swapped out

2014-06-11 Thread Django

#22534: Checks fail on non-swappable ForeignKeys when the related model is 
swapped
out
+
 Reporter:  bendavis78  |Owner:  andrewgodwin
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  1.7-beta-2
 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 bendavis78):

 * cc: bendavis78 (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/068.e0cb198ae72f9441fc8bf77327a3dcb0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22775: Management command sqlall should support unmanaged models

2014-06-11 Thread Django

Comment (by shai):

May I suggest a workaround:

1. Edit your app models, comment out the "managed=False" lines.
2. Use sqlall, save output.
3. Restore models.

Now you have a sql file you can use instead of manual labor.

Or, if you're terribly worried about forgetting to restore the models --

1. Start a new project. Direct it to a database that has the tables.
2. startapp
3. inspectdb
4. sqlall
5. Throw away the project.

This can even be done in a script, in case your unmanaged models change
and you need to re-do this often.

This one actually points in the direction of a possible solution -- it
could be a flag on the `inspectdb` command (`--sql` or some such).

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

--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.62cf8c00ebd5794c8b3daf3ee9f53712%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22812: Reformat and restructure lookup API documentation

2014-06-11 Thread Django

#22812: Reformat and restructure lookup API documentation
--+
Reporter: jorgecarleitao| Owner: jorgecarleitao
Type: Cleanup/optimization | Status: new
Component: Documentation |Version: master
Severity: Normal| Keywords:
Triage Stage: Unreviewed| Has patch: 0
Easy pickings: 0 | UI/UX: 0
--+
Currently the API documentation docs/ref/models/custom-lookups.txt has
some formatting issues, and mixes the howto with the API references, see
https://docs.djangoproject.com/en/dev/ref/models/custom-lookups/

Here I'm proposing to separate these two concepts:

1. Adding a new howto - docs/howto/custom-lookups.txt - for custom
lookups, which includes section
https://docs.djangoproject.com/en/dev/ref/models/custom-lookups/#a-simple-
lookup-example to section https://docs.djangoproject.com/en/dev/ref/models
/custom-lookups/#how-django-determines-the-lookups-and-transforms-which-
are-used with potential improvements.

2. Renaming "custom-lookups.txt" to "lookups.txt" in ref/models to be the
documentation of lookups API, with references for the public interfaces of
`RegisterLookupMixin`, `Lookup`, `Transform`.

Optionally, because the BuiltIn lookups are part of this new API, they
could be documented in 2., but this may not be possible due to backward
compatibility of documentation urls (devs?)

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

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

[django/django] 64d94c: Fixed #22487: Separated schema migration from data...

2014-06-11 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 64d94cffc73fc4de1389e16d98142d253155b325
  
https://github.com/django/django/commit/64d94cffc73fc4de1389e16d98142d253155b325
  Author: Shai Berger 
  Date:   2014-06-11 (Wed, 11 Jun 2014)

  Changed paths:
M tests/migration_test_data_persistence/migrations/0001_initial.py
A tests/migration_test_data_persistence/migrations/0002_add_book.py

  Log Message:
  ---
  Fixed #22487: Separated schema migration from data migration in test

The data migration failed on Oracle, killing the entire test suite.

Thanks timo for reporting the Oracle breakage,
and andrewgodwin for suggesting the solution.


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

[django/django] fa42cf: [1.7.x] Fixed #22487: Separated schema migration f...

2014-06-11 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: fa42cf77b26bc1f09f9d62bc14338b295d700d87
  
https://github.com/django/django/commit/fa42cf77b26bc1f09f9d62bc14338b295d700d87
  Author: Shai Berger 
  Date:   2014-06-11 (Wed, 11 Jun 2014)

  Changed paths:
M tests/migration_test_data_persistence/migrations/0001_initial.py
A tests/migration_test_data_persistence/migrations/0002_add_book.py

  Log Message:
  ---
  [1.7.x] Fixed #22487: Separated schema migration from data migration in test

The data migration failed on Oracle, killing the entire test suite.

Thanks timo for reporting the Oracle breakage,
and andrewgodwin for suggesting the solution.

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

Re: [Django] #22487: Moving from initial_data to data migrations stops test data persisting

2014-06-11 Thread Django

#22487: Moving from initial_data to data migrations stops test data persisting
-+-
 Reporter:  andrewgodwin |Owner:
 Type:  Bug  |  andrewgodwin
Component:  Testing framework|   Status:  closed
 Severity:  Release blocker  |  Version:
 Keywords:   |  1.7-beta-1
Has patch:  0|   Resolution:  fixed
  Needs tests:  0| Triage Stage:  Accepted
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Shai Berger ):

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


Comment:

 In [changeset:"fa42cf77b26bc1f09f9d62bc14338b295d700d87"]:
 {{{
 #!CommitTicketReference repository=""
 revision="fa42cf77b26bc1f09f9d62bc14338b295d700d87"
 [1.7.x] Fixed #22487: Separated schema migration from data migration in
 test

 The data migration failed on Oracle, killing the entire test suite.

 Thanks timo for reporting the Oracle breakage,
 and andrewgodwin for suggesting the solution.

 Backport of 64d94cf from master
 }}}

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

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

Re: [Django] #22487: Moving from initial_data to data migrations stops test data persisting

2014-06-11 Thread Django

#22487: Moving from initial_data to data migrations stops test data persisting
-+-
 Reporter:  andrewgodwin |Owner:
 Type:  Bug  |  andrewgodwin
Component:  Testing framework|   Status:  closed
 Severity:  Release blocker  |  Version:
 Keywords:   |  1.7-beta-1
Has patch:  0|   Resolution:  fixed
  Needs tests:  0| Triage Stage:  Accepted
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Shai Berger ):

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


Comment:

 In [changeset:"64d94cffc73fc4de1389e16d98142d253155b325"]:
 {{{
 #!CommitTicketReference repository=""
 revision="64d94cffc73fc4de1389e16d98142d253155b325"
 Fixed #22487: Separated schema migration from data migration in test

 The data migration failed on Oracle, killing the entire test suite.

 Thanks timo for reporting the Oracle breakage,
 and andrewgodwin for suggesting the solution.
 }}}

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

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

Re: [Django] #22809: Refactor model field references

2014-06-11 Thread Django

#22809: Refactor model field references
-+-
 Reporter:  jorgecarleitao   |Owner:
 Type:   |  jorgecarleitao
  Cleanup/optimization   |   Status:  new
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by jorgecarleitao):

 * has_patch:  0 => 1


Comment:

 Pull request: https://github.com/django/django/pull/2796

 Both sections of the docs still require a major editorial process on
 wording and references to models,
 either to be addressed in this ticket or another.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.b862915ed39b965eefa58c9662fe553b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22811: Cannot create a settings file that uses both old and new TEST database settings

2014-06-11 Thread Django

#22811: Cannot create a settings file that uses both old and new TEST database
settings
-+-
 Reporter:  timo |Owner:  timo
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:
Component:  Testing framework|  1.7-beta-2
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 Shai agreed we can relax this and throw an error only if `TEST` and
 `TEST_*` differ.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.b09c8d0cbe9c4e8bf40fc5f49c337edb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22811: Cannot create a settings file that uses both old and new TEST database settings

2014-06-11 Thread Django

#22811: Cannot create a settings file that uses both old and new TEST database
settings
-+-
   Reporter:  timo   |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |Version:  1.7-beta-2
  Component:  Testing|   Keywords:
  framework  |  Has patch:  0
   Severity:  Release|Needs tests:  0
  blocker|  Easy pickings:  0
   Triage Stage: |
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 I'd like to use the following settings on the continuous integration
 server, but an `ImproperlyConfigured("Connection default has both NAME and
 TEST[NAME] specified.")` exception is
 
[https://github.com/django/django/commit/41afae4ce906838fc87d63962104cfb47991f68b#commitcomment-6604478
 currently raised].

 {{{
 # Django <= 1.6
 'TEST_NAME': 'test_django_gis_%s_%s' % (PY_VERSION, BUILD_NAME),
 # Django 1.7+
 'TEST': {
 'NAME': 'test_django_gis_%s_%s' % (PY_VERSION, BUILD_NAME),
 },
 }}}

 I think third-party apps that use multiple versions of Django will also
 run into this and the need to create a separate settings file seems
 overkill.

 It may be a good idea to remove this constraint and to use simply use
 `TEST` if defined, ignoring the `TEST_*` values in that case (without
 warnings so it's possible to silence them).

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.6537c61ce054e6c1fe946c63f0113d83%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22808: ModelMultipleChoiceField does not properly check if value is valid

2014-06-11 Thread Django

#22808: ModelMultipleChoiceField does not properly check if value is valid
+--
 Reporter:  mattias.lindvall@…  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Forms   |  Version:  1.6
 Severity:  Normal  |   Resolution:
 Keywords:  modelform   | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+--
Changes (by maxocub):

 * version:  1.5 => 1.6
 * easy:  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/084.26355023d74eac149e8a7fa82a93f89f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22808: ModelMultipleChoiceField does not properly check if value is valid

2014-06-11 Thread Django

#22808: ModelMultipleChoiceField does not properly check if value is valid
+--
 Reporter:  mattias.lindvall@…  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Forms   |  Version:  1.5
 Severity:  Normal  |   Resolution:
 Keywords:  modelform   | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by maxocub):

 * cc: maxime.turcotte@… (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


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

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

Re: [Django] #22738: Schema migration: test_add_field_temp_default_boolean

2014-06-11 Thread Django

#22738: Schema migration: test_add_field_temp_default_boolean
-+-
 Reporter:  maxi |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Migrations   |  1.7-beta-2
 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):

 * type:  Uncategorized => Cleanup/optimization


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.f89b16f825ff94c2514a9db3ec20%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22653: Need to add database features flag in some of the test cases

2014-06-11 Thread Django

#22653: Need to add database features  flag in some of the test cases
-+-
 Reporter:  rahul.priyadarshi@…  |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Testing framework|  Version:
 Severity:  Normal   |  1.7-beta-2
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"45e47f7b95aad98d91bb40e19dda14ae120980a4"]:
 {{{
 #!CommitTicketReference repository=""
 revision="45e47f7b95aad98d91bb40e19dda14ae120980a4"
 [1.7.x] Fixed #22653 -- Added some database feature flags to tests.

 Thanks Rahul Priyadarshi.

 Backport of 99f5ea9cc8 from master
 }}}

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

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

[django/django] 45e47f: [1.7.x] Fixed #22653 -- Added some database featur...

2014-06-11 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 45e47f7b95aad98d91bb40e19dda14ae120980a4
  
https://github.com/django/django/commit/45e47f7b95aad98d91bb40e19dda14ae120980a4
  Author: Tim Graham 
  Date:   2014-06-11 (Wed, 11 Jun 2014)

  Changed paths:
M tests/admin_views/tests.py
M tests/fixtures_regress/tests.py
M tests/serializers/tests.py
M tests/serializers_regress/tests.py

  Log Message:
  ---
  [1.7.x] Fixed #22653 -- Added some database feature flags to tests.

Thanks Rahul Priyadarshi.

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

Re: [Django] #22653: Need to add database features flag in some of the test cases

2014-06-11 Thread Django

#22653: Need to add database features  flag in some of the test cases
-+-
 Reporter:  rahul.priyadarshi@…  |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Testing framework|  Version:
 Severity:  Normal   |  1.7-beta-2
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"99f5ea9cc8f41724e07b88c6142d0092961ce5e0"]:
 {{{
 #!CommitTicketReference repository=""
 revision="99f5ea9cc8f41724e07b88c6142d0092961ce5e0"
 Fixed #22653 -- Added some database feature flags to tests.

 Thanks Rahul Priyadarshi.
 }}}

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

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

[django/django] 99f5ea: Fixed #22653 -- Added some database feature flags ...

2014-06-11 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 99f5ea9cc8f41724e07b88c6142d0092961ce5e0
  
https://github.com/django/django/commit/99f5ea9cc8f41724e07b88c6142d0092961ce5e0
  Author: Tim Graham 
  Date:   2014-06-11 (Wed, 11 Jun 2014)

  Changed paths:
M tests/admin_views/tests.py
M tests/fixtures_regress/tests.py
M tests/serializers/tests.py
M tests/serializers_regress/tests.py

  Log Message:
  ---
  Fixed #22653 -- Added some database feature flags to tests.

Thanks Rahul Priyadarshi.


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

Re: [Django] #22068: Trailing slash after some test suites leads to test failure

2014-06-11 Thread Django

#22068: Trailing slash after some test suites leads to test failure
-+-
 Reporter:  MattBlack|Owner:
 Type:  Bug  |  akshay1994.leo
Component:  Testing framework|   Status:  closed
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"68efbfde5e35013c14c0c30cabb1c94b80a48807"]:
 {{{
 #!CommitTicketReference repository=""
 revision="68efbfde5e35013c14c0c30cabb1c94b80a48807"
 Fixed #22068 -- Made runtests.py remove trailing slashes from test labels.

 When using tab-completion it's easy to accidentally run a test with
 a trailing slash, which causes INSTALLED_APPS to be set incorrectly.
 Normalize the test labels to avoid this common error.

 Thanks MattBlack for the suggestion.
 }}}

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

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

Re: [Django] #22666: (Generic)IPAddressField index never used on PostgreSQL, inconsistent behavior

2014-06-11 Thread Django

#22666: (Generic)IPAddressField index never used on PostgreSQL, inconsistent
behavior
-+-
 Reporter:  intgr|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:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * type:  Uncategorized => Bug


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.e1550593f956b9db91b225a06fe43553%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22778: Specify default value for a Model's RelatedFields related_name.

2014-06-11 Thread Django

#22778: Specify default value for a Model's RelatedFields related_name.
-+-
 Reporter:  renaud.parent@…  |Owner:  anonymous
 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:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"7bd2ad1dd9fc449ed1b4832fab5c975d7c8aa895"]:
 {{{
 #!CommitTicketReference repository=""
 revision="7bd2ad1dd9fc449ed1b4832fab5c975d7c8aa895"
 [1.7.x] Created a new tests folder (`model_options`).

 And moved `tablespaces` option tests to it.
 The new folder can be used to test models/options, like the new option
 added in refs #22778.

 Backport of 5a3ae7e260 from master
 }}}

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

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

[django/django] 7bd2ad: [1.7.x] Created a new tests folder (`model_options...

2014-06-11 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 7bd2ad1dd9fc449ed1b4832fab5c975d7c8aa895
  
https://github.com/django/django/commit/7bd2ad1dd9fc449ed1b4832fab5c975d7c8aa895
  Author: Moayad Mardini 
  Date:   2014-06-11 (Wed, 11 Jun 2014)

  Changed paths:
A tests/model_options/__init__.py
A tests/model_options/models/__init__.py
A tests/model_options/models/tablespaces.py
A tests/model_options/test_tablespaces.py
R tests/tablespaces/__init__.py
R tests/tablespaces/models.py
R tests/tablespaces/tests.py

  Log Message:
  ---
  [1.7.x] Created a new tests folder (`model_options`).

And moved `tablespaces` option tests to it.
The new folder can be used to test models/options, like the new option
added in refs #22778.

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

Re: [Django] #22778: Specify default value for a Model's RelatedFields related_name.

2014-06-11 Thread Django

#22778: Specify default value for a Model's RelatedFields related_name.
-+-
 Reporter:  renaud.parent@…  |Owner:  anonymous
 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:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"5a3ae7e260f68602b25dbe3fc6ed13249a5c6515"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5a3ae7e260f68602b25dbe3fc6ed13249a5c6515"
 Created a new tests folder (`model_options`).

 And moved `tablespaces` option tests to it.
 The new folder can be used to test models/options, like the new option
 added in refs #22778.
 }}}

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

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

[django/django] 5a3ae7: Created a new tests folder (`model_options`).

2014-06-11 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 5a3ae7e260f68602b25dbe3fc6ed13249a5c6515
  
https://github.com/django/django/commit/5a3ae7e260f68602b25dbe3fc6ed13249a5c6515
  Author: Moayad Mardini 
  Date:   2014-06-11 (Wed, 11 Jun 2014)

  Changed paths:
A tests/model_options/__init__.py
A tests/model_options/models/__init__.py
A tests/model_options/models/tablespaces.py
A tests/model_options/test_tablespaces.py
R tests/tablespaces/__init__.py
R tests/tablespaces/models.py
R tests/tablespaces/tests.py

  Log Message:
  ---
  Created a new tests folder (`model_options`).

And moved `tablespaces` option tests to it.
The new folder can be used to test models/options, like the new option
added in refs #22778.


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

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

2014-06-11 Thread Django

#19869: Make changing the active language inside `LiveTestServerCase` possible
---+
 Reporter:  void   |Owner:  gchp
 Type:  New feature|   Status:  assigned
Component:  Testing framework  |  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 gchp):

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

[django/django] 68efbf: Fixed #22068 -- Made runtests.py remove trailing s...

2014-06-11 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 68efbfde5e35013c14c0c30cabb1c94b80a48807
  
https://github.com/django/django/commit/68efbfde5e35013c14c0c30cabb1c94b80a48807
  Author: Preston Timmons 
  Date:   2014-06-11 (Wed, 11 Jun 2014)

  Changed paths:
M tests/runtests.py

  Log Message:
  ---
  Fixed #22068 -- Made runtests.py remove trailing slashes from test labels.

When using tab-completion it's easy to accidentally run a test with
a trailing slash, which causes INSTALLED_APPS to be set incorrectly.
Normalize the test labels to avoid this common error.

Thanks MattBlack for the suggestion.


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

[Django] #22810: full_result_count optimization is wrong in the presence of custom ListFilters

2014-06-11 Thread Django

#22810: full_result_count optimization is wrong in the presence of custom
ListFilters
---+
Reporter: gwahl@…| Owner: nobody
Type: Uncategorized | Status: new
Component: contrib.admin |Version: 1.6
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
---+
ChangeList.get_results performs an optimization when counting the total
number of results, disregarding list filters. It assumes that if there are
no query parameters, the full count is the same as the filtered count.
This is incorrect when a custom list filter does filtering when there are
no query parameters.

In my case, the list filter filters the objects by default, and removes
the filtering with a query parameter. The optimization incorrectly assumes
that there is no filtering by default, so the total result count is wrong.

https://github.com/django/django/blob/master/django/contrib/admin/views/main.py#L172,
see 'Perform a slight optimization'.

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

--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.498e76b3a9106ba57eccbe25616cabb3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22068: Trailing slash after some test suites leads to test failure

2014-06-11 Thread Django

#22068: Trailing slash after some test suites leads to test failure
-+-
 Reporter:  MattBlack|Owner:
 Type:  Bug  |  akshay1994.leo
Component:  Testing framework|   Status:  new
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by prestontimmons):

 The idea here looks fine to me. The patch no longer works since the update
 from optparse to argparse.

 Here's an updated one that does the same thing:

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

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.6723a703854cfe31219903d673d0d0f7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22809: Refactor model field references

2014-06-11 Thread Django

#22809: Refactor model field references
-+-
 Reporter:  jorgecarleitao   |Owner:
 Type:   |  jorgecarleitao
  Cleanup/optimization   |   Status:  new
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 Yes, probably at the bottom of the page in their own section sounds good.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.5897a386d84abbd22337043a8673f0eb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22068: Trailing slash after some test suites leads to test failure

2014-06-11 Thread Django

#22068: Trailing slash after some test suites leads to test failure
-+-
 Reporter:  MattBlack|Owner:
 Type:  Bug  |  akshay1994.leo
Component:  Testing framework|   Status:  new
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by prestontimmons):

 Oops. You're right. There is a tests.py in `django/contrib/admin`. The
 unittest discovery doesn't find tests in it, though.

 This is because it only has one test case based on `StaticLiveServerCase`
 which doesn't specify any `test_` methods.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.c6b0a26dcc9a7eba812145a1ca551e00%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #20392: Rearrange transactional behavior in django.test.TestCase: savepoints around tests

2014-06-11 Thread Django

#20392: Rearrange transactional behavior in django.test.TestCase: savepoints 
around
tests
-+-
 Reporter:  xelnor   |Owner:
 Type:  New feature  |   Status:  new
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  test atomic  | Triage Stage:  Accepted
  savepoint  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by smeatonj):

 * status:  assigned => new
 * cc: josh.smeaton@… (added)
 * owner:  smeatonj =>


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.d074df6ab6c6588465b07d69a73da3e7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #20392: Rearrange transactional behavior in django.test.TestCase: savepoints around tests

2014-06-11 Thread Django

Comment (by smeatonj):

I had a go at implementing the ideas in this ticket:
https://github.com/jarshwah/django/tree/testcase-optimization

Test cases that use fixtures improved by a factor of about 3.
Unfortunately, this only represents about 10% of the entire test suite, so
doesn't make a huge impact. I also ran into some weird threading issues
with sqlite that was causing a segmentation fault.

I'm going to bow out at this point, but I'm more than happy to help if
someone else would like to continue on the patch.

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

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

[Django] #22809: Refactor model field references

2014-06-11 Thread Django

#22809: Refactor model field references
--+
 Reporter:  jorgecarleitao|  Owner:  jorgecarleitao
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 At the moment, the API references of the model Field are scattered in
 `docs/howto/custom-model-field.txt` and `docs/ref/models/fields.txt`.

 I propose to move all the references to `docs/ref/models/fields.txt` and
 keep the `howto` part of the documentation more focused on the subject,
 e.g. avoiding defining

 {{{
 .. method:: Field.get_prep_value(value)
 }}}

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

Re: [Django] #21430: Raise Warning when unpickling Models and QuerySet from different version

2014-06-11 Thread Django

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

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


Comment:

 In [changeset:"42736ac8e8c31137131714013951249a09e6e7d4"]:
 {{{
 #!CommitTicketReference repository=""
 revision="42736ac8e8c31137131714013951249a09e6e7d4"
 Fixed #21430 -- Added a RuntimeWarning when unpickling Models and
 QuerySets from a different Django version.

 Thanks FunkyBob for the suggestion, prasoon2211 for the initial patch,
 and akaariai, loic, and charettes for helping in shaping the patch.
 }}}

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

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

[django/django] 42736a: Fixed #21430 -- Added a RuntimeWarning when unpick...

2014-06-11 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 42736ac8e8c31137131714013951249a09e6e7d4
  
https://github.com/django/django/commit/42736ac8e8c31137131714013951249a09e6e7d4
  Author: Anubhav Joshi 
  Date:   2014-06-11 (Wed, 11 Jun 2014)

  Changed paths:
M django/db/__init__.py
M django/db/models/base.py
M django/db/models/query.py
M django/db/utils.py
M django/utils/version.py
M docs/ref/models/instances.txt
M docs/ref/models/querysets.txt
M docs/releases/1.8.txt
A tests/model_regress/test_pickle.py
M tests/queryset_pickle/models.py
M tests/queryset_pickle/tests.py

  Log Message:
  ---
  Fixed #21430 -- Added a RuntimeWarning when unpickling Models and QuerySets 
from a different Django version.

Thanks FunkyBob for the suggestion, prasoon2211 for the initial patch,
and akaariai, loic, and charettes for helping in shaping the patch.


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

[Django] #22808: ModelMultipleChoiceField does not properly check if value is valid

2014-06-11 Thread Django

#22808: ModelMultipleChoiceField does not properly check if value is valid
+---
Reporter: mattias.lindvall@… | Owner: nobody
Type: Bug | Status: new
Component: Forms |Version: 1.5
Severity: Normal | Keywords: modelform
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
+---
ModelMultipleChoiceField does try to check if value is valid by doing a
query here:
https://github.com/django/django/blob/stable/1.6.x/django/forms/models.py#L1185

However, it only cathes ValueError, assuming that filter() is capable of
even using the value.
If the value is a weird data type like list or dict, the call to filter
throws TypeError.
ModelMultipleChoiceField.clean should catch TypeError, in addition to
ValueError, on line 1187.

Here is gist with a complete minimal app that demonstrates how this can
happen: https://gist.github.com/thnee/8e7c6b22f350582efe57/
Specifically the file: 4. views.py.

It is tested with 1.6.5, using 100% default settings in a clean test
project.

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

--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.6da8d3bc4478e9ff7d41cc32b384a7f9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22778: Specify default value for a Model's RelatedFields related_name.

2014-06-11 Thread Django

#22778: Specify default value for a Model's RelatedFields related_name.
-+-
 Reporter:  renaud.parent@…  |Owner:  anonymous
 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:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by RenaudParent):

 I have pushed a new commit based on previous comments here :
 
https://github.com/RenaudParent/django/commit/8710030d4c52b1c542e735fdf026fdcd0842518a

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

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

Re: [Django] #22778: Specify default value for a Model's RelatedFields related_name.

2014-06-11 Thread Django

#22778: Specify default value for a Model's RelatedFields related_name.
-+-
 Reporter:  renaud.parent@…  |Owner:  anonymous
 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:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by RenaudParent):

 * needs_better_patch:  1 => 0


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

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

Re: [Django] #22807: Strange manage.py check warning when using cached template loader

2014-06-11 Thread Django

#22807: Strange manage.py check warning when using cached template loader
---+--
Reporter: jdimov |Owner: nobody
Type: Bug| Status: closed
Component: Testing framework | Version: 1.7-beta-2
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 |UI/UX: 0
---+--
Changes (by bmispelon):

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

Comment:

Hi,

This particular check tries to detect a certain configuration using some
heuristics and unfortunately, it can result in some false-positives.

You'll find more details in the comments of the corresponding function:

https://github.com/django/django/blob/master/django/core/checks/compatibility/django_1_6_0.py#L17-L88

I'm going to close this as `wontfix` but if you have some ideas on how to
improve the heuristics, please feel free to reopen the ticket.

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

Re: [Django] #22788: Custom migration operations are rewritten incorrectly

2014-06-11 Thread Django

#22788: Custom migration operations are rewritten incorrectly
+
 Reporter:  schinckel   |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by schinckel):

 I have a branch (almost) ready for a Pull Request.

 https://github.com/schinckel/django/tree/ticket_22788

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.565931a674b92344fa82051d266678de%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22788: Custom migration operations are rewritten incorrectly

2014-06-11 Thread Django

#22788: Custom migration operations are rewritten incorrectly
+
 Reporter:  schinckel   |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by schinckel):

 Better patch does contain tests, but I couldn't come up with a way to make
 the test fail when two classes have the same name, but a different path.

 I needed to import the class using `from ... import ...` syntax, as
 otherwise there were issues related to namespacing and the term
 migrations, which I may try to work out.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.b62dbb2b1862a06da565be4da860f3e5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22807: Strange manage.py check warning when using cached template loader

2014-06-11 Thread Django

#22807: Strange manage.py check warning when using cached template loader
---+
 Reporter:  jdimov |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Testing framework  |Version:  1.7-beta-2
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 With Django 1.7, when I have TEMPLATE_LOADERS defined in the settings.py
 file to use caching, the ./manage.py check command complains with the
 following seemingly unrelated warning:


 {{{
 $ ./manage.py check
 System check identified some issues:

 WARNINGS:
 ?: (1_6.W001) Some project unittests may not execute as expected.
 HINT: Django 1.6 introduced a new default test runner. It looks
 like this project was generated using Django 1.5 or earlier. You should
 ensure your tests are all running & behaving as expected. See
 https://docs.djangoproject.com/en/dev/releases/1.6/#new-test-runner for
 more information.

 }}}

 When I remove the setting, I get the expected "System check identified no
 issues (0 silenced)."

 The setting in question is this:


 {{{
 TEMPLATE_LOADERS = (
 ('django.template.loaders.cached.Loader', (
 'django.template.loaders.filesystem.Loader',
 'django.template.loaders.app_directories.Loader',
 )),
 )
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.cc3a44c773858e771c8b316b63eadc9d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22804: A warning should be issued when an invalid separator is passed to signing.Signer

2014-06-11 Thread Django

#22804: A warning should be issued when an invalid separator is passed to
signing.Signer
--+
 Reporter:  wolever   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:  1.6
 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
--+

Comment (by mlavin):

 If you can't distinguish the data from the signature then the signature
 can't be verified. A warning is not strong enough. This should be an
 exception.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.b1e7ac86f7e1ec0aad753b7c83488724%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22577: The makemigrations management command has a problem with migrations dir

2014-06-11 Thread Django

#22577: The makemigrations management command has a problem with migrations dir
-+-
 Reporter:  japrogramer@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  makemigrations,  | Triage Stage:
  fail, init, file   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by david@…):

 I got this because I'd created a new migrations folder, but forgot to make
 it a Python package (no` __init__.py`) while I was migrating an app from
 South.

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

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

Re: [Django] #22728: get_or_create with field lookups cause empty values

2014-06-11 Thread Django

* stage: Unreviewed => Accepted

Comment:

For reference, the mailing list discussion is here:
https://groups.google.com/forum/#!topic/django-developers/EbLRpYB_1WI

As someone else mentionned on the mailing list, I'm not sure either if we
can do something that works in the general case.

The fact that this "works" currently and that it silently drops the field
that has a lookup seems quite dangerous (and not intentional).
For this reason, I'd be in favor of throwing an error if a user attempts
to use lookups in a `get_or_create` call (similar to what happens if you
try and use one in `create()`).

I'll mark this as `accepted` on this basis.

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

Re: [Django] #22804: A warning should be issued when an invalid separator is passed to signing.Signer

2014-06-11 Thread Django

#22804: A warning should be issued when an invalid separator is passed to
signing.Signer
--+
 Reporter:  wolever   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:  1.6
 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 bmispelon):

 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 Hi,

 I'll mark this as accepted on the basis that the current behavior leaves
 the user open to serious issues.

 However, wouldn't it be better to go through the deprecation process and
 raise an error eventually? I can't think of a reason why a user would want
 to pass a separator that has a chance to appear in the encoded data.

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

[Django] #22806: Some lookups/transforms don't have lookup_name

2014-06-11 Thread Django

#22806: Some lookups/transforms don't have lookup_name
--+
 Reporter:  jorgecarleitao|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 because `RegisterLookupMixin.register_lookup` requires the lookup to have
 a `lookup_name`, any transformation or lookup without it raises an
 AttributeError when registered.

 in `contrib.postgres.fields.array`, some Transforms don't have
 `lookup_name` defined.

 One will have to check out if we are missing any other.

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

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

Re: [Django] #22660: Dependencies between non-migrated and migrated apps break migration

2014-06-11 Thread Django

#22660: Dependencies between non-migrated and migrated apps break migration
-+-
 Reporter:  yakky|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:
 Severity:  Normal   |  1.7-beta-2
 Keywords:  migrations,  |   Resolution:
  dependencies   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by anonymous):

 * type:  Uncategorized => Bug


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.775f0b204ca496104b604ad70de88c15%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] e163a3: Removed an unused local variable, fixes a flake8 e...

2014-06-11 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e163a3d17b2551001677b615ccdaeadf17705d29
  
https://github.com/django/django/commit/e163a3d17b2551001677b615ccdaeadf17705d29
  Author: Alex Gaynor 
  Date:   2014-06-11 (Wed, 11 Jun 2014)

  Changed paths:
M tests/settings_tests/tests.py

  Log Message:
  ---
  Removed an unused local variable, fixes a flake8 error


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

Re: [Django] #22680: I/O operation on closed file

2014-06-11 Thread Django

#22680: I/O operation on closed file
-+-
 Reporter:  shelinanton@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  File |  Version:
  uploads/storage|  1.7-beta-2
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Florian Apolloner ):

 In [changeset:"1ff11304dcebbabdede8ef3d659ca0e54055e2fd"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1ff11304dcebbabdede8ef3d659ca0e54055e2fd"
 [1.7.x] Fixed #22680 --  I/O operation on closed file.

 This patch is two-fold; first it ensure that Django does close everything
 in
 request.FILES at the end of the request and secondly the storage system
 should
 no longer close any files during save, it's up to the caller to handle
 that --
 or let Django close the files at the end of the request.

 Backport of e2efc8965edf684aaf48621680ef54b84e116576 from master.
 }}}

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

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

[django/django] 1ff113: [1.7.x] Fixed #22680 -- I/O operation on closed f...

2014-06-11 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 1ff11304dcebbabdede8ef3d659ca0e54055e2fd
  
https://github.com/django/django/commit/1ff11304dcebbabdede8ef3d659ca0e54055e2fd
  Author: Florian Apolloner 
  Date:   2014-06-11 (Wed, 11 Jun 2014)

  Changed paths:
M django/core/files/storage.py
M django/core/files/uploadedfile.py
M django/core/handlers/base.py
M django/http/multipartparser.py
M django/http/request.py
M docs/releases/1.7.txt
M tests/file_storage/tests.py
M tests/file_uploads/tests.py
M tests/file_uploads/urls.py
M tests/file_uploads/views.py

  Log Message:
  ---
  [1.7.x] Fixed #22680 --  I/O operation on closed file.

This patch is two-fold; first it ensure that Django does close everything in
request.FILES at the end of the request and secondly the storage system should
no longer close any files during save, it's up to the caller to handle that --
or let Django close the files at the end of the request.

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

90 matches

Mail list logo