date:20091009

Re: [Django] #12006: UUID field needed

2009-10-09 Thread Django

#12006: UUID field needed
---+
  Reporter:  ungerik   | Owner:  nobody
Status:  closed| Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:
Resolution:  duplicate |  Keywords:  uuid  
 Stage:  Design decision needed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by kmtracey):

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

Comment:

 Isn't this #4682?

-- 
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] #12006: UUID field needed

2009-10-09 Thread Django

#12006: UUID field needed
---+
  Reporter:  ungerik   | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:
Resolution:|  Keywords:  uuid  
 Stage:  Design decision needed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by Alex):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Design decision needed
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 Marking as DDN because there's no reason this has to live in Django core.
 Frankly I'm inclined to wontfix, but alas perhaps cooler heads will
 prevail.

-- 
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] #12006: UUID field needed

2009-10-09 Thread Django

#12006: UUID field needed
--+-
 Reporter:  ungerik   |   Owner:  nobody
   Status:  new   |   Milestone:  1.2   
Component:  Database layer (models, ORM)  | Version:
 Keywords:  uuid  |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 128 bit integer field or emulation if db backend doesn't support that
 integer size or native UUIDs.
 Text format/parse methods would be nice at the field object.

-- 
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] #3594: Translation problem in javascript

2009-10-09 Thread Django

#3594: Translation problem in javascript
---+
  Reporter:  karsu | Owner:  arkx
Status:  new   | Milestone:  
 Component:  Internationalization  |   Version:  SVN 
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by arkx):

  * owner:  msaelices => arkx
  * status:  reopened => new

-- 
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] #2131: HttpResponseSendFile for serving static files handler-specific sendfile mechanism

2009-10-09 Thread Django

#2131: HttpResponseSendFile for serving static files handler-specific sendfile
mechanism
---+
  Reporter:  ymasuda[at]ethercube.com  | Owner:  ccahoon
Status:  new   | Milestone:  1.2
 Component:  Core framework|   Version:  SVN
Resolution:|  Keywords: 
 Stage:  Fixed on a branch | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by AntonBessonov):

 * cc: exe...@gmail.com (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] #12005: django.forms.fields.email_re doesn't handle single-letter subdomains

2009-10-09 Thread Django

#12005: django.forms.fields.email_re doesn't handle single-letter subdomains
-+--
  Reporter:  Gumnos  | Owner:  nobody   
 
Status:  new | Milestone:   
 
 Component:  Forms   |   Version:  SVN  
 
Resolution:  |  Keywords:  email_re subdomain speed 
single letter
 Stage:  Unreviewed  | Has_patch:  1
 
Needs_docs:  0   |   Needs_tests:  0
 
Needs_better_patch:  0   |  
-+--
Changes (by Gumnos):

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

Comment:

 This may conflict with r11603 but should resolve the same email_re issue
 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 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #12005: django.forms.fields.email_re doesn't handle single-letter subdomains

2009-10-09 Thread Django

#12005: django.forms.fields.email_re doesn't handle single-letter subdomains
+---
 Reporter:  Gumnos  |   Owner:  nobody
   Status:  new |   Milestone:
Component:  Forms   | Version:  SVN   
 Keywords:  email_re subdomain speed single letter  |   Stage:  Unreviewed
Has_patch:  1   |  
+---
 When domain-validating logic was moved from validators to
 forms.fields.email_re single-letter sub-domains are no longer caught.
 There were also some speed issues when processing longer email addresses
 that were resolved in 1.1.1 and 1.0.4 that this patch should also address
 in a similar manner.  There may be a similar issue with
 forms.fields.url_re but I didn't get a chance to hack that too.

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

[Changeset] r11616 - in django/branches/releases/1.0.X: . django

2009-10-09 Thread noreply


Author: ubernostrum
Date: 2009-10-09 17:18:16 -0500 (Fri, 09 Oct 2009)
New Revision: 11616

Modified:
   django/branches/releases/1.0.X/django/__init__.py
   django/branches/releases/1.0.X/setup.py
Log:
[1.0.X] Reset 1.0 branch packaging data post-release.

Modified: django/branches/releases/1.0.X/django/__init__.py
===
--- django/branches/releases/1.0.X/django/__init__.py   2009-10-09 22:17:43 UTC 
(rev 11615)
+++ django/branches/releases/1.0.X/django/__init__.py   2009-10-09 22:18:16 UTC 
(rev 11616)
@@ -1,4 +1,4 @@
-VERSION = (1, 0, 4, 'final', 0)
+VERSION = (1, 0, 5, 'alpha', 0)
 
 def get_version():
 version = '%s.%s' % (VERSION[0], VERSION[1])

Modified: django/branches/releases/1.0.X/setup.py
===
--- django/branches/releases/1.0.X/setup.py 2009-10-09 22:17:43 UTC (rev 
11615)
+++ django/branches/releases/1.0.X/setup.py 2009-10-09 22:18:16 UTC (rev 
11616)
@@ -74,7 +74,6 @@
 name = "Django",
 version = version.replace(' ', '-'),
 url = 'http://www.djangoproject.com/',
-download_url = 
'http://media.djangoproject.com/releases/1.0.4/Django-1.0.4.tar.gz',
 author = 'Django Software Foundation',
 author_email = 'foundat...@djangoproject.com',
 description = 'A high-level Python Web framework that encourages rapid 
development and clean, pragmatic design.',


