Re: [Django] #17785: PostgreSQL Introspection: get_relations() broken after drop column

[Django]

#17785: PostgreSQL Introspection: get_relations() broken after drop column
-+-
 Reporter:  guettli  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  psycopg2 |  Unreviewed
  introspection  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by guettli):

 * type:  Uncategorized => Bug


Comment:

 I updated the patch. A dictionary was not needed. A list is enough. I
 would prefere to return column names from get_relations(), but of course I
 need to fit to the current API: Returns a dictionary of
 {{{
 {field_index: (field_index_other_table, other_table)}
 }}}

-- 
Ticket URL: 
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] #17784: per-view cache broken in latest 1.4beta

[Django]

#17784: per-view cache broken in latest 1.4beta
---+--
 Reporter:  hemabe@…   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Uncategorized  |  Version:  SVN
 Severity:  Normal |   Resolution:  invalid
 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 mattmcc):

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


Comment:

 I'm fairly certain this never worked.  Decorators expect a callable
 argument (your view).

 https://docs.djangoproject.com/en/1.3/topics/cache/#specifying-per-view-
 cache-in-the-urlconf

-- 
Ticket URL: 
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] #17789: when i use a custom FieldListFilter class for a given field.

[Django]

#17789: when i use a custom FieldListFilter class for a given field.
---+-
 Reporter:  Kidwind|  Owner:  nobody
 Type:  Bug| Status:  new
Component:  contrib.admin  |Version:  1.3
 Severity:  Normal |   Keywords:  FieldListFilter
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  0  |  UI/UX:  0
---+-
 when i use a custom FieldListFilter class for a given field.

 list_filter = ('Site', ('RelationModel__Field', MyCustomFieldListFilter),)

 i get "Filtering by RelationModel__Field__exact not allowed"

-- 
Ticket URL: 
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] #17777: MD5PasswordHasher is not using salt

[Django]

#1: MD5PasswordHasher is not using salt
-+-
 Reporter:  gunnar@… |Owner:  PaulM
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  Version:
 Severity:  Release blocker  |  1.4-beta-1
 Keywords:  MD5PasswordHasher|   Resolution:
  MD5 salt login | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by PaulM):

 * type:  Uncategorized => Bug


Comment:

 This is related to the fact that we actually had 2 separate forms of MD5
 hashing historically, and the md5 hasher in the patch only deals with one
 of them:

 
https://code.djangoproject.com/browser/django/branches/releases/1.3.X/django/contrib/auth/models.py#L268

 
https://code.djangoproject.com/browser/django/branches/releases/1.3.X/django/contrib/auth/models.py#L31

-- 
Ticket URL: 
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] #17788: bulk_create() "too many SQL variables" error

[Django]

#17788: bulk_create() "too many SQL variables" error
--+
 Reporter:  alpar |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.4-beta-1
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 I tried to `bulk_create()` lots of (e.g. >300) objects with Django 1.4b1 +
 sqlite backend. It fails with
 {{{
 django.db.utils.DatabaseError: too many SQL variables
 }}}

 It makes the use of `bulk_create()` quite risky.

 Wouldn't is be possible the automatically break up the list of objects to
 smaller pieces when it turns out to be too large?

-- 
Ticket URL: 
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] #5622: Empty ipaddress raises an error (invalid input syntax for type inet: "")

[Django]

#5622: Empty ipaddress raises an error (invalid input syntax for type inet: "")
-+
 Reporter:  anonymous|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  SVN
 Severity:  Normal   |   Resolution:
 Keywords:  sprintdec01  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by jodym@…):

 * cc: jodym@… (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] #17764: Documentation out-of-date: django.contrib.auth.utils no longer exists.

[Django]

#17764: Documentation out-of-date: django.contrib.auth.utils no longer exists.
-+-
 Reporter:  mbt  |Owner:  PaulM
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:
 Severity:  Release blocker  |  1.4-beta-1
 Keywords:  authentication   |   Resolution:
  documentation  easy-pickings   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by aaugustin):

 * owner:  nobody => 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] #17777: MD5PasswordHasher is not using salt

[Django]

#1: MD5PasswordHasher is not using salt
-+-
 Reporter:  gunnar@… |Owner:  PaulM
 Type:  Uncategorized|   Status:  new
Component:  contrib.auth |  Version:
 Severity:  Release blocker  |  1.4-beta-1
 Keywords:  MD5PasswordHasher|   Resolution:
  MD5 salt login | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

 * owner:  nobody => PaulM
 * 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] #17786: Exception when running the tests under Oracle

[Django]

#17786: Exception when running the tests under Oracle
---+--
 Reporter:  aaugustin  |Owner:  aaugustin
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.4-beta-1
 Severity:  Release blocker|   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by aaugustin):

 * owner:  nobody => aaugustin
 * stage:  Unreviewed => Accepted


Comment:

 Yes, the problem has several solutions, it's mostly a matter of choosing
 the less ugly :)

 Assigning to myself since I have an Oracle setup where I can test this.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #17787: Clear setting-dependant caches when settings are overridden (in tests)

[Django]

#17787: Clear setting-dependant caches when settings are overridden (in tests)
---+--
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.4-beta-1
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by aaugustin):

 #17744 is an instance of this problem, with `MEDIA_ROOT`.

-- 
Ticket URL: 
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] #17744: override_settings has no effect on FileSystemStorage()

[Django]

#17744: override_settings has no effect on FileSystemStorage()
-+-
 Reporter:  mvt  |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  File |  Version:
  uploads/storage|  1.4-beta-1
 Severity:  Release blocker  |   Resolution:  duplicate
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 This is a particular instance of the general problem tracked in #17787
 (which I just created). Let's keep the more general ticket.

 A note was added to the docs in r17597, resolving the "release blocker"
 aspect.

-- 
Ticket URL: 
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] #16366: contrib.auth.tests.context_processors.AuthContextProcessorTests.test_session_not_accessed fails when project loads other middleware that access the session.

[Django]

