date:20090204

Re: [Django] #10196: width/height_field not being set on ImageField

2009-02-04 Thread Django

#10196: width/height_field not being set on ImageField
---+
  Reporter:  vicvicvic | Owner:  nobody 

Status:  new   | Milestone: 

 Component:  File uploads/storage  |   Version:  SVN

Resolution:|  Keywords:  imagefield, 
width_field
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  1  

Needs_better_patch:  0 |  
---+
Comment (by Alex):

 I don't see anything that leads me to believe it would, but since that
 problem applies to ImageFields only my guess is it's either this or
 something similar.

-- 
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] #10196: width/height_field not being set on ImageField

2009-02-04 Thread Django

#10196: width/height_field not being set on ImageField
---+
  Reporter:  vicvicvic | Owner:  nobody 

Status:  new   | Milestone: 

 Component:  File uploads/storage  |   Version:  SVN

Resolution:|  Keywords:  imagefield, 
width_field
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  1  

Needs_better_patch:  0 |  
---+
Comment (by kmtracey):

 Any idea if this will also fix #10121?

-- 
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] #10197: Annotate breaks pickling of QuerySet

2009-02-04 Thread Django

#10197: Annotate breaks pickling of QuerySet
---+
  Reporter:  ja...@thelances.net   | Owner:  nobody 
   
Status:  new   | Milestone: 
   
 Component:  Database layer (models, ORM)  |   Version:  SVN
   
Resolution:|  Keywords:  pickle, 
queryset, annotate
 Stage:  Unreviewed| Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

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

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

[Django] #10197: Annotate breaks pickling of QuerySet

2009-02-04 Thread Django

#10197: Annotate breaks pickling of QuerySet
--+-
 Reporter:  ja...@thelances.net   |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  SVN   
 Keywords:  pickle, queryset, annotate|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 I'm using the latest version from svn (as of 1-4-09) and python2.5.  I'm
 trying to pickle a QuerySet that is using annotate and I'm getting the
 following error:
 {{{
 raise TypeError, "can't pickle %s objects" % base.__name__
 TypeError: can't pickle function objects
 }}}

 Here is what I'm trying to do:
 (ProductChannel has OneToMany relationship with ProductChannelImage)
 {{{
 pc = ProductChannel.objects.filter(supplier=supplier)
 pc = pc.filter(status='new')
 pc = pc.annotate(num_images=Count('productchannelimage'))
 ...
 request.session['pc_qs'] = dumps(pc.query)
 }}}

 Before I added the annotation to the query it was pickling just fine.

-- 
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] #10196: width/height_field not being set on ImageField

2009-02-04 Thread Django

#10196: width/height_field not being set on ImageField
---+
  Reporter:  vicvicvic | Owner:  nobody 

Status:  new   | Milestone: 

 Component:  File uploads/storage  |   Version:  SVN

Resolution:|  Keywords:  imagefield, 
width_field
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  1  

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

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

Comment:

 This fix looks to be correct, could you please add a testcase?

-- 
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] #10196: width/height_field not being set on ImageField

2009-02-04 Thread Django

#10196: width/height_field not being set on ImageField
-+--
 Reporter:  vicvicvic|   Owner:  nobody
   Status:  new  |   Milestone:
Component:  File uploads/storage | Version:  SVN   
 Keywords:  imagefield, width_field  |   Stage:  Unreviewed
Has_patch:  1|  
-+--
 [9766] broke (width|height)_field for ImageField. They are not being
 updated properly because ImageField.save is not being called.

 This was reported both in #10044 and on http://groups.google.com/group
 /django-
 users/browse_thread/thread/6fb4b1e8ec37fda3/eaf739b883e66fcf#eaf739b883e66fcf
 but I can't seem to find a ticket for it.

 At any rate, I believe I have found the problem and am submitting a patch
 which restores functionality.

-- 
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] #10044: FileField should accept assignment of File objects

2009-02-04 Thread Django

#10044: FileField should accept assignment of File objects
---+
  Reporter:  Gulopine  | Owner:  Gulopine