--~--~-~--~~~---~--~~
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] r11615 - in django/branches/releases/1.1.X: . django

2009-10-09 Thread noreply


Author: ubernostrum
Date: 2009-10-09 17:17:43 -0500 (Fri, 09 Oct 2009)
New Revision: 11615

Modified:
   django/branches/releases/1.1.X/django/__init__.py
   django/branches/releases/1.1.X/setup.py
Log:
[1.1.X] Reset 1.1 branch packaging data post-release.

Modified: django/branches/releases/1.1.X/django/__init__.py
===
--- django/branches/releases/1.1.X/django/__init__.py   2009-10-09 22:16:10 UTC 
(rev 11614)
+++ django/branches/releases/1.1.X/django/__init__.py   2009-10-09 22:17:43 UTC 
(rev 11615)
@@ -1,4 +1,4 @@
-VERSION = (1, 1, 1, 'final', 0)
+VERSION = (1, 1, 2, 'alpha', 0)
 
 def get_version():
 version = '%s.%s' % (VERSION[0], VERSION[1])

Modified: django/branches/releases/1.1.X/setup.py
===
--- django/branches/releases/1.1.X/setup.py 2009-10-09 22:16:10 UTC (rev 
11614)
+++ django/branches/releases/1.1.X/setup.py 2009-10-09 22:17:43 UTC (rev 
11615)
@@ -74,7 +74,6 @@
 name = "Django",
 version = version.replace(' ', '-'),
 url = 'http://www.djangoproject.com/',
-download_url = 
'http://media.djangoproject.com/releases/1.1.1/Django-1.1.1.tar.gz',
 author = 'Django Software Foundation',
 author_email = 'foundat...@djangoproject.com',
 description = 'A high-level Python Web framework that encourages rapid 
development and clean, pragmatic design.',


--~--~-~--~~~---~--~~
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] #11537: localflavor for india's state choices are not tuples

2009-10-09 Thread Django

#11537: localflavor for india's state choices are not tuples
-+--
  Reporter:  zbyte64 | Owner:  lars
Status:  assigned| Milestone:  
 Component:  django.contrib.localflavor  |   Version:  SVN 
Resolution:  |  Keywords:  
 Stage:  Accepted| Has_patch:  1   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by lars):

  * owner:  nobody => lars
  * status:  new => assigned
  * has_patch:  0 => 1

Comment:

 This should fix this ticket and at least bring it in line with the current
 status of the other localflavors.

 The state Uttaranchal has been renamed to Uttarakhand in 2007. With this
 change the license plate has changed from UA to UK. As people might rely
 on UA as a key in their databases I didn't change this one. The ISO code
 is yet another one (UL). The
 [http://docs.djangoproject.com/en/dev/ref/contrib/localflavor/#india-in
 documentation] says "Input is normalized to the standard two-letter
 vehicle registration abbreviation for the given state or territory." so
 this is not really 100% true at the moment. But as I'm not from India and
 I don't know how important this change is I left it as it was.

-- 
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] r11613 - django/tags/releases

2009-10-09 Thread noreply


Author: jacob
Date: 2009-10-09 17:12:05 -0500 (Fri, 09 Oct 2009)
New Revision: 11613

Added:
   django/tags/releases/1.0.4/
Log:
Tag 1.0.4


Copied: django/tags/releases/1.0.4 (from rev 11612, 
django/branches/releases/1.0.X)


--~--~-~--~~~---~--~~
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] r11612 - django/tags/releases

2009-10-09 Thread noreply


Author: jacob
Date: 2009-10-09 17:11:15 -0500 (Fri, 09 Oct 2009)
New Revision: 11612

Added:
   django/tags/releases/1.1.1/
Log:
Tag 1.1.1.


Copied: django/tags/releases/1.1.1 (from rev 11611, 
django/branches/releases/1.1.X)


--~--~-~--~~~---~--~~
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] r11611 - django/branches/releases/1.1.X

2009-10-09 Thread noreply


Author: ubernostrum
Date: 2009-10-09 17:07:49 -0500 (Fri, 09 Oct 2009)
New Revision: 11611

Modified:
   django/branches/releases/1.1.X/setup.py
Log:
[1.1.X] Really fix the download_url. We already manually tweaked it on pypi, so 
this is just my inner perfectionist complaining.

Modified: django/branches/releases/1.1.X/setup.py
===
--- django/branches/releases/1.1.X/setup.py 2009-10-09 21:29:17 UTC (rev 
11610)
+++ django/branches/releases/1.1.X/setup.py 2009-10-09 22:07:49 UTC (rev 
11611)
@@ -74,7 +74,7 @@
 name = "Django",
 version = version.replace(' ', '-'),
 url = 'http://www.djangoproject.com/',
-download_url = 
'http://media.djangoproject.com/releases/1.1/Django-1.1.1.tar.gz',
+download_url = 
'http://media.djangoproject.com/releases/1.1.1/Django-1.1.1.tar.gz',
 author = 'Django Software Foundation',
 author_email = 'foundat...@djangoproject.com',
 description = 'A high-level Python Web framework that encourages rapid 
development and clean, pragmatic design.',


--~--~-~--~~~---~--~~
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] r11610 - django/branches/releases/1.0.X

2009-10-09 Thread noreply


Author: ubernostrum
Date: 2009-10-09 16:29:17 -0500 (Fri, 09 Oct 2009)
New Revision: 11610

