[Django] #18969: ORM filtering with "year" lookup for dates

2012-09-16 Thread Django 
#18969: ORM filtering with "year" lookup for dates
-+
 Reporter:  saippuakauppias  |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  ORM aggregation  |Version:  1.3
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 When I do query with lookup in orm:

 {{{
 Document.objects.filter(given_on__year=1).values_list('given_on',
 flat=True)
 }}}
 or
 {{{
 Document.objects.filter(given_on__year='0001').values_list('given_on',
 flat=True)
 }}}

 I get results:
 {{{
 [datetime.date(2012, 8, 31), datetime.date(2012, 8, 31),
 datetime.date(2012, 8, 29), '...(remaining elements truncated)...']
 }}}

 But I would expect dates in interval 0001-01-01 ... 0001-12-31 (-MM-
 DD).

 Generated SQL query:
 {{{
 print
 Document.objects.filter(given_on__year='0001').values_list('given_on').query
 }}}


 {{{
 SELECT "documents_document"."given_on"
 FROM "documents_document"
 WHERE "documents_document"."given_on" BETWEEN 1-01-01 00:00:00 and 1-12-31
 23:59:59.99
 ORDER BY "documents_document"."created_on" DESC
 }}}

 In django not possible give results with first year.

 PS: question in [http://stackoverflow.com/questions/12425853/postgresql-
 between-with-datetime stackoverflow]
 PPS: tested in Django 1.3.2 version

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18968: Spatialite GML test failure

2012-09-16 Thread Django 
#18968: Spatialite GML test failure
+--
 Reporter:  bkg |Owner:  bkg
 Type:  Bug |   Status:  assigned
Component:  GIS |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by bkg):

 * has_patch:  0 => 1


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18968: Spatialite GML test failure

2012-09-16 Thread Django 
#18968: Spatialite GML test failure
+--
 Reporter:  bkg |Owner:  bkg
 Type:  Bug |   Status:  assigned
Component:  GIS |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by bkg):

 A simple fix is available here:

 https://github.com/bkg/django/tree/ticket_18968

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18968: Spatialite GML test failure

2012-09-16 Thread Django 
#18968: Spatialite GML test failure
+--
 Reporter:  bkg |Owner:  bkg
 Type:  Bug |   Status:  assigned
Component:  GIS |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by bkg):

 * status:  new => assigned
 * 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18968: Spatialite GML test failure

2012-09-16 Thread Django 
#18968: Spatialite GML test failure
+
 Reporter:  bkg |  Owner:  bkg
 Type:  Bug | Status:  new
