date:20110201

Re: [Django] #12699: Possible version/link confusion on the djangoproject.org home page

2011-02-01 Thread Django

#12699: Possible version/link confusion on the djangoproject.org home page
---+
   Reporter:  sopor0qv | Owner:  justinlilly   
 Status:  assigned | Milestone:  1.3   
  Component:  Django Web site  |   Version:  1.1   
 Resolution:   |  Keywords:  tutorial links
   Triage Stage:  Accepted | Has patch:  1 
Needs documentation:  0|   Needs tests:  0 
Patch needs improvement:  0|  
---+
Changes (by justinlilly):

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


Comment:

 https://github.com/jacobian/djangoproject.com/pull/10

-- 
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] #14628: Document which settings can be changed at runtime

2011-02-01 Thread Django

#14628: Document which settings can be changed at runtime
-+--
   Reporter:  NicoEchaniz| Owner:  nobody  
 Status:  new| Milestone:  
  Component:  Documentation  |   Version:  1.2 
 Resolution: |  Keywords:  settings django.conf
   Triage Stage:  Accepted   | Has patch:  0   
Needs documentation:  0  |   Needs tests:  0   
Patch needs improvement:  0  |  
-+--

Comment (by NicoEchaniz):

 Ramiro, that portion of the documentation is exactly what jacob was
 refering to during the chat session that spawned this ticket and it would
 need some modification if this ticket were to be solved.
 It should clearly keep the general warning tone, that's what I meant with
 my previous comment where I just tried to clarify the fact that adding
 this information to the documentation does not necessarily mean
 encouraging people to change settings at runtime.

 The mentioned paragraph, instead of saying:
 "You shouldn't alter settings in your applications at runtime.

 Could read:
 "You shouldn't alter settings in your applications at runtime unless you
 know exactly what you are doing and know how to handle the related issues
 (eg. threading problems)."

 And then refer to the distinction between the different types of setting
 that jacob describes in
 [http://code.djangoproject.com/ticket/14628#comment:1 comment:1].

 This would be clear enough for everyone and useful for those with the
 particular needs this ticket initends to address.

-- 
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] #14338: Search bar on the docs should include 1.2, & 1.1

2011-02-01 Thread Django

#14338: Search bar on the docs should include 1.2, & 1.1
---+
   Reporter:  varikin  | Owner:  jacobkm

 Status:  closed   | Milestone:  1.3

  Component:  Django Web site  |   Version:  1.2

 Resolution:  fixed|  Keywords:  docs search google 
versions
   Triage Stage:  Accepted | Has patch:  1  

Needs documentation:  0|   Needs tests:  0  

Patch needs improvement:  0|  
---+
Changes (by justinlilly):

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


Comment:

 Fixed with the latest rollout of search.

-- 
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] #10700: Searching 1.0 docs -- results link to dev docs

2011-02-01 Thread Django

#10700: Searching 1.0 docs -- results link to dev docs
---+
   Reporter:  kmtracey | Owner:  jacob 
 Status:  closed   | Milestone:
  Component:  Django Web site  |   Version:  SVN   
 Resolution:  fixed|  Keywords:  search
   Triage Stage:  Accepted | Has patch:  0 
Needs documentation:  0|   Needs tests:  0 
Patch needs improvement:  0|  
---+
Changes (by justinlilly):

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


Comment:

 Should be fixed with the latest search rollout.

-- 
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] #14862: bad links

2011-02-01 Thread Django

#14862: bad links
---+
   Reporter:  kurdy| Owner:  justinlilly
 Status:  new  | Milestone:  1.3
  Component:  Django Web site  |   Version:  1.2
 Resolution:   |  Keywords: 
   Triage Stage:  Accepted | Has patch:  1  
Needs documentation:  0|   Needs tests:  0  
Patch needs improvement:  0|  
---+
Changes (by justinlilly):

  * owner:  => justinlilly
  * has_patch:  0 => 1


Comment:

 https://github.com/jacobian/djangoproject.com/pull/9

-- 
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] #7325: Wrong numbers in modeltests.

2011-02-01 Thread Django

#7325: Wrong numbers in modeltests.
---+
   Reporter:  sebastian_noack  | Owner:  justinlilly
 Status:  assigned | Milestone: 
  Component:  Documentation|   Version:  SVN
 Resolution:   |  Keywords: 
   Triage Stage:  Accepted | Has patch:  1  
Needs documentation:  0|   Needs tests:  0  
Patch needs improvement:  0|  
---+
Changes (by justinlilly):

  * component:  Django Web site => Documentation


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

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

Re: [Django] #7325: Wrong numbers in modeltests.

2011-02-01 Thread Django

#7325: Wrong numbers in modeltests.
---+
   Reporter:  sebastian_noack  | Owner:  justinlilly
 Status:  assigned | Milestone: 
  Component:  Django Web site  |   Version:  SVN
 Resolution:   |  Keywords: 
   Triage Stage:  Accepted | Has patch:  1  
Needs documentation:  0|   Needs tests:  0  
Patch needs improvement:  0|  
---+
Changes (by justinlilly):

  * has_patch:  0 => 1


Comment:

 https://github.com/django/django/pull/12

-- 
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] #15206: Group: use select_related for permissions on admin change_form

2011-02-01 Thread Django

#15206: Group: use select_related for permissions on admin change_form
--+-
   Reporter:  acdha   | Owner:  acdha
 Status:  assigned| Milestone:   
  Component:  Authentication  |   Version:  1.2  
 Resolution:  |  Keywords:   
   Triage Stage:  Accepted| Has patch:  1
Needs documentation:  0   |   Needs tests:  1
Patch needs improvement:  0   |  
--+-
Changes (by russellm):

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


Comment:

 This can be tested using assertNumQueries in a test within the admin_views
 regression 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.

Re: [Django] #15207: Signals now send the 'using' kwarg, but this isn't documented as new.

2011-02-01 Thread Django

#15207: Signals now send the 'using' kwarg, but this isn't documented as new.
+---
   Reporter:  Keryn Knight | 
Owner:  nobody 
 Status:  new   | 
Milestone:  1.3
  Component:  Documentation |   
Version:  SVN
 Resolution:|  
Keywords:  using signals easy-pickings
   Triage Stage:  Ready for checkin | Has 
patch:  0  
Needs documentation:  0 |   Needs 
tests:  0  
Patch needs improvement:  0 |  
+---
Changes (by russellm):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Ready for checkin
  * needs_tests:  => 0
  * needs_docs:  => 0


Comment:

 Marking RFC beacuse it's an easy markup change.

-- 
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] #15208: Document ModelAdmin.formfield_for_choice_field

2011-02-01 Thread Django

#15208: Document ModelAdmin.formfield_for_choice_field
-+--
   Reporter:  julien | Owner:  nobody
 Status:  new| Milestone:  1.3   
  Component:  Documentation  |   Version:  1.2   
 Resolution: |  Keywords:
   Triage Stage:  Ready for checkin  | Has patch:  1 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--
Changes (by russellm):

  * stage:  Unreviewed => Ready for checkin


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

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

Re: [Django] #15209: Manager.raw() allow for WITH ( ... ) SELECT