#16366: 
contrib.auth.tests.context_processors.AuthContextProcessorTests.test_session_not_accessed
fails when project loads other middleware that access the session.
-+-
 Reporter:  jsdalton |Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  SVN
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  test | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 In [17598]:
 {{{
 #!CommitTicketReference repository="" revision="17598"
 Fixed #16366 -- Prevented some failures of the django.contrib.auth tests
 when run within a project. Thanks to everyone who contributed to 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.

[Changeset] r17598 - django/trunk/django/contrib/auth/tests

[noreply]

Author: aaugustin
Date: 2012-02-27 14:54:35 -0800 (Mon, 27 Feb 2012)
New Revision: 17598

Modified:
   django/trunk/django/contrib/auth/tests/context_processors.py
Log:
Fixed #16366 -- Prevented some failures of the django.contrib.auth tests when 
run within a project. Thanks to everyone who contributed to the patch.


Modified: django/trunk/django/contrib/auth/tests/context_processors.py
===
--- django/trunk/django/contrib/auth/tests/context_processors.py
2012-02-27 22:52:07 UTC (rev 17597)
+++ django/trunk/django/contrib/auth/tests/context_processors.py
2012-02-27 22:54:35 UTC (rev 17598)
@@ -1,9 +1,11 @@
 import os
 
-from django.conf import settings
+from django.conf import global_settings
 from django.contrib.auth import authenticate
 from django.db.models import Q
+from django.template import context
 from django.test import TestCase
+from django.test.utils import override_settings
 
 
 class AuthContextProcessorTests(TestCase):
@@ -13,28 +15,31 @@
 urls = 'django.contrib.auth.tests.urls'
 fixtures = ['context-processors-users.xml']
 
-def setUp(self):
-self.old_TEMPLATE_DIRS = settings.TEMPLATE_DIRS
-settings.TEMPLATE_DIRS = (
-os.path.join(os.path.dirname(__file__), 'templates'),
-)
-
-def tearDown(self):
-settings.TEMPLATE_DIRS = self.old_TEMPLATE_DIRS
-
+@override_settings(
+MIDDLEWARE_CLASSES=global_settings.MIDDLEWARE_CLASSES,
+
TEMPLATE_CONTEXT_PROCESSORS=global_settings.TEMPLATE_CONTEXT_PROCESSORS,
+)
 def test_session_not_accessed(self):
 """
 Tests that the session is not accessed simply by including
 the auth context processor
 """
+context._standard_context_processors = None
+
 response = self.client.get('/auth_processor_no_attr_access/')
 self.assertContains(response, "Session not accessed")
 
+@override_settings(
+MIDDLEWARE_CLASSES=global_settings.MIDDLEWARE_CLASSES,
+
TEMPLATE_CONTEXT_PROCESSORS=global_settings.TEMPLATE_CONTEXT_PROCESSORS,
+)
 def test_session_is_accessed(self):
 """
 Tests that the session is accessed if the auth context processor
 is used and relevant attributes accessed.
 """
+context._standard_context_processors = None
+
 response = self.client.get('/auth_processor_attr_access/')
 self.assertContains(response, "Session accessed")
 
@@ -86,3 +91,9 @@
 # See bug #12060
 self.assertEqual(response.context['user'], user)
 self.assertEqual(user, response.context['user'])
+
+AuthContextProcessorTests = override_settings(
+TEMPLATE_DIRS = (
+os.path.join(os.path.dirname(__file__), 'templates'),
+)
+)(AuthContextProcessorTests)

-- 
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] #17787: Clear setting-dependant caches when settings are overridden (in tests)

[Django]

#17787: Clear setting-dependant caches when settings are overridden (in tests)
---+--
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.4-beta-1
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by aaugustin):

 In [17597]:
 {{{
 #!CommitTicketReference repository="" revision="17597"
 Clarified the fact that the signal_changed signal isn't used by Django
 itself (yet). Refs #17787.
 }}}

-- 
Ticket URL: 
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.

[Changeset] r17597 - django/trunk/docs/topics

[noreply]

Author: aaugustin
Date: 2012-02-27 14:52:07 -0800 (Mon, 27 Feb 2012)
New Revision: 17597

Modified:
   django/trunk/docs/topics/testing.txt
Log:
Clarified the fact that the signal_changed signal isn't used by Django itself 
(yet). Refs #17787.


Modified: django/trunk/docs/topics/testing.txt
===
--- django/trunk/docs/topics/testing.txt2012-02-27 21:15:25 UTC (rev 
17596)
+++ django/trunk/docs/topics/testing.txt2012-02-27 22:52:07 UTC (rev 
17597)
@@ -1477,11 +1477,13 @@
 
 .. note::
 
-When overriding settings make sure to also handle the cases in which
-Django or your app's code uses a cache or similar feature that retains
-state even if the setting is changed. Django provides the
-:data:`django.test.signals.setting_changed` signal to connect cleanup
-and other state-resetting callbacks to.
+When overriding settings make sure to also handle the cases in which your
+app's code uses a cache or similar feature that retains state even if the
+setting is changed. Django provides the
+:data:`django.test.signals.setting_changed` signal to connect cleanup and
+other state-resetting callbacks to. Note that this signal isn't currently
+used by Django itself, so changing built-in settings may not yield the
+results you expect.
 
 Emptying the test outbox
 

-- 
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] #17787: Clear setting-dependant caches when settings are overridden (in tests)

[Django]

#17787: Clear setting-dependant caches when settings are overridden (in tests)
---+--
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.4-beta-1
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by aaugustin):

 It would be nice to add a note mentioning this limitation in the 1.4 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17787: Clear setting-dependant caches when settings are overridden (in tests)

[Django]

#17787: Clear setting-dependant caches when settings are overridden (in tests)
---+--
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.4-beta-1
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by aaugustin):

 * owner:  aaugustin => nobody
 * severity:  Release blocker => Normal
 * stage:  Design decision needed => Accepted


Comment:

 We discussed this on IRC and determined that:
 - this should be fixed eventually — `override_settings` doesn't reach its
 full potential until then
 - this doesn't need to be fixed in 1.4 — `override_settings` is useful,
 even without this, and we don't want to make too intrusive changes at this
 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] #2140: short_description in admin for get_absolute_url doesn't work due to currying

[Django]

#2140: short_description in admin for get_absolute_url doesn't work due to
currying
+
 Reporter:  Rudolph |Owner:  nobody
 Type:  defect  |   Status:  closed
Component:  contrib.admin   |  Version:  SVN
 Severity:  normal  |   Resolution:  fixed
 Keywords:  nfa-changelist  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by anonymous):

 * ui_ux:   => 0
 * easy:   => 0


Comment:

 More details at http://www.youtube.com/watch?v=XPpXll4GmwE

-- 
Ticket URL: 
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] #17627: contrib.admin.util is misnamed

[Django]

