[Django] #9654: `list_display_links` does not respect an empty tuple.

[Django]

#9654: `list_display_links` does not respect an empty tuple.
--+-
 Reporter:  mdh   |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  django.contrib.admin  | Version:  1.0   
 Keywords:|   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 The admin's change list page will link the first column to the change page
 for each item even if you explicitly specify an empty tuple as the value
 of `list_display_links`.  Although it is unusual not to want any of the
 columns to link to the default change page, this can come up if you are
 using other extensions to the admin to build a custom interface for a
 given model.  The underlying issue is very easy to address: it arises
 because the admin uses an empty tuple as the default value, when it could
 just as easily have used `None` as the default value instead.

 I've attached a simple patch.  It's not obvious to me how to test this
 with the test fixtures currently available, so I haven't written any
 tests.  If people like this but think it needs tests and can give me a
 hint about how to approach them I'd be happy to write them.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #2782: mod_python's request.META["SERVER_PORT"] is always set to 0

[Django]

#2782: mod_python's request.META["SERVER_PORT"] is always set to 0
-+--
  Reporter:  anonymous   | Owner:  adrian
Status:  reopened| Milestone:
 Component:  Core framework  |   Version:
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by kmtracey):

 Malcolm, OK, so I was going to re-commit the old fix, but I tested it
 first, with this little test view I had used earlier:

 {{{
 #!python
 def portno(request):
 return HttpResponse("Port number in request is %d" %
 request.META["SERVER_PORT"])
 }}}

 This fails (!TypeError) with the previously-applied fix because it casts
 to a str for consistency with the other headers.  However until now this
 particular header has been an int, so I think it now needs to stay that
 way?  Or because till now it has been mostly useless (except on this
 Windows machine I've got where the old code does report the real port
 number) are we OK changing the type?  I'm tending to think not, and that
 we need to keep the same type it has been so far...but wondering if you
 have a different opinion?

 (And I'd be interested in one of you magic crystal balls that reports
 who's who when posting anonymously...)

-- 
Ticket URL: 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #2782: mod_python's request.META["SERVER_PORT"] is always set to 0

[Django]

#2782: mod_python's request.META["SERVER_PORT"] is always set to 0
-+--
  Reporter:  anonymous   | Owner:  adrian
Status:  reopened| Milestone:
 Component:  Core framework  |   Version:
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by mtredinnick):

 Err ... #2865, not #2685, but you get the idea.

-- 
Ticket URL: 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #2782: mod_python's request.META["SERVER_PORT"] is always set to 0

[Django]

#2782: mod_python's request.META["SERVER_PORT"] is always set to 0
-+--
  Reporter:  anonymous   | Owner:  adrian
Status:  reopened| Milestone:
 Component:  Core framework  |   Version:
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by mtredinnick):

  * stage:  Unreviewed => Accepted

Comment:

 karen: the previous anonymous comment was ymasuda, who was the guy who
 reported #2685. He gave it a quick check with a current mod_python on his
 Mac. So whether you get to it first, or I do, doesn't matter. But I want
 to commit this. It's necessary for constructing the full URL.

-- 
Ticket URL: 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9645: Documentation generated with docutils 0.4 has broken css due to broken ids

[Django]

#9645: Documentation generated with docutils 0.4 has broken css due to broken 
ids
+---
  Reporter:  waltercruz | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by mtredinnick):

 So, I've confirmed that the problem doesn't occur for me with the vanilla
 docutils-0.4 tarball (in fact, there's no significant different between
 that and what Fedora 8 ships). So it's not docutils doing this.

 What version of Sphinx are you using to generate the documentation?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #2782: mod_python's request.META["SERVER_PORT"] is always set to 0

[Django]

#2782: mod_python's request.META["SERVER_PORT"] is always set to 0
-+--
  Reporter:  anonymous   | Owner:  adrian
Status:  reopened| Milestone:
 Component:  Core framework  |   Version:
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by kmtracey):

 Interesting.  The problem is not recreatable on the first box I tried (a
 Windows test box).  It's running Apache/2.2.8 (Win32) mod_python/3.3.1
 Python/2.5.2, and the current SVN code correctly sets the port number.
 Since the doc referenced mentions Apache 2.0, I figured it was fixed by
 Apache 2.2.  However after you reported seeing port 0 returned on Apache
 2.2.8, I tried it on my Linux box, running Apache/2.2.4 (Ubuntu)
 mod_python/3.3.1 Python/2.5.1 and sure enough it reports port 0 with the
 current code.  So it seems more common than not (granted based on an
 unscientific 3-random-machine test) that the existing code doesn't work.
 In neither case I tried did the patch code cause any problem, so I'm
 inclined to put it back in.

-- 
Ticket URL: 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9645: Documentation generated with docutils 0.4 has broken css due to broken ids

[Django]

#9645: Documentation generated with docutils 0.4 has broken css due to broken 
ids
+---
  Reporter:  waltercruz | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by mtredinnick):

 I'm not about to run "easy_install" anything on my system, but I'd
 forgotten it might be hanging around on PyPI. I grabbed the tarball from
 there and will see what washes out. 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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9645: Documentation generated with docutils 0.4 has broken css due to broken ids

[Django]

#9645: Documentation generated with docutils 0.4 has broken css due to broken 
ids
+---
  Reporter:  waltercruz | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by waltercruz):

 You can install docutils 0.4 using easy_install easy_install docutils==0.4
 . You can do it in a virtualenv. How can I send you more docs and tests ?
 What kind of docs and tests do you need?

-- 
Ticket URL: 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9645: Documentation generated with docutils 0.4 has broken css due to broken ids

[Django]

#9645: Documentation generated with docutils 0.4 has broken css due to broken 
ids
+---
  Reporter:  waltercruz | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by mtredinnick):

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

Comment:

 I cannot repeat this problem with docutils-0.4, at least as installed on
 my system (and it doesn't look like Fedora have made any significant
 patches that will have changed). Sadly, the docutils page at sourceforge
 doesn't seem to provide any way to download the vanilla 0.4 tarball, so I
 can't confirm it one way or the other.

 I think this might turn out to be a case of "we can't support everything",
 but it would be nice to know why somebody is seeing an issue with 0.4 and
 somebody else (me) isn't.

-- 
Ticket URL: 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9648: Admin extrastyle template block wrapped in [ifIE] css condition

[Django]

#9648: Admin extrastyle template block wrapped in [ifIE] css condition
--+-
  Reporter:  anonymous| Owner:  wilson  

Status:  new  | Milestone:  post-1.0

 Component:  Template system  |   Version:  SVN 

Resolution:   |  Keywords:  css, block, admin, 
templates
 Stage:  Unreviewed   | Has_patch:  0   

Needs_docs:  0|   Needs_tests:  0   