Status:  closed| Milestone:  
 Component:  File uploads/storage  |   Version:  1.0 
Resolution:  fixed |  Keywords:  
 Stage:  Unreviewed| Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  1 |  
---+
Changes (by Alex):

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

Comment:

 This bug has been fixed, please open a new ticket since thats a seperate
 issue(even if it's a consequence of this)(I think a ticket is already
 open).

-- 
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] #10195: Missing leading colon in syndication.txt

2009-02-04 Thread Django

#10195: Missing leading colon in syndication.txt
---+
 Reporter:  toxik  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 [source:/django/trunk/docs/ref/contrib/syndication.txt
 contrib/syndication.txt] is missing a leading colon on the `:meth:` role
 at line 262.

-- 
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] #7324: {{ block.super }} doesn't work with nested {% block %} statements

2009-02-04 Thread Django

#7324: {{ block.super }} doesn't work with nested {% block %} statements
--+-
  Reporter:  jeverling| Owner:  nobody  
Status:  closed   | Milestone:  
 Component:  Template system  |   Version:  SVN 
Resolution:  invalid  |  Keywords:  block.super template
 Stage:  Unreviewed   | Has_patch:  0   
Needs_docs:  0|   Needs_tests:  0   
Needs_better_patch:  0|  
--+-
Comment (by kmtracey):

 OK, just for clarity and so people don't have to unzip the project.  The
 parent template `new/test.html` contains:

 {{{
 {% block main %}
 New content
 {% block submain %}This should be inherited{% endblock %}
 {% endblock %}
 }}}

 The child template, `templates-top/test.html` contains:

 {{{
 {% extends "new/test.html" %}
 {% comment %}Gets around infinite recursion bug by namespacing with a
 directory{% endcomment %}
 {% block main %}
 Top-level main block
 {% comment %}remove this block.super and it all disappears. But I only
 want the block.super from inside "submain"{% endcomment %}
 {{ block.super }}
 {% block submain %}
 my new sub-content
 {{ block.super }}
 {% comment %}I expect this block.super to contain the content of
 "submain" from new/test.html, because I'm extending it. It is empty,
 UNLESS "main" has a block.super call, in which case it's echoed TWICE{%
 endcomment %}
 {% endblock %}

 {% endblock %}

 }}}

 Consider what the child template is doing.  By including a {% block main
 %} it is saying "I want to override the contents of the block named "main"
 in the parent template with this content I am specifying here."  When it
 does that, block "submain" ceases to exist, as the "submain" block was
 declared within block main in the parent.  If you discard the contents of
 the parent template's main block in favor of what is in the child
 template, then you lose the "submain" block entirely.  You can get it back
 by including block.super in the child's "main" override, but then anything
 else you have in the child's "main" is simply appended to the parent's
 "main" content, which doesn't seem to be what you want.

 I said this earlier and I'll say it again: django-users would be a better
 place to outline what you are looking to achieve and get ideas on how to
 accomplish it.  There is a much larger audience there than in the ticket
 system.  So far as I can see there is not a bug here, it's just a case of
 the template inheritance mechanism not quite working the way you'd like it
 to.

-- 
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] #10179: admin broken on FileField with blank=True

2009-02-04 Thread Django

#10179: admin broken on FileField with blank=True
--+-
  Reporter:  malte| Owner:  nobody 
Status:  new  | Milestone: 
 Component:  django-admin.py  |   Version:  1.0
Resolution:   |  Keywords:  admin filefield bug
 Stage:  Unreviewed   | Has_patch:  0  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Comment (by erwinell...@gmail.com):

 Malte suggests that this might have something to do with using SQLite, but
 I came across this problem on PostgreSQL as well.

-- 
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] #10179: admin broken on FileField with blank=True

2009-02-04 Thread Django

#10179: admin broken on FileField with blank=True
--+-
  Reporter:  malte| Owner:  nobody 
Status:  new  | Milestone: 
 Component:  django-admin.py  |   Version:  1.0