2011-02-01 Thread Django

#15209: Manager.raw() allow for WITH ( ... ) SELECT
+---
   Reporter:  carbonXT  | Owner:  
nobody 
 Status:  new   | Milestone:  1.4   
 
  Component:  Database layer (models, ORM)  |   Version:  SVN   
 
 Resolution:|  Keywords:  with, 
Manager.raw()
   Triage Stage:  Accepted  | Has patch:  1 
 
Needs documentation:  1 |   Needs tests:  1 
 
Patch needs improvement:  1 |  
+---
Changes (by russellm):

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


Comment:

 Accepted on principle; a WITH clause is easy to identify,

 However, if all backends don't support a feature, then validation should
 be a backend-specific feature.

 In addition, the patch requires tests and documentation updates.

-- 
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] #5863: list_display does not allow functions of referenced objects

2011-02-01 Thread Django

#5863: list_display does not allow functions of referenced objects
+---
   Reporter:  Beat Bolli   | Owner:  
nobody  
 Status:  closed| Milestone:
  
  Component:  django.contrib.admin  |   Version:  
SVN 
 Resolution:  wontfix   |  Keywords:  
list_display
   Triage Stage:  Design decision needed| Has patch:  1 
  
Needs documentation:  1 |   Needs tests:  0 
  
Patch needs improvement:  1 |  
+---
Changes (by kmtracey):

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


Comment:

 Replying to [comment:27 Herman S]:
 >
 > As the parent/child relationship is reversed from what Django's
 ModelAdmin.inlines expect, there seems to not be a solution for my
 problem.

 There's a trivially-easy solution you can code: methods on your model or
 model admin that return the information you desire, listed in your
 list_display.

 I'm closing this wontfix; having it be open seems to be confusing people
 into thinking the requested function of allowing a specific field from a
 related model to be shown in list_display is not possible. It is possible,
 quite easily, with a feature (callables in list_display) added since this
 ticket was originally opened. That feature is more powerful than simply
 allowing traversal to a related model's field, so the syntax of how to do
 it is not exactly the same as it would be if just that one piece was
 implemented. But given the more powerful thing has been implemented, I
 don't believe the addition of another way of doing the same thing is
 necessary or worth the implementation/maintenance effort.

-- 
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] #15209: Manager.raw() allow for WITH ( ... ) SELECT

2011-02-01 Thread Django

#15209: Manager.raw() allow for WITH ( ... ) SELECT
--+-
 Reporter:  carbonXT  |  Owner:  nobody
   Status:  new   |  Milestone:  1.4   
Component:  Database layer (models, ORM)  |Version:  SVN   
 Keywords:  with, Manager.raw()   |   Triage Stage:  Unreviewed
Has patch:  1 |  
--+-
 The !RawQuery object used by Manager.raw() validates input SQL to ensure
 that only SELECT queries can be ran through it.  This is done such that
 SELECT queries with using a WITH (...) clause fail validation.

 I propose changing the validation of the SQL such that SELECTs with these
 WITH clauses are ok.

 The attached patch does that.  It also does not weaken the validation as
 preceding WITH clauses can only be used with SELECT statements. Re:

  * Postgres: http://www.postgresql.org/docs/9.0/static/sql-select.html
  * Oracle: http://www.oracle-base.com/articles/misc/WithClause.php
  * Other backends don't support the WITH clause.

-- 
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] #15208: Document ModelAdmin.formfield_for_choice_field

2011-02-01 Thread Django

#15208: Document ModelAdmin.formfield_for_choice_field
-+--
   Reporter:  julien | Owner:  nobody
 Status:  new| Milestone:  1.3   
  Component:  Documentation  |   Version:  1.2   
 Resolution: |  Keywords:
   Triage Stage:  Unreviewed | Has patch:  1 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--
Changes (by julien):

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


Comment:

 Correction from the original description: "formfield_for_foreignkey and
 formfield_for_manytomany *are documented* but formfield_for_choice_field
 isn't".

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

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

[Django] #15208: Document ModelAdmin.formfield_for_choice_field

2011-02-01 Thread Django

#15208: Document ModelAdmin.formfield_for_choice_field
---+
 Reporter:  julien |  Owner:  nobody
   Status:  new|  Milestone:  1.3   
Component:  Documentation  |Version:  1.2   
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  1  |  
---+
 `formfield_for_foreignkey` and `formfield_for_manytomany` but
 `formfield_for_choice_field` isn't. I think that
 `formfield_for_choice_field` is very useful and that it should be part of
 the official API. See patch attached.

-- 
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] #5863: list_display does not allow functions of referenced objects

2011-02-01 Thread Django

#5863: list_display does not allow functions of referenced objects
+---
   Reporter:  Beat Bolli   | Owner:  
nobody  
 Status:  reopened  | Milestone:
  
  Component:  django.contrib.admin  |   Version:  
SVN 
 Resolution:|  Keywords:  
list_display
   Triage Stage:  Design decision needed| Has patch:  1 
  
Needs documentation:  1 |   Needs tests:  0 
  
Patch needs improvement:  1 |  
+---

Comment (by Herman S):

 This needs attention.

 I have the following models:
 * Applicant
 * Application, which has a field "applicant =
 models.ForeignKey(Applicant)"

 In ApplicationAdmin I'm trying to request the applicants name, phone,
 email etc. with:[[BR]]
 list_display = ['status', 'interview' ... 'applicant__name',
 'applicant__email']

 As the parent/child relationship is reversed from what Django's
 ModelAdmin.inlines expect, there seems to not be a solution for my
 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] #15199: Allow MEDIA_ROOT inside STATIC_ROOT

2011-02-01 Thread Django

#15199: Allow MEDIA_ROOT inside STATIC_ROOT
--+-
   Reporter:  brutasse| Owner: 
 Status:  closed  | Milestone:  1.3
  Component:  django.contrib.staticfiles  |   Version:  SVN
 Resolution:  wontfix |  Keywords:  blocker
   Triage Stage:  Accepted| Has patch:  1  
Needs documentation:  0   |   Needs tests:  0  
Patch needs improvement:  1   |  
--+-
Changes (by carljm):

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


Comment:

 After further IRC discussion with jezdez, closing this wontfix. Supporting
 a configuration with MEDIA_ROOT inside STATIC_ROOT introduces a number of
 additional complexities and couplings between staticfiles and the MEDIA_*
 settings, which we are trying to avoid, and it's not clear what meaningful
 benefits it buys us. The main mentioned benefit was to only require one
 alias on the front-end webserver: that seems minor, since an alias is e.g.
 just one line in an nginx conf file. In any case, the same result can be
 achieved by putting MEDIA_ROOT and STATIC_ROOT side by side in a parent
 directory, and aliasing the front-end webserver to that parent directory.

-- 
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] #15207: Signals now send the 'using' kwarg, but this isn't documented as new.

2011-02-01 Thread Django

#15207: Signals now send the 'using' kwarg, but this isn't documented as new.
--+-
 Reporter:  Keryn Knight |  Owner:  nobody
   Status:  new   |  Milestone:  1.3   
