date:20120105

[Django] #17506: Minor tidyup in session DB backend

2012-01-05 Thread Django

#17506: Minor tidyup in session DB backend
--+-
 Reporter:  FunkyBob  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  contrib.sessions  |Version:  SVN
 Severity:  Normal|   Keywords:  session
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  1 |  UI/UX:  0
--+-
 The ORM docs suggest using exists() can be more efficient than
 try:get()/except:

 Here's a patch to do just that in the session DB backend.

-- 
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] #17505: import typo

2012-01-05 Thread Django

#17505: import typo
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.3
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by carljm):

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


Comment:

 You are using the development documentation with Django 1.3. Use the
 Django 1.3 docs instead. In the development version of Django,
 "django.conf.urls" is correct.

-- 
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] #17505: import typo

2012-01-05 Thread Django

#17505: import typo
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.3
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 On https://docs.djangoproject.com/en/dev/intro/tutorial04/

 Section:

 Change it like so:
 from django.conf.urls import patterns, include, url

 "from django.conf.urls" should be "from django.conf.urls.defaults"

-- 
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] #17498: meta option "no_index"

2012-01-05 Thread Django

#17498: meta option "no_index"
---+--
 Reporter:  kace   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  1.2
 Severity:  Normal |   Resolution:
 Keywords:  admin  | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by kace):

 * needs_better_patch:  1 => 0


Comment:

 I just attached a new patch that implements in a cleaner way.  Only
 touches "django/contrib/admin/sites.py" and
 "django/contrib/admin/options.py" and changes/adds three lines of code.
 Could be easily ported to other versions I think.  To suppress indexing,
 one adds the option "no_index=True" to the "admin.site.register" function
 (as proposed in previous comment).

-- 
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] #17504: User.objects.create_user() wrong email domain part identification

2012-01-05 Thread Django

#17504: User.objects.create_user() wrong email domain part identification
--+
 Reporter:  fero  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by aaugustin):

 * needs_tests:  0 => 1
 * easy:  0 => 1
 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #17504: User.objects.create_user() wrong email domain part identification

2012-01-05 Thread Django

#17504: User.objects.create_user() wrong email domain part identification
--+--
 Reporter:  fero  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by fero):

 * needs_better_patch:   => 0
 * has_patch:  0 => 1
 * 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] #17504: User.objects.create_user() wrong email domain part identification

2012-01-05 Thread Django

#17504: User.objects.create_user() wrong email domain part identification
--+
 Reporter:  fero  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  contrib.auth  |Version:  SVN
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 According to http://tools.ietf.org/html/rfc3696#section-3 the "@" symbol
 can be part of the local part of an email address, so
 
[https://code.djangoproject.com/browser/django/trunk/django/contrib/auth/models.py#L129
 line 129 of contrib.auth.models] is bugged.

 The unbelivable complex ;) patch is:
 {{{
 -email_name, domain_part = email.strip().split('@', 1)
 +email_name, domain_part = email.strip().rsplit('@', 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] #17066: Exception TypeError when using GeoIP

2012-01-05 Thread Django

#17066: Exception TypeError when using GeoIP
+
 Reporter:  mitar   |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  GIS |  Version:  1.3
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by robbyd):

 +1 I am getting this bug as well. Django 1.3.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] #14574: Initial values support for inline model formsets

2012-01-05 Thread Django

#14574: Initial values support for inline model formsets
-+-
 Reporter:  simon29  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  SVN
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  inlineformset_factory  |  Needs documentation:  0
  BaseInlineFormSet  |  Patch needs improvement:  0
  BaseModelFormSet   |UI/UX:  0
Has patch:  1|
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by claudep):

 * cc: claude@… (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] #17464: [patch] Work with partial forms with the generic CreateView

2012-01-05 Thread Django

#17464: [patch] Work with partial forms with the generic CreateView
---+
 Reporter:  madjar |Owner:  madjar
 Type:  New feature|   Status:  assigned
Component:  Generic views  |  Version:  1.3
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by madjar):

 I'm not sure adding both save_form and save_model would be useful. Do you
 think save_model would be enough?

 Also, is

 {{{
 obj = form.save(commit=False)
 obj.save()
 }}}
 strictly equivalent to
 {{{
 form.save()
 }}}
 ? According to
 https://code.djangoproject.com/browser/django/trunk/django/forms/models.py#L84,
 there is also some m2m work in the second one, so shouldn't this be
 {{{
 obj = form.save(commit=False)
 form.save_m2m()
 obj.save()
 }}}
 ?

-- 
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] #13223: ValueError with inline and save as new

2012-01-05 Thread Django

#13223: ValueError with inline and save as new
+
 Reporter:  lucalenardi |Owner:
 Type:  Bug |   Status:  new
Component:  contrib.admin   |  Version:  1.1
 Severity:  Normal  |   Resolution:
 Keywords:  admin, save-as-new  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+
Changes (by ramiro):

 * needs_better_patch:  0 => 1


Comment:

 I've attached an updates version of the patch that simply allows it to
 apply cleanly in trunk.

 But th OP in ticket #17417 (slightly related to this one) makes a good
 point regarding the current buggy behavior and that isn't fixed by this
 patch:

 ''If you press "Save as New" without changing the slug field a
 ValidationError? is raised, and the for is displayed to the user with a
 warning (as it should). However, '''the url is that of the old entity'''
 ...''

 That means that at that point the user is presented with the admin add
 view/form for a new instance of the model, pre-filled with values of the
 original instance (the one whose edit view/form she was looking at when
 she decided to press the ''Save as new'' button) but the URL in the
 browser address bar hasn't changed.

 IMHO this is semantically incorrect and puts comment:5 in a new
 perspective. Perhaps we need to implement an intermediate view as
 suggested 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.

Re: [Django] #13926: GeometryCollections are not visible in OSMGeoAdmin

2012-01-05 Thread Django

#13926: GeometryCollections are not visible in OSMGeoAdmin
---+
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  GIS|  Version:  1.2
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by elpaso66):

 * cc: apasotti@… (added)
 * ui_ux:   => 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] #10762: Gzip Middleware Should Compress 201 (Created) Responses

2012-01-05 Thread Django

#10762: Gzip Middleware Should Compress 201 (Created) Responses
--+
 Reporter:  rwagner@… |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  HTTP handling |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:  middleware gzip   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by madjar):

 * cc: madjar (added)
 * needs_tests:  1 => 0


Comment:

 Here are simple tests to check that long responses are compressed and
 short responses are not, regardless of the return type. Are they ok ?

-- 
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] #17506: Minor tidyup in session DB backend

Re: [Django] #17505: import typo

[Django] #17505: import typo

Re: [Django] #17498: meta option "no_index"

Re: [Django] #17504: User.objects.create_user() wrong email domain part identification

Re: [Django] #17504: User.objects.create_user() wrong email domain part identification

[Django] #17504: User.objects.create_user() wrong email domain part identification

Re: [Django] #17066: Exception TypeError when using GeoIP

Re: [Django] #14574: Initial values support for inline model formsets

Re: [Django] #17464: [patch] Work with partial forms with the generic CreateView

Re: [Django] #13223: ValueError with inline and save as new

Re: [Django] #13926: GeometryCollections are not visible in OSMGeoAdmin

Re: [Django] #10762: Gzip Middleware Should Compress 201 (Created) Responses

13 matches

Site Navigation

Mail list logo

Footer information