#17627: contrib.admin.util is misnamed
--+
 Reporter:  PaulM |Owner:  lukegb
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  contrib.admin |  Version:  SVN
 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 lukegb):

 * status:  new => assigned


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #17627: contrib.admin.util is misnamed

[Django]

#17627: contrib.admin.util is misnamed
--+
 Reporter:  PaulM |Owner:  lukegb
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admin |  Version:  SVN
 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 lukegb):

 * status:  assigned => new
 * owner:  viciu => lukegb


Comment:

 Assigning to self after 3 weeks.

-- 
Ticket URL: 
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] #17787: Clear setting-dependant caches when settings are overridden (in tests)

[Django]

#17787: Clear setting-dependant caches when settings are overridden (in tests)
-+-
 Reporter:  aaugustin|Owner:  aaugustin
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:
 Severity:  Release blocker  |  1.4-beta-1
 Keywords:   |   Resolution:
Has patch:  0| Triage Stage:  Design
  Needs tests:  0|  decision needed
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

 * owner:  nobody => aaugustin


-- 
Ticket URL: 
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] #16366: contrib.auth.tests.context_processors.AuthContextProcessorTests.test_session_not_accessed fails when project loads other middleware that access the session.

[Django]

#16366: 
contrib.auth.tests.context_processors.AuthContextProcessorTests.test_session_not_accessed
fails when project loads other middleware that access the session.
-+-
 Reporter:  jsdalton |Owner:  aaugustin
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  Version:  SVN
 Severity:  Release blocker  |   Resolution:
 Keywords:  test | 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 aaugustin):

 Replying to [comment:13 claudep]:
 > I'd better see the context._standard_context_processors cache emptied in
 override_settings itself, instead of in each test. Let the committer
 decide what's the preferred approach.

 I've created #17787 to track the more general problem. Until a decision is
 made on that ticket, we can use an ad-hoc reset — we're already doing that
 in several tests.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #17787: Clear setting-dependant caches when settings are overridden (in tests)

[Django]

#17787: Clear setting-dependant caches when settings are overridden (in tests)
-+-
   Reporter:  aaugustin  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Testing|Version:  1.4-beta-1
  framework  |   Keywords:
   Severity:  Release|  Has patch:  0
  blocker|Needs tests:  0
   Triage Stage:  Design |  Easy pickings:  0
  decision needed|
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 r16237 introduced a `setting_changed` signal, triggered by the
 `override_settings` decorator / context manager.

 However, Django doesn't use this signal to reset caches that depend on
 built-in settings. In the current state of thing, the signal is only
 usable is third-party code.

 Is this a design choice or a bug?

 Marking as release blocker since it's a major bug in a new feature.

-- 
Ticket URL: 
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] #17786: Exception when running the tests under Oracle

[Django]

#17786: Exception when running the tests under Oracle
---+--
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.4-beta-1
 Severity:  Release blocker|   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by akaariai):

 * cc: anssi.kaariainen@… (added)


Comment:

 This is almost definitely connected to r17411. That patch caused the drop
 database code to use a new connection for dropping the database. The
 Oracle code expects the dropping to be done by the same connection.

 The right fix seems to be returning the "remember" dictionary from the
 _create_test_db(), and then again passing it to _destroy_test_db(). Or,
 you could get hacky and have a class level remember variable in the
 creation code, mapping connection alias to remember dictionary of that
 alias. It should work but as said, it is a little ugly... Even uglier is
 just assigning the creation from the old connection to the new temporary
 connection.

-- 
Ticket URL: 
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] #17605: It is not documented how to work with ManyToMany relations

[Django]

#17605: It is not documented how to work with ManyToMany relations
-+
 Reporter:  kmike|Owner:  ramiro
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  1.3
 Severity:  Release blocker  |   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 ramiro):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #8492: Nesting applications can cause name collision in admin

[Django]

#8492: Nesting applications can cause name collision in admin
-+--
 Reporter:  chris_dickinson  |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  contrib.admin|  Version:  SVN
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by anonymous):

 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


Comment:

 'nest.lhs',http://www.wvweightloss.com/ #comment this app to make the
 application work again 'lhs',

-- 
Ticket URL: 
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.

[Changeset] r17596 - in django/trunk: django/db/backends/mysql django/db/backends/oracle django/db/backends/sqlite3 tests/modeltests/timezones

[noreply]

Author: aaugustin
Date: 2012-02-27 13:15:25 -0800 (Mon, 27 Feb 2012)
New Revision: 17596

Modified:
   django/trunk/django/db/backends/mysql/base.py
   django/trunk/django/db/backends/oracle/base.py
   django/trunk/django/db/backends/sqlite3/base.py
   django/trunk/tests/modeltests/timezones/tests.py
Log:
Fixed #17755 -- Ensured datetime objects that bypass the model layer (for 
instance, in raw SQL queries) are converted to UTC before sending them to the 
database when time zone support is enabled. Thanks Anssi for the report.