Component:  Documentation |Version:  SVN   
 Keywords:  using signals easy-pickings   |   Triage Stage:  Unreviewed
Has patch:  0 |  
--+-
 The API [http://docs.djangoproject.com/en/dev/ref/signals/ reference
 documentation on signals] adds in documentation on the new 'using'
 parameter, but this isn't addressed with the usual callout  annotation I'd
 expect, explaining that it is new in development/svn/1.3.

 I've taken the liberty of marking it as easy-pickings & 1.3, as it should
 be simple enough if it's not a dupe.

 I can't think of any more pertinent details, but if clarification is
 required, let me know.

-- 
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] #15206: Group: use select_related for permissions on admin change_form

2011-02-01 Thread Django

#15206: Group: use select_related for permissions on admin change_form
--+-
   Reporter:  acdha   | Owner:  acdha
 Status:  assigned| Milestone:   
  Component:  Authentication  |   Version:  1.2  
 Resolution:  |  Keywords:   
   Triage Stage:  Unreviewed  | Has patch:  1
Needs documentation:  0   |   Needs tests:  0
Patch needs improvement:  0   |  
--+-
Changes (by acdha):

  * status:  new => assigned
  * needs_docs:  => 0
  * needs_tests:  => 0
  * needs_better_patch:  => 0


Comment:

 Simple patch against 1.2.X:
 https://github.com/acdha/django/compare/django-1.2.X...bug-15206

-- 
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] #15206: Group: use select_related for permissions on admin change_form

2011-02-01 Thread Django

#15206: Group: use select_related for permissions on admin change_form
+---
 Reporter:  acdha   |  Owner:  acdha 
   Status:  new |  Milestone:
Component:  Authentication  |Version:  1.2   
 Keywords:  |   Triage Stage:  Unreviewed
Has patch:  1   |  
+---
 django.contrib.auth uses select_related on the User permissions manytomany
 widget but does not on Group, causing O(n) queries when generating the
 page.

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

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

Re: [Django] #15199: Allow MEDIA_ROOT inside STATIC_ROOT

2011-02-01 Thread Django

#15199: Allow MEDIA_ROOT inside STATIC_ROOT
--+-
   Reporter:  brutasse| Owner: 
 Status:  new | Milestone:  1.3
  Component:  django.contrib.staticfiles  |   Version:  SVN
 Resolution:  |  Keywords:  blocker
   Triage Stage:  Accepted| Has patch:  1  
Needs documentation:  0   |   Needs tests:  0  
Patch needs improvement:  1   |  
--+-

Comment (by jezdez):

 Replying to [comment:2 brutasse]:
 > Hmmm this is trickier. With the patch applied, the media files aren't
 served by staticfiles but defining a custom view won't work either.
 >
 > {{{
 > urlpatterns += patterns('django.contrib.staticfiles.views',
 > url(r'^static/media/(?P.*)$', 'serve',
 > {'document_root': settings.MEDIA_ROOT}),
 > )
 > }}}
 >
 > The 'serve' view is called, but the options dict is not passed to the
 view. 'document_root' is swallowed somewhere and ends up as None in the
 view, something bad probably happens in the staticfiles handler. If I
 change MEDIA_URL to '/static_media/' and the URL pattern to
 {{{r'^static_media/(?P.*)$'}}}, the options dict is correctly passed
 to the view.

 Not sure what you mean with "something bad happens", the view looks just
 fine: source:django/trunk/django/contrib/staticfiles/views.py#L23

 > I thought modifying _should_handle() on !StaticFilesHandler would do the
 job, but apparently it's not enough. The staticfiles handler isn't
 transparently giving the control back to the parent WSGIHandler if
 _should_handle returns false.

-- 
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] #15190: collectstatic should not symlink files that are already symlinked

2011-02-01 Thread Django

#15190: collectstatic should not symlink files that are already symlinked
--+-
   Reporter:  bendavis78  | Owner:  jezdez  
   
 Status:  assigned| Milestone:  1.3 
   
  Component:  django.contrib.staticfiles  |   Version:  
1.3-beta   
 Resolution:  |  Keywords:  
staticfiles
   Triage Stage:  Accepted| Has patch:  1   
   
Needs documentation:  0   |   Needs tests:  0   
   
Patch needs improvement:  0   |  
--+-
Changes (by jezdez):

  * has_patch:  0 => 1


Comment:

 The attached patch solves a few problems of collectstatic:

 - Reliance on set() and therefor not guaranteed order
 - Deleting symlinks even if they refer to the same files
 - Code smell, such as missing comments
 - Shows which directory it copies/links now

-- 
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] #15190: collectstatic should not symlink files that are already symlinked

2011-02-01 Thread Django

#15190: collectstatic should not symlink files that are already symlinked
--+-
   Reporter:  bendavis78  | Owner:  jezdez  
   
 Status:  assigned| Milestone:  1.3 
   
  Component:  django.contrib.staticfiles  |   Version:  
1.3-beta   
 Resolution:  |  Keywords:  
staticfiles
   Triage Stage:  Accepted| Has patch:  0   
   
Needs documentation:  0   |   Needs tests:  0   
   
Patch needs improvement:  0   |  
--+-
Changes (by jezdez):

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


-- 
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] #15129: Invalid order of applying formats

2011-02-01 Thread Django

#15129: Invalid order of applying formats
+---
   Reporter:  tonnzor   | Owner:  nobody
 Status:  new   | Milestone:  1.3   
  Component:  Internationalization  |   Version:  1.2   
 Resolution:|  Keywords:
   Triage Stage:  Ready for checkin | Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  1 |  
+---
Changes (by tonnzor):

  * stage:  Accepted => Ready for checkin


Comment:

 I suppose that is ready for check-in

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

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

Re: [Django] #13618: prepopulated_fields crashes with get_readonly_fields

2011-02-01 Thread Django

#13618: prepopulated_fields crashes with get_readonly_fields
+---
   Reporter:  tonnzor   | Owner:  tobias
 Status:  assigned  | Milestone:  1.3   
  Component:  django.contrib.admin  |   Version:  SVN   
 Resolution:|  Keywords:
   Triage Stage:  Ready for checkin | Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Changes (by tonnzor):

  * stage:  Accepted => Ready for checkin


Comment:

 The patch is ready for check-in. I had just checked that test fails on
 unmodified trunk and passes on fixed version

-- 
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] #14702: Add a "needs info" state to tickets

2011-02-01 Thread Django

#14702: Add a "needs info" state to tickets
---+
   Reporter:  dmoisset | Owner:  nobody
 Status:  new  | Milestone:  1.3   
  Component:  Django Web site  |   Version:  1.2   
 Resolution:   |  Keywords:
   Triage Stage:  Accepted | Has patch:  0 
Needs documentation:  0|   Needs tests:  0 
Patch needs improvement:  0|  
---+
Changes (by ramiro):

  * needs_docs:  1 => 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] #10284: ModelFormSet - objects are deleted even if commit=False

2011-02-01 Thread Django

#10284: ModelFormSet - objects are deleted even if commit=False
--+-
   Reporter:  laureline.guerin@…  | Owner:  
Wedg
 Status:  assigned| Milestone:  

  Component:  Forms   |   Version:  
