Re: [Django] #3566: Proposal: ORM aggregation support

[Django]

#3566: Proposal: ORM aggregation support
+---
  Reporter:  Honza Král <[EMAIL PROTECTED]>  | Owner:  russellm 
   
Status:  assigned   | Milestone:
  
 Component:  Database layer (models, ORM)   |   Version:  SVN   
  
Resolution: |  Keywords:  orm 
aggregation group by
 Stage:  Someday/Maybe  | Has_patch:  1 
  
Needs_docs:  0  |   Needs_tests:  1 
  
Needs_better_patch:  1  |  
+---
Changes (by anonymous):

 * cc: marinho (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] #9799: django.db.models.sql.query.BaseQuery.get_count() works wrong with GROUP BY

[Django]

#9799: django.db.models.sql.query.BaseQuery.get_count() works wrong with GROUP 
BY
--+-
 Reporter:  syabro|   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  1.0   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Query produced by get_count is
 {{{
 #!mysql
 SELECT COUNT(*) FROM table
 }}}
 which returned one row, f.e. (5) . Ok, it's works.
 Lets add an GROUP BY statement:
 {{{
 #!mysql
 SELECT COUNT(*) FROM table GROUP BY field
 }}}
 It's returned an list of row with count of grouped rows, f.e. (4, 23, 1,
 1, 5)
 In ge_count we see
 {{{
 #!python
 data = obj.execute_sql(SINGLE)
 if not data:
 return 0
 number = data[0]
 }}}
 So it's return only first value of the list instead of list's width. With
 our example it's 5.
 Solutions are:
 1. Return cursor's row_count
 2. Modify query to
 {{{
 #!mysql
 SELECT (*) FROM (SELECT COUNT(*) FROM table GROUP BY field) AS 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] #2134: [patch] add comment object to comments/posted template

[Django]

#2134: [patch] add comment object to comments/posted template
+---
  Reporter:  [EMAIL PROTECTED]   | Owner:  alsleme 
Status:  closed | Milestone:  
 Component:  HTTP handling  |   Version:  SVN 
Resolution:  invalid|  Keywords:  ortho tri cyclen
 Stage:  Accepted   | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by marvin):

  * keywords:  => ortho tri cyclen

Comment:

 http://ortho-tri-cyclen.krevetko.co.cc

-- 
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] #494: Collapse in admin interface for inline related objects

[Django]

#494: Collapse in admin interface for inline related objects
---+
  Reporter:  [EMAIL PROTECTED]   | Owner:  aptiko   
   
Status:  assigned  | Milestone:  post-1.0   
 
 Component:  django.contrib.admin  |   Version:  newforms-admin 
 
Resolution:|  Keywords:  edit_inline, 
nfa-someday
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  1 |   Needs_tests:  0  
 
Needs_better_patch:  1 |  
---+
Changes (by aptiko):

  * owner:  xian => aptiko
  * status:  new => assigned

Comment:

 SmileyChris, thanks for reviewing my patch. I'm working on 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] #5688: missing word in Windows install instructions

[Django]

#5688: missing word in Windows install instructions
--+-
  Reporter:  [EMAIL PROTECTED]  | Owner:  anonymous
Status:  closed   | Milestone:   
 Component:  Documentation|   Version:  SVN  
Resolution:  duplicate|  Keywords:   
 Stage:  Accepted | Has_patch:  1
Needs_docs:  0|   Needs_tests:  0
Needs_better_patch:  1|  
--+-
Comment (by thor574):

 I see this has not been fixed in the documentation still, it is really
 fast to fix, just add word "python" in front of "python.py install".

-- 
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] #9796: Aggregate classes unnescarily use instance attributes.

[Django]

#9796: Aggregate classes unnescarily use instance attributes.
--+-
  Reporter:  Alex | Owner: 
Status:  closed   | Milestone: 
 Component:  ORM aggregation  |   Version:  1.0
Resolution:  fixed|  Keywords: 
 Stage:  Unreviewed   | Has_patch:  0  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by russellm):

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

Comment:

 Resolved in aggregates Github branch, commit
 b60d79f001a687b71e2069adcd17c1953ef1d256.

-- 
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] #5688: missing word in Windows install instructions

[Django]

#5688: missing word in Windows install instructions
--+-
  Reporter:  [EMAIL PROTECTED]  | Owner:  anonymous
Status:  closed   | Milestone:   
 Component:  Documentation|   Version:  SVN  
Resolution:  duplicate|  Keywords:   
 Stage:  Accepted | Has_patch:  1
Needs_docs:  0|   Needs_tests:  0
Needs_better_patch:  1|  
--+-
Comment (by thor574):

 Correction:
 I see this has not been fixed in the documentation still, it is really
 fast to fix, just add word "path-to-python-dir/python" in front of
 "python.py install".
 (I use Vista)

-- 
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] #5688: missing word in Windows install instructions

[Django]

#5688: missing word in Windows install instructions
--+-
  Reporter:  [EMAIL PROTECTED]  | Owner:  anonymous
Status:  closed   | Milestone:   
 Component:  Documentation|   Version:  SVN  
Resolution:  duplicate|  Keywords:   
 Stage:  Accepted | Has_patch:  1
Needs_docs:  0|   Needs_tests:  0
Needs_better_patch:  1|  
--+-
Comment (by thor574):

 It is now hard to admit it also works without what I just said.  It works
 even better (clean display output).  I would delete my two comments if I
 could.

-- 
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] #494: Collapse in admin interface for inline related objects

[Django]

#494: Collapse in admin interface for inline related objects
---+
  Reporter:  [EMAIL PROTECTED]   | Owner:  aptiko   
   
Status:  assigned  | Milestone:  post-1.0   
 
 Component:  django.contrib.admin  |   Version:  newforms-admin 
 
Resolution:|  Keywords:  edit_inline, 
nfa-someday
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by aptiko):

  * needs_better_patch:  1 => 0
  * needs_docs:  1 => 0

Comment:

 I just uploaded an updated patch, with the following differences from the
 previous one:

  1. Previous patch would only work if the model admin contained another
 fieldset that specified "classes". I fixed this.
  2. It fixes the incorrect closing of  with .
  3. It includes the necessary changes in generic_inlineformset_factory.
  4. It includes documentation.

 Please note, however, that I have not tested
 generic_inlineformset_factory. I merely made the change and checked that
 the file compiles.

-- 
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] #9800: Syndication Framework could implement isPermaLink": "false" to better follow the recommendations of the RSS Advisory Board

[Django]

#9800: Syndication Framework could implement isPermaLink": "false"  to better
follow the recommendations of the RSS Advisory Board
---+
 Reporter:  martin <[EMAIL PROTECTED]>  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  RSS framework  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 [http://www.rssboard.org/rss-profile-1#element-channel-item-guid]

 RSS feeds should include a guid:isPermaLink": "false"  element when the
 guid is not a permalink.

 Otherwise if guid is not a link and item's link are not unique. RSS isn't
 valid.

 Take a look here: [http://www.hoboes.com/Mimsy/?ART=669]

-- 
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] #8989: Syndication Framework could implement atom:l...@rel=self to better follow the recommendations of the RSS Advisory Board

[Django]

#8989: Syndication Framework could implement atom:[EMAIL PROTECTED] to better 
follow
the recommendations of the RSS Advisory Board
+---
  Reporter:  [EMAIL PROTECTED]  | Owner:  arthurk 
Status:  assigned   | Milestone:  post-1.0
 Component:  RSS framework  |   Version:  1.0 
Resolution: |  Keywords:  
 Stage:  Accepted   | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by martin <[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
-~--~~~~--~~--~--~---

Re: [Django] #2134: [patch] add comment object to comments/posted template

[Django]

#2134: [patch] add comment object to comments/posted template
+---
  Reporter:  [EMAIL PROTECTED]   | Owner:  alsleme
Status:  closed | Milestone: 
 Component:  HTTP handling  |   Version:  SVN
Resolution:  invalid|  Keywords: 
 Stage:  Accepted   | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by Alex):

  * keywords:  ortho tri cyclen =>

-- 
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] #9801: niSJuzAemPyNGpvkMK