Resolution:   |  Keywords:  admin filefield bug
 Stage:  Unreviewed   | Has_patch:  0  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Comment (by erwinell...@gmail.com):

 Replying to [comment:2 ramiro]:
 > (reformatted description)
 >
 > malte: What version of Django are you using? If youa re using a revision
 from trunk latter that r9766, can you please try with r9765 and report
 back?


 Ramiro: I can confirm that this problem does not exist in r9755 and starts
 appearing as of r9766.

 (For others: A thread on this on Django Users Google Group can be found
 here [http://groups.google.com/group/django-
 users/browse_thread/thread/b618845843bced67/8905992cb00ec0a1])

-- 
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] #10166: Cookie test fails in login() view

2009-02-04 Thread Django

#10166: Cookie test fails in login() view
-+--
  Reporter:  iakbar  | Owner:  nobody   

Status:  new | Milestone:   

 Component:  Authentication  |   Version:  1.0  

Resolution:  |  Keywords:  authentication, cookie, 
login
 Stage:  Unreviewed  | Has_patch:  1

Needs_docs:  0   |   Needs_tests:  1

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

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

Comment:

 The fix is simple. Line 21 of the default django.contrib.auth.views file
 (of the 1.0.2 release) should be :

 form = AuthenticationForm(data=request.POST, request=request)

 instead of

 form = AuthenticationForm(data=request.POST)

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

Re: [Django] #7133: django admin: radio_admin is broken with addPopup and RelatedObjectLookups.js

2009-02-04 Thread Django

#7133: django admin: radio_admin is broken with addPopup and
RelatedObjectLookups.js
-+--
  Reporter:  trbs| Owner:  nobody   

Status:  closed  | Milestone:   

 Component:  django.contrib.admin|   Version:  newforms-admin   

Resolution:  duplicate   |  Keywords:  radio_admin, 
relatedobjectlookups nfa_someday
 Stage:  Design decision needed  | Has_patch:  1

Needs_docs:  0   |   Needs_tests:  0

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

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

Comment:

 I don't see why a new ticket was needed here -- the identified problem
 could as easily have been fixed under this ticket as a new one.  You could
 have changed the summary, version, etc. to more accurately describe the
 current situation, if necessary.  But, since you've created a new ticket
 and put the patch there, we can use that one.  (You also could have closed
 this yourself -- no special privs are needed to close tickets.)

-- 
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] #10121: ImageField loses data when re-saving from admin

2009-02-04 Thread Django

#10121: ImageField loses data when re-saving from admin
---+
  Reporter:  Uninen| Owner: 

Status:  new   | Milestone: 

 Component:  django.contrib.admin  |   Version:  SVN

Resolution:|  Keywords:  admin, ImageField, 
save
 Stage:  Unreviewed| Has_patch:  0  

Needs_docs:  0 |   Needs_tests:  0  

Needs_better_patch:  0 |  
---+
Comment (by kmtracey):

 Replying to [comment:5 Valera Grishin]:
 > I have the same problem.
 > Any workarounds before it is fixed in trunk?

 The simplest workaround is to back off to r9765, or use the 1.0.X branch
 instead of trunk.  If, however, you want to pick up trunk-only changes
 that have been made since then, just not r9766, you could, in your local
 tree, do a reverse merge to undo the effects of r9766, as is described
 here, for example:

 http://markphip.blogspot.com/2007/01/how-to-undo-commit-in-subversion.html

 (minus the commit part).  Those are the workarounds I can think of.  (If
 someone who is having trouble with the effects of r9766 could investigate
 and come up with a fix that achieves the goals of r9766 without the
 problems it introduced, that would be even better.)

-- 
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] #5711: serialize doesn't work with extra()

2009-02-04 Thread Django

#5711: serialize doesn't work with extra()
-+--
  Reporter:  valan...@gmail.com  | Owner:  nobody
Status:  new | Milestone:
 Component:  Serialization   |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by bthomas):

 * cc: btho...@ncircle.com (added)

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

[Django] #10194: allow model instance as argument to HttpResponseRedirect constructor

2009-02-04 Thread Django