SVN 
 Resolution:  |  Keywords:  

   Triage Stage:  Design decision needed  | Has patch:  
1   
Needs documentation:  0   |   Needs tests:  
0   
Patch needs improvement:  0   |  
--+-
Changes (by denilsonsa):

 * cc: denilsonsa@… (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] #15169: With gis.mysql backend BooleanField convert to Python as 1|0 instead of True|False

2011-02-01 Thread Django

#15169: With gis.mysql backend BooleanField convert to Python as 1|0 instead of
True|False
+---
   Reporter:  zmsmith   | Owner:  jbronn
 Status:  assigned  | Milestone:  1.3   
  Component:  GIS   |   Version:  1.2   
 Resolution:|  Keywords:  BooleanField, GIS,
   Triage Stage:  Accepted  | Has patch:  0 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Changes (by jbronn):

  * milestone:  => 1.3


-- 
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] #15194: Need 'geos_c' as library name for Windows

2011-02-01 Thread Django

#15194: Need 'geos_c' as library name for Windows
+---
   Reporter:  master| Owner:  jbronn
 Status:  assigned  | Milestone:  1.3   
  Component:  GIS   |   Version:  1.2   
 Resolution:|  Keywords:  geos_c
   Triage Stage:  Accepted  | Has patch:  0 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---

Comment (by jbronn):

 Replying to [ticket:15194 master]:
 > By the way, who provides the lib as 'libgeos_c-1' ? Cygwin ? A comment
 about originators is welcome.

 Excellent question.  The Application Stack Builder (ASB) that comes with
 the Windows distribution of PostgreSQL allowed users to install PostGIS,
 and is the source of `libgeos_c-1.dll`.   I assume it was named that way
 to prevent conflicting with other libraries, like !FWTools.

-- 
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] #15194: Need 'geos_c' as library name for Windows

2011-02-01 Thread Django

#15194: Need 'geos_c' as library name for Windows
+---
   Reporter:  master| Owner:  jbronn
 Status:  assigned  | Milestone:  1.3   
  Component:  GIS   |   Version:  1.2   
 Resolution:|  Keywords:  geos_c
   Triage Stage:  Accepted  | Has patch:  0 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Changes (by jbronn):

  * status:  new => assigned
  * owner:  nobody => jbronn
  * milestone:  => 1.3


-- 
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] #15203: admin search_fields splitting query

2011-02-01 Thread Django

#15203: admin search_fields splitting query
+---
   Reporter:  wkornewald| Owner:  nobody
 Status:  reopened  | Milestone:  1.3   
  Component:  django.contrib.admin  |   Version:  1.2   
 Resolution:|  Keywords:
   Triage Stage:  Unreviewed| Has patch:  1 
Needs documentation:  1 |   Needs tests:  1 
Patch needs improvement:  1 |  
+---

Comment (by wkornewald):

 Thanks for the note. That was caused by a typo. The new patch should work
 correctly, but I should really better write a few unit tests which check
 all important cases. ;)

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

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

Re: [Django] #10797: Set up Trac so post-commit hook sends emails

2011-02-01 Thread Django

#10797: Set up Trac so post-commit hook sends emails
---+
   Reporter:  carljm   | Owner:  nobody
 Status:  closed   | Milestone:
  Component:  Django Web site  |   Version:
 Resolution:  fixed|  Keywords:
   Triage Stage:  Accepted | Has patch:  0 
Needs documentation:  0|   Needs tests:  0 
Patch needs improvement:  0|  
---+
Changes (by jacob):

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


Comment:

 This should have been fixed by the update to 0.12.

-- 
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] #15201: CACHE_MIDDLEWARE_ANONYMOUS_ONLY is ugly, misleading, and unnecessary, and should be deprecated

2011-02-01 Thread Django

#15201: CACHE_MIDDLEWARE_ANONYMOUS_ONLY is ugly, misleading, and unnecessary, 
and
should be deprecated
+---
   Reporter:  carljm| Owner:  nobody
 Status:  new   | Milestone:
  Component:  Cache system  |   Version:  SVN   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  0 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Changes (by russellm):

  * needs_docs:  => 0
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * 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] #15197: yaml serialization to HttpResponse fails

2011-02-01 Thread Django

#15197: yaml serialization to HttpResponse fails
-+--
   Reporter:  fourga38   | Owner:  nobody
 Status:  new| Milestone:
  Component:  Serialization  |   Version:  1.2   
 Resolution: |  Keywords:  yaml  
   Triage Stage:  Accepted   | Has patch:  0 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--
Changes (by russellm):

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


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

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

Re: [Django] #15198: AuthenticationForm.clean call does not have request set

2011-02-01 Thread Django

#15198: AuthenticationForm.clean call does not have request set
--+-
   Reporter:  Ciantic | Owner:  nobody
 Status:  new | Milestone:
  Component:  Authentication  |   Version:  SVN   
 Resolution:  |  Keywords:
   Triage Stage:  Accepted| Has patch:  1 
Needs documentation:  0   |   Needs tests:  0 
Patch needs improvement:  1   |  
--+-
Changes (by russellm):

  * stage:  Unreviewed => Accepted


Comment:

 Seems like a reasonable suggestion -- although the issue with the cookie
 check obviously still needs to be resolved.

-- 
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] #15178: Development server hangs very often when used with IE9 beta

2011-02-01 Thread Django

#15178: Development server hangs very often when used with IE9 beta
--+-
   Reporter:  cataliniacob| Owner:  nobody  
  
 Status:  closed  | Milestone:  
  
  Component:  Core framework  |   Version:  SVN 
  
 Resolution:  worksforme  |  Keywords:  ie9 
development-server
   Triage Stage:  Unreviewed  | Has patch:  0   
  
Needs documentation:  0   |   Needs tests:  0   
  
Patch needs improvement:  0   |  
--+-
Changes (by russellm):

  * status:  new => closed
  * resolution:  => worksforme
  * component:  Uncategorized => Core framework


Comment:

 Jezdez hasn't been able to reproduce this; the mailing list thread seems
 to suggest that the problem may lie with network settings on the box in
 question.

 If you can narrow down *specific* test conditions that reproduce, feel
 free to reopen with details.

-- 
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] #15204: Fix help_text documentation

2011-02-01 Thread Django

#15204: Fix help_text documentation
-+--
   Reporter:  prestontimmons | Owner:  nobody
 Status:  new| Milestone:  1.3   
  Component:  Documentation  |   Version:  1.2   
 Resolution: |  Keywords:
   Triage Stage:  Ready for checkin  | Has patch:  1 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--
Changes (by russellm):

  * needs_docs:  => 0
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * stage:  Unreviewed => Ready for checkin


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

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

Re: [Django] #15203: admin search_fields splitting query

2011-02-01 Thread Django

#15203: admin search_fields splitting query
+---
   Reporter:  wkornewald| Owner:  nobody
 Status:  reopened  | Milestone:  1.3   
  Component:  django.contrib.admin  |   Version:  1.2   
 Resolution:|  Keywords:
   Triage Stage:  Unreviewed| Has patch:  1 