Modified:
   django/branches/releases/1.0.X/setup.py
Log:
[1.0.X] Correct download URL.

Modified: django/branches/releases/1.0.X/setup.py
===
--- django/branches/releases/1.0.X/setup.py 2009-10-09 21:08:21 UTC (rev 
11609)
+++ django/branches/releases/1.0.X/setup.py 2009-10-09 21:29:17 UTC (rev 
11610)
@@ -74,7 +74,7 @@
 name = "Django",
 version = version.replace(' ', '-'),
 url = 'http://www.djangoproject.com/',
-download_url = 
'http://media.djangoproject.com/releases/1.1/Django-1.0.4.tar.gz',
+download_url = 
'http://media.djangoproject.com/releases/1.0.4/Django-1.0.4.tar.gz',
 author = 'Django Software Foundation',
 author_email = 'foundat...@djangoproject.com',
 description = 'A high-level Python Web framework that encourages rapid 
development and clean, pragmatic design.',


--~--~-~--~~~---~--~~
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] #11198: Forms URLfield regex takes infinite to validate a long field

2009-10-09 Thread Django

#11198: Forms URLfield regex takes infinite to validate a long field
-+--
  Reporter:  marcob  | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Forms   |   Version:  SVN   
Resolution:  fixed   |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by jacob):

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

Comment:

 Fixed in [11603]. [11604], [11605].

-- 
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] r11609 - django/branches/releases/1.1.X

2009-10-09 Thread noreply


Author: ubernostrum
Date: 2009-10-09 16:08:21 -0500 (Fri, 09 Oct 2009)
New Revision: 11609

Modified:
   django/branches/releases/1.1.X/setup.py
Log:
[1.1.X] Update setup.py for security release.

Modified: django/branches/releases/1.1.X/setup.py
===
--- django/branches/releases/1.1.X/setup.py 2009-10-09 21:07:57 UTC (rev 
11608)
+++ django/branches/releases/1.1.X/setup.py 2009-10-09 21:08:21 UTC (rev 
11609)
@@ -74,6 +74,7 @@
 name = "Django",
 version = version.replace(' ', '-'),
 url = 'http://www.djangoproject.com/',
+download_url = 
'http://media.djangoproject.com/releases/1.1/Django-1.1.1.tar.gz',
 author = 'Django Software Foundation',
 author_email = 'foundat...@djangoproject.com',
 description = 'A high-level Python Web framework that encourages rapid 
development and clean, pragmatic design.',


--~--~-~--~~~---~--~~
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] r11608 - django/branches/releases/1.0.X

2009-10-09 Thread noreply


Author: ubernostrum
Date: 2009-10-09 16:07:57 -0500 (Fri, 09 Oct 2009)
New Revision: 11608

Modified:
   django/branches/releases/1.0.X/setup.py
Log:
[1.0.X] Update setup.py for security release.

Modified: django/branches/releases/1.0.X/setup.py
===
--- django/branches/releases/1.0.X/setup.py 2009-10-09 21:06:47 UTC (rev 
11607)
+++ django/branches/releases/1.0.X/setup.py 2009-10-09 21:07:57 UTC (rev 
11608)
@@ -74,6 +74,7 @@
 name = "Django",
 version = version.replace(' ', '-'),
 url = 'http://www.djangoproject.com/',
+download_url = 
'http://media.djangoproject.com/releases/1.1/Django-1.0.4.tar.gz',
 author = 'Django Software Foundation',
 author_email = 'foundat...@djangoproject.com',
 description = 'A high-level Python Web framework that encourages rapid 
development and clean, pragmatic design.',


--~--~-~--~~~---~--~~
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] r11607 - django/branches/releases/1.0.X/django

2009-10-09 Thread noreply


Author: ubernostrum
Date: 2009-10-09 16:06:47 -0500 (Fri, 09 Oct 2009)
New Revision: 11607

Modified:
   django/branches/releases/1.0.X/django/__init__.py
Log:
[1.0.X] Bump version number for security release.

Modified: django/branches/releases/1.0.X/django/__init__.py
===
--- django/branches/releases/1.0.X/django/__init__.py   2009-10-09 21:06:09 UTC 
(rev 11606)
+++ django/branches/releases/1.0.X/django/__init__.py   2009-10-09 21:06:47 UTC 
(rev 11607)
@@ -1,4 +1,4 @@
-VERSION = (1, 0, 4, 'alpha', 0)
+VERSION = (1, 0, 4, 'final', 0)
 
 def get_version():
 version = '%s.%s' % (VERSION[0], VERSION[1])


--~--~-~--~~~---~--~~
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] r11606 - django/branches/releases/1.1.X/django

2009-10-09 Thread noreply


Author: ubernostrum
Date: 2009-10-09 16:06:09 -0500 (Fri, 09 Oct 2009)
New Revision: 11606

Modified:
   django/branches/releases/1.1.X/django/__init__.py
Log:
[1.1.X] Bump version number for security release.

Modified: django/branches/releases/1.1.X/django/__init__.py
===
--- django/branches/releases/1.1.X/django/__init__.py   2009-10-09 20:59:25 UTC 
(rev 11605)
+++ django/branches/releases/1.1.X/django/__init__.py   2009-10-09 21:06:09 UTC 
(rev 11606)
@@ -1,4 +1,4 @@
-VERSION = (1, 1, 1, 'alpha', 0)
+VERSION = (1, 1, 1, 'final', 0)
 
 def get_version():
 version = '%s.%s' % (VERSION[0], VERSION[1])