[Django]

#9801: niSJuzAemPyNGpvkMK
---+
Reporter:  anonymous   |   Owner:  nobody
  Status:  new |   Component:  Uncategorized 
 Version:  1.0 |Keywords:  FCvlSSYLfuvQebxMdI
   Stage:  Unreviewed  |   Has_patch:  0 
---+
 Sed9g9  http://ifdlnpohtxep.com/";>ifdlnpohtxep,
 [url=http://kkiuxqtivlcz.com/]kkiuxqtivlcz[/url],
 [link=http://aolbtiobeciz.com/]aolbtiobeciz[/link],
 http://fkffjidxqiha.com/

-- 
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] #9801: spam

[Django]

#9801: spam
+---
  Reporter:  anonymous  | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.0   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Alex):

  * status:  new => closed
 * cc: asTWxzgbrdjvMPKHlU (removed)
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * summary:  niSJuzAemPyNGpvkMK => spam
  * keywords:  FCvlSSYLfuvQebxMdI =>
  * needs_docs:  => 0
  * resolution:  => invalid

Old description:

> Sed9g9  http://ifdlnpohtxep.com/";>ifdlnpohtxep,
> [url=http://kkiuxqtivlcz.com/]kkiuxqtivlcz[/url],
> [link=http://aolbtiobeciz.com/]aolbtiobeciz[/link],
> http://fkffjidxqiha.com/

New description:

 spam

-- 
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] #9802: dluoyuGAIM

[Django]

#9802: dluoyuGAIM
+---
 Reporter:  anonymous   |   Owner:  nobody
   Status:  new |   Milestone:  post-1.0  
Component:  Uncategorized   | Version:  1.0   
 Keywords:  BZIyqJwjBBSpWKQNdd  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 De9osq  http://ttejfzxsbpzv.com/";>ttejfzxsbpzv,
 [url=http://jbziazgckkkd.com/]jbziazgckkkd[/url],
 [link=http://ymxduymwwita.com/]ymxduymwwita[/link],
 http://qzuaznrtfehx.com/

-- 
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] #9802: SPAM

[Django]

#9802: SPAM
+---
  Reporter:  anonymous  | Owner:  nobody  
Status:  closed | Milestone:  post-1.0
 Component:  Uncategorized  |   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
 * cc: qsJTxrVmhNj (removed)
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * summary:  dluoyuGAIM => SPAM
  * keywords:  BZIyqJwjBBSpWKQNdd =>
  * needs_docs:  => 0
  * resolution:  => invalid

Old description:

> De9osq  http://ttejfzxsbpzv.com/";>ttejfzxsbpzv,
> [url=http://jbziazgckkkd.com/]jbziazgckkkd[/url],
> [link=http://ymxduymwwita.com/]ymxduymwwita[/link],
> http://qzuaznrtfehx.com/

New description:

 spam

-- 
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] #9546: GenericForeignKey + model inheritance: uses wrong content type

[Django]

#9546: GenericForeignKey + model inheritance: uses wrong content type
---+
  Reporter:  miracle2k | Owner:  nobody
Status:  new   | Milestone:
 Component:  Contrib apps  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by tekNico):

 * cc: tekNico (added)
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 I've been bitten by this one 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
-~--~~~~--~~--~--~---

[Django] #9803: AuthenticationForm not showing errors.

[Django]

#9803: AuthenticationForm not showing errors.
---+
 Reporter:  anonymous  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 The view:

 {{{
 def userlogin(request):
 if request.method == "POST":
 form = forms.AuthenticationForm(request.POST)
 if form.is_valid():
 return HttpResponseRedirect(request.GET['next'])
 else:
 form = forms.AuthenticationForm()
 return render_to_response("login.html",
 {
 "form": form,
 "style":request.GET.get("style"),
 "title":"login",
 "path": request.path
 })
 }}}

 The template:
 {{{
 {% extends "template.html" %}

 {% block content %}
 login...
 browse anonymously
 otherwise.
 
 {{ form.errors }}
 
 
 {{
 form.username.label_tag }}
 {{
 form.username }}
 {{
 form.password.label_tag }}
 {{
 form.password }}
 
 
 
 
 {% endblock %}
 }}}

-- 
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] #9803: AuthenticationForm not showing errors.

[Django]

#9803: AuthenticationForm not showing errors.
+---
  Reporter:  anonymous  | Owner:  nobody
Status:  new| Milestone:
 Component:  Uncategorized  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by cgrady):

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

Comment:

 To be clear, while his example has slight issues (like not showing per-
 field errors), the form itself doesn't validate if you don't provide both
 user AND password.

 So if you leave both blank, or leave one blank, you get back a form with
 no errors, no matter how you display it.

 Only if you give both will it bother trying to validate - the fields
 should at least be required so they'll error when empty.

-- 
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] #9803: AuthenticationForm not showing errors.

[Django]

#9803: AuthenticationForm not showing errors.
+---
  Reporter:  anonymous  | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   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
  * resolution:  => invalid

Comment:

 Although no import is shown I'm assuming
 `django.contrib.auth.forms.AuthenticationForm` is what's being used here.

 The fields are required, see:
 
http://code.djangoproject.com/browser/django/tags/releases/1.0/django/contrib/auth/forms.py#L54

 where no required=False is specified for the fields so they are both
 required by default.  The problem with the posted code is the request.POST
 dictionary is being given as the first positional parameter, but for this
 form the first positional parameter is expected to be a request object.
 So the form that is created is not bound, meaning is_valid() will be false
 but also it won't have any errors.  Either pass request in as the first
 positional parameter (it's apparently used to ensure cookies are working)
 or pass request.POST as data=request.POST.

-- 
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] #8160: ModelFormset ignores form properties

[Django]

#8160: ModelFormset ignores form properties
+---
  Reporter:  andrew.mcmu...@ifi.uio.no  | Owner:  justinf 
Status:  new| Milestone:  post-1.0
 Component:  Forms  |   Version:  SVN 
Resolution: |  Keywords:  formset 
 Stage:  Accepted   | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  1   
Needs_better_patch:  0  |  
+---
Changes (by punteney):

 * cc: ja...@geniusrocket.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
-~--~~~~--~~--~--~---

[Changeset] r9644 - django/trunk/django/db/backends/oracle

[noreply]

Author: mboersma
Date: 2008-12-11 14:12:00 -0600 (Thu, 11 Dec 2008)
New Revision: 9644

Modified:
   django/trunk/django/db/backends/oracle/base.py
Log:
Reformatted PL/SQL flush left so "manage.py sqlall [app] | manage.py dbshell" 
works with Oracle.  Also some PEP8 cleanup.