Modified: django/trunk/django/db/backends/mysql/base.py
===
--- django/trunk/django/db/backends/mysql/base.py   2012-02-27 19:04:33 UTC 
(rev 17595)
+++ django/trunk/django/db/backends/mysql/base.py   2012-02-27 21:15:25 UTC 
(rev 17596)
@@ -4,6 +4,7 @@
 Requires MySQLdb: http://sourceforge.net/projects/mysql-python
 """
 
+import datetime
 import re
 import sys
 
@@ -24,6 +25,7 @@
 
 from MySQLdb.converters import conversions
 from MySQLdb.constants import FIELD_TYPE, CLIENT
+from _mysql import string_literal
 
 from django.db import utils
 from django.db.backends import *
@@ -33,7 +35,7 @@
 from django.db.backends.mysql.introspection import DatabaseIntrospection
 from django.db.backends.mysql.validation import DatabaseValidation
 from django.utils.safestring import SafeString, SafeUnicode
-from django.utils.timezone import is_aware, is_naive, utc
+from django.utils import timezone
 
 # Raise exceptions for database warnings if DEBUG is on
 from django.conf import settings
@@ -45,15 +47,27 @@
 IntegrityError = Database.IntegrityError
 
 # It's impossible to import datetime_or_None directly from MySQLdb.times
-datetime_or_None = conversions[FIELD_TYPE.DATETIME]
+parse_datetime = conversions[FIELD_TYPE.DATETIME]
 
-def datetime_or_None_with_timezone_support(value):
-dt = datetime_or_None(value)
+def parse_datetime_with_timezone_support(value):
+dt = parse_datetime(value)
 # Confirm that dt is naive before overwriting its tzinfo.
-if dt is not None and settings.USE_TZ and is_naive(dt):
-dt = dt.replace(tzinfo=utc)
+if dt is not None and settings.USE_TZ and timezone.is_naive(dt):
+dt = dt.replace(tzinfo=timezone.utc)
 return dt
 
+def adapt_datetime_with_timezone_support(value, conv):
+# Equivalent to DateTimeField.get_db_prep_value. Used only by raw SQL.
+if settings.USE_TZ:
+if timezone.is_naive(value):
+warnings.warn(u"SQLite received a naive datetime (%s)"
+  u" while time zone support is active." % value,
+  RuntimeWarning)
+default_timezone = timezone.get_default_timezone()
+value = timezone.make_aware(value, default_timezone)
+value = value.astimezone(timezone.utc).replace(tzinfo=None)
+return string_literal(value.strftime("%Y-%m-%d %H:%M:%S"), conv)
+
 # MySQLdb-1.2.1 returns TIME columns as timedelta -- they are more like
 # timedelta in terms of actual behavior as they are signed and include days --
 # and Django expects time, so we still need to override that. We also need to
@@ -66,7 +80,8 @@
 FIELD_TYPE.TIME: util.typecast_time,
 FIELD_TYPE.DECIMAL: util.typecast_decimal,
 FIELD_TYPE.NEWDECIMAL: util.typecast_decimal,
-FIELD_TYPE.DATETIME: datetime_or_None_with_timezone_support,
+FIELD_TYPE.DATETIME: parse_datetime_with_timezone_support,
+datetime.datetime: adapt_datetime_with_timezone_support,
 })
 
 # This should match the numerical portion of the version numbers (we can treat
@@ -268,9 +283,9 @@
 return None
 
 # MySQL doesn't support tz-aware datetimes
-if is_aware(value):
+if timezone.is_aware(value):
 if settings.USE_TZ:
-value = value.astimezone(utc).replace(tzinfo=None)
+value = value.astimezone(timezone.utc).replace(tzinfo=None)
 else:
 raise ValueError("MySQL backend does not support 
timezone-aware datetimes when USE_TZ is False.")
 
@@ -282,7 +297,7 @@
 return None
 
 # MySQL doesn't support tz-aware times
-if is_aware(value):
+if timezone.is_aware(value):
 raise ValueError("MySQL backend does not support timezone-aware 
times.")
 
 # MySQL doesn't support microseconds

Modified: django/trunk/django/db/backends/oracle/base.py
===
--- django/trunk/django/db/backends/oracle/base.py  2012-02-27 19:04:33 UTC 
(rev 17595)
+++ django/trunk/django/db/backends/oracle/base.py  2012-02-27 21:15:25 UTC 
(rev 17596)
@@ -52,7 +52,7 @@
 from django.db.backends.oracle.creation import DatabaseCreation
 from django.db.backends.oracle.introspection import DatabaseIntrospection
 from django.utils.encoding import smart_str, force_unicode
-from django.utils.timezone import is_aware, is_naive, utc
+from 

Re: [Django] #17755: Use database adapters for converting time zone aware datetimes in raw queries

[Django]

#17755: Use database adapters for converting time zone aware datetimes in raw
queries
-+-
 Reporter:  akaariai |Owner:  aaugustin
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |  1.4-beta-1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  akaariai | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 In [17596]:
 {{{
 #!CommitTicketReference repository="" revision="17596"
 Fixed #17755 -- Ensured datetime objects that bypass the model layer (for
 instance, in raw SQL queries) are converted to UTC before sending them to
 the database when time zone support is enabled. Thanks Anssi for the
 report.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #915: Admin breadcrumb links assume app is rooted at /admin/

[Django]

#915: Admin breadcrumb links assume app is rooted at /admin/
---+--
 Reporter:  oggie rob  |Owner:  adrian
 Type:  defect |   Status:  closed
Component:  contrib.admin  |  Version:
 Severity:  normal |   Resolution:  fixed
 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 anonymous):

 * ui_ux:   => 0
 * easy:   => 0


Comment:

 I guess http://www.wvweightloss.com/ still assumes certain locations but
 might be a little less likely to fail under some modifications

-- 
Ticket URL: 
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] #17786: Exception when running the tests under Oracle

[Django]

#17786: Exception when running the tests under Oracle
-+
   Reporter:  aaugustin  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Testing framework  |Version:  1.4-beta-1
   Severity:  Release blocker|   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 {{{
 Destroying test database for alias 'default'...
 Traceback (most recent call last):
   File "runtests.py", line 323, in 
 options.failfast, args)
   File "runtests.py", line 166, in django_tests
 failures = test_runner.run_tests(test_labels, extra_tests=extra_tests)
   File "/var/lib/jenkins/jobs/Django +
 Oracle/workspace/django/test/simple.py", line 383, in run_tests
 self.teardown_databases(old_config)
   File "/var/lib/jenkins/jobs/Django +
 Oracle/workspace/django/test/simple.py", line 351, in teardown_databases
 connection.creation.destroy_test_db(old_name, self.verbosity)
   File "/var/lib/jenkins/jobs/Django +
 Oracle/workspace/django/db/backends/creation.py", line 378, in
 destroy_test_db
 new_connection.creation._destroy_test_db(test_database_name,
 verbosity)
   File "/var/lib/jenkins/jobs/Django +
 Oracle/workspace/django/db/backends/oracle/creation.py", line 126, in
 _destroy_test_db
 self.connection.settings_dict["USER"] = self.remember['user']
 KeyError: 'user'
 }}}

 This could be to be a consequence of r17411.

-- 
Ticket URL: 
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] #4102: Allow UPDATE of only specific fields in model.save()

[Django]

#4102: Allow UPDATE of only specific fields in model.save()
-+-
 Reporter:  Collin Grady |Owner:  cgrady
   |   Status:  new
 Type:  New feature  |  Version:  SVN
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  1
 Keywords:  update fields sql|  Patch needs improvement:  1
  row table modified |UI/UX:  0
Has patch:  1|
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by akaariai):

 Implementing only_fields kwarg for model .save() sounds like a plan. That
 would be really useful feature, simple to implement and I think nobody
 will give a -1 to that idea.

 In ticket #17332 is a patch which should allow (with minor changes)
 override of model._state. Also, the `ModelState` does have some methods in
 it which allow tracking of dirty field state (of course, implemented in a
 custom state class). That way 3rd party projects could pretty easily
 implement tracking of dirty field state in the way they wish (hashing,
 flags, storing the old values...). Using the ._state information you can
 then implement custom .save() which automatically saves only changed
 fields. Note that the important parts of the patch are the `ModelState`
 changes, and where .update()/clear() are called, rest is irrelevant to
 this ticket.

 It seems clear that a default behavior of saving only changed fields will
 not get into Django core.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.

[Changeset] r17595 - in django/trunk/docs/topics: . _images

[noreply]

Author: ramiro
Date: 2012-02-27 11:04:33 -0800 (Mon, 27 Feb 2012)
New Revision: 17595

Added:
   django/trunk/docs/topics/_images/
   django/trunk/docs/topics/_images/django_unittest_classes_hierarchy.png
Modified:
   django/trunk/docs/topics/testing.txt
Log:
Added a diagram of the hierarchy of our TestCase subclasses to the testing docs.

Added: django/trunk/docs/topics/_images/django_unittest_classes_hierarchy.png
===
(Binary files differ)


Property changes on: 
django/trunk/docs/topics/_images/django_unittest_classes_hierarchy.png
___
Added: svn:mime-type
   + application/octet-stream

Modified: django/trunk/docs/topics/testing.txt
===
--- django/trunk/docs/topics/testing.txt2012-02-27 14:40:36 UTC (rev 
17594)
+++ django/trunk/docs/topics/testing.txt2012-02-27 19:04:33 UTC (rev 
17595)
@@ -1089,6 +1089,9 @@
 Normal Python unit test classes extend a base class of
 :class:`unittest.TestCase`. Django provides a few extensions of this base 
class:
 
+.. image:: _images/django_unittest_classes_hierarchy.png
+   :alt: Django hierarchy of unit testing helper classes (TestCase subclasses)
+
 .. class:: TestCase()
 
 This class provides some additional capabilities that can be useful for testing

-- 
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] #17785: PostgreSQL Introspection: get_relations() broken after drop column

[Django]

#17785: PostgreSQL Introspection: get_relations() broken after drop column
-+-
 Reporter:  guettli  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  psycopg2 |  Unreviewed
  introspection  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by claudep):

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


Comment:

 Did you explore the possibility to use the column name as the relations
 dict key instead of an index, which seems very fragile to me?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #4102: Allow UPDATE of only specific fields in model.save()

[Django]

#4102: Allow UPDATE of only specific fields in model.save()
-+-
 Reporter:  Collin Grady |Owner:  cgrady
   |   Status:  new
 Type:  New feature  |  Version:  SVN
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  1
 Keywords:  update fields sql|  Patch needs improvement:  1
  row table modified |UI/UX:  0
Has patch:  1|
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by mattlong):

 * cc: mattlong (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] #17750: User.get_profile() returns cached object when database object has changed

[Django]

#17750: User.get_profile() returns cached object when database object has 
changed
--+
 Reporter:  rjalves   |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.auth  |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by claudep):

 For me, it looks rather fine now.[[BR]]
 Did you try to use the more convenient override_settings decorator for the
 AUTH_PROFILE_MODULE in tests (you can find examples in
 regressiontests/cache/tests.py)?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #16074: Class-based views clash get_context_data

[Django]

#16074: Class-based views clash get_context_data
-+-
 Reporter:  emyller  |Owner:  tobias
 Type:  Bug  |   Status:  assigned
Component:  Generic views|  Version:  SVN
 Severity:  Normal   |   Resolution:
 Keywords:  cbv  | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by anonymous):

 * stage:  Accepted => Ready for checkin


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #4102: Allow UPDATE of only specific fields in model.save()

[Django]

#4102: Allow UPDATE of only specific fields in model.save()
-+-
 Reporter:  Collin Grady |Owner:  cgrady
   |   Status:  new
 Type:  New feature  |  Version:  SVN
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  1
 Keywords:  update fields sql|  Patch needs improvement:  1
  row table modified |UI/UX:  0
Has patch:  1|
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by mattlong):

 After reviewing the history of this ticket, it seems what started as a
 simple opt-in feature request of adding a field white-list to the Model's
 save function morphed into a complicated dirty flag approach that
 obviously has many edge cases and performance implications given that this
 ticket has been open for 5 years now. Just compare the very first proposed
 patch to the latest to see what I mean.

 Unfortunately, this seemed to have happened without much discussion about
 the relative merits of each approach. I would prefer the Django ORM leave
 it to me to decide which fields I would like to update rather than relying
 on it to correctly infer which fields I would like updated. Clearly some
 people differently and favor the dirty flag approach for a more hands-off
 approach. As such, I propose adding support for both methods so that
 developers can choose the right approach for their use 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17750: User.get_profile() returns cached object when database object has changed

[Django]

#17750: User.get_profile() returns cached object when database object has 
changed
--+
 Reporter:  rjalves   |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.auth  |  Version:  SVN
 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 rjalves):

 * needs_better_patch:  1 => 0


Comment:

 Please confirm that patch is acceptable.

-- 
Ticket URL: 
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] #17762: Multi-db apps (no Django test suite) testing fails to create in-memory sqlite DBs

[Django]

#17762: Multi-db apps (no Django test suite) testing fails to create in-memory
sqlite DBs
-+-
 Reporter:  agriffis |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (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 agriffis):

 Replying to [comment:5 aaugustin]:
 > IIRC there's a special case to make Django do the right thing if you
 omit `'NAME': ':memory:',` from the definition of both databases. Could
 you try that?

 That works, but I actually don't need a workaround (I have those). Thanks
 though! I filed this ticket to get the underlying issue fixed of Django
 recognizing explicitly temporary SQLite databases.

-- 
Ticket URL: 
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] #17785: PostgreSQL Introspection: get_relations() broken after drop column

[Django]

#17785: PostgreSQL Introspection: get_relations() broken after drop column
--+
 Reporter:  guettli   |  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.3
 Severity:  Normal|   Keywords:  psycopg2
 Triage Stage:  Unreviewed|  introspection
Easy pickings:  0 |  Has patch:  1
  |  UI/UX:  0
--+
 Hi,

 if a column gets dropped postgreSQL does not update the attnum of columns
 which have a higher attnum:

 {{{

 # oid: select oid from pg_class where relname='modwork_buchungskreis';

 modwork_eins_d=> select attrelid, attname, atttypid,  attnum from
 pg_attribute where attrelid = 149923 order by attnum; attrelid |
 attname| atttypid | attnum
 --+--+--+
149923 | tableoid |   26 | -7
149923 | cmax |   29 | -6
149923 | xmax |   28 | -5
149923 | cmin |   29 | -4
149923 | xmin |   28 | -3
149923 | ctid |   27 | -1
149923 | id   | 1043 |  1
149923 | name | 1043 |  2
149923 | pg.dropped.3 |0 |  3
149923 | pg.dropped.4 |0 |  4
149923 | default  |   16 |  5
149923 | beschreibung | 1043 |  6
149923 | archiv   | 1043 |  7
149923 | email_sender_id  | 1043 |  8


 }}}

 BTW, the same bug is in django/db/backends/postgresql/introspection.py

 Patch attached. I think it is overkill to write a unittest for this.
 Please let me know if you want a test.

-- 
Ticket URL: 
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] #17761: save_base() does not properly detect when MTI parent key is unset

[Django]

#17761: save_base() does not properly detect when MTI parent key is unset
-+-
 Reporter:  agriffis |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (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|
-+-
Changes (by agriffis):

 * needs_tests:  1 => 0


Comment:

 I've attached a regression test patch, so I'm unchecking "Needs tests"
 (though the meaning of that field is unclear, does it mean "issue needs a
 test in django" or "ticket needs a test attached?" I'm interpreting it as
 the latter)

-- 
Ticket URL: 
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] #17762: Multi-db apps (no Django test suite) testing fails to create in-memory sqlite DBs

[Django]

#17762: Multi-db apps (no Django test suite) testing fails to create in-memory
sqlite DBs
-+-
 Reporter:  agriffis |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (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 aaugustin):

 IIRC there's a special case to make Django do the right thing if you omit
 `'NAME': ':memory:',` from the definition of both databases. Could you try
 that?

-- 
Ticket URL: 
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] #17762: Multi-db apps (no Django test suite) testing fails to create in-memory sqlite DBs

[Django]

#17762: Multi-db apps (no Django test suite) testing fails to create in-memory
sqlite DBs
-+-
 Reporter:  agriffis |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (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 agriffis):

 Replying to [comment:3 ramiro]:
 > Could you give us more details how are you getting the ''"Django fails
 to create multiple in-memory SQLite databases, instead it creates only one
 (which is populated only with the table definitions for the default DB)"''
 failure you describe so others can reproduce it?

 Thanks for the time you've put into this, and the instructions for
 creating the mdb app! I wasn't sure how to quickly make an isolated test
 case for this. I see the problem using the mdb app with the following
 `DATABASES` definition:

 {{{
 #!python
 DATABASES = {
 'default': {
 'ENGINE': 'django.db.backends.sqlite3',
 'NAME': ':memory:',
 },
 'other': {
 'ENGINE': 'django.db.backends.sqlite3',
 'NAME': ':memory:',
 }
 }
 }}}

 which results in:

 {{{
 $ ./manage.py test -v2 mdb 2>&1 | grep Creating
 Creating test database for alias 'default' (':memory:')...
 Creating tables ...
 Creating table auth_permission
 Creating table auth_group_permissions
 Creating table auth_group
 Creating table auth_user_user_permissions
 Creating table auth_user_groups
 Creating table auth_user
 Creating table auth_message
 Creating table django_content_type
 Creating table django_session
 Creating table django_site
 Creating table mdb_review
 Creating table mdb_person
 Creating table mdb_book_authors
 Creating table mdb_book
 Creating table mdb_pet
 Creating table mdb_userprofile
 }}}

 At the time I originally saw the problem, I was working on a large,
 venerable Django app that calls out its test DB settings explicitly as
 shown above. It's not an ordinary way to declare `DATABASES`, but I don't
 think Django should be mistaking the two databases as one since the
 `':memory:'` name is special for SQLite.

 Regarding:
 > The patch doesn't seem to make any sense, though.

 The base `test_db_signature()` distinguishes unique databases by the
 combination of `ENGINE`, `NAME`, etc.  SQLite databases are distinguished
 by `NAME` except for `':memory:'` and `''` (on-disk temporary DB) which
 are unique per-connection even if the `NAME` is the same as another
 connection. I figured `id(self.connection)` accurately identifies unique
 databases in this case.  Does it make sense with that explanation?

-- 
Ticket URL: 
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] #17784: per-view cache broken in latest 1.4beta

[Django]

#17784: per-view cache broken in latest 1.4beta
---+
 Reporter:  hemabe@…   |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Uncategorized  |Version:  SVN
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I'm using cache_page in the URLconf. It worked in 1.4 alpha, but is broken
 in the latest 1.4 beta.

 Details:
 My urls.py looks like this:


 {{{
 url(r'^latest$', cache_page(60 * 15)('latest'), name='deugg_latest')

 }}}

 This worked in 1.4 alpha, but is now broken in the latest 1.4 svn trunk.
 I get this error:


 {{{
 TypeError at /deugg/latest
 'str' object is not callable

 Exception Location: /usr/local/lib/python2.7/dist-
 packages/django/utils/decorators.py in _wrapped_view, line 91
 }}}


 Any ideas?

-- 
Ticket URL: 
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.

[Changeset] r17594 - django/trunk/docs/ref/contrib

[noreply]

Author: lukeplant
Date: 2012-02-27 06:40:36 -0800 (Mon, 27 Feb 2012)
New Revision: 17594

Modified:
   django/trunk/docs/ref/contrib/csrf.txt
Log:
Added versionadded info for ensure_csrf_cookie decorator

Modified: django/trunk/docs/ref/contrib/csrf.txt
===
--- django/trunk/docs/ref/contrib/csrf.txt  2012-02-27 14:40:27 UTC (rev 
17593)
+++ django/trunk/docs/ref/contrib/csrf.txt  2012-02-27 14:40:36 UTC (rev 
17594)
@@ -349,6 +349,8 @@
 
 .. function:: ensure_csrf_cookie(view)
 
+.. versionadded:: 1.4
+
 This decorator forces a view to send the CSRF cookie.
 
 Scenarios

-- 
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.

[Changeset] r17593 - django/trunk/docs/ref/contrib

[noreply]

Author: lukeplant
Date: 2012-02-27 06:40:27 -0800 (Mon, 27 Feb 2012)
New Revision: 17593

Modified:
   django/trunk/docs/ref/contrib/csrf.txt
Log:
Fixed ReST typo in CSRF docs.

Modified: django/trunk/docs/ref/contrib/csrf.txt
===
--- django/trunk/docs/ref/contrib/csrf.txt  2012-02-27 13:29:56 UTC (rev 
17592)
+++ django/trunk/docs/ref/contrib/csrf.txt  2012-02-27 14:40:27 UTC (rev 
17593)
@@ -366,7 +366,7 @@
 CsrfViewMiddleware.process_view not used
 
 
-There are cases when ``CsrfViewMiddleware.process_view``` may not have run
+There are cases when ``CsrfViewMiddleware.process_view`` may not have run
 before your view is run - 404 and 500 handlers, for example - but you still
 need the CSRF token in a form.
 

-- 
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.

[Changeset] r17592 - django/trunk/tests/regressiontests/admin_views

[noreply]

Author: ramiro
Date: 2012-02-27 05:29:56 -0800 (Mon, 27 Feb 2012)
New Revision: 17592

Modified:
   django/trunk/tests/regressiontests/admin_views/tests.py
Log:
Modified tests introduced in r15452 to not run 31 test cases twice. Thanks 
Julien for discovering this.

Modified: django/trunk/tests/regressiontests/admin_views/tests.py
===
--- django/trunk/tests/regressiontests/admin_views/tests.py 2012-02-26 
21:17:58 UTC (rev 17591)
+++ django/trunk/tests/regressiontests/admin_views/tests.py 2012-02-27 
13:29:56 UTC (rev 17592)
@@ -607,14 +607,22 @@
 self.assertTrue('custom_filter_template.html' in [t.name for t in 
response.templates])
 
 
-class AdminJavaScriptTest(AdminViewBasicTest):
+class AdminJavaScriptTest(TestCase):
+fixtures = ['admin-views-users.xml']
+
 urls = "regressiontests.admin_views.urls"
 
+def setUp(self):
+self.client.login(username='super', password='secret')
+
+def tearDown(self):
+self.client.logout()
+
 def testSingleWidgetFirsFieldFocus(self):
 """
 JavaScript-assisted auto-focus on first field.
 """
-response = self.client.get('/test_admin/%s/admin_views/picture/add/' % 
self.urlbit)
+response = self.client.get('/test_admin/%s/admin_views/picture/add/' % 
'admin')
 self.assertContains(
 response,
 'document.getElementById("id_name").focus();'
@@ -625,7 +633,7 @@
 JavaScript-assisted auto-focus should work if a model/ModelAdmin setup
 is such that the first form field has a MultiWidget.
 """