--~--~-~--~~~---~--~~
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] #7923: Add links when using raw_id_fields in admin

2009-10-09 Thread Django

#7923: Add links when using raw_id_fields in admin
---+
  Reporter:  julianb   | Owner:  julianb
Status:  assigned  | Milestone:  1.2
 Component:  django.contrib.admin  |   Version:  SVN
Resolution:|  Keywords:  admin raw_id_fields
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Comment (by mrts):

 The patch has been merged into the patch attached to #7028 as both issues
 are tightly related. Will not update the patch here any more.

-- 
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] #7028: Better raw_id_fields feedback in newform-admins branch

2009-10-09 Thread Django

#7028: Better raw_id_fields feedback in newform-admins branch
---+
  Reporter:  Marcob   | Owner:  nobody 
  
Status:  new   | Milestone:  1.2
  
 Component:  django.contrib.admin  |   Version:  1.0
  
Resolution:|  Keywords:  
raw-id-fields nfa-someday
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  1  
  
Needs_better_patch:  1 |  
---+
Changes (by mrts):

  * needs_better_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
-~--~~~~--~~--~--~---

[Changeset] r11605 - in django/branches/releases/1.0.X: django/forms tests/regressiontests/forms

2009-10-09 Thread noreply


Author: jacob
Date: 2009-10-09 15:59:25 -0500 (Fri, 09 Oct 2009)
New Revision: 11605

Modified:
   django/branches/releases/1.0.X/django/forms/fields.py
   django/branches/releases/1.0.X/tests/regressiontests/forms/fields.py
Log:
SECURITY ALERT: Corrected regular expressions for URL and email fields.

Certain email addresses/URLs could trigger a catastrophic backtracking
situation, causing 100% CPU and server overload. If deliberately triggered, this
could be the basis of a denial-of-service attack.

This security vulnerability was disclosed in public, so we're skipping our
normal security release process to get the fix out as soon as possible.

This is a security related update. A full announcement will follow.