Needs documentation:  1 |   Needs tests:  1 
Patch needs improvement:  1 |  
+---
Changes (by kmtracey):

  * needs_better_patch:  0 => 1


Comment:

 The updated patch still breaks the case I was concerned about above. When
 I've got multiple fields in search_fields, say:

 {{{
 #!python
 search_fields = ('=name', '=adopted_name', 'markings',
 'adopter__name',)
 }}}

 (Happens to be a DB tracking cat adoptions for a rescue group.) Anyway,
 with current trunk code, if I enter "Lucky tabby" in the search box I get
 hits: cats with an (exact) name or adopted name of Lucky, and tabby
 somewhere in the markings field. This result I believe is correct, it
 matches my expectations and the documentation.

 With the (updated) patch, I get no hits, which I don't believe is the
 correct result for this case.

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

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

Re: [Django] #15194: Need 'geos_c' as library name for Windows

2011-02-01 Thread Django

#15194: Need 'geos_c' as library name for Windows
+---
   Reporter:  master| Owner:  nobody
 Status:  new   | Milestone:
  Component:  GIS   |   Version:  1.2   
 Resolution:|  Keywords:  geos_c
   Triage Stage:  Accepted  | Has patch:  0 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Changes (by russellm):

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


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

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

Re: [Django] #15205: Built-in server doesn't serve admin statics

2011-02-01 Thread Django

#15205: Built-in server doesn't serve admin statics
--+-
   Reporter:  pestaa  | Owner:  
 Status:  closed  | Milestone:  
  Component:  django.contrib.staticfiles  |   Version:  1.3-beta
 Resolution:  fixed   |  Keywords:  
   Triage Stage:  Unreviewed  | Has patch:  0   
Needs documentation:  0   |   Needs tests:  0   
Patch needs improvement:  0   |  
--+-
Changes (by carljm):

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


Comment:

 This was an issue in the 1.3 beta, but should be fixed in trunk (r15119).
 Please reopen if you can reproduce on latest trunk.

-- 
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] #13618: prepopulated_fields crashes with get_readonly_fields

2011-02-01 Thread Django

#13618: prepopulated_fields crashes with get_readonly_fields
+---
   Reporter:  tonnzor   | Owner:  tobias
 Status:  assigned  | Milestone:  1.3   
  Component:  django.contrib.admin  |   Version:  SVN   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---

Comment (by russellm):

 Nobody is going to commit anything unless someone marks the ticket Ready
 For Checkin. If you think tobias' patch is ready for trunk, change the
 ticket state and it will be put on our todo list.

-- 
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] #14702: Add a "needs info" state to tickets

2011-02-01 Thread Django

#14702: Add a "needs info" state to tickets
---+
   Reporter:  dmoisset | Owner:  nobody
 Status:  new  | Milestone:  1.3   
  Component:  Django Web site  |   Version:  1.2   
 Resolution:   |  Keywords:
   Triage Stage:  Accepted | Has patch:  0 
Needs documentation:  1|   Needs tests:  0 
Patch needs improvement:  0|  
---+

Comment (by jacob):

 The hard part here is updating the docs to refer to the new state and
 explaining how it works. The Trac change will only take a second. I'll get
 to the docs at some point, but if someone wants to give me a doc patch
 I'll do the Trac change when I check it in.

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

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

Re: [Django] #14083: Python module index on docs page is empty

2011-02-01 Thread Django

#14083: Python module index on docs page is empty
---+
   Reporter:  JirkaV   | Owner:  justinlilly
 Status:  closed   | Milestone: 
  Component:  Django Web site  |   Version:  1.2
 Resolution:  fixed|  Keywords: 
   Triage Stage:  Accepted | Has patch:  0  
Needs documentation:  0|   Needs tests:  0  
Patch needs improvement:  0|  
---+
Changes (by jacob):

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


Comment:

 Fixed, more thanks to Justin Lilly.

-- 
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] #10178: Bogus timezone listed in documentation

2011-02-01 Thread Django

#10178: Bogus timezone listed in documentation
---+
   Reporter:  dannyman | Owner:  jacob
 Status:  closed   | Milestone:   
  Component:  Django Web site  |   Version:  1.0  
 Resolution:  fixed|  Keywords:   
   Triage Stage:  Accepted | Has patch:  0
Needs documentation:  0|   Needs tests:  0
Patch needs improvement:  0|  
---+
Changes (by jacob):

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


Comment:

 Fixed, more thanks to Justin Lilly.

-- 
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] #13288: 'Community' page double-escapes entities

2011-02-01 Thread Django

#13288: 'Community' page double-escapes entities
---+
   Reporter:  wandernauta  | Owner:  justinlilly
 Status:  closed   | Milestone: 
  Component:  Django Web site  |   Version:  1.1
 Resolution:  fixed|  Keywords:  site   
   Triage Stage:  Accepted | Has patch:  0  
Needs documentation:  0|   Needs tests:  0  
Patch needs improvement:  0|  
---+
Changes (by jacob):

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


Comment:

 Fixed, more thanks to Justin Lilly.

-- 
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] #15205: Built-in server doesn't serve admin statics

2011-02-01 Thread Django

#15205: Built-in server doesn't serve admin statics
+---
 Reporter:  pestaa  |  Owner:
   Status:  new |  Milestone:
Component:  django.contrib.staticfiles  |Version:  1.3-beta  
 Keywords:  |   Triage Stage:  Unreviewed
Has patch:  0   |  
+---
 `serve` view does not always unify backward-slashes. Admin panel looks
 very naked under Windows.

 Bug probably appeared in 1.3 as I've completed the tutorial with 1.2 and
 didn't notice the same effect.

-- 
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] #13618: prepopulated_fields crashes with get_readonly_fields

2011-02-01 Thread Django

#13618: prepopulated_fields crashes with get_readonly_fields
+---
   Reporter:  tonnzor   | Owner:  tobias
 Status:  assigned  | Milestone:  1.3   
  Component:  django.contrib.admin  |   Version:  SVN   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---

Comment (by tonnzor):

 Current patch seems to be ready for merging into repository. Is anybody
 going to do that? That's the last thing to do here.

-- 
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] #15203: admin search_fields splitting query

2011-02-01 Thread Django

#15203: admin search_fields splitting query
+---
   Reporter:  wkornewald| Owner:  nobody
 Status:  reopened  | Milestone:  1.3   
  Component:  django.contrib.admin  |   Version:  1.2   
 Resolution:|  Keywords:
   Triage Stage:  Unreviewed| Has patch:  1 
Needs documentation:  1 |   Needs tests:  1 
Patch needs improvement:  0 |  
+---

Comment (by wkornewald):

 OK, I've updated the patch. The query string must still be split in case
 there are multiple fields, but additionally, exact matches on the whole
 query string should also be taken into account. In case of just a single
 search field the query should not be split.

 The patch doesn't tread `__search` differently, anymore, since splitting
 is still necessary for multiple search fields, anyway.

 The patch still doesn't have any documentation and unit tests. I'll try to
 push a complete patch in the next few weeks, but that'll probably be too
 late for the 1.3 release.

-- 
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] #15202: Changeset 15376 breaks implementation

2011-02-01 Thread Django