Modified: django/trunk/django/db/backends/oracle/base.py
===
--- django/trunk/django/db/backends/oracle/base.py  2008-12-11 07:31:41 UTC 
(rev 9643)
+++ django/trunk/django/db/backends/oracle/base.py  2008-12-11 20:12:00 UTC 
(rev 9644)
@@ -1,7 +1,7 @@
 """
 Oracle database backend for Django.
 
-Requires cx_Oracle: http://www.python.net/crew/atuining/cx_Oracle/
+Requires cx_Oracle: http://cx-oracle.sourceforge.net/
 """
 
 import os
@@ -35,6 +35,7 @@
 
 
 class DatabaseOperations(BaseDatabaseOperations):
+
 def autoinc_sql(self, table, column):
 # To simulate auto-incrementing primary keys in Oracle, we have to
 # create a sequence and a trigger.
@@ -43,26 +44,26 @@
 tbl_name = self.quote_name(table)
 col_name = self.quote_name(column)
 sequence_sql = """
-DECLARE
-i INTEGER;
-BEGIN
-SELECT COUNT(*) INTO i FROM USER_CATALOG
-WHERE TABLE_NAME = '%(sq_name)s' AND TABLE_TYPE = 
'SEQUENCE';
-IF i = 0 THEN
-EXECUTE IMMEDIATE 'CREATE SEQUENCE "%(sq_name)s"';
-END IF;
-END;
-/""" % locals()
+DECLARE
+i INTEGER;
+BEGIN
+SELECT COUNT(*) INTO i FROM USER_CATALOG
+WHERE TABLE_NAME = '%(sq_name)s' AND TABLE_TYPE = 'SEQUENCE';
+IF i = 0 THEN
+EXECUTE IMMEDIATE 'CREATE SEQUENCE "%(sq_name)s"';
+END IF;
+END;
+/""" % locals()
 trigger_sql = """
-CREATE OR REPLACE TRIGGER "%(tr_name)s"
-BEFORE INSERT ON %(tbl_name)s
-FOR EACH ROW
-WHEN (new.%(col_name)s IS NULL)
-BEGIN
-SELECT "%(sq_name)s".nextval
-INTO :new.%(col_name)s FROM dual;
-END;
-/""" % locals()
+CREATE OR REPLACE TRIGGER "%(tr_name)s"
+BEFORE INSERT ON %(tbl_name)s
+FOR EACH ROW
+WHEN (new.%(col_name)s IS NULL)
+BEGIN
+SELECT "%(sq_name)s".nextval
+INTO :new.%(col_name)s FROM dual;
+END;
+/""" % locals()
 return sequence_sql, trigger_sql
 
 def date_extract_sql(self, lookup_type, field_name):
@@ -118,7 +119,8 @@
 # always defaults to uppercase.
 # We simplify things by making Oracle identifiers always uppercase.
 if not name.startswith('"') and not name.endswith('"'):
-name = '"%s"' % util.truncate_name(name.upper(), 
self.max_name_length())
+name = '"%s"' % util.truncate_name(name.upper(),
+   self.max_name_length())
 return name.upper()
 
 def random_function_sql(self):
@@ -150,8 +152,8 @@
 sql = ['%s %s %s;' % \
 (style.SQL_KEYWORD('DELETE'),
  style.SQL_KEYWORD('FROM'),
- style.SQL_FIELD(self.quote_name(table))
- ) for table in tables]
+ style.SQL_FIELD(self.quote_name(table)))
+for table in tables]
 # Since we've just deleted all the rows, running our sequence
 # ALTER code will reset the sequence to 0.
 for sequence_info in sequences:
@@ -179,7 +181,9 @@
 output.append(query % {'sequence': sequence_name,
'table': table_name,
'column': column_name})
-break # Only one AutoField is allowed per model, so don't 
bother continuing.
+# Only one AutoField is allowed per model, so don't
+# continue to loop
+break
 for f in model._meta.many_to_many:
 table_name = self.quote_name(f.m2m_db_table())
 sequence_name = get_sequence_name(f.m2m_db_table())
@@ -193,7 +197,8 @@
 return ''
 
 def tablespace_sql(self, tablespace, inline=False):
-return "%sTABLESPACE %s" % ((inline and "USING INDEX " or ""), 
self.quote_name(tablespace))
+return "%sTABLESPACE %s" % ((inline and "USING INDEX " or ""),
+self.quote_name(tablespace))
 
 def value_to_db_time(self, value):
 if value is None:
@@ -246,10 +251,16 @@
 if len(settings.DATABASE_HOST.strip()) == 0:
 settings.DATABASE_HOST = 'localhost'
 if len(settings.DATABASE_PORT.strip()) != 0:
-dsn = Database.makedsn(settings.DATABASE_HOST, 
int(settings.DATABASE_PORT), settings.DATABASE_NAME)
-self.connection = Database.connect(settings.DATABASE_USER, 
settings.DATABASE_PASS

[Changeset] r9645 - django/branches/releases/1.0.X/django/db/backends/oracle

[noreply]

Author: mboersma
Date: 2008-12-11 14:12:34 -0600 (Thu, 11 Dec 2008)
New Revision: 9645

Modified:
   django/branches/releases/1.0.X/django/db/backends/oracle/base.py
Log:
[1.0.X] Reformatted PL/SQL flush left so "manage.py sqlall [app] | manage.py 
dbshell" works with Oracle.  Also some PEP8 cleanup.


Modified: django/branches/releases/1.0.X/django/db/backends/oracle/base.py
===
--- django/branches/releases/1.0.X/django/db/backends/oracle/base.py
2008-12-11 20:12:00 UTC (rev 9644)
+++ django/branches/releases/1.0.X/django/db/backends/oracle/base.py
2008-12-11 20:12:34 UTC (rev 9645)
@@ -1,7 +1,7 @@
 """
 Oracle database backend for Django.
 
-Requires cx_Oracle: http://www.python.net/crew/atuining/cx_Oracle/
+Requires cx_Oracle: http://cx-oracle.sourceforge.net/
 """
 
 import os
@@ -35,6 +35,7 @@
 
 
 class DatabaseOperations(BaseDatabaseOperations):
+
 def autoinc_sql(self, table, column):
 # To simulate auto-incrementing primary keys in Oracle, we have to
 # create a sequence and a trigger.
@@ -43,26 +44,26 @@
 tbl_name = self.quote_name(table)
 col_name = self.quote_name(column)
 sequence_sql = """
-DECLARE
-i INTEGER;
-BEGIN
-SELECT COUNT(*) INTO i FROM USER_CATALOG
-WHERE TABLE_NAME = '%(sq_name)s' AND TABLE_TYPE = 
'SEQUENCE';
-IF i = 0 THEN
-EXECUTE IMMEDIATE 'CREATE SEQUENCE "%(sq_name)s"';
-END IF;
-END;
-/""" % locals()
+DECLARE
+i INTEGER;
+BEGIN
+SELECT COUNT(*) INTO i FROM USER_CATALOG
+WHERE TABLE_NAME = '%(sq_name)s' AND TABLE_TYPE = 'SEQUENCE';
+IF i = 0 THEN
+EXECUTE IMMEDIATE 'CREATE SEQUENCE "%(sq_name)s"';
+END IF;
+END;
+/""" % locals()
 trigger_sql = """
-CREATE OR REPLACE TRIGGER "%(tr_name)s"
-BEFORE INSERT ON %(tbl_name)s
-FOR EACH ROW
-WHEN (new.%(col_name)s IS NULL)
-BEGIN
-SELECT "%(sq_name)s".nextval
-INTO :new.%(col_name)s FROM dual;
-END;
-/""" % locals()
+CREATE OR REPLACE TRIGGER "%(tr_name)s"
+BEFORE INSERT ON %(tbl_name)s
+FOR EACH ROW
+WHEN (new.%(col_name)s IS NULL)
+BEGIN
+SELECT "%(sq_name)s".nextval
+INTO :new.%(col_name)s FROM dual;
+END;
+/""" % locals()
 return sequence_sql, trigger_sql
 
 def date_extract_sql(self, lookup_type, field_name):
@@ -118,7 +119,8 @@
 # always defaults to uppercase.
 # We simplify things by making Oracle identifiers always uppercase.
 if not name.startswith('"') and not name.endswith('"'):
-name = '"%s"' % util.truncate_name(name.upper(), 
self.max_name_length())
+name = '"%s"' % util.truncate_name(name.upper(),
+   self.max_name_length())
 return name.upper()
 
 def random_function_sql(self):
@@ -150,8 +152,8 @@
 sql = ['%s %s %s;' % \
 (style.SQL_KEYWORD('DELETE'),
  style.SQL_KEYWORD('FROM'),
- style.SQL_FIELD(self.quote_name(table))
- ) for table in tables]
+ style.SQL_FIELD(self.quote_name(table)))
+for table in tables]
 # Since we've just deleted all the rows, running our sequence
 # ALTER code will reset the sequence to 0.
 for sequence_info in sequences:
@@ -179,7 +181,9 @@
 output.append(query % {'sequence': sequence_name,
'table': table_name,
'column': column_name})
-break # Only one AutoField is allowed per model, so don't 
bother continuing.
+# Only one AutoField is allowed per model, so don't
+# continue to loop
+break
 for f in model._meta.many_to_many:
 table_name = self.quote_name(f.m2m_db_table())
 sequence_name = get_sequence_name(f.m2m_db_table())
@@ -193,7 +197,8 @@
 return ''
 
 def tablespace_sql(self, tablespace, inline=False):
-return "%sTABLESPACE %s" % ((inline and "USING INDEX " or ""), 
self.quote_name(tablespace))
+return "%sTABLESPACE %s" % ((inline and "USING INDEX " or ""),
+self.quote_name(tablespace))
 
 def value_to_db_time(self, value):
 if value is None:
@@ -246,10 +251,16 @@
 if len(settings.DATABASE_HOST.strip()) == 0:
 settings.DATABASE_HOST = 'localhost'
 if len(settings.DATABASE_PORT.strip()) != 0:
-dsn = Database.makedsn(settings.DATABASE_HOST, 
int(settings.DATABASE_PORT), settings.DATABASE_NAME)
-self.c

[Django] #9804: sqlflush fails for ManyToMany with inherited intermediary

[Django]

#9804: sqlflush fails for ManyToMany with inherited intermediary
-+--
 Reporter:  jdimov   |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Database layer (models, ORM) | Version:  1.0   
 Keywords:  ManyToMany, sqlflush, sequence_list  |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 There's a bug in the sequence_list method of
 django.db.backends.BaseDatabaseIntrospection, but I don't know how to fix
 it.  It has to do with Many-to-Many relationships through intermediary
 models, where the intermediary model itself is inherited from a non-
 abstract base model.  In this case, the sequnece_list contains id sequence
 counter which do not (and should not) actually exist, because the model
 uses the base model's id counter.

 The result of all this is that the manage.py sqlflush command fails, and I
 can't run my tests.

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

[Django] #9805: reverse() does not add SCRIPT_NAME to the returned URL if called from modules that contain middleware

[Django]

#9805: reverse() does not add SCRIPT_NAME to the returned URL if called from
modules that contain middleware
+---
 Reporter:  ElliottM|   Owner:  nobody
   Status:  new |   Milestone:
Component:  Core framework  | Version:  1.0   
 Keywords:  |   Stage:  Unreviewed
Has_patch:  1   |  
+---
 For example, take the following middleware.py file, with one example
 middleware thing that redirects you to the login page if you are not
 logged in:

 {{{login_url=reverse('login')

 class LoginMiddleware():
 def process_request(self, request):
 if(request.user.is_anonymous() and
 request.path!=login_url):
 #force login
 return
 HttpResponseRedirect(login_url+'?next='+request.path)}}}

 In this case, login_url will be correct except for the fact that it will
 be missing the SCRIPT_NAME. Putting the reverse() call inside the
 process_request function solves the problem, but it makes no sense at all
 to call that reverse function for every request when it can be called once
 at server startup.

 The cause is in django.core.handles.wsgi and
 django.core.handlers.modpython

 {{{
 if self._request_middleware is None:
self.load_middleware()

 set_script_prefix(req.get_options().get('django.root', ''))
 }}}

 As you can see, "set_script_prefix" is called AFTER middleware is loaded,
 so the script name is still unset when reverse() is called in the
 middleware above. Moving the set_script_prefix call above the
 load_middleware function solves 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] #9805: reverse() does not add SCRIPT_NAME to the returned URL if called from middleware modules

[Django]

#9805: reverse() does not add SCRIPT_NAME to the returned URL if called from
middleware modules
-+--
  Reporter:  ElliottM| Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:  1.0   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by ElliottM):

  * needs_better_patch:  => 0
  * summary:  reverse() does not add SCRIPT_NAME to the returned URL if
  called from modules that contain middleware =>
  reverse() does not add SCRIPT_NAME to the
  returned URL if called from middleware modules
  * 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
-~--~~~~--~~--~--~---

[Django] #9806: GeometryField crashes contrib.gis.admin

[Django]

#9806: GeometryField crashes contrib.gis.admin
---+
 Reporter:  ingenieroariel |   Owner:  nobody
   Status:  new|   Milestone:
Component:  GIS| Version:  1.0   
 Keywords:  admin, gis, GeometryField  |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 I tried to load this basic model in django.contrib.gis admin and I ended
 up with a:
 {{{Exception Value: Invalid OGR String Type "GEOMETRY"}}}
 {{{
 class SimpleGeo(models.Model):
  geom = models.GeometryField(null=True, blank=True)

 admin.site.register(SimpleGeo, admin.GeoModelAdmin)
 }}}

 I have inserted two objects, a Point and a Polygon and when using the
 shell,
 I got the correct geom_type in both cases and dir listed the right
 attributes and methods for each field.

 The line that triggers the error is:
 