Needs_better_patch:  0|  
--+-
Changes (by mtredinnick):

  * owner:  nobody => wilson
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * needs_docs:  => 0

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9653: Add a runservercp command which uses cherrypy as the main server (allows for multiple threads)

[Django]

#9653: Add a runservercp command which uses cherrypy as the main server (allows
for multiple threads)
--+-
  Reporter:  [EMAIL PROTECTED]  | Owner:  nobody
Status:  closed   | Milestone:
 Component:  Uncategorized|   Version:  1.0   
Resolution:  wontfix  |  Keywords:
 Stage:  Unreviewed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by russellm):

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

Comment:

 Tarken: Good guess :-)

 While this is a reasonable solution for the particular problem you have
 posed, it's a niche problem, and we're not going to add a dependency on
 CherryPy to the Django core in order to solve a niche problem.

 However, I heartily encourage you to publish this as a snippet or maintain
 it as an external application.

-- 
Ticket URL: 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r9509 - django/trunk/django/conf/locale/da/LC_MESSAGES

[noreply]

Author: kmtracey
Date: 2008-11-20 17:07:50 -0600 (Thu, 20 Nov 2008)
New Revision: 9509

Modified:
   django/trunk/django/conf/locale/da/LC_MESSAGES/django.mo
   django/trunk/django/conf/locale/da/LC_MESSAGES/django.po
Log:
Fixed #8612 -- Bug-fxing Danish translation update.  Same patch as r9491 on 
1.0.X branch.


Modified: django/trunk/django/conf/locale/da/LC_MESSAGES/django.mo
===
(Binary files differ)

Modified: django/trunk/django/conf/locale/da/LC_MESSAGES/django.po
===
--- django/trunk/django/conf/locale/da/LC_MESSAGES/django.po2008-11-20 
19:02:17 UTC (rev 9508)
+++ django/trunk/django/conf/locale/da/LC_MESSAGES/django.po2008-11-20 
23:07:50 UTC (rev 9509)
@@ -6,7 +6,7 @@
 msgstr ""
 "Project-Id-Version: Django 1.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2008-11-05 21:55+0100\n"
+"POT-Creation-Date: 2008-11-16 20:27+0100\n"
 "PO-Revision-Date: 2008-11-07 20:41+0200\n"
 "Last-Translator: Finn Gruwier Larsen<[EMAIL PROTECTED]>\n"
 "Language-Team: \n"
@@ -99,114 +99,122 @@
 msgstr "Hebræisk"
 
 #: conf/global_settings.py:65
+msgid "Hindi"
+msgstr "Hindi"
+
+#: conf/global_settings.py:66
 msgid "Croatian"
 msgstr "Kroatisk"
 
-#: conf/global_settings.py:66
+#: conf/global_settings.py:67
 msgid "Icelandic"
 msgstr "Islandsk"
 
-#: conf/global_settings.py:67
+#: conf/global_settings.py:68
 msgid "Italian"
 msgstr "Italiensk"
 
-#: conf/global_settings.py:68
+#: conf/global_settings.py:69
 msgid "Japanese"
 msgstr "Japansk"
 
-#: conf/global_settings.py:69
+#: conf/global_settings.py:70
 msgid "Georgian"
 msgstr "Georgisk"
 
-#: conf/global_settings.py:70
+#: conf/global_settings.py:71
 msgid "Korean"
 msgstr "Koreansk"
 
-#: conf/global_settings.py:71
+#: conf/global_settings.py:72
 msgid "Khmer"
 msgstr "Khmer"
 
-#: conf/global_settings.py:72
+#: conf/global_settings.py:73
 msgid "Kannada"
 msgstr "Kannada"
 
-#: conf/global_settings.py:73
+#: conf/global_settings.py:74
 msgid "Latvian"
 msgstr "Lettisk"
 
-#: conf/global_settings.py:74
+#: conf/global_settings.py:75
 msgid "Lithuanian"
 msgstr "Litauisk"
 
-#: conf/global_settings.py:75
+#: conf/global_settings.py:76
 msgid "Macedonian"
 msgstr "Makedonsk"
 
-#: conf/global_settings.py:76
+#: conf/global_settings.py:77
 msgid "Dutch"
 msgstr "Hollandsk"
 
-#: conf/global_settings.py:77
+#: conf/global_settings.py:78
 msgid "Norwegian"
 msgstr "Norsk"
 
-#: conf/global_settings.py:78
+#: conf/global_settings.py:79
 msgid "Polish"
 msgstr "Polsk"
 
-#: conf/global_settings.py:79
+#: conf/global_settings.py:80
 msgid "Portuguese"
 msgstr "Portugisisk"
 
-#: conf/global_settings.py:80
+#: conf/global_settings.py:81
 msgid "Brazilian Portuguese"
 msgstr "Brasiliansk portugisisk"
 
-#: conf/global_settings.py:81
+#: conf/global_settings.py:82
 msgid "Romanian"
 msgstr "Rumænsk"
 
-#: conf/global_settings.py:82
+#: conf/global_settings.py:83
 msgid "Russian"
 msgstr "Russisk"
 
-#: conf/global_settings.py:83
+#: conf/global_settings.py:84
 msgid "Slovak"
 msgstr "Slovakisk"
 
-#: conf/global_settings.py:84
+#: conf/global_settings.py:85
 msgid "Slovenian"
 msgstr "Slovensk"
 
-#: conf/global_settings.py:85
+#: conf/global_settings.py:86
 msgid "Serbian"
 msgstr "Serbisk"
 
-#: conf/global_settings.py:86
+#: conf/global_settings.py:87
 msgid "Swedish"
 msgstr "Svensk"
 
-#: conf/global_settings.py:87
+#: conf/global_settings.py:88
 msgid "Tamil"
 msgstr "Tamil"
 
-#: conf/global_settings.py:88
+#: conf/global_settings.py:89
 msgid "Telugu"
 msgstr "Telugu"
 
-#: conf/global_settings.py:89
+#: conf/global_settings.py:90
+msgid "Thai"
+msgstr "Thai"
+
+#: conf/global_settings.py:91
 msgid "Turkish"
 msgstr "Tyrkisk"
 
-#: conf/global_settings.py:90
+#: conf/global_settings.py:92
 msgid "Ukrainian"
 msgstr "Ukrainsk"
 
-#: conf/global_settings.py:91
+#: conf/global_settings.py:93
 msgid "Simplified Chinese"
 msgstr "Forenklet kinesisk"
 
-#: conf/global_settings.py:92
+#: conf/global_settings.py:94
 msgid "Traditional Chinese"
 msgstr "Traditionelt kinesisk"
 
@@ -348,6 +356,11 @@
 msgid "Add %s"
 msgstr "Tilføj %s"
 