#15202: Changeset 15376 breaks implementation
--+-
   Reporter:  liorsion| Owner: 
 Status:  closed  | Milestone: 
  Component:  django.contrib.staticfiles  |   Version:  SVN
 Resolution:  invalid |  Keywords: 
   Triage Stage:  Unreviewed  | Has patch:  0  
Needs documentation:  0   |   Needs tests:  0  
Patch needs improvement:  0   |  
--+-
Changes (by carljm):

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


Comment:

 No, adding STATIC_ROOT to STATICFILES_DIRS is not sensible, and will break
 things. STATIC_ROOT is a _destination_ directory, not a _source_ directory
 for static files. Adding STATIC_ROOT to STATICFILES_DIRS is, in essence,
 asking "collectstatic" to do an infinite recursive copy. The fact that
 some people are doing this indicates even more clearly the need for the
 code check to alert them that they are misunderstanding how these settings
 work.

 The docs were not as clear on this point as they should have been, and in
 fact contained some outright misleading statements about STATIC_ROOT, so
 it's not surprising people have been confused about this. I reworked them
 yesterday and today to hopefully provide better clarity before the 1.3
 release.

-- 
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] #15204: Fix help_text documentation

2011-02-01 Thread Django

#15204: Fix help_text documentation
+---
 Reporter:  prestontimmons  |  Owner:  nobody
   Status:  new |  Milestone:  1.3   
Component:  Documentation   |Version:  1.2   
 Keywords:  |   Triage Stage:  Unreviewed
Has patch:  1   |  
+---
 In changeset [13522], rendering of the help_text attribute was modified to
 be wrapped in a span element. The current documentation still reflects the
 old rendering: http://docs.djangoproject.com/en/dev/ref/forms/fields
 /#help-text

-- 
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] #15094: Convert STATICFILES_DIRS into a tuple if set as string

2011-02-01 Thread Django

#15094: Convert STATICFILES_DIRS into a tuple if set as string
--+-
   Reporter:  oxy | Owner:  nobody
 Status:  reopened| Milestone:
  Component:  django.contrib.staticfiles  |   Version:  SVN   
 Resolution:  |  Keywords:
   Triage Stage:  Accepted| Has patch:  1 
Needs documentation:  0   |   Needs tests:  0 
Patch needs improvement:  0   |  
--+-
Changes (by jezdez):

  * component:  Contrib apps => django.contrib.staticfiles


-- 
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] #15094: Convert STATICFILES_DIRS into a tuple if set as string

2011-02-01 Thread Django

#15094: Convert STATICFILES_DIRS into a tuple if set as string
+---
   Reporter:  oxy   | Owner:  nobody
 Status:  reopened  | Milestone:
  Component:  Contrib apps  |   Version:  SVN   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Changes (by jezdez):

  * status:  closed => reopened
  * resolution:  wontfix =>
  * 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] #15203: admin search_fields splitting query

2011-02-01 Thread Django

#15203: admin search_fields splitting query
+---
   Reporter:  wkornewald| Owner:  nobody
 Status:  reopened  | Milestone:  1.3   
  Component:  django.contrib.admin  |   Version:  1.2   
 Resolution:|  Keywords:
   Triage Stage:  Unreviewed| Has patch:  1 
Needs documentation:  1 |   Needs tests:  1 
Patch needs improvement:  0 |  
+---
Changes (by wkornewald):

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


Comment:

 Right, I've overlooked that. But I don't agree that this ticket is
 invalid. Django's current behavior is not right. Splitting the string is
 very confusing and I'm pretty sure it's unnecessary in the case of
 `__search`. I'll fix the patch.

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

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

Re: [Django] #15199: Allow MEDIA_ROOT inside STATIC_ROOT

2011-02-01 Thread Django

#15199: Allow MEDIA_ROOT inside STATIC_ROOT
--+-
   Reporter:  brutasse| Owner: 
 Status:  new | Milestone:  1.3
  Component:  django.contrib.staticfiles  |   Version:  SVN
 Resolution:  |  Keywords:  blocker
   Triage Stage:  Accepted| Has patch:  1  
Needs documentation:  0   |   Needs tests:  0  
Patch needs improvement:  1   |  
--+-
Changes (by carljm):

  * keywords:  => blocker
  * stage:  Unreviewed => Accepted


Comment:

 This is a 1.3 blocker, because it's a significant problem with a new
 feature in 1.3.

-- 
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] #15203: admin search_fields splitting query

2011-02-01 Thread Django

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

Comment:

(When formatting only one inline backtick is needed; doubling them
effectively removes them.)

I think you have overlooked the case of multiple fields listed in
search_fields. I have used fields prefixed with equal in search_fields and
I currently do get the results I expect, based on the

[http://docs.djangoproject.com/en/dev/ref/contrib/admin/#django.contrib.admin.ModelAdmin.search_fields
existing doc], when entering multiple words in the search field. (One word
entered can match exactly the equal-preceded field in search_fields and
another can match some other field in search fields.) The doc already
notes that it's not possible to search for an exact match on a value that
contains a space. As far as I can see current behavior is easily
understandable and documented, even if it is restrictive on what exactly
you can search for. I think the change you propose would break the case
where there are multiple fields in search_fields.

--
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] #15203: admin search_fields splitting query

2011-02-01 Thread Django

#15203: admin search_fields splitting query
+---
   Reporter:  wkornewald| Owner:  nobody
 Status:  new   | Milestone:  1.3   
  Component:  django.contrib.admin  |   Version:  1.2   
 Resolution:|  Keywords:
   Triage Stage:  Unreviewed| Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---

Old description:

> When you specify a ModelAdmin search_field as exact (with "=" prefix) the
> user's search query is split() and then multiple ``__iexact`` filters are
> applied, one for each word. This behavior doesn't make sense with a
> CharField because we're doing an iexact match (there's no way two
> distinct filters can match at the same time, except if we're doing a
> JOIN). It should just take the whole query and match against that.
>
> The same problem probably also affects ``__search`` queries (with an "@"
> prefix). The string should probably also be passed directly to the DB.

New description:

 When you specify a ModelAdmin search_field as exact (with "=" prefix) the
 user's search query is split() and then multiple `__iexact` filters are
 applied, one for each word. This behavior doesn't make sense with a
 !CharField because we're doing an iexact match (there's no way two
 distinct filters can match at the same time, except if we're doing a
 JOIN). It should just take the whole query and match against that.

 The same problem probably also affects `__search` queries (with an "@"
 prefix). The string should probably also be passed directly to the DB.

--

Comment (by ramiro):

 (!WikiFormatted slightly description)

-- 
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] #14303: admin inline form id attribute numbering order and uniqueness is lost

2011-02-01 Thread Django

#14303: admin inline form id attribute numbering order and uniqueness is lost
+---
   Reporter:  m0nonoke  | Owner:  nobody
  
 Status:  new   | Milestone:  1.3   
  
  Component:  django.contrib.admin  |   Version:  SVN   
  
 Resolution:|  Keywords:  inline 
javascript, sprintdec2010
   Triage Stage:  Ready for checkin | Has patch:  1 
  
