date:20120515

Re: [Django] #3214: [patch] raw sql file doesn't recognize quotes correctly

2012-05-15 Thread Django

#3214: [patch] raw sql file doesn't recognize quotes correctly
-+-
 Reporter:  shaunc  |Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  rawsql   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Xof):

 * cc: Xof (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 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18194: File-based session never expire

2012-05-15 Thread Django

#18194: File-based session never expire
--+
 Reporter:  ej|Owner:  PaulM
 Type:  Bug   |   Status:  new
Component:  contrib.sessions  |  Version:  1.4
 Severity:  Release blocker   |   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by crodjer):

 * status:  assigned => new
 * owner:  crodjer => PaulM


-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18254: Add support for `as ` to the staticfiles {% static %} template tag.

2012-05-15 Thread Django

#18254: Add support for `as ` to the staticfiles {% static %} template
tag.
-+
 Reporter:  melinath |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.staticfiles  |  Version:  master
 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
-+

Comment (by niwi):

 I have sent a pull-request with possible solution to this issue.
 (https://github.com/django/django/pull/66)

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18318: admin_scripts.tests.expected_query_re missing mssql quote characters

2012-05-15 Thread Django

#18318: admin_scripts.tests.expected_query_re missing mssql quote characters
---+
 Reporter:  manfre |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by manfre):

 * needs_better_patch:  1 => 0


Comment:

 Patch updated to use quote_name.

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #18323: Date-based generic views mix dates and datetimes unsafely

2012-05-15 Thread Django

#18323: Date-based generic views mix dates and datetimes unsafely
-+-
   Reporter:  aaugustin  |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |Version:  master
  Component:  Generic|   Keywords:  refactoring
  views  |  Has patch:  1
   Severity:  Normal |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 Date-based generic views can use either a !DateField or a !DateTimeField.
 But the logic of the lookups to handle these two cases is a bit fuzzy.
 When time zone support is enabled, it isn't correct (or at least, not
 obviously so).

 In order to make the code less fragile, I rewrote much of the interval
 handling logic.

 This patch:
 - adds some explicit conversions between dates and datetimes, accounting
 for the current time zone,
 - makes the code generally clearer and possibly more correct — off-by-the-
 UTC-offset bugs are less likely when `USE_TZ = True`.

 As a side effect, this patch is likely to fix two bugs:
 - an egde case where accessing next_day/week/month/year on a
 !DateTimeField could 404 even with allow_empty = False due to
 approximative filtering,
 - #17192.

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #13844: Errors when using character fields for aggregation

2012-05-15 Thread Django

#13844: Errors when using character fields for aggregation
-+-
 Reporter:  zegrep@… |Owner:  wogan
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.2
  (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 valhallasw):

 The proposed solution does not solve the underlying design issue: this
 conversion should be done *in the fields*, not in the database backend!
 I.e.

 {{{
 def convert_values(self, value, field):
 return field.convert_value(value)
 }}}

 and I expect (but am not 100% certain) that field.to_python() already does
 exactly what should happen. The differences I can see at the moment are a)
 the default float() and b) CommaSeparatedIntegerField (which shouldn't be
 cast to int in the first place).

 a) the default to_python implementation is just
 {{{def to_python(self, value):
 return value
 }}}

 b) the CommaSeparatedIntegerField is actually just a charfield with a
 specific validation.

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18320: Unit test model_formsets_regress.FormsetTests.test_extraneous_query_is_not_run expects wrong number of queries

2012-05-15 Thread Django

#18320: Unit test
model_formsets_regress.FormsetTests.test_extraneous_query_is_not_run
expects wrong number of queries
---+
 Reporter:  manfre |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by manfre):

 * needs_better_patch:  1 => 0


Comment:

 The other backends are able to pull the insert id from the cursor without
 an additional query.

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18320: Unit test model_formsets_regress.FormsetTests.test_extraneous_query_is_not_run expects wrong number of queries

2012-05-15 Thread Django

#18320: Unit test
model_formsets_regress.FormsetTests.test_extraneous_query_is_not_run
expects wrong number of queries
---+
 Reporter:  manfre |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by manfre):

 * needs_better_patch:  0 => 1