Modified: django/branches/releases/1.0.X/django/forms/fields.py
===
--- django/branches/releases/1.0.X/django/forms/fields.py   2009-10-09 
20:59:05 UTC (rev 11604)
+++ django/branches/releases/1.0.X/django/forms/fields.py   2009-10-09 
20:59:25 UTC (rev 11605)
@@ -421,7 +421,7 @@
 email_re = re.compile(
 r"(^[-!#$%&'*+/=?^_`{}|~0-9A-Z]+(\.[-!#$%&'*+/=?^_`{}|~0-9A-Z]+)*"  # 
dot-atom
 
r'|^"([\001-\010\013\014\016-\037!#-\[\]-\177]|\\[\001-011\013\014\016-\177])*"'
 # quoted-string
-r')@(?:[A-Z0-9]+(?:-*[A-Z0-9]+)*\.)+[A-Z]{2,6}$', re.IGNORECASE)  # domain
+r')@(?:[A-Z0-9](?:[A-Z0-9-]{0,61}[A-Z0-9])?\.)+[A-Z]{2,6}\.?$', 
re.IGNORECASE)  # domain
 
 class EmailField(RegexField):
 default_error_messages = {
@@ -532,7 +532,7 @@
 
 url_re = re.compile(
 r'^https?://' # http:// or https://
-r'(?:(?:[A-Z0-9]+(?:-*[A-Z0-9]+)*\.)+[A-Z]{2,6}|' #domain...
+r'(?:(?:[A-Z0-9](?:[A-Z0-9-]{0,61}[A-Z0-9])?\.)+[A-Z]{2,6}\.?|' #domain...
 r'localhost|' #localhost...
 r'\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3})' # ...or ip
 r'(?::\d+)?' # optional port

Modified: django/branches/releases/1.0.X/tests/regressiontests/forms/fields.py
===
--- django/branches/releases/1.0.X/tests/regressiontests/forms/fields.py
2009-10-09 20:59:05 UTC (rev 11604)
+++ django/branches/releases/1.0.X/tests/regressiontests/forms/fields.py
2009-10-09 20:59:25 UTC (rev 11605)
@@ -767,6 +767,13 @@
 >>> f.clean('exam...@valid-with-hyphens.com')
 u'exam...@valid-with-hyphens.com'
 
+# Check for runaway regex security problem. This will take for-freeking-ever
+# if the security fix isn't in place.
+>>> f.clean('viewx3dtextx26q...@yahoo.comx26latlngx3d15854521645943074058')
+Traceback (most recent call last):
+...
+ValidationError: [u'Enter a valid e-mail address.']
+
 >>> f = EmailField(required=False)
 >>> f.clean('')
 u''
@@ -972,6 +979,32 @@
 Traceback (most recent call last):
 ...
 ValidationError: [u'Enter a valid URL.']
+>>> f.clean('.')
+Traceback (most recent call last):
+...
+ValidationError: [u'Enter a valid URL.']
+>>> f.clean('com.')
+Traceback (most recent call last):
+...
+ValidationError: [u'Enter a valid URL.']
+>>> f.clean('http://example.com.')
+u'http://example.com./'
+>>> f.clean('example.com.')
+u'http://example.com./'
+
+# hangs "forever" if catastrophic backtracking in ticket:#11198 not fixed
+>>> f.clean('http://%s' % ("X"*200,))
+Traceback (most recent call last):
+...
+ValidationError: [u'Enter a valid URL.']
+
+# a second test, to make sure the problem is really addressed, even on 
+# domains that don't fail the domain label length check in the regex
+>>> f.clean('http://%s' % ("X"*60,))
+Traceback (most recent call last):
+...
+ValidationError: [u'Enter a valid URL.']
+
 >>> f.clean('http://.com')
 Traceback (most recent call last):
 ...


--~--~-~--~~~---~--~~
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] r11604 - in django/branches/releases/1.1.X: django/forms tests/regressiontests/forms

2009-10-09 Thread noreply


Author: jacob
Date: 2009-10-09 15:59:05 -0500 (Fri, 09 Oct 2009)
New Revision: 11604

Modified:
   django/branches/releases/1.1.X/django/forms/fields.py
   django/branches/releases/1.1.X/tests/regressiontests/forms/fields.py
Log:
[1.1.X] SECURITY ALERT: Corrected regular expressions for URL and email fields.

Certain email addresses/URLs could trigger a catastrophic backtracking
situation, causing 100% CPU and server overload. If deliberately triggered, this
could be the basis of a denial-of-service attack.

This security vulnerability was disclosed in public, so we're skipping our
normal security release process to get the fix out as soon as possible.

This is a security related update. A full announcement will follow.



Modified: django/branches/releases/1.1.X/django/forms/fields.py
===
--- django/branches/releases/1.1.X/django/forms/fields.py   2009-10-09 
20:57:59 UTC (rev 11603)
+++ django/branches/releases/1.1.X/django/forms/fields.py   2009-10-09 
20:59:05 UTC (rev 11604)
@@ -421,7 +421,7 @@
 email_re = re.compile(
 r"(^[-!#$%&'*+/=?^_`{}|~0-9A-Z]+(\.[-!#$%&'*+/=?^_`{}|~0-9A-Z]+)*"  # 
dot-atom
 
r'|^"([\001-\010\013\014\016-\037!#-\[\]-\177]|\\[\001-011\013\014\016-\177])*"'
 # quoted-string
-r')@(?:[A-Z0-9]+(?:-*[A-Z0-9]+)*\.)+[A-Z]{2,6}$', re.IGNORECASE)  # domain
+r')@(?:[A-Z0-9](?:[A-Z0-9-]{0,61}[A-Z0-9])?\.)+[A-Z]{2,6}\.?$', 
re.IGNORECASE)  # domain
 
 class EmailField(RegexField):
 default_error_messages = {
@@ -532,7 +532,7 @@
 
 url_re = re.compile(
 r'^https?://' # http:// or https://
-r'(?:(?:[A-Z0-9]+(?:-*[A-Z0-9]+)*\.)+[A-Z]{2,6}|' #domain...
+r'(?:(?:[A-Z0-9](?:[A-Z0-9-]{0,61}[A-Z0-9])?\.)+[A-Z]{2,6}\.?|' #domain...
 r'localhost|' #localhost...
 r'\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3})' # ...or ip
 r'(?::\d+)?' # optional port

Modified: django/branches/releases/1.1.X/tests/regressiontests/forms/fields.py
===
--- django/branches/releases/1.1.X/tests/regressiontests/forms/fields.py
2009-10-09 20:57:59 UTC (rev 11603)
+++ django/branches/releases/1.1.X/tests/regressiontests/forms/fields.py
2009-10-09 20:59:05 UTC (rev 11604)
@@ -767,6 +767,13 @@
 >>> f.clean('exam...@valid-with-hyphens.com')
 u'exam...@valid-with-hyphens.com'
 
+# Check for runaway regex security problem. This will take for-freeking-ever
+# if the security fix isn't in place.
+>>> f.clean('viewx3dtextx26q...@yahoo.comx26latlngx3d15854521645943074058')
+Traceback (most recent call last):
+...
+ValidationError: [u'Enter a valid e-mail address.']
+
 >>> f = EmailField(required=False)
 >>> f.clean('')
 u''
@@ -972,6 +979,32 @@
 Traceback (most recent call last):
 ...
 ValidationError: [u'Enter a valid URL.']
+>>> f.clean('.')
+Traceback (most recent call last):
+...
+ValidationError: [u'Enter a valid URL.']
+>>> f.clean('com.')
+Traceback (most recent call last):
+...
+ValidationError: [u'Enter a valid URL.']
+>>> f.clean('http://example.com.')
+u'http://example.com./'
+>>> f.clean('example.com.')
+u'http://example.com./'
+
+# hangs "forever" if catastrophic backtracking in ticket:#11198 not fixed
+>>> f.clean('http://%s' % ("X"*200,))
+Traceback (most recent call last):
+...
+ValidationError: [u'Enter a valid URL.']
+
+# a second test, to make sure the problem is really addressed, even on 
+# domains that don't fail the domain label length check in the regex
+>>> f.clean('http://%s' % ("X"*60,))
+Traceback (most recent call last):
+...
+ValidationError: [u'Enter a valid URL.']
+
 >>> f.clean('http://.com')
 Traceback (most recent call last):
 ...


--~--~-~--~~~---~--~~
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] #7028: Better raw_id_fields feedback in newform-admins branch

2009-10-09 Thread Django

#7028: Better raw_id_fields feedback in newform-admins branch
---+
  Reporter:  Marcob   | Owner:  nobody 
  
Status:  new   | Milestone:  1.2
  
 Component:  django.contrib.admin  |   Version:  1.0
  
Resolution:|  Keywords:  
raw-id-fields nfa-someday
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  1  
  
Needs_better_patch:  0 |  
---+
Comment (by mrts):

 I've implemented this and also integrated #7923 in my !GitHub branch:
 http://github.com/mrts/django/commits/ticket7028

 Admin widget tests pass, but there's a regression in admin views tests --
 a spurious `False` appears into the output, but I haven't yet got time to
 figure out from where (probably a trivial problem somewhere).

 Attaching a patch.

 IMHO #7923 can be closed as duplicate.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] r11603 - in django/trunk: django/forms tests/regressiontests/forms

2009-10-09 Thread noreply


Author: jacob
Date: 2009-10-09 15:57:59 -0500 (Fri, 09 Oct 2009)
New Revision: 11603

Modified:
   django/trunk/django/forms/fields.py
   django/trunk/tests/regressiontests/forms/fields.py
Log:
SECURITY ALERT: Corrected regular expressions for URL and email fields.

Certain email addresses/URLs could trigger a catastrophic backtracking 
situation, causing 100% CPU and server overload. If deliberately triggered, 
this could be the basis of a denial-of-service attack.

This security vulnerability was disclosed in public, so we're skipping our
normal security release process to get the fix out as soon as possible.

This is a security related update. A full announcement, as well as backports 
for the 1.1.X and 1.0.X series will follow.

Modified: django/trunk/django/forms/fields.py
===
--- django/trunk/django/forms/fields.py 2009-10-08 13:32:23 UTC (rev 11602)
+++ django/trunk/django/forms/fields.py 2009-10-09 20:57:59 UTC (rev 11603)
@@ -421,7 +421,7 @@
 email_re = re.compile(
 r"(^[-!#$%&'*+/=?^_`{}|~0-9A-Z]+(\.[-!#$%&'*+/=?^_`{}|~0-9A-Z]+)*"  # 
dot-atom
 
r'|^"([\001-\010\013\014\016-\037!#-\[\]-\177]|\\[\001-011\013\014\016-\177])*"'
 # quoted-string
-r')@(?:[A-Z0-9]+(?:-*[A-Z0-9]+)*\.)+[A-Z]{2,6}$', re.IGNORECASE)  # domain
+r')@(?:[A-Z0-9](?:[A-Z0-9-]{0,61}[A-Z0-9])?\.)+[A-Z]{2,6}\.?$', 
re.IGNORECASE)  # domain
 
 class EmailField(RegexField):
 default_error_messages = {
@@ -532,7 +532,7 @@
 
 url_re = re.compile(
 r'^https?://' # http:// or https://
-r'(?:(?:[A-Z0-9]+(?:-*[A-Z0-9]+)*\.)+[A-Z]{2,6}|' #domain...
+r'(?:(?:[A-Z0-9](?:[A-Z0-9-]{0,61}[A-Z0-9])?\.)+[A-Z]{2,6}\.?|' #domain...
 r'localhost|' #localhost...
 r'\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3})' # ...or ip
 r'(?::\d+)?' # optional port

Modified: django/trunk/tests/regressiontests/forms/fields.py
===
--- django/trunk/tests/regressiontests/forms/fields.py  2009-10-08 13:32:23 UTC 
(rev 11602)
+++ django/trunk/tests/regressiontests/forms/fields.py  2009-10-09 20:57:59 UTC 
(rev 11603)
@@ -767,6 +767,13 @@
 >>> f.clean('exam...@valid-with-hyphens.com')
 u'exam...@valid-with-hyphens.com'
 
+# Check for runaway regex security problem. This will take for-freeking-ever
+# if the security fix isn't in place.
+>>> f.clean('viewx3dtextx26q...@yahoo.comx26latlngx3d15854521645943074058')
+Traceback (most recent call last):
+...
+ValidationError: [u'Enter a valid e-mail address.']
+
 >>> f = EmailField(required=False)
 >>> f.clean('')
 u''
@@ -972,6 +979,32 @@
 Traceback (most recent call last):
 ...
 ValidationError: [u'Enter a valid URL.']
+>>> f.clean('.')
+Traceback (most recent call last):
+...
+ValidationError: [u'Enter a valid URL.']
+>>> f.clean('com.')
+Traceback (most recent call last):
+...
+ValidationError: [u'Enter a valid URL.']
+>>> f.clean('http://example.com.')
+u'http://example.com./'
+>>> f.clean('example.com.')
+u'http://example.com./'
+
+# hangs "forever" if catastrophic backtracking in ticket:#11198 not fixed
+>>> f.clean('http://%s' % ("X"*200,))
+Traceback (most recent call last):
+...
+ValidationError: [u'Enter a valid URL.']
+
+# a second test, to make sure the problem is really addressed, even on 
+# domains that don't fail the domain label length check in the regex
+>>> f.clean('http://%s' % ("X"*60,))
+Traceback (most recent call last):
+...
+ValidationError: [u'Enter a valid URL.']
+
 >>> f.clean('http://.com')
 Traceback (most recent call last):
 ...


--~--~-~--~~~---~--~~
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] #7808: Form Preview does not work with file uploads

2009-10-09 Thread Django

#7808: Form Preview does not work with file uploads
-+--
  Reporter:  ian_brasil  | Owner:  nobody
Status:  reopened| Milestone:  1.0   
 Component:  Uncategorized   |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by anonymous):

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