-response = 
self.client.get('/test_admin/%s/admin_views/reservation/add/' % self.urlbit)
+response = 
self.client.get('/test_admin/%s/admin_views/reservation/add/' % 'admin')
 self.assertContains(
 response,
 'document.getElementById("id_start_date_0").focus();'
@@ -640,7 +648,7 @@
 """
 with override_settings(DEBUG=False):
 response = self.client.get(
-'/test_admin/%s/admin_views/section/add/' % self.urlbit)
+'/test_admin/%s/admin_views/section/add/' % 'admin')
 self.assertNotContains(response, 'jquery.js')
 self.assertContains(response, 'jquery.min.js')
 self.assertNotContains(response, 'prepopulate.js')
@@ -653,7 +661,7 @@
 self.assertContains(response, 'inlines.min.js')
 with override_settings(DEBUG=True):
 response = self.client.get(
-'/test_admin/%s/admin_views/section/add/' % self.urlbit)
+'/test_admin/%s/admin_views/section/add/' % 'admin')
 self.assertContains(response, 'jquery.js')
 self.assertNotContains(response, 'jquery.min.js')
 self.assertContains(response, 'prepopulate.js')

-- 
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] #17782: django.contrib.gis.feeds.Feed uses deprecated API

[Django]

#17782: django.contrib.gis.feeds.Feed uses deprecated API
-+-
 Reporter:  richard@…|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.3
Component:  GIS  |   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

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


Comment:

 This was fixed in r16539
 (https://code.djangoproject.com/changeset/16539#file26)

-- 
Ticket URL: 
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] #15040: Boolean fields return 0 and 1 when loaded through select_related

[Django]

#15040: Boolean fields return 0 and 1 when loaded through select_related
-+-
 Reporter:  homm |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.2
  (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|
-+-
Changes (by ramiro):

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

[Django] #17783: Budgets Are Essential For Business Success

[Django]

#17783: Budgets Are Essential For Business Success
---+
 Reporter:  vebikike   |  Owner:  nobody
 Type:  bug / defect   | Status:  new
Component:  Uncategorized  |Version:  1.3
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  0
UI/UX:  0  |
---+
 I'm perfectly asking.Today, at hand are plenty of statistics entry jobs
 available on the Internet.No Risk" Lawsuit Loans are to no avail of
 commencing accepted banking approaches regular lenders match.For instance,
 impart, a team bought a terrace swiss timepiece imitations together and
 therefore separated or divorced.Affiliates will typically be furnished
 through a sales page.Whatever with the purpose of my be for you.If you are
 having imitation timepiece difficulty with your child having a technology
 advantage over you, this can be a lofty help.Unfortunately, the enormous
 divorce moreover domestic violence industry thrives on this unjust denial
 of a [http://rolexreplica.webgarden.com imitation timepiece] fathers
 rights - court kidnapping of his children, extortion payments, moreover
 denial of constitutional due process; [http://rolexreplica.webgarden.com
 timepiece imitations] moreover it works to maintain this injustice.The
 best style to resolve FMV is to work among someone already familiar among
 the area or resolve physically through local websites showing recent sales
 histories.do you need to start working in this career?You may thing about
 starting off by running for someone running a timepiece imitation business
 akin to that in your idea so that you can learn the intricacies of the
 business and you will have a kick set off on your own.The country has not
 recovered from the recession and many people who lost their jobs
 [http://rolexreplica.webgarden.com timepiece imitation] in the last years
 are still looking for employment, so if you are looking recruit employees,
 there is plenty of fish in the sea to choose from, right?Before business
 coins or bullions it is suggested to superstore something like to stumble
 imitation timepiecees on the paramount agreement.To keep positive cash
 drift moreover momentum in sales the mountain developments have to
 [http://rolexreplica.webgarden.com swiss timepiece imitation] work harder
 to earn the investment euro.Pilgrim's Pride not compulsory as much in the
 release by stating such synergies were "expected to come primarily from
 the optimization of production along with distribution facilities along
 with cost savings in purchasing, production, logistics, along with
 SG".Ryanair also declare an offer that if you buy five Ryanair flights
 using the credit card, you will get a free flight.Just for the reason that
 your business is now on the Online doesn't mean that the basics of useful
 marketing don't apply.Stop!A personal computer (of course, you by now give
 birth imitation timepiece to one of those or you wouldn't be reading
 this!Other than the mobile cell swiss imitation timepiece timepiece
 receiver searches, you may also search for landlines and other
 unlisted/unpublished imitation timepiece numbers as well.Reason mortal is
 they are the timepiece imitation maximum wage jobs available online along
 with call for [http://rolexreplica.webgarden.com timepiece imitation
 cheap] little to no experience.Awesome.some call the, "information based
 organization.In order to figure how much money you bottle afford to invest
 is to stare at your savings.You might timepiece imitation want to
 utilization the Florida Bar's eminent domain working group (www.

-- 
Ticket URL: 
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] #17782: django.contrib.gis.feeds.Feed uses deprecated API

[Django]

#17782: django.contrib.gis.feeds.Feed uses deprecated API
--+
 Reporter:  richard@… |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  GIS   |Version:  1.3
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 django.contrib.gis.feeds.Feed inherits from
 django.contrib.syndication.feeds.Feed which is deprecated in favour of
 django.contrib.syndication.views.Feed.

-- 
Ticket URL: 
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] #17781: Django cache middleware does not set "Age" header as described in rfc2616

[Django]

#17781: Django cache middleware does not set "Age" header as described in 
rfc2616
-+
 Reporter:  corentin.chary@… |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Core (Cache system)  |Version:  SVN
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 Django cache middleware set "Cache-Control: max-age=" and "Expires", but
 does not set "Age".
 This can be an issue, because "max-age" in frozen, so you can only rely on
 "Expires" for expiration time. Having the "Age" header set would allow the
 client to now when this page was cached by django.

 This feature would require adding a cache.age(key) function in all cache
 backends, which is far from trival, especially with backends such as
 memcached.

-- 
Ticket URL: 
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] #16819: list_editable breaks multipage changelists

[Django]

#16819: list_editable breaks multipage changelists
-+
 Reporter:  anossov@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  SVN
 Severity:  Release blocker  |   Resolution:
 Keywords:  admin list_editable  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by julien):

 A patch added to #17198 fixes this issue.

-- 
Ticket URL: 
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] #17198: In admin results can be omitted due to pagination and inadequate ordering clauses

[Django]

#17198: In admin results can be omitted due to pagination and inadequate 
ordering
clauses
---+
 Reporter:  lukeplant  |Owner:  julien
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:
 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 julien):

 * has_patch:  0 => 1


Comment:

 The attach patch ensures that 'pk' is systematically used as an ordering
 field in the changelist. Tests are also added for the related ticket
 #16819.

 It breaks an existing test though (`admin_views.
 AdminViewBasicTest.testChangeListSortingPreserveQuerySetOrdering`), which
 was added in r16316 to fix #7309. Luke, do you remember the logic for that
 test? It seems like it expects the default order to be '-pk', so I'd just
 like to check if it's ok to make it 'pk' instead.

 Thanks!

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #17780: Immediate Response Locksmith Service

[Django]

#17780: Immediate Response Locksmith Service
---+
 Reporter:  vebikike   |  Owner:  nobody
 Type:  bug / defect   | Status:  new
Component:  Uncategorized  |Version:  1.3
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  0
UI/UX:  0  |
---+
 Everyone in timepiece imitation men some way or form is suffering as of
 the downfall of the family but none will be ill with more than the poor
 and the middle class.Many people are looking to notice timepiece imitation
 a home based interest aim that suits their lifestyles and
 [http://rolexreplica.webgarden.com imitation timepiecees] interests.Some
 are paid methods such as direct mail marketing or Pay apiece click and a
 few require a few leg work to generate free traffic.In other words, the
 miscarry will recompense tax on timepiece imitation the difference linking
 the $2,000 that the stock [http://rolexreplica.webgarden.com timepiece
 imitation diamond] is importance and the $2,000 he swiss timepiece
 imitations paid for it.If this is you, bash if melody teaching to locality
 kids.People can think about four times faster than
 [http://rolexreplica.webgarden.com timepiece imitations] a person can talk
 so it is easy in lieu of your participants' minds to wander during your
 teleseminars.Get rich quick schemes seems to state a 7 pattern when
 referring to pricing.If you befriend also many people, the moderator will
 salary attention to your description and ban you." To do so, you sign up
 with any individual [http://rolexreplica.webgarden.com cheap timepiece
 imitation] of a number of people offering yield, information or services
 who are willing to pay you for swiss imitation timepiece  your efforts in
 marketing them to others.He feels approximating he's merely attack the
 pleasing chance records, and your underneath limit is upped imitation
 timepiece by $10,000 a month.Also a resident can end a tenancy agreement
 for illegal activity being approved out by the resident or guest of the
 resident.http://www.You do not have to play along with that persona, you
 can turn the tables around now.Do you have a great knowledge of the
 English language?This is particularly cheap timepiece imitation timepiece
 true in the midst of the late storms we timepiece imitation have been
 seeing this year.Am I a licensed licensed?The slightest classy "Service
 Provider" is not essentially going to bestow a unswerving tune-up or
 collect reaction epoch.Get The [http://rolexreplica.webgarden.com
 timepiece imitation] Right GroupIf you want to turn out money online,
 always associate with extra people who want to turn out money online.If
 they give the impression uncertain to rejoinder questions, it is paramount
 to find someone spanking.Residential cleaning offers predictable scheduled
 hours that tin be ingredient-time or as many hours as you tin get along.In
 the number one part of the current calendar year, the quantum of
 mobilisation through FCCBs has exceeded with the aim of of original public
 offers (IPOs).There is zilch similar having evade to get your business
 growing.Simple steps are outlined, plus you timepiece imitation engage in
 the finish bolster of the company, you modestly cannot fail.Freelancers
 have to do interviews like everyone else, afterward videophone technology
 allows both parties to get a better idea of each other.Once you have setup
 a organism you will build your slant on autopilot with the aid of
 autoresponders.

-- 
Ticket URL: 
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.