Component:  GIS |Version:  master
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 The GML returned from Spatialite has changed format in version 3.0 and
 above. When testing with Spatialite 3.0 and 3.1, the regex in test_gml no
 longer returns a match.

 {{{
 ==
 FAIL: test_gml (django.contrib.gis.tests.geoapp.tests.GeoQuerySetTest)
 Testing GML output from the database using GeoQuerySet.gml().
 --
 Traceback (most recent call last):
   File
 
"/home/brian/.virtualenvs/django/django.git/django/contrib/gis/tests/geoapp/tests.py",
 line 530, in test_gml
 self.assertTrue(gml_regex.match(ptown.gml))
 AssertionError: None is not true

 --
 Ran 234 tests in 6.342s

 FAILED (failures=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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18484: csrfmiddlewaretoken enclosed in redundant invisible div

2012-09-16 Thread Django 
#18484: csrfmiddlewaretoken enclosed in redundant invisible div
-+
 Reporter:  hedleyroos@… |Owner:  nobody
 Type:  Uncategorized|   Status:  reopened
Component:  Forms|  Version:  1.4
 Severity:  Release blocker  |   Resolution:
 Keywords:  csrf | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by simonb):

 * cc: bnomis@… (added)
 * component:  Uncategorized => Forms


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18967: django.core.mail.EmailMessage._create_mime_attachment incorrectly encodes message/rfc822 attachments in base64, breaks in Evolution and Thunderbird (was: django.core.mail._create_

2012-09-16 Thread Django 
#18967: django.core.mail.EmailMessage._create_mime_attachment incorrectly 
encodes
message/rfc822 attachments in base64, breaks in Evolution and Thunderbird
-+--
 Reporter:  micolous |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Mail)  |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+--
Changes (by micolous):

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


Comment:

 I've created a patch and pull request:
 https://github.com/django/django/pull/373

 This patch is against Django master.

 There are some changes in the behaviour of
 django.core.mail.EmailMessage.attach:

 * message/rfc822 attachments may be a email.message.Message object (not
 just a string)
 * When passing in a string attachment, Django will now automatically
 convert it to email.message.Message internally for
 email.mime.message.MIMEMessage.  This means that if the message/rfc822
 attachment is not well-formed, an exception may be thrown.
 * Per RFC2046, the attached message headers must be ASCII encoded.  As a
 result SafeMIMEMessage checks headers with ASCII encoding.

 This also implements SafeMIMEMessage (like the other SafeMIME* classes).

 The tests currently pass, however there are no specific tests in this
 patch for this functionality.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18967: django.core.mail._create_mime_attachment incorrectly encodes message/rfc822 attachments in base64, breaks in Evolution and Thunderbird

2012-09-16 Thread Django 
#18967: django.core.mail._create_mime_attachment incorrectly encodes 
message/rfc822
attachments in base64, breaks in Evolution and Thunderbird
-+
 Reporter:  micolous |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Core (Mail)  |Version:  1.4
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 Django appears to insert message/rfc822 attachments in base64 encoding.
 This breaks display in Novell Evolution
 [https://bugzilla.gnome.org/show_bug.cgi?id=651197 #651197] and Mozilla
 Thunderbird [https://bugzilla.mozilla.org/show_bug.cgi?id=333880 #333880].

 This behaviour is similar to some other mail clients (namely Gmail and
 Microsoft Outlook), but is non-standard according to
 [http://www.ietf.org/rfc/rfc2046.txt RFC2046]:

5.2.1.  RFC822 Subtype
No encoding other than "7bit", "8bit", or "binary" is permitted for the
 body of a "message/rfc822" entity.

 The Mozilla Thunderbird bug entry seems to indicate that with certain
 versions of Thunderbird, this behaviour is accepted, but this seems to
 change sporadically.  They believe that encoding message/rfc822
 attachments in this fashion is not acceptable behaviour.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18616: New auth signal: user_login_failed

2012-09-16 Thread Django 
#18616: New auth signal: user_login_failed
-+-
 Reporter:  micolous |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:
 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 micolous):

 I've now merged django/master into my pull request.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18966: Add View source to documentation

2012-09-16 Thread Django 
#18966: Add View source to documentation
---+
 Reporter:  thikonom   |  Owner:  nobody
 Type:  New feature| Status:  new
Component:  Documentation  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I know that this will require a lot of work, but i think it would be
 useful if we had a View Source link next to each method, ... described in
 the docs.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18965: Properly deprecate PROFANITIES_LIST.

2012-09-16 Thread Django 
#18965: Properly deprecate PROFANITIES_LIST.
--+--
 Reporter:  tomchristie   |Owner:  nobody
 Type:  Uncategorized |   Status:  new
Component:  contrib.comments  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by tomchristie):

 * cc: tom@… (added)
 * needs_docs:   => 0
 * needs_tests:   => 0
 * needs_better_patch:   => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18748: Remove dupe-avoidance logic from the ORM

2012-09-16 Thread Django 
#18748: Remove dupe-avoidance logic from the ORM
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Ready for
 Severity:  Normal   |  checkin
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by akaariai):

 OK, I now know what exclude was used for - when combining queries and the
 rhs query has two joins for the same connection we must exclude the alias
 used for the first connection. As an example:
 {{{
 q1 = qs.filter(m2m__f=1)
 q2 = qs.filter(m2m__f=1).filter(m2m__f=2)
 }}}
 Now, we have two joins for m2m in q2, and specifically they have the same
 connections for the m2m joins. If we do (q1|q2), then we will reuse all
 joins for the first m2m join. If we don't exclude the alias used for the
 first m2m join, then we will again reuse the same join for the second m2m
 join. This would result in having just one join in the combined query.
 This is wrong, as the original rhs query had two joins.

 I have done a fix for this in the
 https://github.com/akaariai/django/compare/dupe_away, specifically in
 
https://github.com/akaariai/django/commit/da96154a72c4c4ca53cce198a82bb6af3f87ff64
 - note that the exclude arg is still gone, instead I use the reuse arg
 here.

 I also reworked the .join() implementation
 
(https://github.com/akaariai/django/commit/b42280f45c7cd0fcde835ee4665e9d67327fda1d).
 I feel the code is much improved, but I can't claim to understand the
 existing code in full. I am afraid that there are other regressions
 lurking...

 If anybody can review this I would much appreciate it!

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #12836: Model.get_absolute_url lose method attributes

2012-09-16 Thread Django 
#12836: Model.get_absolute_url lose method attributes
-+-
 Reporter:  minmax   |Owner:  minmax
 Type:  Bug  |   Status:  reopened
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:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Caleb Smith ):

 In [changeset:"210fd7c658a44e51f4696555b3ce71498db55d96"]:
 {{{
 #!CommitTicketReference repository=""
 revision="210fd7c658a44e51f4696555b3ce71498db55d96"
 refs #12836 - Added a test to assure permalink wraps method attributes
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 210fd7: refs #12836 - Added a test to assure permalink wra...

2012-09-16 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 210fd7c658a44e51f4696555b3ce71498db55d96
  
https://github.com/django/django/commit/210fd7c658a44e51f4696555b3ce71498db55d96
  Author: Caleb Smith 
  Date:   2012-09-08 (Sat, 08 Sep 2012)

  Changed paths:
M tests/regressiontests/model_permalink/models.py
M tests/regressiontests/model_permalink/tests.py

  Log Message:
  ---
  refs #12836 - Added a test to assure permalink wraps method attributes


  Commit: a630d08483267fbeb461f2fb06313d0e17ef6d44
  
https://github.com/django/django/commit/a630d08483267fbeb461f2fb06313d0e17ef6d44
  Author: Florian Apolloner 
  Date:   2012-09-16 (Sun, 16 Sep 2012)

  Changed paths:
M tests/regressiontests/model_permalink/models.py
M tests/regressiontests/model_permalink/tests.py

  Log Message:
  ---
  Merge pull request #360 from calebsmith/add-permalink-wraps-test

Ticket #12836 - Added a test to assure permalink wraps method attributes


Compare: https://github.com/django/django/compare/f399a804c943...a630d0848326

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17485: Queries with both deferred fields and select_related defer field.name instead of field.attname

2012-09-16 Thread Django 
#17485: Queries with both deferred fields and select_related defer field.name
instead of field.attname
-+-
 Reporter:  konk |Owner:  akaariai
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Release blocker  | Triage Stage:  Ready for
 Keywords:  defer|  checkin
  select_related |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Anssi Kääriäinen ):

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


Comment:

 In [changeset:"f399a804c9436a5d3ef9e2b73c337904af2c753d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f399a804c9436a5d3ef9e2b73c337904af2c753d"
 Fixed #17485 regression -- only + select_related interaction

 When doing deeper than one level select_related() + only queries(), the
 code introduced in b6c356b7bb97f3d6d4831b31e67868313bbbc090 errored
 incorrectly.

 Thanks to mrmachine for report & test case.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] f399a8: Fixed #17485 regression -- only + select_related i...

2012-09-16 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: f399a804c9436a5d3ef9e2b73c337904af2c753d
  
https://github.com/django/django/commit/f399a804c9436a5d3ef9e2b73c337904af2c753d
  Author: Anssi Kääriäinen 
  Date:   2012-09-16 (Sun, 16 Sep 2012)

  Changed paths:
M django/db/models/sql/compiler.py
M tests/regressiontests/defer_regress/models.py
M tests/regressiontests/defer_regress/tests.py

  Log Message:
  ---
  Fixed #17485 regression -- only + select_related interaction

When doing deeper than one level select_related() + only queries(), the
code introduced in b6c356b7bb97f3d6d4831b31e67868313bbbc090 errored
incorrectly.

Thanks to mrmachine for report & test case.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18965: Properly deprecate PROFANITIES_LIST.

2012-09-16 Thread Django 
#18965: Properly deprecate PROFANITIES_LIST.
--+
 Reporter:  tomchristie   |  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  contrib.comments  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Okay, so it's been set to an empty tuple now, tho I *believe* that
 formally removing it has been mentioned at a couple of DjangoCon talks
 this year, although I could be mistaken.
 Closest thing I can find online is this gist of Adrian's keynote which
 mentions it (without context) - https://gist.github.com/3643761
 If this gets the thumbs up I'll make the required pull request.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18896: get_or_create breaks for ManyToMany

2012-09-16 Thread Django 
#18896: get_or_create breaks for ManyToMany
-+-
 Reporter:  mattlong |Owner:  thikonom
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (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 thikonom):

 * owner:  nobody => thikonom


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18896: get_or_create breaks for ManyToMany

2012-09-16 Thread Django 
#18896: get_or_create breaks for ManyToMany
-+-
 Reporter:  mattlong |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (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 thikonom):

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


Comment:

 I think the problem here is the '''unique=True''' constraint.  I
 reproduced your code using Mysql, it failed with an ''"Duplicate entry
 'foo' for key 'text'"'' Integrityerror, but when i removed the unique
 constraint then it worked as expected.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18947: Uploaded files have exec bit set by default

2012-09-16 Thread Django 
#18947: Uploaded files have exec bit set by default
-+-
 Reporter:  lotheac  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  File |  Version:  master
  uploads/storage|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by apollo13):

 FILE_UPLOAD_PERMISSIONS still can override it, this change is just here to
 provide a more sensible default, see
 
https://github.com/lotheac/django/blob/67f844ed7b21ae154a5575a389d366571226b9d4/django/core/files/storage.py#L221

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18964: defaultfilters test passes unexpectedly under Python 3

2012-09-16 Thread Django 
#18964: defaultfilters test passes unexpectedly under Python 3
-+
 Reporter:  russellm |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Uncategorized|  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:  python3  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by russellm):

 * keywords:   => python3
 * version:  1.4 => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #18964: defaultfilters test passes unexpectedly under Python 3

2012-09-16 Thread Django 
#18964: defaultfilters test passes unexpectedly under Python 3
---+
   Reporter:  russellm |  Owner:  nobody
   Type:  Bug  | Status:  new
  Component:  Uncategorized|Version:  1.4
   Severity:  Release blocker  |   Keywords:
   Triage Stage:  Accepted |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+
 defaultfilters.DefaultFiltersTests.test_floatformat_fail is currently
 marked as an expected failure; and under Python 2, it does fail.

 Under Python 3 (at least, with Python 3.2.3 64 bit under OSX), the test
 passes.

 It's entirely possible that the resolution is "don't worry about it" -
 after all, there are worse problems than an unexpected test pass. However,
 since it is an oddity in test suite results that may have gone unnoticed
 (since 'unexpected pass' would be easy to miss in test suite results), I'm
 marking this as a release blocker.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18947: Uploaded files have exec bit set by default

2012-09-16 Thread Django 
#18947: Uploaded files have exec bit set by default
-+-
 Reporter:  lotheac  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  File |  Version:  master
  uploads/storage|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 How does this relate to
 [https://docs.djangoproject.com/en/dev/ref/settings/#file-upload-
 permissions settings.FILE_UPLOAD_PERMISSIONS]?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18957: Add next/previous buttons when editing a model in the admin site

2012-09-16 Thread Django 
#18957: Add next/previous buttons when editing a model in the admin site
---+--
 Reporter:  palkeo |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by thikonom):

 Yes.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 8d75b1: Clearer wording for defer docs

2012-09-16 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 8d75b1176f280b8949aee8dc961a2acd0dacffcd
  
https://github.com/django/django/commit/8d75b1176f280b8949aee8dc961a2acd0dacffcd
  Author: Preston Holmes 
  Date:   2012-09-15 (Sat, 15 Sep 2012)

  Changed paths:
M docs/ref/models/querysets.txt

  Log Message:
  ---
  Clearer wording for defer docs


  Commit: 935a8635c2fe5b702c18027818ef4cceda4d83cd
  
https://github.com/django/django/commit/935a8635c2fe5b702c18027818ef4cceda4d83cd
  Author: Florian Apolloner 
  Date:   2012-09-16 (Sun, 16 Sep 2012)

  Changed paths:
M docs/ref/models/querysets.txt

  Log Message:
  ---
  Merge pull request #372 from ptone/patch-2

Clearer wording for defer docs


Compare: https://github.com/django/django/compare/e4d338ac9b0d...935a8635c2fe

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 171494: Fixes docs typo

2012-09-16 Thread GitHub 
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 17149496a001b0ec8af382ef5a65499c0a651f43
  
https://github.com/django/django/commit/17149496a001b0ec8af382ef5a65499c0a651f43
  Author: Camilo Nova 
  Date:   2012-09-15 (Sat, 15 Sep 2012)

  Changed paths:
M docs/topics/logging.txt

  Log Message:
  ---
  Fixes docs typo


  Commit: e4d338ac9b0d67756cdd3437a31ed0e7e5061f59
  
https://github.com/django/django/commit/e4d338ac9b0d67756cdd3437a31ed0e7e5061f59
  Author: Florian Apolloner 
  Date:   2012-09-16 (Sun, 16 Sep 2012)

  Changed paths:
M docs/topics/logging.txt

  Log Message:
  ---
  Merge pull request #371 from camilonova/fix_docs_typo

Fixes docs typo


Compare: https://github.com/django/django/compare/c555741aa784...e4d338ac9b0d

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.