+#: contrib/admin/options.py:559 contrib/admin/options.py:673
+#, python-format
+msgid "%(name)s object with primary key %(key)r does not exist."
+msgstr "Der findes ikke et %(name)s-objekt med primærnøgle %(key)r."
+
 #: contrib/admin/options.py:606
 #, python-format
 msgid "Change %s"
@@ -462,7 +475,7 @@
 
 #: contrib/admin/templates/admin/500.html:4
 #: contrib/admin/templates/admin/app_index.html:8
-#: contrib/admin/templates/admin/base.html:31
+#: contrib/admin/templates/admin/base.html:33
 #: contrib/admin/templates/admin/change_form.html:17
 #: contrib/admin/templates/admin/change_list.html:8
 #: contrib/admin/templates/admin/delete_confirmation.html:6
@@ -506,18 +519,18 @@
 msgid "%(name)s"
 msgstr "%(name)s"
 
-#: contrib/admin/templates/admin/base.html:26
+#: contrib/admin/templates/admin/bas

Re: [Django] #9653: Add a runservercp command which uses cherrypy as the main server (allows for multiple threads)

[Django]

#9653: Add a runservercp command which uses cherrypy as the main server (allows
for multiple threads)
--+-
  Reporter:  [EMAIL PROTECTED]  | Owner:  nobody
Status:  new  | Milestone:
 Component:  Uncategorized|   Version:  1.0   
Resolution:   |  Keywords:
 Stage:  Unreviewed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by Tarken):

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

Comment:

 I'm going to guess that this ticket is going to be a wontfix.

 For recent discussion of multi-threaded operation, see ticket:3357 and
 http://groups.google.com/group/django-
 developers/browse_thread/thread/442b00303f6b4fb5

-- 
Ticket URL: 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9653: Add a runservercp command which uses cherrypy as the main server (allows for multiple threads)

[Django]

#9653: Add a runservercp command which uses cherrypy as the main server (allows
for multiple threads)
-+--
 Reporter:  [EMAIL PROTECTED]  |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Uncategorized| Version:  1.0   
 Keywords:   |   Stage:  Unreviewed
Has_patch:  1|  
-+--
 Stuff like: http://www.djangosnippets.org/snippets/999/ can't be tested on
 the development server cause the main development server is single
 threaded.  CherryPy provides a production ready wsgiserver that is written
 in complete python and is a great alternative to the built in one.

 This is a patch for a runservercp which takes the same arguments as the
 main development server.

-- 
Ticket URL: 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9652: base.css is not loaded in admin index.html

[Django]

#9652: base.css is not loaded in admin index.html
---+
  Reporter:  zhaoz | Owner:  nobody
Status:  closed| Milestone:
 Component:  django.contrib.admin  |   Version:  1.0   
Resolution:  invalid   |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by kmtracey):

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

Comment:

 I don't understand.  dashboard.css on the 1.0.X branch (and in the 1.0.2
 release) hasn't changed in 3 years and does import base.css:

 
http://code.djangoproject.com/browser/django/tags/releases/1.0.2/django/contrib/admin/media/css/dashboard.css

 None of the css reorganization that has been done recently has been
 backported to the 1.0.X branch, as it is not strictly bug-fixing.  It
 rather sounds like you have installed 1.0.2 on top of a trunk checkout or
 something, and so have a mishmash of both.

-- 
Ticket URL: 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9652: base.css is not loaded in admin index.html

[Django]

#9652: base.css is not loaded in admin index.html
--+-
 Reporter:  zhaoz |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  django.contrib.admin  | Version:  1.0   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Due to change in
 [source:django/trunk/contrib/admin/media/css/dashboard.css#9463] base.css
 is no longer being imported in dashboard.css.

 However,
 
[source:django/tags/releases/1.0.2/django/contrib/admin/templates/admin/index.html]
 overrides stylesheet instead of extrastyle.

 This is fixed in trunk, but the relased 1.0.2 version has this bug.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r9508 - django/branches/releases/1.0.X/django/contrib/admin/views

[noreply]

Author: ubernostrum
Date: 2008-11-20 13:02:17 -0600 (Thu, 20 Nov 2008)
New Revision: 9508

Modified:
   django/branches/releases/1.0.X/django/contrib/admin/views/main.py
Log:
[1.0.X] OneToOne? filtering should only apply in a popup selection from the 
related model. This was [9507] in trunk.


Modified: django/branches/releases/1.0.X/django/contrib/admin/views/main.py
===
--- django/branches/releases/1.0.X/django/contrib/admin/views/main.py   
2008-11-20 19:01:40 UTC (rev 9507)
+++ django/branches/releases/1.0.X/django/contrib/admin/views/main.py   
2008-11-20 19:02:17 UTC (rev 9508)
@@ -237,7 +237,7 @@
 qs = qs.distinct()
 break
 
-if self.opts.one_to_one_field:
+if self.is_popup and self.opts.one_to_one_field:
 qs = 
qs.complex_filter(self.opts.one_to_one_field.rel.limit_choices_to)
 
 return qs


--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r9507 - django/trunk/django/contrib/admin/views

[noreply]

Author: ubernostrum
Date: 2008-11-20 13:01:40 -0600 (Thu, 20 Nov 2008)
New Revision: 9507

Modified:
   django/trunk/django/contrib/admin/views/main.py
Log:
OneToOne filtering should only apply in a popup selection from the related 
model.


Modified: django/trunk/django/contrib/admin/views/main.py
===
--- django/trunk/django/contrib/admin/views/main.py 2008-11-19 16:24:11 UTC 
(rev 9506)
+++ django/trunk/django/contrib/admin/views/main.py 2008-11-20 19:01:40 UTC 
(rev 9507)
@@ -237,7 +237,7 @@
 qs = qs.distinct()
 break
 
-if self.opts.one_to_one_field:
+if self.is_popup and self.opts.one_to_one_field:
 qs = 
qs.complex_filter(self.opts.one_to_one_field.rel.limit_choices_to)
 
 return qs


--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9651: [9297] breaks save_as in inline admin forms

[Django]

#9651: [9297] breaks save_as in inline admin forms
---+
  Reporter:  yamad | Owner:  nobody  
Status:  new   | Milestone:  post-1.0
 Component:  django.contrib.admin  |   Version:  
Resolution:|  Keywords:  
 Stage:  Unreviewed| Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by yamad):

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

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9651: [9297] breaks save_as in inline admin forms

[Django]

#9651: [9297] breaks save_as in inline admin forms
--+-
 Reporter:  yamad |   Owner:  nobody
   Status:  new   |   Milestone:  post-1.0  
Component:  django.contrib.admin  | Version:
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Changeset [9297] seems to have done something much like ticket #5828 back
 from newforms-admin, but only for save_as.  All inline forms are required
 when using the "Save as New" option.

 Using [9296] allows save_as to work.