#10194: allow model instance as argument to HttpResponseRedirect constructor
---+
 Reporter:  Daniel Pope   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  HTTP handling  | Version:  1.0   
 Keywords:  shortcut wishlist  |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Something I do fairly often is

 {{{
 return HttpResponseRedirect(model_inst.get_absolute_url())
 }}}

 It just occurred to me that

 {{{
 return HttpResponseRedirect(model_inst)
 }}}

 would be much more concise, and in the long run, more legible.

 Obviously this would constitute an association between {{{django.http}}}
 and {{{django.db.model}}} which I believe we try to avoid in general.
 Perhaps a more appropriate for such a shortcut would be

 {{{
 from django.shortcuts import redirect
 return redirect(model_inst)
 }}}

-- 
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] #10121: ImageField loses data when re-saving from admin

2009-02-04 Thread Django

#10121: ImageField loses data when re-saving from admin
---+
  Reporter:  Uninen| Owner: 

Status:  new   | Milestone: 

 Component:  django.contrib.admin  |   Version:  SVN

Resolution:|  Keywords:  admin, ImageField, 
save
 Stage:  Unreviewed| Has_patch:  0  

Needs_docs:  0 |   Needs_tests:  0  

Needs_better_patch:  0 |  
---+
Comment (by Valera Grishin):

 I have the same problem.
 Any workarounds before it is fixed in 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
-~--~~~~--~~--~--~---

[Django] #10193: Meaning of 'path to file' parameter is unclear in documentation

2009-02-04 Thread Django

#10193: Meaning of 'path to file' parameter is unclear in documentation
---+
 Reporter:  Art_S  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 The document at

 http://docs.djangoproject.com/en/dev/topics/files/

 says:

 default_storage.save('/path/to/file', ContentFile('new content'))

 There is some ambiguity in the example given. One can assume that
 '/path/to/file' refers only to a path but not path-name of the file.

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

2009-02-04 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
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

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

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

[Django] #10192: Add support for App Engine

2009-02-04 Thread Django

#10192: Add support for App Engine
--+-
 Reporter:  anonymous |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  1.0   
 Keywords:  app engine|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 I've started writing a proposal describing what could be necessary for an
 App Engine port of Django on my app-engine-patch project site (which is a
 more high-level port of Django's features to App Engine where you have to
 use Google's Model class):

 http://code.google.com/p/app-engine-patch/wiki/DjangoAppEnginePort

 It might be possible to get most of Django ported, so at least simple apps
 could be used on App Engine without any modifications. The big problems
 start with transactions, though. I could help with an official port, but I
 can't implement the (quite big) modifications alone.

-- 
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] #10057: ModelAdmin.render_change_form should not override the 'has_delete' option

2009-02-04 Thread Django

#10057: ModelAdmin.render_change_form should not override the 'has_delete' 
option
---+
  Reporter:  rajeesh   | Owner:  nobody 
  
Status:  new   | Milestone:  post-1.0   
  
 Component:  django.contrib.admin  |   Version:  SVN
  
Resolution:|  Keywords:  ModelAdmin 
render_change_form
 Stage:  Unreviewed| Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Comment (by anonymous):

 Well, what happened to this?

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

Re: [Django] #10183: assertContains fails when there is unicode in the response content

2009-02-04 Thread Django

#10183: assertContains fails when there is unicode in the response content
+---
  Reporter:  drakonen   | Owner:  nobody
  
Status:  new| Milestone:  post-1.0  
  
 Component:  Testing framework  |   Version:  1.0   
  
Resolution: |  Keywords:  testcases, 
assertContains, assertNotContains
 Stage:  Unreviewed | Has_patch:  1 
  
Needs_docs:  0  |   Needs_tests:  0 
  