[http://code.djangoproject.com/browser/django/trunk/django/contrib/gis/admin/options.py#L84
 'geom_type' : OGRGeomType(db_field._geom), in
 django/contrib/gis/admin/options.py#L84]

 I think one of two things should happen:
  * 1. Either the admin defaults to showing a plain text field whenever
 that happens or
  * 2. (pony alert) we find a way to look for the _geom of the instance and
 not the class.

 Full traceback below:
 {{{
 Traceback:
 File "/Library/Python/2.5/site-packages/django/core/handlers/base.py" in
 get_response
   86. response = callback(request, *callback_args,
 **callback_kwargs)
 File "/Library/Python/2.5/site-packages/django/contrib/admin/sites.py" in
 root
   158. return self.model_page(request, *url.split('/', 2))
 File "/Library/Python/2.5/site-packages/django/views/decorators/cache.py"
 in _wrapped_view_func
   44. response = view_func(request, *args, **kwargs)
 File "/Library/Python/2.5/site-packages/django/contrib/admin/sites.py" in
 model_page
   177. return admin_obj(request, rest_of_url)
 File "/Library/Python/2.5/site-packages/django/contrib/admin/options.py"
 in __call__
   197. return self.change_view(request, unquote(url))
 File "/Library/Python/2.5/site-packages/django/db/transaction.py" in
 _commit_on_success
   238. res = func(*args, **kw)
 File "/Library/Python/2.5/site-packages/django/contrib/admin/options.py"
 in change_view
   573. ModelForm = self.get_form(request, obj)
 File "/Library/Python/2.5/site-packages/django/contrib/admin/options.py"
 in get_form
   277. return modelform_factory(self.model, **defaults)
 File "/Library/Python/2.5/site-packages/django/forms/models.py" in
 modelform_factory
   318.   'formfield_callback':
 formfield_callback})
 File "/Library/Python/2.5/site-packages/django/forms/models.py" in __new__
   180.   opts.exclude,
 formfield_callback)
 File "/Library/Python/2.5/site-packages/django/forms/models.py" in
 fields_for_model
   147. formfield = formfield_callback(f)
 File "/Library/Python/2.5/site-
 packages/django/contrib/gis/admin/options.py" in formfield_for_dbfield
   58. kwargs['widget'] = self.get_map_widget(db_field)
 File "/Library/Python/2.5/site-
 packages/django/contrib/gis/admin/options.py" in get_map_widget
   76. class OLMap(self.widget):
 File "/Library/Python/2.5/site-
 packages/django/contrib/gis/admin/options.py" in OLMap
   84.   'geom_type' : OGRGeomType(db_field._geom),
 File "/Library/Python/2.5/site-
 packages/django/contrib/gis/gdal/geomtype.py" in __init__
   29. raise OGRException('Invalid OGR String Type "%s"' %
 type_input)
 }}}

-- 
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] #9807: GeometryField crashes contrib.gis.admin

[Django]

#9807: GeometryField crashes contrib.gis.admin
---+
 Reporter:  ingenieroariel |   Owner:  nobody
   Status:  new|   Milestone:
Component:  GIS| Version:  1.0   
 Keywords:  admin, gis, GeometryField  |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 I tried to load this basic model in django.contrib.gis admin and I ended
 up with a:
 {{{Exception Value: Invalid OGR String Type "GEOMETRY"}}}
 {{{
 class SimpleGeo(models.Model):
  geom = models.GeometryField(null=True, blank=True)

 admin.site.register(SimpleGeo, admin.GeoModelAdmin)
 }}}

 I have inserted two objects, a Point and a Polygon and when using the
 shell,
 I got the correct geom_type in both cases and dir listed the right
 attributes and methods for each field.

 The line that triggers the error is:
 
[http://code.djangoproject.com/browser/django/trunk/django/contrib/gis/admin/options.py#L84
 'geom_type' : OGRGeomType(db_field._geom), in
 django/contrib/gis/admin/options.py#L84]

 I think one of two things should happen:
  * 1. Either the admin defaults to showing a plain text field whenever
 that happens or
  * 2. (pony alert) we find a way to look for the _geom of the instance and
 not the class.

 Full traceback below:
 {{{
 Traceback:
 File "/Library/Python/2.5/site-packages/django/core/handlers/base.py" in
 get_response
   86. response = callback(request, *callback_args,
 **callback_kwargs)
 File "/Library/Python/2.5/site-packages/django/contrib/admin/sites.py" in
 root
   158. return self.model_page(request, *url.split('/', 2))
 File "/Library/Python/2.5/site-packages/django/views/decorators/cache.py"
 in _wrapped_view_func
   44. response = view_func(request, *args, **kwargs)
 File "/Library/Python/2.5/site-packages/django/contrib/admin/sites.py" in
 model_page
   177. return admin_obj(request, rest_of_url)
 File "/Library/Python/2.5/site-packages/django/contrib/admin/options.py"
 in __call__
   197. return self.change_view(request, unquote(url))
 File "/Library/Python/2.5/site-packages/django/db/transaction.py" in
 _commit_on_success
   238. res = func(*args, **kw)
 File "/Library/Python/2.5/site-packages/django/contrib/admin/options.py"
 in change_view
   573. ModelForm = self.get_form(request, obj)
 File "/Library/Python/2.5/site-packages/django/contrib/admin/options.py"
 in get_form
   277. return modelform_factory(self.model, **defaults)
 File "/Library/Python/2.5/site-packages/django/forms/models.py" in
 modelform_factory
   318.   'formfield_callback':
 formfield_callback})
 File "/Library/Python/2.5/site-packages/django/forms/models.py" in __new__
   180.   opts.exclude,
 formfield_callback)
 File "/Library/Python/2.5/site-packages/django/forms/models.py" in
 fields_for_model
   147. formfield = formfield_callback(f)
 File "/Library/Python/2.5/site-
 packages/django/contrib/gis/admin/options.py" in formfield_for_dbfield
   58. kwargs['widget'] = self.get_map_widget(db_field)
 File "/Library/Python/2.5/site-
 packages/django/contrib/gis/admin/options.py" in get_map_widget
   76. class OLMap(self.widget):
 File "/Library/Python/2.5/site-
 packages/django/contrib/gis/admin/options.py" in OLMap
   84.   'geom_type' : OGRGeomType(db_field._geom),
 File "/Library/Python/2.5/site-
 packages/django/contrib/gis/gdal/geomtype.py" in __init__
   29. raise OGRException('Invalid OGR String Type "%s"' %
 type_input)
 }}}

-- 
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] #9807: GeometryField crashes contrib.gis.admin

[Django]

#9807: GeometryField crashes contrib.gis.admin
-+--
  Reporter:  ingenieroariel  | Owner:  nobody   
Status:  closed  | Milestone:   
 Component:  GIS |   Version:  1.0  
Resolution:  duplicate   |  Keywords:  admin, gis, GeometryField
 Stage:  Unreviewed  | Has_patch:  0
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Changes (by ingenieroariel):

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

Comment:

 Duplicate of #9806

-- 
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] #1946: [patch] to allow overriding of default sequence name

[Django]

#1946: [patch] to allow overriding of default sequence name
---+
  Reporter:  ab...@cabal.org.uk| Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  1 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Changes (by robhudson):

 * cc: treborhud...@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] #8906: django.contrib.auth settings.py URL's aren't portable

[Django]

#8906: django.contrib.auth settings.py URL's aren't portable
-+--
  Reporter:  levity  | Owner:  lygaret
Status:  assigned| Milestone: 
 Component:  Authentication  |   Version:  1.0
Resolution:  |  Keywords: 
 Stage:  Unreviewed  | Has_patch:  0  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by lygaret):

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

Comment:

 Hey a couple of us here ran into this and coded up a quick

-- 
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] #8906: django.contrib.auth settings.py URL's aren't portable

[Django]

#8906: django.contrib.auth settings.py URL's aren't portable
-+--
  Reporter:  levity  | Owner:  lygaret
Status:  assigned| Milestone: 
 Component:  Authentication  |   Version:  1.0
Resolution:  |  Keywords: 
 Stage:  Unreviewed  | Has_patch:  1  
Needs_docs:  0   |   Needs_tests:  1  
Needs_better_patch:  0   |  
-+--
Changes (by lygaret):

  * has_patch:  0 => 1
  * needs_tests:  0 => 1