-- 
Ticket URL: 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9649: [bug] invalid attribute value passed form model constructor

[Django]

#9649: [bug] invalid attribute value passed form model constructor
---+
  Reporter:  ales_zoulek   | Owner:  nobody 
 
Status:  new   | Milestone: 
 
 Component:  Database layer (models, ORM)  |   Version:  1.0
 
Resolution:|  Keywords:  bug model 
orm foreignkey
 Stage:  Unreviewed| Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by iky <[EMAIL PROTECTED]>):

 * cc: [EMAIL PROTECTED] (added)
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 Validating of assigned values should be done by Filed, not by a Model

 Alternative solution:
 {{{
 +++ django/db/models/base.py(working copy)
 @@ -224,7 +224,7 @@
  # keywords, or default.

  for field in fields_iter:
 -rel_obj = None
 +rel_obj = False
  if kwargs:
  if isinstance(field.rel, ManyToOneRel):
  try:
 @@ -249,7 +249,7 @@
  # instead of field.attname (e.g. "user" instead of "user_id")
 so
  # that the object gets properly cached (and type checked) by
 the
  # RelatedObjectDescriptor.
 -if rel_obj:
 +if rel_obj is not False:
  setattr(self, field.name, rel_obj)
  else:
  setattr(self, field.attname, val)
 }}}

 Then:

 {{{
 In [2]: models.AModel(b=23.0, c=None).c_id
 ---
 ValueErrorTraceback (most recent call
 last)

 ... in ()

 ...django/django/db/models/base.pyc in __init__(self, *args, **kwargs)
 251 # RelatedObjectDescriptor.
 252 if rel_obj is not False:
 --> 253 setattr(self, field.name, rel_obj)
 254 else:
 255 setattr(self, field.attname, val)

 ...django/django/db/models/fields/related.pyc in __set__(self, instance,
 value)
 259 if value is None and self.field.null == False:
 260 raise ValueError('Cannot assign None: "%s.%s" does not
 allow null values.' %
 --> 261 (instance._meta.object_name,
 self.field.name))
 262 elif value is not None and not isinstance(value,
 self.field.rel.to):
 263 raise ValueError('Cannot assign "%r": "%s.%s" must be
 a "%s" instance.' %

 ValueError: Cannot assign None: "AModel.c" does not allow null values.
 }}}

-- 
Ticket URL: 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9650: Initial value for CharField primary key is not hidden in admin's inline form

[Django]

#9650: Initial value for CharField primary key is not hidden in admin's inline
form
--+-
 Reporter:  Tarken|   Owner:  nobody
   Status:  new   |   Milestone:
Component:  django.contrib.admin  | Version:  1.0   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Given the following:

 {{{
 #!python
 from django.db import models
 from django.contrib import admin

 class Client(models.Model):
 client_name = models.CharField(max_length=255)

 class ClientDomain(models.Model):
 domain_name = models.CharField(max_length=255, primary_key=True)
 client = models.ForeignKey(Client)

 class DomainInline(admin.TabularInline):
 model = ClientDomain
 extra = 1

 class ClientAdmin(admin.ModelAdmin):
 inlines = (DomainInline,)

 admin.site.register(Client, ClientAdmin)
 }}}

 The following HTML is generated in the "extra" inline:
 {{{
 #!text/html
 
   
   
 
 
   
 
 }}}

 And for existing record inlines:
 {{{
 #!text/html
 
   localhost
   
   
 
 
   
 
 }}}

 I am using the 1.0.X SVN branch.

-- 
Ticket URL: 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9638: Add %(app_label)s to the related_name format string for abstract models

[Django]

#9638: Add %(app_label)s to the related_name format string for abstract models
--+-
  Reporter:  [EMAIL PROTECTED]  | Owner:  anonymous
Status:  assigned | Milestone:  
 
 Component:  Core framework   |   Version:  1.0 
 
Resolution:   |  Keywords:  
 
 Stage:  Accepted | Has_patch:  1   
 
Needs_docs:  0|   Needs_tests:  0   
 
Needs_better_patch:  0|  
--+-
Changes (by [EMAIL PROTECTED]):

  * owner:  nobody => anonymous
  * needs_better_patch:  1 => 0
  * status:  new => assigned
  * needs_tests:  1 => 0
  * needs_docs:  1 => 0

Comment:

 Here is an updated patch that adds tests and documentation for the
 feature.  I ran the tests with an sqlite database and they all passed.   I
 also ran them on a mysql database (the only other database that I happened
 to have installed) and I got some failures:

 {{{
 [EMAIL PROTECTED]:~/Projects/django/trunk/tests$ python runtests.py
 --settings mysql_settings
 
/home/lakin/Projects/django/trunk/tests/regressiontests/templates/loaders.py:14:
 UserWarning: Module _mysql was already imported from /var/lib/python-
 support/python2.5/_mysql.so, but /var/lib/python-support/python2.5 is
 being added to sys.path
   import pkg_resources
 /home/lakin/Projects/django/trunk/django/db/backends/mysql/base.py:83:
 Warning: Incorrect string value: '\xE6\x9E\x97\xE5\x8E\x9F...' for column
 'headline' at row 1
   return self.cursor.execute(query, args)
 /home/lakin/Projects/django/trunk/django/db/backends/mysql/base.py:83:
 Warning: Incorrect datetime value: '2005%' for column 'pub_date' at row 1
   return self.cursor.execute(query, args)
 /home/lakin/Projects/django/trunk/django/db/backends/mysql/base.py:83:
 Warning: Incorrect string value: '\xE6\x88\x91\xE9\x9A\xBB...' for column
 'file' at row 1
   return self.cursor.execute(query, args)
 ==
 FAIL: Doctest: modeltests.serializers.models.__test__.API_TESTS
 --
 Traceback (most recent call last):
   File "/home/lakin/Projects/django/trunk/django/test/_doctest.py", line
 2180, in runTest
 raise self.failureException(self.format_failure(new.getvalue()))
 AssertionError: Failed doctest test for
 modeltests.serializers.models.__test__.API_TESTS
   File
 "/home/lakin/Projects/django/trunk/tests/modeltests/serializers/models.py",
 line unknown line number, in API_TESTS

 --
 File
 "/home/lakin/Projects/django/trunk/tests/modeltests/serializers/models.py",
 line ?, in modeltests.serializers.models.__test__.API_TESTS
 Failed example:
 ac.save(); mv.save()
 Exception raised:
 Traceback (most recent call last):
   File "/home/lakin/Projects/django/trunk/django/test/_doctest.py",
 line 1267, in __run
 compileflags, 1) in test.globs
   File "", line 1, in
 
 ac.save(); mv.save()
   File "/home/lakin/Projects/django/trunk/django/db/models/base.py",
 line 311, in save
 self.save_base(force_insert=force_insert,
 force_update=force_update)
   File "/home/lakin/Projects/django/trunk/django/db/models/base.py",
 line 358, in save_base
 manager.filter(pk=pk_val).extra(select={'a':
 1}).values('a').order_by())):
   File "/home/lakin/Projects/django/trunk/django/db/models/query.py",
 line 191, in __nonzero__
 iter(self).next()
   File "/home/lakin/Projects/django/trunk/django/db/models/query.py",
 line 185, in _result_iter
 self._fill_cache()
   File "/home/lakin/Projects/django/trunk/django/db/models/query.py",
 line 618, in _fill_cache
 self._result_cache.append(self._iter.next())
   File "/home/lakin/Projects/django/trunk/django/db/models/query.py",
 line 659, in iterator
 for row in self.query.results_iter():
   File
 "/home/lakin/Projects/django/trunk/django/db/models/sql/query.py", line
 206, in results_iter
 for rows in self.execute_sql(MULTI):
   File
 "/home/lakin/Projects/django/trunk/django/db/models/sql/query.py", line
 1734, in execute_sql
 cursor.execute(sql, params)
   File
 "/home/lakin/Projects/django/trunk/django/db/backends/mysql/base.py", line
 83, in execute
 return self.cursor.execute(query, args)
   File "/var/lib/python-support/python2.5/MySQLdb/cursors.py", line
 166, in execute
 self.errorhandler(self, exc, value)
   File "/var/lib/python-support/python2.5/MySQLdb/connections.py",
 line 35, in defaulterrorhandler
 raise errorclass, errorvalue
 Operation

Re: [Django] #9644: Cache miss (maybe locmem cache backend is not thread-safe?)

[Django]

#9644: Cache miss (maybe locmem cache backend is not thread-safe?)
---+
  Reporter:  pihentagy | Owner:  nobody 
  
Status:  new   | Milestone: 
  
 Component:  Cache system  |   Version:  1.0
  
Resolution:|  Keywords:  thread safe, cache, 
exception
 Stage:  Unreviewed| Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by pihentagy):

  * keywords:  thread safe, cache, 404, not found => thread safe, cache,
   exception