Needs_better_patch:  0  |  
+---
Changes (by trbs):

  * keywords:  => testcases, assertContains, assertNotContains
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 A little rational behind the patch;

 Python raised the UnicodeDecodeError because it's asked to count a unicode
 string within a non-unicode string.
 HttpResponse's content property uses smart_str to create content data, it
 would seem to make sense to do
 the same for any text used in assertContains and assertNotContains.

 I've added an updated patch to this ticket which uses smart_str(text,
 response._charset) which matches the HttpResponse
 object behavior. Could also have used settings.DEFAULT_CHARSET but it
 seems with ticket #10190 this might change later on so response._charset
 seems a safer bet :)

-- 
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] #7133: django admin: radio_admin is broken with addPopup and RelatedObjectLookups.js

2009-02-04 Thread Django

#7133: django admin: radio_admin is broken with addPopup and
RelatedObjectLookups.js
-+--
  Reporter:  trbs| Owner:  nobody   

Status:  new | Milestone:   

 Component:  django.contrib.admin|   Version:  newforms-admin   

Resolution:  |  Keywords:  radio_admin, 
relatedobjectlookups nfa_someday
 Stage:  Design decision needed  | Has_patch:  1

Needs_docs:  0   |   Needs_tests:  0

Needs_better_patch:  0   |  
-+--
Comment (by trbs):

 As far as i can see this is not applicable anymore on post-Django 1.0
 Recommend closing the ticket. (also added a patch to a new ticket,
 fixing/adding the dynamic additions of items to a radiolist in the admin:
 #10191 )

-- 
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] #10191: Fix / Add support for radiobuttons after adding item with popup in Django Admin

2009-02-04 Thread Django

#10191: Fix / Add support for radiobuttons after adding item with popup in 
Django
Admin
+---
 Reporter:  trbs|   
Owner:  nobody
   Status:  new |   
Milestone:  post-1.0  
Component:  django.contrib.admin| 
Version:  1.0   
 Keywords:  admin, radio, radiolist, dismissAddAnotherPopup, popup  |   
Stage:  Unreviewed
Has_patch:  1   |  
+---
 The following patch adds support for dynamically adding radiobutton items
 to the admin page.

 Without this patch the newly added item through the popup menu does not
 get added to the page and
 the user must reload the page before being able to select the new item.

 The patch adds an extra case to dismissAddAnotherPopup in
 RelatedObjectsLookup.js which creates and appends the necessary html to
 the list of radiobuttons on the page.

 Tested with django.contrib.redirects and a slightly modified version of
 django-podcast.
 Works (for me) on Firefox, IE and Opera.

-- 
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] #10196: width/height_field not being set on ImageField

Re: [Django] #10196: width/height_field not being set on ImageField

Re: [Django] #10197: Annotate breaks pickling of QuerySet

[Django] #10197: Annotate breaks pickling of QuerySet

Re: [Django] #10196: width/height_field not being set on ImageField

[Django] #10196: width/height_field not being set on ImageField

Re: [Django] #10044: FileField should accept assignment of File objects

[Django] #10195: Missing leading colon in syndication.txt

Re: [Django] #7324: {{ block.super }} doesn't work with nested {% block %} statements

Re: [Django] #10179: admin broken on FileField with blank=True

Re: [Django] #10179: admin broken on FileField with blank=True

Re: [Django] #10166: Cookie test fails in login() view

Re: [Django] #7133: django admin: radio_admin is broken with addPopup and RelatedObjectLookups.js

Re: [Django] #10121: ImageField loses data when re-saving from admin

Re: [Django] #5711: serialize doesn't work with extra()

[Django] #10194: allow model instance as argument to HttpResponseRedirect constructor

Re: [Django] #10121: ImageField loses data when re-saving from admin

[Django] #10193: Meaning of 'path to file' parameter is unclear in documentation

Re: [Django] #10192: Add support for App Engine

[Django] #10192: Add support for App Engine

Re: [Django] #10057: ModelAdmin.render_change_form should not override the 'has_delete' option

Re: [Django] #10183: assertContains fails when there is unicode in the response content

Re: [Django] #7133: django admin: radio_admin is broken with addPopup and RelatedObjectLookups.js

[Django] #10191: Fix / Add support for radiobuttons after adding item with popup in Django Admin

24 matches

Site Navigation

Mail list logo

Footer information