Comment:

 This should be mentioned in the FormPreview 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 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11993: ValueError: Cannot convert NaN to integer in regressiontests.defaultfilters.tests using Python 2.6.3

2009-10-09 Thread Django

#11993: ValueError: Cannot convert NaN to integer in
regressiontests.defaultfilters.tests using Python 2.6.3
+---
  Reporter:  kklimonda  | Owner:  nobody
Status:  new| Milestone:
 Component:  Uncategorized  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by kklimonda):

  * 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
-~--~~~~--~~--~--~---

Re: [Django] #6630: Fieldsets for newforms

2009-10-09 Thread Django

#6630: Fieldsets for newforms
+---
  Reporter:  Petr Marhoun   | Owner:  
nobody 
Status:  new| Milestone:
 
 Component:  Forms  |   Version:  
SVN
Resolution: |  Keywords:  
feature
 Stage:  Design decision needed | Has_patch:  1 
 
Needs_docs:  1  |   Needs_tests:  0 
 
Needs_better_patch:  1  |  
+---
Changes (by carljm):

 * cc: carljm (added)

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

[Django] #12004: Registering abstract model with admin gives confusing / misleading error

2009-10-09 Thread Django

#12004: Registering abstract model with admin gives confusing / misleading error
---+
 Reporter:  Matt Smalley   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  django.contrib.admin   | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 It makes perfect sense that an abstract model cannot be registered with
 admin. However, the abstract model is listed with the rest and there is no
 error until the page for that model is requested from the admin interface.
 Doing so gives:

 {{{
 'str' object has no attribute '_default_manager'
 }}}

 This is a bit mysterious, and IMO would be better handled at the time of
 registering the model with something more explicit. Also, since this error
 occurs in some other hard-to-identify cases (see
 [http://code.djangoproject.com/ticket/10405 #10405], among others), I
 spent a lot of time going down blind alleys in search of the source of the
 problem.

-- 
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] #3591: add support for custom app_label and verbose_name

2009-10-09 Thread Django

#3591: add support for custom app_label and verbose_name
-+--
  Reporter:  jkocherhans | Owner:  adrian
Status:  reopened| Milestone:
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by mbeachy):

 * cc: mbea...@gmail.com (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] #11010: Add a foundation for rowlevel permissions in Django