Comment:

 Thanks for the fix.

 (I feared to peak in to the source, but that was an easy fix)

-- 
Ticket URL: 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9207: Failing test code when using contenttypes app.

[Django]

#9207: Failing test code when using contenttypes app.
+---
  Reporter:  oliverandrich  | Owner:  nobody
Status:  new| Milestone:
 Component:  Contrib apps   |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by aball):

 It turns out that what I was seeing seemed to be due to my running {{{
 python manage.py sqlflush | python manage.py dbshell }}} instead of {{{
 python manage.py flush --noinput --verbosity=0 }}} in unittests that I run
 via RPC to a running Django instance (not run by {{{ python manage.py test
 }}}).  Using {{{ sqlflush }}} instead of {{{ flush }}} probably caused the
 post_syncdb hook for the contenttypes app to not get invoked, caching the
 contenttype cache to not be cleared.  Things work fine if I use the {{{
 flush }}} command instead.

 Replying to [comment:6 aball]:
 > I'm seeing this also with MySQL and two custom apps installed with only
 the contenttypes app.
 >
 > Replying to [comment:5 mattgrayson]:
 > > I'm getting the same kind of error, but not involving the auth module.
 Workaround does not work for me.
 > >
 > > Tried stripping down the installed apps to just contenttypes and the
 single app using contenttypes.
 > >
 > > When tests run I get errors like:
 > >
 > > {{{
 > > IntegrityError: (1452, 'Cannot add or update a child row: a foreign
 key constraint fails (`test_libsite/ems_link`,
 > > CONSTRAINT `content_type_id_refs_id_47084aec` FOREIGN KEY
 (`content_type_id`) REFERENCES `django_content_type` (`id`))')
 > > }}}

-- 
Ticket URL: 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9649: [bug] invalid attribute value passed form model constructor

[Django]

#9649: [bug] invalid attribute value passed form model constructor
--+-
 Reporter:  ales_zoulek   |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  1.0   
 Keywords:  bug model orm foreignkey  |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 '''How to simulate'''


 models.py
 {{{
 from django.db import models


 class CModel(models.Model):
 x = models.CharField(max_length=20)

 def __unicode__(self):
 return self.x


 class AModel(models.Model):
 a = models.FloatField()
 b = models.FloatField()
 c = models.ForeignKey(CModel)

 def __unicode__(self):
 return u"%s" % self.a

 }}}
 shell:
 {{{
 In [1]: from t.a import models

 In [2]: models.AModel(a=23.0, c=None).c_id

 In [3]: models.AModel(b=23.0, c=None).c_id
 Out[3]: 23.0

 }}}

 '''Reason'''


 Invalid if clause in django/db/models/base.py:242

 When rel_obj is set to None, but field.null is set to False, the 'val'
 variable is NOT set in the whole FOR-cycle and thus the previous value
 gets used.

 '''Solution'''

 insead of:
 {{{
 242 if rel_obj is None and field.null:
 243 val = None
 }}}
 there should be:
 {{{
 242 if rel_obj is None:
 243 val = None
 244 if not field.null:
 245 raise TypeError, "Attribute %s could
 not be null" % field.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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9207: Failing test code when using contenttypes app.

[Django]

#9207: Failing test code when using contenttypes app.
+---
  Reporter:  oliverandrich  | Owner:  nobody
Status:  new| Milestone:
 Component:  Contrib apps   |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by aball):

 * cc: [EMAIL PROTECTED] (added)

Comment:

 I'm seeing this also with MySQL and two custom apps installed with only
 the contenttypes app.

 Replying to [comment:5 mattgrayson]:
 > I'm getting the same kind of error, but not involving the auth module.
 Workaround does not work for me.
 >
 > Tried stripping down the installed apps to just contenttypes and the
 single app using contenttypes.
 >
 > When tests run I get errors like:
 >
 > {{{
 > IntegrityError: (1452, 'Cannot add or update a child row: a foreign key
 constraint fails (`test_libsite/ems_link`,
 > CONSTRAINT `content_type_id_refs_id_47084aec` FOREIGN KEY
 (`content_type_id`) REFERENCES `django_content_type` (`id`))')
 > }}}

-- 
Ticket URL: 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9648: Admin extrastyle template block wrapped in [ifIE] css condition

[Django]

#9648: Admin extrastyle template block wrapped in [ifIE] css condition
--+-
 Reporter:  anonymous |   Owner:  nobody
   Status:  new   |   Milestone:  post-1.0  
Component:  Template system   | Version:  SVN   
 Keywords:  css, block, admin, templates  |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 I just upgraded a site from 1.0 to 1.1 pre-alpha SVN-9506 and noticed my
 admin css is bonked.

 It appears that the most recent admin/base.html now places the {% block
 extrastyle %} within an [ifIE] css condition, which is why my css fails on
 all other browsers when I override the base_site.html found in the
 /contrib/admin/templates directory

 I have moved to using {% block extreahead %} instead but just wanted to
 throw the ticket up here in case maybe this was just a miss.

 The solution would be to move the block outside of the [ifIE] condition.

-- 
Ticket URL: 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9644: Cache miss (maybe locmem cache backend is not thread-safe?)

[Django]

#9644: Cache miss (maybe locmem cache backend is not thread-safe?)
---+
  Reporter:  pihentagy | Owner:  nobody 
   
Status:  new   | Milestone: 
   
 Component:  Cache system  |   Version:  1.0
   
Resolution:|  Keywords:  thread safe, cache, 404, 
not found
 Stage:  Unreviewed| Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Comment (by mrts):

 pihentagy, this should fix 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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9644: Cache miss (maybe locmem cache backend is not thread-safe?)

[Django]

#9644: Cache miss (maybe locmem cache backend is not thread-safe?)
---+
  Reporter:  pihentagy | Owner:  nobody 
   
Status:  new   | Milestone: 
   
 Component:  Cache system  |   Version:  1.0
   
Resolution:|  Keywords:  thread safe, cache, 404, 
not found
 Stage:  Unreviewed| Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

  * 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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9644: Cache miss (maybe locmem cache backend is not thread-safe?)

[Django]

#9644: Cache miss (maybe locmem cache backend is not thread-safe?)
---+
  Reporter:  pihentagy | Owner:  nobody 
   
Status:  new   | Milestone: 
   
 Component:  Cache system  |   Version:  1.0
   
Resolution:|  Keywords:  thread safe, cache, 404, 
not found
 Stage:  Unreviewed| Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Comment (by mrts):

 Perhaps the reason lies in lines 58-59, where first a reading lock is
 released and subsequently a writing lock acquired when the value has
 expired. Between these two operations another thread may have deleted the
 key, i.e. the following scenario occurs:

 {{{
 Thread 1: foo = cache.get('foo')
 Thread 1: acquire read lock
  ...
 Thread 1: if expiration > time.time(): False, i.e. value is expired
 Thread 1: release read lock
 Thread 2: foo = cache.get('foo')
 Thread 2: acquire read lock
  ...
 Thread 2: if expiration > time.time(): False, i.e. value is expired
 Thread 2: release read lock
 Thread 2: acquire write lock
 Thread 2: delete key from cache and return
 Thread 1: acquire write lock
 Thread 1: delete key from cache and return --> KeyError
 }}}

-- 
Ticket URL: 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9596: Comparing a DateTimeField to a date is too hard

[Django]

#9596: Comparing a DateTimeField to a date is too hard
---+
  Reporter:  [EMAIL PROTECTED]  | Owner:  nobody
   
Status:  new   | Milestone:  post-1.0   
  
 Component:  Database layer (models, ORM)  |   Version:  SVN
  
Resolution:|  Keywords:  
lookup_type date datetimefield compare comparison query_term field lookup
 Stage:  Unreviewed| Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by zgoda):

 * cc: [EMAIL PROTECTED] (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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #8885: HTML markup appearing in title of doc page

[Django]

#8885: HTML markup appearing in title of doc page
--+-
  Reporter:  gkelly   | Owner:  nobody
Status:  new  | Milestone:
 Component:  Django Web site  |   Version:  1.0   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by ramiro):

 #9647 was also a duplicate, and it suggested:
 {{{
 Maybe a |safe filter is needed to be appended to the title tag to allow
 these characters to be unescaped?
 }}}

-- 
Ticket URL: 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9647: Lots of doc pages have escaped HTML chars in them

[Django]

#9647: Lots of doc pages have escaped HTML chars in them
+---
  Reporter:  anonymous  | Owner:  nobody
Status:  closed | Milestone:
 Component:  Documentation  |   Version:  1.0   
Resolution:  duplicate  |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by ramiro):

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

Comment:

 Duplicate of #8885

-- 
Ticket URL: 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9647: Lots of doc pages have escaped HTML chars in them

[Django]

#9647: Lots of doc pages have escaped HTML chars in them
---+
 Reporter:  anonymous  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Example: http://docs.djangoproject.com/en/dev/ref/contrib/comments/ -- the
 title is "Django’s comments framework".

 Other pages on the docs pages have the same problem in the title.

 Maybe a |safe filter is needed to be appended to the title tag to allow
 these characters to be unescaped?

-- 
Ticket URL: 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #7972: allow argv options anywhere on command line

[Django]

#7972: allow argv options anywhere on command line
--+-
  Reporter:  mukappa  | Owner:  nobody
Status:  closed   | Milestone:
 Component:  django-admin.py  |   Version:  SVN   
Resolution:  invalid  |  Keywords:
 Stage:  Unreviewed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by mukappa):

 Sorry, my brain saw what it wanted to see, not what was there in the
 excerpt from the optparse doc.

 Nonetheless, optparse allows mixing options anywhere between and around
 args, and I'll leave it at 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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #8334: Allow add/create on m2m intermediate tables if all the non-FK fields have defaults or are NULLable

[Django]

#8334: Allow add/create on m2m intermediate tables if all the non-FK fields have
defaults or are NULLable
---+
  Reporter:  pihentagy | Owner:  nobody 
  
Status:  new   | Milestone:  post-1.0   
  
 Component:  Database layer (models, ORM)  |   Version:  SVN
  
Resolution:|  Keywords:  manytomany 
through default add create
 Stage:  Accepted  | Has_patch:  0  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by ales_zoulek):

 * cc: [EMAIL PROTECTED] (added)