Comment:

 Er, didn't get the comment finished...

 Anyway, we coded up a quick patch, and the built in tests are working. I'm
 having trouble figuring out how to write a test that will invoke the
 @login_required decorator though, so if anyone would like to give us a
 hand that would be great.

 The test cases are as follows:

  1. Ensure that a view decorated with @login_required redirects to
 settings.LOGIN_URL when get_script_prefix() is ''
  2. Ensure that, after set_script_prefix('/some/long/path'),
 @login_required redirects to /some/long/path/ + settings.LOGIN_URL
  3. Ensure that, after logging in with no next? parameter, the login form
 redirects you to settings.LOGIN_REDIRECT_URL when get_script_prefix() is
 ''
  4. Ensure that, after logging in with no next? parameter, the login form
 redirects you to /some/long/path + settings.LOGIN_REDIRECT_URL when the
 script_prefix is set
  5. Ensure that, after logging in with a next? parameter, the login form
 redirects you to the next? parameter with no change to the path,
 irrespective of script_prefix

-- 
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] #8906: django.contrib.auth settings.py URL's aren't portable

[Django]

#8906: django.contrib.auth settings.py URL's aren't portable
-+--
  Reporter:  levity  | Owner: 
Status:  new | Milestone: 
 Component:  Authentication  |   Version:  1.0
Resolution:  |  Keywords: 
 Stage:  Unreviewed  | Has_patch:  1  
Needs_docs:  0   |   Needs_tests:  1  
Needs_better_patch:  0   |  
-+--
Changes (by lygaret):

  * owner:  lygaret =>
  * status:  assigned => new

Comment:

 After being told on IRC that it's not worth pursuing, nevermind then.

-- 
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] #9808: UXAPqeof

[Django]

#9808: UXAPqeof
---+
Reporter:  anonymous   |   Owner:  nobody   
  Status:  new |   Component:  Uncategorized
 Version:  1.0 |Keywords:  fjPAPBBxNkLEn
   Stage:  Unreviewed  |   Has_patch:  0
---+
 A0PPIJ  http://dhribwuoejer.com/";>dhribwuoejer,
 [url=http://lfqdksjdtmig.com/]lfqdksjdtmig[/url],
 [link=http://sgsijglfaygw.com/]sgsijglfaygw[/link],
 http://miuhbvkmpwzd.com/

-- 
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] #9809: BbFYtVfthYhSyq

[Django]

#9809: BbFYtVfthYhSyq
---+
 Reporter:  anonymous  |   Owner:  nobody
   Status:  new|   Milestone:  post-1.0  
Component:  Uncategorized  | Version:  1.0   
 Keywords:  aCCiwyFdgvm|   Stage:  Unreviewed
Has_patch:  0  |  
---+
 BdKfAh  http://xqtprzqywhci.com/";>xqtprzqywhci,
 [url=http://jhjktmnilvdx.com/]jhjktmnilvdx[/url],
 [link=http://eeaoxwdquhon.com/]eeaoxwdquhon[/link],
 http://yikqudgnbbdc.com/

-- 
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] #9808: spam

[Django]

#9808: spam
+---
  Reporter: | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.0   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Alex):

  * status:  new => closed
  * reporter:  anonymous =>
 * cc: ZPUtUzeEXHMmnRUqWcd (removed)
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * summary:  UXAPqeof => spam
  * keywords:  fjPAPBBxNkLEn =>
  * needs_docs:  => 0
  * resolution:  => invalid

Old description:

> A0PPIJ  http://dhribwuoejer.com/";>dhribwuoejer,
> [url=http://lfqdksjdtmig.com/]lfqdksjdtmig[/url],
> [link=http://sgsijglfaygw.com/]sgsijglfaygw[/link],
> http://miuhbvkmpwzd.com/

New description:

 spam

-- 
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] #9809: spam

[Django]

#9809: spam
+---
  Reporter: | Owner:  nobody  
Status:  closed | Milestone:  post-1.0
 Component:  Uncategorized  |   Version:  1.0 
Resolution:  invalid|  Keywords:  
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by Alex):

  * status:  new => closed
  * reporter:  anonymous =>
 * cc: gCaRfBFnbRRDKG (removed)
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * summary:  BbFYtVfthYhSyq => spam
  * keywords:  aCCiwyFdgvm =>
  * needs_docs:  => 0
  * resolution:  => invalid

Old description:

> BdKfAh  http://xqtprzqywhci.com/";>xqtprzqywhci,
> [url=http://jhjktmnilvdx.com/]jhjktmnilvdx[/url],
> [link=http://eeaoxwdquhon.com/]eeaoxwdquhon[/link],
> http://yikqudgnbbdc.com/

New description:

 spam

-- 
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] #9799: django.db.models.sql.query.BaseQuery.get_count() works wrong with GROUP BY

[Django]

#9799: django.db.models.sql.query.BaseQuery.get_count() works wrong with GROUP 
BY
---+
  Reporter:  syabro| Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.0   
Resolution:  wontfix   |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by mtredinnick):

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

Comment:

 This is true, but it's not currently intended to work with group_by. This
 is noted in the comment where the count query is set up. Making this work
 is part of the broader "adding aggregation" support to Django scheduled
 for 1.1. You'll want to follow #3566 for progress on that if you're
 interested.

 Closing as wontfix, since the limitation is intentional, and the API
 you're using is not public API (there's no public group_by API at the
 moment) and we're developing the public API in #3566.

-- 
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] #9805: reverse() does not add SCRIPT_NAME to the returned URL if called from middleware modules

[Django]

#9805: reverse() does not add SCRIPT_NAME to the returned URL if called from
middleware modules
-+--
  Reporter:  ElliottM| Owner:  mtredinnick
Status:  new | Milestone: 
 Component:  Core framework  |   Version:  1.0
Resolution:  |  Keywords: 
 Stage:  Unreviewed  | Has_patch:  1  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by mtredinnick):

  * owner:  nobody => mtredinnick

Old description:

> For example, take the following middleware.py file, with one example
> middleware thing that redirects you to the login page if you are not
> logged in:
>
> {{{login_url=reverse('login')
>
> class LoginMiddleware():
> def process_request(self, request):
> if(request.user.is_anonymous() and
> request.path!=login_url):
> #force login
> return
> HttpResponseRedirect(login_url+'?next='+request.path)}}}
>
> In this case, login_url will be correct except for the fact that it will
> be missing the SCRIPT_NAME. Putting the reverse() call inside the
> process_request function solves the problem, but it makes no sense at all
> to call that reverse function for every request when it can be called
> once at server startup.
>
> The cause is in django.core.handles.wsgi and
> django.core.handlers.modpython
>
> {{{
> if self._request_middleware is None:
>self.load_middleware()
>
> set_script_prefix(req.get_options().get('django.root', ''))
> }}}
>
> As you can see, "set_script_prefix" is called AFTER middleware is loaded,
> so the script name is still unset when reverse() is called in the
> middleware above. Moving the set_script_prefix call above the
> load_middleware function solves the problem.