2009-10-09 Thread Django

#11010: Add a foundation for rowlevel permissions in Django
-+--
  Reporter:  apollo13| Owner:  nobody
Status:  new | Milestone:  1.2   
 Component:  Authentication  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Changes (by jezdez):

  * needs_better_patch:  0 => 1
  * stage:  Design decision needed => Accepted
  * needs_docs:  0 => 1

Comment:

 Setting to accepted after talking to jacobian and apollo13 in #django-dev.

-- 
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] #11010: Add a foundation for rowlevel permissions in Django

2009-10-09 Thread Django

#11010: Add a foundation for rowlevel permissions in Django
-+--
  Reporter:  apollo13| Owner:  nobody
Status:  new | Milestone:  1.2   
 Component:  Authentication  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  1 
Needs_better_patch:  0   |  
-+--
Changes (by jezdez):

 * cc: jezdez (added)
  * has_patch:  0 => 1
  * needs_tests:  0 => 1

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

Re: [Django] #11978: 'Duplicate key value violates unique constraint' error while changing inline admin model

2009-10-09 Thread Django

#11978: 'Duplicate key value violates unique constraint' error while changing
inline admin model
-+--
  Reporter:  kozlenko| Owner:  nobody
Status:  closed  | Milestone:
 Component:  Forms   |   Version:  1.1   
Resolution:  invalid |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by kozlenko):

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

Comment:

 Issue resolved. Problem was in internal Secondary exception.
 It catch quietly but breaks form submission.

-- 
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] #12003: Admin application deltes related objects on "null=True" relation.

2009-10-09 Thread Django

#12003: Admin application deltes related objects on "null=True" relation.
---+
 Reporter:  x_O|   Owner:  nobody
   Status:  new|   Milestone:
Component:  django.contrib.admin   | Version:  1.1   
 Keywords:  admin delete remove related null True  |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 We have two models
 {{{
 class First(db.models):
 second_item = models.ForeignKey('Second',null=True)
 ...

 class  (db.models):
 ...
 }}}


 Both models registered in admin.py as AdminModels.

 Trying to delete object created from "Second" class
 which is RELATED to other one created from "First" class, admin tells that
 will remove also that "First" object. Important is that relation in
 ForeignKey is null.

 My interpretation of that "null=True" for admin.contrib: should set First
 objects with 'second_item' attribute = None.

 Checked against 1.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] #12002: Models inherited from multiple Models

2009-10-09 Thread Django