Comment:

 I did just a quick workaround. It's far from complete and universal code,
 but it works for me and could help some of you. :)

 {{{
 from django.db.models.fields.related import
 ReverseManyRelatedObjectsDescriptor as
 DjangoReverseManyRelatedObjectsDescriptor
 from django.db import models



 class
 ReverseManyRelatedObjectsDescriptor(DjangoReverseManyRelatedObjectsDescriptor):
 """Partialy supports add method in ManyToManyField with 'through'"""
 def __get__(self, *args, **kwargs):
 manager = super(ReverseManyRelatedObjectsDescriptor,
 self).__get__(*args, **kwargs)
 def add(*objs):
 manager._add_items(manager.source_col_name,
 manager.target_col_name, *objs)
 add.alters_data = True
 manager.add = add
 return manager


 class ManyToManyField(models.ManyToManyField):

 def contribute_to_class(self, cls, name):
 ret = super(ManyToManyField, self).contribute_to_class(cls, name)
 setattr(cls, self.name, ReverseManyRelatedObjectsDescriptor(self))
 return ret

 # Continue with your models here. Use ManyToManyField class where needed.
 class A(models.Model)
 b = ManyToManyField(B, through=AB)

 ...
 }}}

-- 
Ticket URL: 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9646: contrib.admin does app index page does not check ModelAdmin.has_add_permission(request)