Needs documentation:  0 |   Needs tests:  0 
  
Patch needs improvement:  0 |  
+---
Changes (by julien):

  * stage:  Accepted => Ready for checkin


Comment:

 RFC'ing my own patch but hopefully this is a simple-enough fix to allow me
 to do that :)

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

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

Re: [Django] #14830: Default value for radio button not preserved when dynamically creating new inlines

2011-02-01 Thread Django

#14830: Default value for radio button not preserved when dynamically creating 
new
inlines
+---
   Reporter:  julien| Owner:  nobody   
 Status:  new   | Milestone:  1.3  
  Component:  django.contrib.admin  |   Version:  1.2  
 Resolution:|  Keywords:  sprintdec2010
   Triage Stage:  Ready for checkin | Has patch:  1
Needs documentation:  0 |   Needs tests:  0
Patch needs improvement:  0 |  
+---
Changes (by julien):

  * stage:  Accepted => Ready for checkin


Comment:

 Even though this is not recommended practice, I'm taking the liberty to
 RFC my own patch to be sure this annoying bug grabs the attention of core
 devs before 1.3 ships ;-)

-- 
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] #15111: manage.py test fails if sites app not installed

2011-02-01 Thread Django

#15111: manage.py test fails if sites app not installed
-+--
   Reporter:  wkornewald | Owner:  nobody
 Status:  new| Milestone:  1.3   
  Component:  Contrib apps   |   Version:  SVN   
 Resolution: |  Keywords:
   Triage Stage:  Ready for checkin  | Has patch:  1 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--
Changes (by wkornewald):

 * cc: wkornewald@… (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] #14881: Do not assume ``User.id`` to be an integer in django.contrib.auth's pasword reset feature

2011-02-01 Thread Django

#14881: Do not assume ``User.id`` to be an integer in django.contrib.auth's 
pasword
reset feature
--+-
   Reporter:  jonash  | Owner:  nobody
 Status:  new | Milestone:
  Component:  Authentication  |   Version:  SVN   
 Resolution:  |  Keywords:
   Triage Stage:  Design decision needed  | Has patch:  1 
Needs documentation:  1   |   Needs tests:  1 
Patch needs improvement:  1   |  
--+-
Changes (by wkornewald):

 * cc: wkornewald@… (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] #14571: Update jQuery (was: Update jQuery to v1.4.4)

2011-02-01 Thread Django

#14571: Update jQuery
+---
   Reporter:  robhudson | Owner:  nobody

 Status:  new   | Milestone:  1.4   

  Component:  django.contrib.admin  |   Version:  1.2   

 Resolution:|  Keywords:  jquery 
sprintnov13
   Triage Stage:  Accepted  | Has patch:  1 

Needs documentation:  0 |   Needs tests:  0 

Patch needs improvement:  0 |  
+---
Changes (by julien):

  * milestone:  1.3 => 1.4


Comment:

 jQuery 1.5 was released yesterday :)
 http://blog.jquery.com/2011/01/31/jquery-15-released/

 This is not critical for 1.3 but certainly worthwhile for 1.4.

-- 
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] #13564: Provide class attributes for form fields

2011-02-01 Thread Django

#13564: Provide class attributes for form fields
+---
   Reporter:  h3| Owner:  trebor74hr
 Status:  assigned  | Milestone:
  Component:  Forms |   Version:  1.2-beta  
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---

Comment (by trebor74hr):

 Replying to [comment:13 julien]:
 > Feel free to create a new ticket for (2) and mention #13564 as a related
 ticket.

 I'm still not convinced that (2) should be created as ticket at all.
 Automatically filling css properties of fields/widgets is backward
 incompatible change, and therefore could cause problems. On the other
 hand, I use django.forms a lot, and in the cases like (2) is, I create my
 own base Form class (by inheriting django.forms.Form) and put all common
 functionality in there. Then I inherit this Form. Example for (2):

 {{{
 from django import forms

 class Form(forms.Form):
 def get_field_css_classes(self, bf, css_classes):
 css_classes.add("django-%s" % bf.field.__class__.__name__.lower())
 return css_classes

 class UserRegistrationForm(Form):
 ...
 }}}

 My suggestion is to solve only (1) and (2) could serve as example in
 documentation like explained.

 btw. I don't know if regular django user takes advantages of creating own
 customized Forms/Widgets/Fields + inheritance, but I have a feeling that
 this is not very often the case. If this is true, then I suggest stronger
 promotion of this powerful django feature. For the start, such approach
 could be (more) emphasized in the official django documentation (with
 examples).

-- 
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] #13774: add optional rel_db_type() method for model field

2011-02-01 Thread Django

#13774: add optional rel_db_type() method for model field
+---
   Reporter:  Suor  | Owner:  Suor  

 Status:  reopened  | Milestone:

  Component:  Database layer (models, ORM)  |   Version:  1.2   

 Resolution:|  Keywords:  db, 
ForeignKey, related fields
   Triage Stage:  Accepted  | Has patch:  1 

Needs documentation:  1 |   Needs tests:  1 

Patch needs improvement:  0 |  
+---
Changes (by wkornewald):

 * cc: wkornewald@… (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] #13960: abstract file upload/download handling

2011-02-01 Thread Django

#13960: abstract file upload/download handling
--+-
   Reporter:  wkornewald  | Owner:  nobody
 Status:  new | Milestone:
  Component:  File uploads/storage|   Version:  SVN   
 Resolution:  |  Keywords:
   Triage Stage:  Design decision needed  | Has patch:  1 
Needs documentation:  0   |   Needs tests:  0 
Patch needs improvement:  1   |  
--+-
Changes (by wkornewald):

 * cc: wkornewald@… (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] #13721: pass extra content-type values to file upload handlers

2011-02-01 Thread Django

#13721: pass extra content-type values to file upload handlers
+---
   Reporter:  wkornewald| Owner:  nobody
 Status:  new   | Milestone:  1.3   
  Component:  File uploads/storage  |   Version:  1.2   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Changes (by wkornewald):

 * cc: wkornewald@… (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] #12844: improve lazy loading and resource usage

2011-02-01 Thread Django

#12844: improve lazy loading and resource usage
--+-
   Reporter:  wkornewald  | Owner:  nobody
 Status:  new | Milestone:
  Component:  Uncategorized   |   Version:  SVN   
 Resolution:  |  Keywords:
   Triage Stage:  Design decision needed  | Has patch:  1 
Needs documentation:  0   |   Needs tests:  0 
Patch needs improvement:  0   |  
--+-
Changes (by wkornewald):

 * cc: wkornewald@… (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] #10192: Add support for App Engine

2011-02-01 Thread Django

#10192: Add support for App Engine
+---
   Reporter:  anonymous | Owner:  
nobody
 Status:  new   | Milestone:

  Component:  Database layer (models, ORM)  |   Version:  1.0   

 Resolution:|  Keywords:  app 
engine
   Triage Stage:  Someday/Maybe | Has patch:  0 

Needs documentation:  0 |   Needs tests:  0 

Patch needs improvement:  0 |  
+---
Changes (by wkornewald):

 * cc: wkornewald (removed)