#12002: Models inherited from multiple Models
---+
 Reporter:  vlastimil.z...@nic.cz  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 In case Model is created as inherited from multiple non-abstract Models
 there is a problem with automatic primary keys at children model save.
 Especially when second parent has one more non-proxy children.

 Assume we have following models:
 {{{
 class Place(models.Model):
   class Meta:
 abstract = False
 proxy = False
 ...
 class Staff(models.Model):
   class Meta:
 abstract = False
 proxy = False
 ...
 class Restaurant(Place, Staff):
   class Meta:
 abstract = False
 proxy = False
 ...
 class OtherStaff(Staff):
   class Meta:
 abstract = False
 proxy = False
 ...
 }}}
 where Place and Staff has automatic primary keys:
 {{{
 id = models.AutoField(primary_key = True)
 }}}
 Then on saving new instance of Restaurant the following happens:
   * Restaurant searches for its parents and finds out Place and Staff
   * While inserting new Place instance, it comes out that it has no
 primary key ("id"), so it is inserted into database with automatic one and
 primary key is returned
   * Discovered primary key of new Place instance is saved to Restaurant
 instance under attribute name of Place primary key ("id")
   * Then new Staff instance is inserted. It looks whether it has a primary
 key and it finds out primary key of Place instance, because it has same
 attribute name for primary key ("id")
   * New Staff instance is saved with primary key of Place instance instead
 its own (Hidden problem: If Staff with same primary key already exists
 then values of that Staff are updated with values from new Restaurant
 instance)
 Following attributes will always be equal: Restaurant.id,
 Restaurant.place_ptr_id, Restaurant.staff_ptr_id, Place.id, Staff.id

 Definitely crashes in case Staff has another children e.g. !OtherStaff,
 then on saving new instance of !OtherStaff:
   * !OtherStaff searches for its parents and finds out Staff
   * While inserting new Staff instance, it comes out that it has no
 primary key ("id"), so it is inserted into database with automatic one
   * In database a next primary key from sequence is found out and Staff is
 supposed to be inserted with that primary key
   * CRASH because Staff with that primary key already exist (created while
 saving Restaurant, but with specified primary key, so sequence was not
 updated)

 Same situation happened in every case Model parents (non-abstract) has
 same attribute name for their primary keys and second one has at least one
 more non-proxy children Model.

 I consider this as a bug although it has easy solution (rename attribute
 name of primary key), because I found no evidence that this situation can
 happen and therefore it should be considered. Also I see no reason for use
 in current state.

 I my opinion the best (and easiest) solution is Exception raised in case
 parent classes has same attribute name for their primary key. A way that
 will solve this entirely and allowed situation that parents can have same
 attribute name of primary keys would be great, but it would be probably
 much too complicated.

-- 
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] #7282: Integrated ldap for contrib.auth

2009-10-09 Thread Django

#7282: Integrated ldap for contrib.auth
-+--
  Reporter:  programmerq | Owner:  nobody
Status:  new | Milestone:
 Component:  Contrib apps|   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  1   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by guettli):

 * cc: h...@tbz-pariv.de (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] #7282: Integrated ldap for contrib.auth

2009-10-09 Thread Django

#7282: Integrated ldap for contrib.auth
-+--
  Reporter:  programmerq | Owner:  nobody
Status:  new | Milestone:
 Component:  Contrib apps|   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  1   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by guettli):

 You mean ticket #2507 (not the changeset).

-- 
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] #7467: [Improvement] Easier way to overwite the admin welcome message

2009-10-09 Thread Django

#7467: [Improvement] Easier way to overwite the admin welcome message
-+--
  Reporter:  Jeff Kowalczyk   | Owner:  nobody
Status:  new | Milestone:
 Component:  django.contrib.admin|   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by anonymous):

 * cc: t.dja...@sandbox.cz (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] #11745: Categories by origin for command listings in "manage.py help"

2009-10-09 Thread Django

#11745: Categories by origin for command listings in "manage.py help"
+---
  Reporter:  Tuttle | Owner:  nobody
Status:  new| Milestone:
 Component:  Uncategorized  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

 * cc: tut...@sandbox.cz (removed)
 * cc: t.dja...@sandbox.cz (added)
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * needs_docs:  => 0

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #11017: Oracle LIKEC query doesn't use index

2009-10-09 Thread Django

#11017: Oracle LIKEC query doesn't use index
---+
  Reporter:  jtiai | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:  oracle
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by jtiai):

 Status update: We've been using reverted version for a good while and no
 anomalies have been occuring. Indices gets used as expected. My suggestion
 is just to revert changes made in [7412].

-- 
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] #7467: [Improvement] Easier way to overwite the admin welcome message

2009-10-09 Thread Django

#7467: [Improvement] Easier way to overwite the admin welcome message
-+--
  Reporter:  Jeff Kowalczyk   | Owner:  nobody
Status:  new | Milestone:
 Component:  django.contrib.admin|   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by Tuttle):

 I second this. There are languages that use different form for vocative,
 thus "Welcome, Vlada" is incorrect. I think this form could fit to the
 majority:

 {{{
 {% trans 'User: ' %}
 {% if user.first_name %}{{ user.first_name }} {{
 user.last_name }}
 {% else %}{{ user.username }}{% endif %}.
 }}}

 It does not matter how to reach it, but currently AFAIK the only way is to
 override entire admin/base.html, which is complex.

 If this applies to your language to, please vote for 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
-~--~~~~--~~--~--~---

[Django] #12001: using form.error_class instead of ErrorList in forms validation docs

2009-10-09 Thread Django

#12001: using form.error_class instead of  ErrorList in forms validation docs
---+
 Reporter:  Suor   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 On page [http://docs.djangoproject.com/en/dev/ref/forms/validation/]
 example shows adding errors to form._error using ErrorList.
 Using self.error_class would be cleaner

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

42 matches

Mail list logo