Comment:

 You raised a valid question. can_return_id_from_insert = False does not
 necessarily imply that a separate query is needed to fetch the return_id.
 Updating patch pending.

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18314: request.build_absolute_uri() functions incorrectly when the path starts with //

2012-05-15 Thread Django

#18314: request.build_absolute_uri() functions incorrectly when the path starts
with //
---+
 Reporter:  anonymous  |Owner:  yoyoma
 Type:  Bug|   Status:  reopened
Component:  HTTP handling  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by yoyoma):

 * needs_tests:  1 => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18319: test_runner.AutoIncrementResetTest should be skipped for mssql

2012-05-15 Thread Django

#18319: test_runner.AutoIncrementResetTest should be skipped for mssql
---+
 Reporter:  manfre |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by manfre):

 * needs_better_patch:  1 => 0


Comment:

 Updated patch to use supports_sequence_reset, instead of vendor.

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18314: request.build_absolute_uri() functions incorrectly when the path starts with //

2012-05-15 Thread Django

#18314: request.build_absolute_uri() functions incorrectly when the path starts
with //
---+
 Reporter:  anonymous  |Owner:  yoyoma
 Type:  Bug|   Status:  reopened
Component:  HTTP handling  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by yoyoma):

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


Comment:

 Pardon my resolving of the ticket.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18217: Date-based generic views use naive datetime objects

2012-05-15 Thread Django

#18217: Date-based generic views use naive datetime objects
-+-
 Reporter:  yumike   |Owner:  aaugustin
 Type:  Bug  |   Status:  reopened
Component:  Generic views|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  0|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18217: Date-based generic views use naive datetime objects

2012-05-15 Thread Django

#18217: Date-based generic views use naive datetime objects
-+-
 Reporter:  yumike   |Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Generic views|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  0|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Fantomas42):

 Hi aaugustin,

 I'm strongly in favor of backporting these two commits.

 Because without these commits, I cannot complete my migration process for
 enabling the time zone support without warnings when I run my test suite.

 I make an intensive usage of the dates based generic views, that's why I'm
 doing this request.

 Regards

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18314: request.build_absolute_uri() functions incorrectly when the path starts with //

2012-05-15 Thread Django

#18314: request.build_absolute_uri() functions incorrectly when the path starts
with //
---+
 Reporter:  anonymous  |Owner:  yoyoma
 Type:  Bug|   Status:  closed
Component:  HTTP handling  |  Version:  1.4
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by yoyoma):

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


Comment:

 I've attached the fix, but if it needs improvements, let me know and I'll
 update the diff ASAP.

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18306: Deferred models should automatically issue update_fields when saving

2012-05-15 Thread Django

#18306: Deferred models should automatically issue update_fields when saving
-+-
 Reporter:  akaariai |Owner:  akaariai
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by akaariai):

 * status:  assigned => new
 * needs_docs:  1 => 0
 * owner:  niwi => akaariai
 * needs_better_patch:  1 => 0


Comment:

 Looks excellent. I will try to find time to work this into core in the
 next couple of days.

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18322: Many django.contrib.sessions unit tests do not respect database supports_timezones feature

2012-05-15 Thread Django

#18322: Many django.contrib.sessions unit tests do not respect database
supports_timezones feature
--+--
 Reporter:  manfre|Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  contrib.sessions  |  Version:  master
 Severity:  Normal|   Resolution:  wontfix
 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 aaugustin):

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


Comment:

 I'm sorry, but this technique doesn't work, for the reasons explained in
 #18321.

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18321: generic_views unit tests are not respecting database feature supports_timezones

2012-05-15 Thread Django

#18321: generic_views unit tests are not respecting database feature
supports_timezones
---+--
 Reporter:  manfre |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:  wontfix
 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 aaugustin):

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