New description:

 For example, take the following middleware.py file, with one example
 middleware thing that redirects you to the login page if you are not
 logged in:

 {{{
 #!python
 login_url=reverse('login')

 class LoginMiddleware():
 def process_request(self, request):
 if(request.user.is_anonymous() and
 request.path!=login_url):
 #force login
 return
 HttpResponseRedirect(login_url+'?next='+request.path)
 }}}

 In this case, login_url will be correct except for the fact that it will
 be missing the SCRIPT_NAME. Putting the reverse() call inside the
 process_request function solves the problem, but it makes no sense at all
 to call that reverse function for every request when it can be called once
 at server startup.

 The cause is in django.core.handles.wsgi and
 django.core.handlers.modpython

 {{{
 #!python
 if self._request_middleware is None:
self.load_middleware()

 set_script_prefix(req.get_options().get('django.root', ''))
 }}}

 As you can see, "set_script_prefix" is called AFTER middleware is loaded,
 so the script name is still unset when reverse() is called in the
 middleware above. Moving the set_script_prefix call above the
 load_middleware function solves the problem.

Comment:

 (Fixed description formatting.)

 This isn't really fixing the problem, so much as hiding it. Loading the
 middlewares should not require access to SCRIPT_NAME (it can change
 between requests and the middleware is only loaded once). So the code you
 give actually contains a small bug -- probably not observable for
 something like the "logout" view, but a bug nonetheless, as it could
 reverse to a different URL for a different request.

 There's a metnion in another ticket that we might add a kind of "lazy"
 reverse() that resolves upon usage, rather than declaration. When I find
 that ticket, I'll drop in a comment here and wontfix this one. Leaving
 open for now to remind me to hunt down the other case.

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

[Django] #9810: HzVLErrfE

[Django]

#9810: HzVLErrfE
---+
Reporter:  anonymous   |   Owner:  nobody  
  Status:  new |   Component:  Uncategorized   
 Version:  1.0 |Keywords:  hpXBBBEogoQPlpzz
   Stage:  Unreviewed  |   Has_patch:  0   