-- 
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] #14924: I18N looks for translations in the reverse order of the apps

2011-02-01 Thread Django

#14924: I18N looks for translations in the reverse order of the apps
+---
   Reporter:  vanschelven   | Owner:  nobody
 Status:  new   | Milestone:  1.3   
  Component:  Internationalization  |   Version:  1.2   
 Resolution:|  Keywords:
   Triage Stage:  Ready for checkin | Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Changes (by jezdez):

  * stage:  Accepted => Ready for checkin
  * milestone:  => 1.3


-- 
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] #15203: admin search_fields splitting query

2011-02-01 Thread Django

#15203: admin search_fields splitting query
+---
   Reporter:  wkornewald| Owner:  nobody
 Status:  new   | Milestone:  1.3   
  Component:  django.contrib.admin  |   Version:  1.2   
 Resolution:|  Keywords:
   Triage Stage:  Unreviewed| Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Changes (by wkornewald):

 * cc: wkornewald@… (added)
  * needs_docs:  => 0
  * needs_tests:  => 0
  * needs_better_patch:  => 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] #15203: admin search_fields splitting query

2011-02-01 Thread Django

#15203: admin search_fields splitting query
--+-
 Reporter:  wkornewald|  Owner:  nobody
   Status:  new   |  Milestone:  1.3   
Component:  django.contrib.admin  |Version:  1.2   
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  1 |  
--+-
 When you specify a ModelAdmin search_field as exact (with "=" prefix) the
 user's search query is split() and then multiple ``__iexact`` filters are
 applied, one for each word. This behavior doesn't make sense with a
 CharField because we're doing an iexact match (there's no way two distinct
 filters can match at the same time, except if we're doing a JOIN). It
 should just take the whole query and match against that.

 The same problem probably also affects ``__search`` queries (with an "@"
 prefix). The string should probably also be passed directly to the DB.

-- 
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] #15198: AuthenticationForm.clean call does not have request set

2011-02-01 Thread Django

#15198: AuthenticationForm.clean call does not have request set
--+-
   Reporter:  Ciantic | Owner:  nobody
 Status:  new | Milestone:
  Component:  Authentication  |   Version:  SVN   
 Resolution:  |  Keywords:
   Triage Stage:  Unreviewed  | Has patch:  1 
Needs documentation:  0   |   Needs tests:  0 
Patch needs improvement:  1   |  
--+-
Changes (by Ciantic):

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


Comment:

 Apparently this patch breaks something, probably having something to do
 with cookie testing.

 (There is this cookie testing feature embeded in `AuthenticationForm`, and
 that needs to be isolated from `request` attribute.)

-- 
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] #15199: Allow MEDIA_ROOT inside STATIC_ROOT

2011-02-01 Thread Django

#15199: Allow MEDIA_ROOT inside STATIC_ROOT
--+-
   Reporter:  brutasse| Owner: 
 Status:  new | Milestone:  1.3
  Component:  django.contrib.staticfiles  |   Version:  SVN
 Resolution:  |  Keywords: 
   Triage Stage:  Unreviewed  | Has patch:  1  
Needs documentation:  0   |   Needs tests:  0  
Patch needs improvement:  1   |  
--+-

Comment (by brutasse):

 Hmmm this is trickier. With the patch applied, the media files aren't
 served by staticfiles but defining a custom view won't work either.

 {{{
 urlpatterns += patterns('django.contrib.staticfiles.views',
 url(r'^static/media/(?P.*)$', 'serve',
 {'document_root': settings.MEDIA_ROOT}),
 )
 }}}

 The 'serve' view is called, but the options dict is not passed to the
 view. 'document_root' is swallowed somewhere and ends up as None in the
 view, something bad probably happens in the staticfiles handler. If I
 change MEDIA_URL to '/static_media/' and the URL pattern to
 {{{r'^static_media/(?P.*)$'}}}, the options dict is correctly passed
 to the view.

 I thought modifying _should_handle() on !StaticFilesHandler would do the
 job, but apparently it's not enough. The staticfiles handler isn't
 transparently giving the control back to the parent WSGIHandler if
 _should_handle returns false.

-- 
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] #15126: Misleading error in ModelForm

2011-02-01 Thread Django

#15126: Misleading error in ModelForm
---+
   Reporter:  ingo@…   | Owner:  nobody 
  
 Status:  new  | Milestone: 
  
  Component:  Forms|   Version:  1.2
  
 Resolution:   |  Keywords:  modelform fields 
attributeerror widget subset
   Triage Stage:  Accepted | Has patch:  1  
  
Needs documentation:  0|   Needs tests:  0  
  
Patch needs improvement:  0|  
---+
Changes (by bpeschier):

  * has_patch:  0 => 1


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

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

Re: [Django] #15126: Misleading error in ModelForm

2011-02-01 Thread Django

#15126: Misleading error in ModelForm
---+
   Reporter:  ingo@…   | Owner:  nobody 
  
 Status:  new  | Milestone: 
  
  Component:  Forms|   Version:  1.2
  
 Resolution:   |  Keywords:  modelform fields 
attributeerror widget subset
   Triage Stage:  Accepted | Has patch:  0  
  
Needs documentation:  0|   Needs tests:  0  
  
Patch needs improvement:  0|  
---+

Comment (by bpeschier):

 The above patch tests both fields and exclude for the error. It also
 includes an extension of the forms-testsuite which tests whether or not
 the validation is done.

 I have two comments with the patch; it would be nice if somebody would
 reflect on them

 1. The patch tests specifically for 'str' because I did not want to impair
 fancy gizmos and create a regression (the docs are not specific on what
 kind of list fields should be). Testing for string tests for the common
 mistake without restricting other iterables

 2. I was not that familiar with testing exceptions thrown by class
 definitions, so I would appreciate a second opinion on them :-)

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

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

[Django] #15202: Changeset 15376 breaks implementation

2011-02-01 Thread Django

#15202: Changeset 15376 breaks implementation
+---
 Reporter:  liorsion|  Owner:
   Status:  new |  Milestone:
Component:  django.contrib.staticfiles  |Version:  SVN   
 Keywords:  |   Triage Stage:  Unreviewed
Has patch:  0   |  
+---
 The changeset 15376  (http://code.djangoproject.com/changeset/15376) added
 a test that caused most known implementations (for example, here:
 http://stackoverflow.com/questions/4565935/django-staticfiles-app-help) -
 there's a lot of sense in letting django look for static files on the
 STATIC_ROOT directory

-- 
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] #15190: collectstatic should not symlink files that are already symlinked

2011-02-01 Thread Django

#15190: collectstatic should not symlink files that are already symlinked
--+-
   Reporter:  bendavis78  | Owner:  nobody  
   
 Status:  new | Milestone:  1.3 
   
  Component:  django.contrib.staticfiles  |   Version:  
1.3-beta   
 Resolution:  |  Keywords:  
staticfiles
   Triage Stage:  Accepted| Has patch:  0   
   
Needs documentation:  0   |   Needs tests:  0   
   
Patch needs improvement:  0   |  
--+-
Changes (by jezdez):

  * component:  Contrib apps => django.contrib.staticfiles


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

76 matches

Mail list logo