Comment:

 MySQL, SQLite and Oracle have `support_timezones = False` because either
 they're unable to store aware datetimes or their Python adapters are
 unable to handle them.

 But it's important to test that they behave correctly when `USE_TZ =
 True`. Your patch would disable several tests for these three backends,
 which isn't acceptable. I suspect you misunderstood the meaning of the
 `supports_timezones` feature flag.

 (Also, there are other tests that require timezone support, starting with
 tests.modeltests.timezones, I'm not sure why the patch only applies to
 tests.regressiontests.generic_views.)

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18306: Deferred models should automatically issue update_fields when saving

2012-05-15 Thread Django

#18306: Deferred models should automatically issue update_fields when saving
-+-
 Reporter:  akaariai |Owner:  niwi
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  1
 Keywords:   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by niwi):

 Now sended pull request: https://github.com/django/django/pull/65

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #18322: Many django.contrib.sessions unit tests do not respect database supports_timezones feature

2012-05-15 Thread Django

#18322: Many django.contrib.sessions unit tests do not respect database
supports_timezones feature
--+
 Reporter:  manfre|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  contrib.sessions  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+
 Many django.contrib.sessions unit tests do not respect database
 supports_timezones feature. These tests should be skipped if the database
 states it does not support

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18320: Unit test model_formsets_regress.FormsetTests.test_extraneous_query_is_not_run expects wrong number of queries

2012-05-15 Thread Django

#18320: Unit test
model_formsets_regress.FormsetTests.test_extraneous_query_is_not_run
expects wrong number of queries
---+
 Reporter:  manfre |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by akaariai):

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


Comment:

 Looks good. But why does this test not fail on any of core backends?

 Not marking as RFC as I haven't actually applied 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 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18319: test_runner.AutoIncrementResetTest should be skipped for mssql

2012-05-15 Thread Django

#18319: test_runner.AutoIncrementResetTest should be skipped for mssql
---+
 Reporter:  manfre |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by akaariai):

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


Comment:

 Add a connection feature "supports_sequence_reset" or somesuch. If you can
 write a patch for this, great. Reason is again other 3rd party backends.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #18321: generic_views unit tests are not respecting database feature supports_timezones

2012-05-15 Thread Django

#18321: generic_views unit tests are not respecting database feature
supports_timezones
---+
 Reporter:  manfre |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Testing framework  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  0  |  UI/UX:  0
---+
 Tests that specifically target timezone support, should be skipped if the
 database backend states it does not support timezones.

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18318: admin_scripts.tests.expected_query_re missing mssql quote characters

2012-05-15 Thread Django

#18318: admin_scripts.tests.expected_query_re missing mssql quote characters
---+
 Reporter:  manfre |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by akaariai):

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


Comment:

 Lets rewrite the test as something like:
 r"create table %s" % connection.ops.quote_name("admin_scripts_article")

 That should work for other 3rd party backends, too.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18317: Raw sql in regressiontests.model_fields.tests.BooleanFieldTests.test_return_type fails with mssql

2012-05-15 Thread Django

#18317: Raw sql in
regressiontests.model_fields.tests.BooleanFieldTests.test_return_type fails
with mssql
---+
 Reporter:  manfre |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by akaariai):

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


Comment:

 I support the idea of allowing the tests to pass on different backends
 than the core backends.

 I am not sure if checking the connection vendor is the right thing to do.
 Usually we use some connection.ops.sql_for_string_len(), but as this is
 used just in testing, that does seem wrong approach, too.

 How about using something else than LEN() there? It doesn't seem to matter
 what function is used in there (in fact, you don't need any function in
 there, right?). So, just get rid of the LEN() call altogether.

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #18320: Unit test model_formsets_regress.FormsetTests.test_extraneous_query_is_not_run expects wrong number of queries

2012-05-15 Thread Django

#18320: Unit test
model_formsets_regress.FormsetTests.test_extraneous_query_is_not_run
expects wrong number of queries
---+
 Reporter:  manfre |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Testing framework  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  0  |  UI/UX:  0
---+
 For database backends with feature ``can_return_id_from_insert = False``,
 there should be an expected second query, which fetches the newly inserted
 pk.

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18314: request.build_absolute_uri() functions incorrectly when the path starts with //

2012-05-15 Thread Django

#18314: request.build_absolute_uri() functions incorrectly when the path starts
with //
---+
 Reporter:  anonymous  |Owner:  yoyoma
 Type:  Bug|   Status:  new
Component:  HTTP handling  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by yoyoma):

 * owner:  nobody => yoyoma


-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #18319: test_runner.AutoIncrementResetTest should be skipped for mssql

2012-05-15 Thread Django

#18319: test_runner.AutoIncrementResetTest should be skipped for mssql
---+
 Reporter:  manfre |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Testing framework  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  0  |  UI/UX:  0
---+
 test_runner.AutoIncrementResetTest should be skipped for mssql

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #18318: admin_scripts.tests.expected_query_re missing mssql quote characters

2012-05-15 Thread Django

#18318: admin_scripts.tests.expected_query_re missing mssql quote characters
---+
 Reporter:  manfre |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Testing framework  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  0  |  UI/UX:  0
---+
 MSSQL quotes entities with square braces [] and not quotes.

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #18317: Raw sql in regressiontests.model_fields.tests.BooleanFieldTests.test_return_type fails with mssql

2012-05-15 Thread Django

#18317: Raw sql in
regressiontests.model_fields.tests.BooleanFieldTests.test_return_type fails
with mssql
---+
 Reporter:  manfre |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Testing framework  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  0  |  UI/UX:  0
---+
 MSSQL calls its user LENGTH function, LEN.

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16882: Clarify in the doc why one should not use 'init_command' after initial database creation

2012-05-15 Thread Django

#16882: Clarify in the doc why one should not use 'init_command' after initial
database creation
--+
 Reporter:  julien|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.3
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by programmerq):

 * cc: jefferya@… (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 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #14646: django.contrib.comments is missing default template for comment_notification_email.txt, and has no documentation of template context

2012-05-15 Thread Django

#14646: django.contrib.comments is missing default template for
comment_notification_email.txt, and has no documentation of template
context
--+-
 Reporter:  tpherndon |Owner:  tzulberti
 Type:  Bug   |   Status:  new
Component:  contrib.comments  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  email, template   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+-
Changes (by programmerq):

 * cc: jefferya@… (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 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #18316: settings.configure() does not apply LOGGING_CONFIG

2012-05-15 Thread Django

#18316: settings.configure() does not apply LOGGING_CONFIG
--+
 Reporter:  luch@…|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Core (Other)  |Version:  1.4
 Severity:  Normal|   Keywords:  settings configure
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 settings.configure() does not call LOGGING_CONFIG:
 {{{
 import my_settings as S
 from django.conf import settings
 settings.configure(S)
 }}}

 While touching settings attribute like management.get_commands() does
 implicit call:
 {{{
 import os
 os.environ["DJANGO_SETTINGS_MODULE"] = "my_settings"

 from django.conf import settings
 settings.INSTALLED_APPS
 }}}

 Full sample is in attach

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #18315: QueryDict.pop is inconsistent

2012-05-15 Thread Django

#18315: QueryDict.pop is inconsistent
---+
 Reporter:  gcbirzan   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  HTTP handling  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 All the 'regular' operations on QueryDict return a single value, with a
 'list' variant for returning a list of items. pop() pops a list, popitem()
 for just one item. This is not only inconsistent, but also not documented.

 I'd prefer a solution that makes pop return a single item, vs mentioning
 it in the docs, but that breaks backwards compatibility.

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16884: Add message level argument to ModelAdmin's message_user

2012-05-15 Thread Django

#16884: Add message level argument to ModelAdmin's message_user
---+
 Reporter:  shelldweller   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  admin  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  1
---+

Comment (by claudep):

 I understand now that message_user may be considered as a single point of
 indirection for all contrib.admin internal calls to the API (e.g. subclass
 ModelAdmin and override message_user to redirect all admin messages).
 Point taken for the decoupling point.

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18277: Startproject/app template documentation confusing

2012-05-15 Thread Django

#18277: Startproject/app template documentation confusing
-+-
 Reporter:  sam@…|Owner:  quinode
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  1.4
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Design
 Keywords:  startproject |  decision needed
  startapp template  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Sam Simmons ):

 Replying to [comment:4 jezdez]:
 > Having written the feature in question, I'm not convinced this is a good
 idea. Needs more discussion on the mailing list.

 I hope you will at least keep the template option and continue to replace
 {{ project_name }}. This has already been useful for a django html5
 boilerplate clone.

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17890: django.contrib.admin.site extra_context

2012-05-15 Thread Django

#17890: django.contrib.admin.site extra_context
+
 Reporter:  riccardodivirgilio  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  contrib.admin   |  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 smuss):

 * needs_tests:  1 => 0


Comment:

 Tests added to 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16884: Add message level argument to ModelAdmin's message_user

2012-05-15 Thread Django

#16884: Add message level argument to ModelAdmin's message_user
---+
 Reporter:  shelldweller   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  admin  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  1
---+

Comment (by claudep):

 Replying to [comment:13 russellm]:
 > There's a good reason to keep messages_user -- it decouples admin from
 the messages app. By subclassing ModelAdmin, you can completely replace
 the use of Django's messages with any other scheme you wish; if you call
 the messages API directly, this obviously isn't possible.

 If by decouple, you mean avoid installing contrib.messages at all, it is
 probably already ruined by the contrib.messages import in options.py. And
 if you want to use your own messaging framework, you don't need
 message_user API for that. The only remaining use-case I can see, would be
 an external app providing a subclassed ModelAdmin that redirects
 message_user to another messages framework. At this point, I wonder if
 this external app would not simply instruct you to send messages with its
 custom messages framework in the first place. In summary, I'm struggling
 to find real use cases for that, but of course, I may miss some obvious
 uses.

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18277: Startproject/app template documentation confusing

2012-05-15 Thread Django

#18277: Startproject/app template documentation confusing
-+-
 Reporter:  sam@…|Owner:  quinode
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  1.4
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Design
 Keywords:  startproject |  decision needed
  startapp template  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by jezdez):

 Having written the feature in question, I'm not convinced this is a good
 idea. Needs more discussion on the mailing list.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18277: Startproject/app template documentation confusing

2012-05-15 Thread Django

#18277: Startproject/app template documentation confusing
-+-
 Reporter:  sam@…|Owner:  quinode
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  1.4
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Design
 Keywords:  startproject |  decision needed
  startapp template  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by jezdez):

 * stage:  Unreviewed => Design decision needed


-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17797: Added PATCH request functionality to django.test.client.Client

2012-05-15 Thread Django

#17797: Added PATCH request functionality to django.test.client.Client
---+
 Reporter:  pfarmer|Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  Test   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by mitar):

 * cc: mmitar@… (added)


Comment:

 +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 this group at 
http://groups.google.com/group/django-updates?hl=en.

[django/django] 085c03: Updated installation instructions.

2012-05-15 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 085c03e08b29fafc92ef49c2a3717ec23cf1c500
  
https://github.com/django/django/commit/085c03e08b29fafc92ef49c2a3717ec23cf1c500
  Author: Aymeric Augustin 
  Date:   2012-05-15 (Tue, 15 May 2012)

  Changed paths:
M INSTALL

  Log Message:
  ---
  Updated installation instructions.

Django 1.5 requires Python 2.6 or 2.7, and setup.py install over a
previous installation doesn't work.



-- 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18019: ./manage.py testserver with in-memory sqlite database fails on 1.4

2012-05-15 Thread Django

#18019: ./manage.py testserver with in-memory sqlite database fails on 1.4
-+-
 Reporter:  hcarvalhoalves   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  1.4
  commands)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  regression   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [6bb85d98b0574aec1aec9fb97c26ce16bc060522]:
 {{{
 #!CommitTicketReference repository=""
 revision="6bb85d98b0574aec1aec9fb97c26ce16bc060522"
 [1.4.x] Fixed #18019 -- Use threaded runserver only when database supports
 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18019: ./manage.py testserver with in-memory sqlite database fails on 1.4

2012-05-15 Thread Django

#18019: ./manage.py testserver with in-memory sqlite database fails on 1.4
-+-
 Reporter:  hcarvalhoalves   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  1.4
  commands)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  regression   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [bb4452f212e211bca7b6b57904d59270ffd7a503]:
 {{{
 #!CommitTicketReference repository=""
 revision="bb4452f212e211bca7b6b57904d59270ffd7a503"
 Fixed #18019 -- Use threaded runserver only when database supports 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16884: Add message level argument to ModelAdmin's message_user

2012-05-15 Thread Django

#16884: Add message level argument to ModelAdmin's message_user
---+
 Reporter:  shelldweller   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  admin  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  1
---+

Comment (by russellm):

 Replying to [comment:12 claudep]:
 > So a proposal would be to simply deprecate the method and suggest using
 the contrib.messages API directly. Other opinions?

 There's a good reason to keep messages_user -- it decouples admin from the
 messages app. By subclassing ModelAdmin, you can completely replace the
 use of Django's messages with any other scheme you wish; if you call the
 messages API directly, this obviously isn't possible.

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

[django/django] 6bb85d: [1.4.x] Fixed #18019 -- Use threaded runserver onl...

2012-05-15 Thread GitHub

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: 6bb85d98b0574aec1aec9fb97c26ce16bc060522
  
https://github.com/django/django/commit/6bb85d98b0574aec1aec9fb97c26ce16bc060522
  Author: Claude Paroz 
  Date:   2012-05-15 (Tue, 15 May 2012)

  Changed paths:
M django/core/management/commands/testserver.py

  Log Message:
  ---
  [1.4.x] Fixed #18019 -- Use threaded runserver only when database supports it.



-- 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

[django/django] bb4452: Fixed #18019 -- Use threaded runserver only when d...

2012-05-15 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: bb4452f212e211bca7b6b57904d59270ffd7a503
  
https://github.com/django/django/commit/bb4452f212e211bca7b6b57904d59270ffd7a503
  Author: Claude Paroz 
  Date:   2012-05-15 (Tue, 15 May 2012)

  Changed paths:
M django/core/management/commands/testserver.py

  Log Message:
  ---
  Fixed #18019 -- Use threaded runserver only when database supports it.



-- 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16884: Add message level argument to ModelAdmin's message_user

2012-05-15 Thread Django

#16884: Add message level argument to ModelAdmin's message_user
---+
 Reporter:  shelldweller   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  admin  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  1
---+

Comment (by claudep):

 Replying to [comment:11 sbaechler]:
 > If you have to import messages anyway now, isn't it easier to just use
 messages.error(request, 'foo') instead of self.message_user(request,
 'foo', level=messages.ERROR) ?
 > Especially since message_user doesn't seem to do anything but call
 messages.info().

 Fair, I admit that the message_user benefit is small. It avoids importing
 the contrib.messages when you use the default level.

 So a proposal would be to simply deprecate the method and suggest using
 the contrib.messages API directly. Other opinions?

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18314: request.build_absolute_uri() functions incorrectly when the path starts with //

2012-05-15 Thread Django

#18314: request.build_absolute_uri() functions incorrectly when the path starts
with //
---+
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  HTTP handling  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by claudep):

 * needs_docs:   => 0
 * needs_better_patch:   => 0
 * type:  Uncategorized => Bug
 * needs_tests:   => 1
 * 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 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17890: django.contrib.admin.site extra_context

2012-05-15 Thread Django

#17890: django.contrib.admin.site extra_context
+
 Reporter:  riccardodivirgilio  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  contrib.admin   |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by claudep):

 * needs_tests:  0 => 1


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15246: Allow to change session expiration without re-saving session data.

2012-05-15 Thread Django

#15246: Allow to change session expiration without re-saving session data.
--+
 Reporter:  zimnyx|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.sessions  |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

 * needs_tests:  0 => 1


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16884: Add message level argument to ModelAdmin's message_user

2012-05-15 Thread Django

#16884: Add message level argument to ModelAdmin's message_user
---+
 Reporter:  shelldweller   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  admin  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  1
---+
Changes (by sbaechler):

 * cc: simon@… (added)


Comment:

 If you have to import messages anyway now, isn't it easier to just use
 messages.error(request, 'foo') instead of self.message_user(request,
 'foo', level=messages.ERROR) ?
 Especially since message_user doesn't seem to do anything but call
 messages.info().

-- 
Ticket URL: 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

51 matches

Mail list logo