---+
 rVpJgx  http://cxynpwpljqrx.com/";>cxynpwpljqrx,
 [url=http://floqijvdrcxp.com/]floqijvdrcxp[/url],
 [link=http://ixgvrndcohij.com/]ixgvrndcohij[/link],
 http://ujrkxlmwqihe.com/

-- 
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] #9811: HDQxWBQpwIVAlVN

[Django]

#9811: HDQxWBQpwIVAlVN
---+
Reporter:  anonymous   |   Owner:  nobody   
  Status:  new |   Component:  Uncategorized
 Version:  1.0 |Keywords:  zHwedqJtxo   
   Stage:  Unreviewed  |   Has_patch:  0
---+
 YZuO7S  http://lcttcgkcdfch.com/";>lcttcgkcdfch,
 [url=http://ddhovbnjwuww.com/]ddhovbnjwuww[/url],
 [link=http://ygrroirvkhot.com/]ygrroirvkhot[/link],
 http://brkfptehgwqd.com/

-- 
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] #9811: SPAM

[Django]

#9811: SPAM
+---
  Reporter:  anonymous  | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   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
 * cc: vnfAAXZZMj (removed)
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * summary:  HDQxWBQpwIVAlVN => SPAM
  * keywords:  zHwedqJtxo =>
  * needs_docs:  => 0
  * resolution:  => invalid

Old description:

> YZuO7S  http://lcttcgkcdfch.com/";>lcttcgkcdfch,
> [url=http://ddhovbnjwuww.com/]ddhovbnjwuww[/url],
> [link=http://ygrroirvkhot.com/]ygrroirvkhot[/link],
> http://brkfptehgwqd.com/

New description:

 spam

-- 
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] #9810: SPAM

[Django]

#9810: SPAM
+---
  Reporter:  anonymous  | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   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
 * cc: TpCoXyRYN (removed)
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * summary:  HzVLErrfE => SPAM
  * keywords:  hpXBBBEogoQPlpzz =>
  * needs_docs:  => 0
  * resolution:  => invalid

Old description:

> rVpJgx  http://cxynpwpljqrx.com/";>cxynpwpljqrx,
> [url=http://floqijvdrcxp.com/]floqijvdrcxp[/url],
> [link=http://ixgvrndcohij.com/]ixgvrndcohij[/link],
> http://ujrkxlmwqihe.com/

New description:

 spam

-- 
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] #9812: zdNlZpqOdMna

[Django]

#9812: zdNlZpqOdMna
---+
Reporter:  anonymous   |   Owner:  nobody   
  Status:  new |   Component:  Uncategorized
 Version:  1.0 |Keywords:  wrxMJSlLNm   
   Stage:  Unreviewed  |   Has_patch:  0
---+
 RbeN21  http://gbbxkbrrbsso.com/";>gbbxkbrrbsso,
 [url=http://zcjjohrurrad.com/]zcjjohrurrad[/url],
 [link=http://bfiozvnrdcyn.com/]bfiozvnrdcyn[/link],
 http://juivaqnoxxer.com/

-- 
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] #9813: nCOtOqOHspvFw

[Django]

#9813: nCOtOqOHspvFw
---+
Reporter:  anonymous   |   Owner:  nobody  
  Status:  new |   Component:  Uncategorized   
 Version:  1.0 |Keywords:  fnIjvCpwNGxcFHwe
   Stage:  Unreviewed  |   Has_patch:  0   
---+
 1bLXDB  http://bxaisicficih.com/";>bxaisicficih,
 [url=http://fgsvjbaybipw.com/]fgsvjbaybipw[/url],
 [link=http://pbygidjflgdh.com/]pbygidjflgdh[/link],
 http://ggjfhmgiogye.com/

-- 
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] #9812: spam

[Django]

#9812: spam
+---
  Reporter: | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.0   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Alex):

  * status:  new => closed
  * reporter:  anonymous =>
 * cc: QaqQoAWVBnysODq (removed)
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * summary:  zdNlZpqOdMna => spam
  * keywords:  wrxMJSlLNm =>
  * needs_docs:  => 0
  * resolution:  => invalid

Old description:

> RbeN21  http://gbbxkbrrbsso.com/";>gbbxkbrrbsso,
> [url=http://zcjjohrurrad.com/]zcjjohrurrad[/url],
> [link=http://bfiozvnrdcyn.com/]bfiozvnrdcyn[/link],
> http://juivaqnoxxer.com/

New description:

 spam

-- 
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] #9813: spam

[Django]

#9813: spam
+---
  Reporter: | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.0   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Alex):

  * status:  new => closed
  * reporter:  anonymous =>
 * cc: pIuXGmfDHxrwkiEEEa (removed)
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * summary:  nCOtOqOHspvFw => spam
  * keywords:  fnIjvCpwNGxcFHwe =>
  * needs_docs:  => 0
  * resolution:  => invalid

Old description:

> 1bLXDB  http://bxaisicficih.com/";>bxaisicficih,
> [url=http://fgsvjbaybipw.com/]fgsvjbaybipw[/url],
> [link=http://pbygidjflgdh.com/]pbygidjflgdh[/link],
> http://ggjfhmgiogye.com/

New description:

 spam

-- 
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] #9814: Python 2.6's sqlite refuses 8-bit SafeStrings

[Django]

#9814: Python 2.6's sqlite refuses 8-bit SafeStrings
--+-
 Reporter:  kmtracey  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  1.0   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 r9467/r9469 modified a test in modeltests/field_defaults to set a field
 value to a utf-8 encoded !SafeString.  This test now fails on Python 2.6
 when using sqlite as the backend:

 {{{
 ==
 FAIL: Doctest: modeltests.field_defaults.models.__test__.API_TESTS
 --
 Traceback (most recent call last):
   File "d:\u\kmt\django\trunk\django\test\_doctest.py", line 2180, in
 runTest
 raise self.failureException(self.format_failure(new.getvalue()))
 AssertionError: Failed doctest test for
 modeltests.field_defaults.models.__test__.API_TESTS
   File "D:\u\kmt\django\trunk\tests\modeltests\field_defaults\models.py",
 line unknown line number, in API_TESTS

 --
 File "D:\u\kmt\django\trunk\tests\modeltests\field_defaults\models.py",
 line ?, in modeltests.field_defaults.models.__test__.API_TESTS
 Failed example:
 a.save()
 Exception raised:
 Traceback (most recent call last):
   File "d:\u\kmt\django\trunk\django\test\_doctest.py", line 1267, in
 __run
 compileflags, 1) in test.globs
   File "", line 1, in
 
 a.save()
   File "d:\u\kmt\django\trunk\django\db\models\base.py", line 328, in
 save
 self.save_base(force_insert=force_insert,
 force_update=force_update)
   File "d:\u\kmt\django\trunk\django\db\models\base.py", line 379, in
 save_base
 rows = manager.filter(pk=pk_val)._update(values)
   File "d:\u\kmt\django\trunk\django\db\models\query.py", line 435, in
 _update
 return query.execute_sql(None)
   File "d:\u\kmt\django\trunk\django\db\models\sql\subqueries.py",
 line 117, in execute_sql
 cursor = super(UpdateQuery, self).execute_sql(result_type)
   File "d:\u\kmt\django\trunk\django\db\models\sql\query.py", line
 1756, in execute_sql
 cursor.execute(sql, params)
   File "d:\u\kmt\django\trunk\django\db\backends\sqlite3\base.py",
 line 169, in execute
 return Database.Cursor.execute(self, query, params)
 ProgrammingError: You must not use 8-bit bytestrings unless you use a
 text_factory that can interpret 8-bit bytestrings (like text_factory =
 str). It is highly recommended that you instead just switch your
 application to Unicode strings.

 --
 Ran 1 test in 0.030s

 FAILED (failures=1)
 }}}

 This can be fixed as regular `str` was fixed for Python 2.6 (r8276) by
 adding `Database.register_adapter(SafeString, lambda s:s.decode('utf-8'))`
 to the appropriate spot in django/db/sqlite3/base.py.  That seems correct
 but just in case I'm missing something I figured I'd check first before
 just doing it.  (I'm not entirely sure when app code would be sending
 !SafeStrings to the DB, but I suppose it can happen and should be
 supported?) Feedback?

-- 
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] #9814: Python 2.6's sqlite refuses 8-bit SafeStrings

[Django]

#9814: Python 2.6's sqlite refuses 8-bit SafeStrings
---+
  Reporter:  kmtracey  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   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:

 This looks like another case like MySQL, where it's doing a bad type
 check. `isinstance(SafeString, str)` is `True`, so it should just work
 with safe strings as strings if it needs strings, like everything else
 does.

 It's not illegal to use `SafeString` wherever all good strings are
 accepted (much like American Express :-) ), so we have to fix this.
 However, if it's only `SafeString` that's the problem, we don't need any
 decoding or encoding. It's already required to be a bytestring, since it's
 a "str" subclass, not a "unicode" subclass. Thus, simple `str()` on the
 object will be the right thing, I suspect.

 Don't have time to test this out now. Only wanted to note that I think (a)
 we should add the adaptor if that's really required, (b) I'm still not
 loving the Python 2.6 developers because this should be completely
 unnecessary as we're already giving them something that acts as a str, and
 (c) we should check `SafeUnicode` for equivalent issues (and if the fact
 that `SafeUnicode` is a unicode means it gets a free ride, please refer to
 point (b)).

-- 
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] #8138: Switch django tests to use transactions

[Django]

#8138: Switch django tests to use transactions
+---
  Reporter:  mremolt| Owner:  nobody  
Status:  new| Milestone:  post-1.0
 Component:  Testing framework  |   Version:  SVN 
Resolution: |  Keywords:  
 Stage:  Accepted   | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Comment (by kmtracey):

 I updated the diff to reasonably current trunk level (it no longer needs
 to include the loaddata change since that function was added to loaddata
 in r8336). I get no failures with that diff and sqlite as the backend.

 Couple of others I've tried:

 MySQL/InnoDB -- I get a  couple of failures in addition to the ones
 "normally" seen in the test suite for that combo.  First, the auth tests
 that use the login() function defined in the test fail because it seems
 the subsequent call doesn't see the session changes that were supposed to
 be made by login().  Switching these tests to use the test client login
 function makes the failures go away (as does using the file session
 backend), so that may be one way to fix these, though I'd like to
 understand it better.  Second, some of the comment testcases are written
 to assume pk's starting at 1 for posted comments.  However on InnoDB
 rolling back a transaction does not roll back the autoincrement sequence
 numbers (see http://bugs.mysql.com/bug.php?id=6714, closed wontfix), so
 when using rollback the comment testcases get a failure due to pk's not
 getting assigned as expected.  Not sure how to fix that one.

 MySQL/MyISAM -- What's supposed to be happening here?  Since transactions
 aren't supported I think we continue to need to use the old way, but we
 don't seem to with the current patch (multiple failures/errors I did not
 look into because unless we're doing something to avoid the rollback use
 in this case I don't see how it would work).  Am I right in thinking we
 need to somehow avoid trying the rollback approach for this combo?

 Postgres, Oracle not tried yet.  Running the old code on the machine where
 I have Postgres (very old tired machine) took 8 hours (!) and Oracle (on a
 different, but still not exactly peppy) machine in brief tests has seemed
 slow as molassas so I may not have the horsepower required to track down
 much on those backends.

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

Re: [Django] #9814: Python 2.6's sqlite refuses 8-bit SafeStrings

[Django]

#9814: Python 2.6's sqlite refuses 8-bit SafeStrings
---+
  Reporter:  kmtracey  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by kmtracey):

 Trying `Database.register_adapter(SafeString, lambda s:str(s))` doesn't
 work.  I'm thinking it doesn't then go through the registered adapters
 again and see that `str`'s have their own adapter (which does a utf-8
 decode)?

 It has no problem with `SafeUnicode`, apparently, since a couple of lines
 prior to the test line that is causing the current failure is saving of a
 field set to a `SafeUnicode` value.  It may be just when it is searching
 through adapters that it isn't really matching properly (we don't have to
 register an adapter for unicode).  I'll look at it again when I'm more
 awake in the AM.

-- 
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] #2134: [patch] add comment object to comments/posted template

[Django]

#2134: [patch] add comment object to comments/posted template
+---
  Reporter:  m...@hudora.de   | Owner:  alsleme
Status:  closed | Milestone: 
 Component:  HTTP handling  |   Version:  SVN
Resolution:  invalid|  Keywords: 
 Stage:  Accepted   | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Comment (by marvin):

 http://nekto.prv.pl/ortho/index.html ortho tri cyclen
 http://nekto.prv.pl/ortho/ortho-tri-cyclen.html ortho tri cyclen
 http://nekto.prv.pl/ortho/facts-about-ortho-tri-cyclen.html facts about
 ortho tri cyclen
 http://nekto.prv.pl/ortho/ortho-tri-cyclen-lo.html ortho tri cyclen lo
 http://nekto.prv.pl/ortho/buy-ortho-tri-cyclen.html buy ortho tri cyclen
 http://nekto.prv.pl/ortho/ortho-tri-cyclen-low.html ortho tri cyclen low

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