[Django]

#9646: contrib.admin does app index page does not check
ModelAdmin.has_add_permission(request)
--+-
 Reporter:  [EMAIL PROTECTED]|   Owner:  nobody
   Status:  new   |   Milestone:
Component:  django.contrib.admin  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 The permission checks implemented in the app index page for contrib admin
 assume that the site is using default Django contrib.auth permssions[1].
 On sites with overridden ModelAdmin.has_add_permission [3] this means that
 the wrong perm string will be checked.

 The proposed patch simply makes AdminSite.app_index do the check in the
 same way as AdminSite.index [2] so that ModelAdmin auth mechanism will be
 invoked.

 [1]:
 
http://code.djangoproject.com/browser/django/trunk/django/contrib/admin/sites.py#L343
 [2]:
 
http://code.djangoproject.com/browser/django/trunk/django/contrib/admin/sites.py#L279
 [3]:
 
http://code.djangoproject.com/browser/django/trunk/django/contrib/admin/options.py#L211

-- 
Ticket URL: 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #399: Bigint field object needed

[Django]

#399: Bigint field object needed
---+
  Reporter:  [EMAIL PROTECTED]| Owner:  permon  

Status:  assigned  | Milestone: 
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  
sprintsept14, bigint
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  1 |  
---+
Changes (by Richard Davies <[EMAIL PROTECTED]>):

 * cc: [EMAIL PROTECTED] (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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9645: Documentation generated with docutils 0.4 has broken css due to broken ids

[Django]

#9645: Documentation generated with docutils 0.4 has broken css due to broken 
ids
---+
 Reporter:  waltercruz |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Hi!

 When generating the django docs with docutils 0.4, some css classes get
 broken. What happens is that docutils -0.5 generate the div ids as "s
 -getting-help" and 0.4 generates these id just as "getting-help". So, some
 minor css get broken when generating css with docutils 0.4. Docutils 0.4
 is still present in a lot of distros.

-- 
Ticket URL: 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #5691: Add the active language to generate the cache key

[Django]

#5691: Add the active language to generate the cache key
-+--
  Reporter:  [EMAIL PROTECTED]  | Owner:  nobody
Status:  new | Milestone:
 Component:  Cache system|   Version:  SVN   
Resolution:  |  Keywords:  cache i18n
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Comment (by aaloy):

 I'm working on a patch which could work as:

 {{{
 cache_key = 'views.decorators.cache.cache_header.%s.%s' % (
   key_prefix, iri_to_uri(request.path))
 if settings.USE_I18N:
cache_key += ".%s" % translation.get_language()
 }}}

 I have tested using other ways of string concatenations and this one is
 the fast way (0.6 s for 10^6 interactions) for the kind of keys we're
 generating.

-- 
Ticket URL: 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #7972: allow argv options anywhere on command line

[Django]

#7972: allow argv options anywhere on command line
--+-
  Reporter:  mukappa  | Owner:  nobody
Status:  closed   | Milestone:
 Component:  django-admin.py  |   Version:  SVN   
Resolution:  invalid  |  Keywords:
 Stage:  Unreviewed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by mukappa):

 from http://www.python.org/doc/2.5.2/lib/module-optparse.html the
 following command lines are all equivalent
 {{{
  -f outfile --quiet
  --quiet --file outfile
  -q -foutfile
  -qfoutfile
 }}}

 I think that implies
 {{{
 $ python manage.py --settings=settings shell
 }}}
 and
 {{{
 $ python manage.py shell --settings=settings
 }}}
 are equivalent.

 but for manage.py (and django-admin.py)
 {{{
 $ python manage.py --settings=settings shell
 Unknown command: '--settings=settings'
 }}}
 manage.py cares where its options are, but I don't see where it needs to.
 I sometimes put an option in the "wrong" place and find it frustrating to
 have to check the usage.

 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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9486: The goal is to make sure the required field's lable be bold

[Django]

#9486: The goal is to make sure the required field's lable be bold
+---
  Reporter:  ctao   | Owner:  nobody  
Status:  closed | Milestone:  post-1.0
 Component:  Uncategorized  |   Version:  1.0 
Resolution:  duplicate  |  Keywords:  
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Old description:

> Here is the svn diff
>
> Index: django/forms/forms.py
> ===
> --- django/forms/forms.py   (revision 9084)
> +++ django/forms/forms.py   (working copy)
> @@ -155,7 +155,13 @@
>  if self.label_suffix:
>  if label[-1] not in ':?.!':
>  label += self.label_suffix
> -label = bf.label_tag(label) or ''
> +
> +attrs = None
> +if bf.field.required:
> +attrs = {'class': 'required'}
> +
> +label = bf.label_tag(label, attrs) or ''
> +
>  else:
>  label = ''
>  if field.help_text:

New description:

 Here is the svn diff
 {{{
 Index: django/forms/forms.py
 ===
 --- django/forms/forms.py   (revision 9084)
 +++ django/forms/forms.py   (working copy)
 @@ -155,7 +155,13 @@
  if self.label_suffix:
  if label[-1] not in ':?.!':
  label += self.label_suffix
 -label = bf.label_tag(label) or ''
 +
 +attrs = None
 +if bf.field.required:
 +attrs = {'class': 'required'}
 +
 +label = bf.label_tag(label, attrs) or ''
 +
  else:
  label = ''
  if field.help_text:
 }}}

Comment (by mtredinnick):

 (Edited description because, due to a Trac bug, it was messing up the
 formatting of the rest of the page.)

-- 
Ticket URL: 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9486: The goal is to make sure the required field's lable be bold

[Django]

#9486: The goal is to make sure the required field's lable be bold
+---
  Reporter:  ctao   | Owner:  nobody  
Status:  closed | Milestone:  post-1.0
 Component:  Uncategorized  |   Version:  1.0 
Resolution:  duplicate  |  Keywords:  
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by mtredinnick):

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

Comment:

 Basically a duplicate of #3512 and #3515 (this is just one specialised
 case of those). One day we'll make a decision about how to handle those
 cases.

-- 
Ticket URL: 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9483: Title template filter is broken

[Django]

#9483: Title template filter is broken
--+-
  Reporter:  hdevries | Owner:  hdevries 
Status:  assigned | Milestone:  post-1.0 
 Component:  Template system  |   Version:  SVN  
Resolution:   |  Keywords:  title template filter
 Stage:  Unreviewed   | Has_patch:  1
Needs_docs:  0|   Needs_tests:  0
Needs_better_patch:  0|  
--+-
Comment (by mtredinnick):

 Why is there a great need to change this. We do what Python at does at the
 moment, which isn't unreasonable. This is an edge-case and whilst it
 doesn't necessarily do what you personally expect, it isn't de-facto wrong
 (normal written text won't have a semi-colon without a space following
 it).

 So, what is the use-case that doesn't work without this change being made?

-- 
Ticket URL: 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9644: Cache miss (maybe locmem cache backend is not thread-safe?)

[Django]

#9644: Cache miss (maybe locmem cache backend is not thread-safe?)
---+
  Reporter:  pihentagy | Owner:  nobody 
   
Status:  new   | Milestone: 
   
 Component:  Cache system  |   Version:  1.0
   
Resolution:|  Keywords:  thread safe, cache, 404, 
not found
 Stage:  Unreviewed| Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * summary:  Cache miss (maybe cache is not thread-safe?) => Cache miss
  (maybe locmem cache backend is not thread-
  safe?)

-- 
Ticket URL: 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9644: Cache miss (maybe cache is not thread-safe?)

[Django]

#9644: Cache miss (maybe cache is not thread-safe?)
---+
  Reporter:  pihentagy | Owner:  nobody 
   
Status:  new   | Milestone: 
   
 Component:  Cache system  |   Version:  1.0
   
Resolution:|  Keywords:  thread safe, cache, 404, 
not found
 Stage:  Unreviewed| Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by pihentagy):

  * needs_better_patch:  => 0
  * summary:  Cache miss (maybe cache is not thread-safe? => Cache miss
  (maybe cache is not thread-safe?)
  * needs_tests:  => 0
  * needs_docs:  => 0

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9644: Cache miss (maybe cache is not thread-safe?

[Django]

#9644: Cache miss (maybe cache is not thread-safe?
+---
 Reporter:  pihentagy   |   Owner:  nobody
   Status:  new |   Milestone:
Component:  Cache system| Version:  1.0   
 Keywords:  thread safe, cache, 404, not found  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 On my site I get errors like the following (4-5 errors per day, the key is
 random).
 Using Django 1.0.

 {{{
 CACHE_BACKEND = 'locmem:///?max_entries=3'
 }}}


 {{{
 Traceback (most recent call last):

   File "/home/profilia/.python/lib/python2.5/site-
 packages/django/core/handlers/base.py", line 86, in get_response

   File "/var/www/profila.hu/www/profila-site-
 wsgi/auction/frontend/views.py", line 250, in toc_item_list
 bookmark=False, request=request,

   File "/home/profilia/.python/lib/python2.5/site-
 packages/django/views/generic/list_detail.py", line 101, in object_list

   File "/home/profilia/.python/lib/python2.5/site-
 packages/django/template/__init__.py", line 176, in render

   File "/home/profilia/.python/lib/python2.5/site-
 packages/django/template/__init__.py", line 768, in render

   File "/home/profilia/.python/lib/python2.5/site-
 packages/django/template/__init__.py", line 781, in render_node

   File "/home/profilia/.python/lib/python2.5/site-
 packages/django/template/loader_tags.py", line 97, in render

   File "/home/profilia/.python/lib/python2.5/site-
 packages/django/template/__init__.py", line 176, in render

   File "/home/profilia/.python/lib/python2.5/site-
 packages/django/template/__init__.py", line 768, in render

   File "/home/profilia/.python/lib/python2.5/site-
 packages/django/template/__init__.py", line 781, in render_node

   File "/home/profilia/.python/lib/python2.5/site-
 packages/django/template/loader_tags.py", line 24, in render

   File "/home/profilia/.python/lib/python2.5/site-
 packages/django/template/__init__.py", line 768, in render

   File "/home/profilia/.python/lib/python2.5/site-
 packages/django/template/__init__.py", line 781, in render_node

   File "/home/profilia/.python/lib/python2.5/site-
 packages/django/template/loader_tags.py", line 111, in render

   File "/home/profilia/.python/lib/python2.5/site-
 packages/django/template/__init__.py", line 176, in render

   File "/home/profilia/.python/lib/python2.5/site-
 packages/django/template/__init__.py", line 768, in render

   File "/home/profilia/.python/lib/python2.5/site-
 packages/django/template/__init__.py", line 781, in render_node

   File "/home/profilia/.python/lib/python2.5/site-
 packages/django/template/defaulttags.py", line 334, in render

   File "/home/profilia/.python/lib/python2.5/site-
 packages/django/template/__init__.py", line 768, in render

   File "/home/profilia/.python/lib/python2.5/site-
 packages/django/template/__init__.py", line 781, in render_node

   File "/home/profilia/.python/lib/python2.5/site-
 packages/django/template/__init__.py", line 925, in render

   File "/home/profilia/.python/lib/python2.5/site-
 packages/django/template/__init__.py", line 768, in render

   File "/home/profilia/.python/lib/python2.5/site-
 packages/django/template/__init__.py", line 781, in render_node

   File "/home/profilia/.python/lib/python2.5/site-
 packages/django/template/defaulttags.py", line 148, in render

   File "/home/profilia/.python/lib/python2.5/site-
 packages/django/template/defaulttags.py", line 255, in render

   File "/home/profilia/.python/lib/python2.5/site-
 packages/django/template/__init__.py", line 768, in render

   File "/home/profilia/.python/lib/python2.5/site-
 packages/django/template/__init__.py", line 781, in render_node

   File "/home/profilia/.python/lib/python2.5/site-
 packages/django/templatetags/cache.py", line 27, in render

   File "/home/profilia/.python/lib/python2.5/site-
 packages/django/core/cache/backends/locmem.py", line 61, in get

 KeyError: u'auctionlot-row:hu:-5002021'
 }}}

-- 
Ticket URL: 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9401: inlineformset_factory raise IntegrityError Exception when correct data (is_valid() method) is ok

[Django]

#9401: inlineformset_factory raise IntegrityError Exception when correct data
(is_valid() method) is ok
-+--
  Reporter:  bartosak| Owner:  nobody  
Status:  new | Milestone:  post-1.0
 Component:  Forms   |   Version:  SVN 
Resolution:  |  Keywords:  
 Stage:  Unreviewed  | Has_patch:  0   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Comment (by bartosak):

 I will check with the last SVN version ASAP. Probably tommorow because im
 moving to new flat today

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9638: Add %(app_label)s to the related_name format string for abstract models

[Django]

#9638: Add %(app_label)s to the related_name format string for abstract models
--+-
  Reporter:  [EMAIL PROTECTED]  | Owner:  nobody
Status:  new  | Milestone:
 Component:  Core framework   |   Version:  1.0   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  1|   Needs_tests:  1 
Needs_better_patch:  1|  
--+-
Changes (by mtredinnick):

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

Comment:

 This is a good idea. The patch needs to include tests and a documentation
 update. The existing tests for this sort of feature are in
 `tests/model_inheritance/tests/` and something new can be added there.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---