Re: [Django] #11995: Use raw_id_fields for 'user' field on contrib.comments.models.Comment

[Django]

#11995: Use raw_id_fields for 'user' field on contrib.comments.models.Comment
--+-
  Reporter:  ubernostrum  | Owner:  nobody
Status:  new  | Milestone:
 Component:  django.contrib.comments  |   Version:  1.1   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by russellm):

  * 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] #11995: Use raw_id_fields for 'user' field on contrib.comments.models.Comment

[Django]

#11995: Use raw_id_fields for 'user' field on contrib.comments.models.Comment
--+-
  Reporter:  ubernostrum  | Owner:  nobody
Status:  new  | Milestone:
 Component:  django.contrib.comments  |   Version:  1.1   
Resolution:   |  Keywords:
 Stage:  Unreviewed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by ubernostrum):

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

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

[Django] #11995: Use raw_id_fields for 'user' field on contrib.comments.models.Comment

[Django]

#11995: Use raw_id_fields for 'user' field on contrib.comments.models.Comment
-+--
 Reporter:  ubernostrum  |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  django.contrib.comments  | Version:  1.1   
 Keywords:   |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 Title really says it all; it's not uncommon to have so many users on a
 site that rendering the normal foreign-key dropdown on a the add/edit page
 makes the admin unusable.

-- 
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] #8576: Multiple AutoFields in a model

[Django]

#8576: Multiple AutoFields in a model
---+
  Reporter:  honeyman  | Owner:  nobody 
   
Status:  reopened  | Milestone: 
   
 Component:  Database layer (models, ORM)  |   Version:  SVN
   
Resolution:|  Keywords:  multiple 
autofield
 Stage:  Design decision needed| Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by seanmonstar):

  * status:  closed => reopened
  * has_patch:  1 => 0
  * resolution:  wontfix =>

Comment:

 while some backends can't support, at the least, PostgreSQL can. You can
 assign multiple values as "serial", only one needs to be primary key.

 And a use case where I've used (has to do with ordering):

 Say I have a bunch of pages in a CMS. The primary auto field would be the
 id.  But I also want you to be able to change the order they show up in.
 By default, the ordering should be as you create them. Meaning my
 page_order column also can't have null values, but should all be a
 sequential number. And it needs to be a different number than the id,
 since the ID doesn't ever change.

 It seems possible to check if the backend picked was one that works
 (Postgres) and if so, not assert primary_key on the AutoFields.  On
 backends where the implementation wouldn't work, you can toss an error. I
 shouldn't be stuck with MySQL functionality if I can use PostgreSQL. :)

-- 
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] #10809: mod_wsgi authentication handler

[Django]

#10809: mod_wsgi authentication handler
-+--
  Reporter:  baumer1122  | Owner:  nobody  
Status:  new | Milestone:  
 Component:  Authentication  |   Version:  SVN 
Resolution:  |  Keywords:  mod_wsgi
 Stage:  Design decision needed  | Has_patch:  1   
Needs_docs:  1   |   Needs_tests:  0   
Needs_better_patch:  1   |  
-+--
Comment (by davidfischer):

 Graham. I understand that the `DJANGO_SETTINGS_MODULE` can be set from
 inside an external mod_wsgi auth script as it is in the
 [http://code.google.com/p/modwsgi/wiki/AccessControlMechanisms mod_wsgi
 docs]. However, this ticket is about putting a generic mod_wsgi auth
 handler into the Django code line. A generic handler would need to somehow
 set `DJANGO_SETTINGS_MODULE` and possibly the Python path. The
 
[http://code.djangoproject.com/browser/django/trunk/django/contrib/auth/handlers/modpython.py
 mod_python handler], for example, must set `DJANGO_SETTINGS_MODULE` into
 `os.environ` before
 {{{
 from django.contrib.auth.models import User
 }}}
 A generic mod_wsgi handler would probably need to do something similar,
 but I'm not sure that's possible. Ideally, I think that the functionality
 and setup of a mod_wsgi auth handler should be very close to
 [http://docs.djangoproject.com/en/1.0/howto/apache-auth/ that] of the
 mod_python auth handler. Ideally, using a mod_wsgi auth handler would be
 as easy as:
 {{{
 
 AuthType Basic
 AuthName "wsgi protected"
 Require valid-user
 # maybe set DJANGO_SETTINGS_MODULE here somehow
 AuthBasicProvider wsgi
 WSGIAuthUserScript  django.contrib.auth.handlers.modwsgi
 
 }}}
 Maintaining an extra custom auth script works fine (I'm using it), but it
 seems like everybody who uses Django/mod_wsgi authentication is going to
 have the same auth script with only the `DJANGO_SETTINGS_MODULE` changed.
 Some abstraction might be nice.

 By the way, mod_wsgi is great! I'm a big fan and I'm not trying to put it
 down.

-- 
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] #10314: TestCase assert methods do not accept a msg parameter

[Django]

#10314: TestCase assert methods do not accept a msg parameter
+---
  Reporter:  wwinham| Owner:  nobody
Status:  closed | Milestone:
 Component:  Testing framework  |   Version:  1.0   
Resolution:  wontfix|  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 As sebleier noted, this is an ill-posed request. Assertions like
 assertFormError raised many different error messages, so a simple one-
 message parameterization will be insufficient.

 If there is a problem with a specific error message (as is suggested by
 comment 3), the the solution is to fix that error message. Suggestions
 welcome.

-- 
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] #10809: mod_wsgi authentication handler

[Django]

#10809: mod_wsgi authentication handler
-+--
  Reporter:  baumer1122  | Owner:  nobody  
Status:  new | Milestone:  
 Component:  Authentication  |   Version:  SVN 
Resolution:  |  Keywords:  mod_wsgi
 Stage:  Design decision needed  | Has_patch:  1   
Needs_docs:  1   |   Needs_tests:  0   
Needs_better_patch:  1   |  
-+--
Comment (by grahamd):

 David. The mod_wsgi package does not need to be changed. You just need to
 have the value of DJANGO_SETTINGS_MODULE be specified in the
 authentication script file. Same with any Python module search path that
 needs to be set.

 {{{
 import sys
 sys.path.append(...)

 import os
 os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings'

 def check_password(environ, user, password):
   ...
 }}}

 The SetEnv variables are not passed to the authentication scripts because
 they are executed during an earlier phase than when SetEnv variables are
 pushed into request environment by Apache.

-- 
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] #11882: Documentation missing for django.contrib.admin.ModelAdmin.formfield_for_manytomany

[Django]

#11882: Documentation missing for
django.contrib.admin.ModelAdmin.formfield_for_manytomany
+---
  Reporter:  Nils L | Owner:  anonymous 
 
Status:  assigned   | Milestone:
 
 Component:  Documentation  |   Version:  1.1   
 
Resolution: |  Keywords:  formfield_for_manytomany, 
admin
 Stage:  Accepted   | Has_patch:  1 
 
Needs_docs:  0  |   Needs_tests:  0 
 
Needs_better_patch:  0  |  
+---
Changes (by Rob Hudson ):

  * 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] #9268: Pass custom form values from post-comment to preview-comment

[Django]

#9268: Pass custom form values from post-comment to preview-comment
--+-
  Reporter:  taojian  | Owner:  stuartk
Status:  closed   | Milestone:  1.1
 Component:  django.contrib.comments  |   Version:  SVN
Resolution:  fixed|  Keywords:  comment preview
 Stage:  Accepted | Has_patch:  1  
Needs_docs:  1|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by mfeet):

  * needs_docs:  0 => 1

Comment:

 I have recently come across this aswell, and again using {{ data.next }}
 does not work.

 Instead the code is making a variable {{ next }} instead available, which
 is wrong in the docs. Is this what is wanted? I thought the way it was
 meant to be accessed was through {{ data.next }}, but this currently is
 not the case.

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

[Django] #11994: save upload file with specify encode

[Django]

#11994: save upload file with specify encode
--+-
 Reporter:  flyinfl...@gmail.com  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  File uploads/storage  | Version:  1.1   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 {{{
 # -*- coding: utf-8 -*-
 # in models.py
 def get_path(instance, filename):
 path = osp.join('uploads', '中文'.encode('utf8'), filename)
 return path
 class Files(models.Model):
 name = models.CharField(max_length=64)
 files = models.FileField(upload_to=get_path, storage=MyStorage)
 }}}

 Upload file with above code on Chinese version MS-Windows, it will get
 strange filename which contains unreadable characters.

 I guess this problem associated with Chinese version MS-Windows using GBK
 encoding by default.
 After read debug a long time and has read
 http://docs.djangoproject.com/en/dev/howto/custom-file-storage/, I think
 use custom storage which could specify save file with specify encode, such
 as GBK could fix my problem.

 Django is a very very very good Web framework, I hope developers could add
 this feature, and please don't try to restrict user or down stream
 developers, thanks.

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

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

[Django]

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

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

Comment:

 It's probably because of this bug and the way it was fixed in Python
 2.6.3: http://bugs.python.org/issue6795, catching ValueError makes test
 pass.

-- 
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] #11993: ValueError: Cannot convert NaN to integer in regressiontests.defaultfilters.tests using Python 2.6.3

[Django]

#11993: ValueError: Cannot convert NaN to integer in
regressiontests.defaultfilters.tests using Python 2.6.3
---+
 Reporter:  kklimonda  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Automatic rebuild of Django 1.1 on Ubuntu 9.10 has shown that the
 following regression test fails on Python 2.6.3:
 {{{
 ==
 FAIL: Doctest: regressiontests.defaultfilters.tests
 --
 Traceback (most recent call last):
   File "/build/buildd/python-django-1.1/django/test/_doctest.py", line
 2180, in runTest
 raise self.failureException(self.format_failure(new.getvalue()))
 AssertionError: Failed doctest test for
 regressiontests.defaultfilters.tests
   File "/build/buildd/python-
 django-1.1/tests/regressiontests/defaultfilters/tests.py", line 2, in
 tests

 --
 File "/build/buildd/python-
 django-1.1/tests/regressiontests/defaultfilters/tests.py", line 53, in
 regressiontests.defaultfilters.tests
 Failed example:
 floatformat(nan) == unicode(nan)
 Exception raised:
 Traceback (most recent call last):
   File "/build/buildd/python-django-1.1/django/test/_doctest.py", line
 1267, in __run
 compileflags, 1) in test.globs
   File "", line 1,
 in 
 floatformat(nan) == unicode(nan)
   File "/build/buildd/python-
 django-1.1/django/template/defaultfilters.py", line 164, in floatformat
 m = int(d) - d
   File "/usr/lib/python2.6/decimal.py", line 1515, in __int__
 raise ValueError("Cannot convert NaN to integer")
 ValueError: Cannot convert NaN to integer

 --
 Ran 859 tests in 408.553s

 FAILED (failures=1)
 }}}
 The same happens with the current trunk 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] #11992: modelformset_factory

[Django]

#11992: modelformset_factory
-+--
  Reporter:  unk2k   | Owner:  nobody
Status:  closed  | Milestone:  1.2   
 Component:  Forms   |   Version:  1.1   
Resolution:  invalid |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Old description:

> Environment:
>
> Request Method: POST
> Request URL: http://panel.raf-leasing.ru:8000/company/finance/2544400/
> Django Version: 1.2 pre-alpha
> Python Version: 2.6.2
> Installed Applications:
> ['sessions', 'company', 'auth', 'lib']
> Installed Middleware:
> ('django.middleware.common.CommonMiddleware',
>  'sessions.middleware.SessionMiddleware',
>  'auth.middleware.AuthMiddleware',
>  'django.middleware.transaction.TransactionMiddleware')
>

> Traceback:
> File "/usr/local/lib/python2.6/dist-
> packages/django/core/handlers/base.py" in get_response
>   92. response = callback(request, *callback_args,
> **callback_kwargs)
> File "/home/r00t/django/rafpaneloracle2/lib/isauth.py" in wrap
>   8. return f(request, *args, **kwargs)
> File "/home/r00t/django/rafpaneloracle2/lib/render.py" in wrapper
>   20. output = func(request, *args, **kw)
> File "/home/r00t/django/rafpaneloracle2/company/views.py" in finance
>   140. formset = FinanceSet(request.POST,
> queryset=Finance.objects.filter(company_id=company.id,
> quarter__in=quarter, year__in=year))
> File "/home/r00t/django/rafpaneloracle2/company/forms.py" in __init__
>   209. super (FinanceForm,self ).__init__(*args,**kwargs) #
> populates the post
> File "/usr/local/lib/python2.6/dist-packages/django/forms/models.py" in
> __init__
>   459. super(BaseModelFormSet, self).__init__(**defaults)
> File "/usr/local/lib/python2.6/dist-packages/django/forms/formsets.py" in
> __init__
>   44. self._construct_forms()
> File "/usr/local/lib/python2.6/dist-packages/django/forms/formsets.py" in
> _construct_forms
>   88. self.forms.append(self._construct_form(i))
> File "/usr/local/lib/python2.6/dist-packages/django/forms/models.py" in
> _construct_form
>   475. pk = self.data[pk_key]
> File "/usr/local/lib/python2.6/dist-
> packages/django/utils/datastructures.py" in __getitem__
>   203. raise MultiValueDictKeyError, "Key %r not found in %r"
> % (key, self)
>
> Exception Type: MultiValueDictKeyError at /company/finance/2544400/
> Exception Value: Key 'form-0-id' not found in  {u'form-0-capital': [u'0,00'], u'form-0-actives': [u'0,00'],
> u'form-2-charity': [u'0,00'], u'form-3-income': [u'0,00'],
> u'form-1-actives': [u'0,00'], u'form-1-charity': [u'0,00'],
> u'form-0-income': [u'0,00'], u'form-1-capital': [u'0,00'],
> u'form-3-capital': [u'0,00'], u'form-3-actives': [u'0,00'], u'form-
> TOTAL_FORMS': [u'4'], u'form-3-charity': [u'0,00'], u'form-2-capital':
> [u'0,00'], u'form-2-actives': [u'0,00'], u'form-0-charity': [u'0,00'], u
> 'form-INITIAL_FORMS': [u'4'], u'form-2-income': [u'0,00'],
> u'form-1-income': [u'0,00']}>

New description:

 {{{
 Environment:

 Request Method: POST
 Request URL: http://panel.raf-leasing.ru:8000/company/finance/2544400/
 Django Version: 1.2 pre-alpha
 Python Version: 2.6.2
 Installed Applications:
 ['sessions', 'company', 'auth', 'lib']
 Installed Middleware:
 ('django.middleware.common.CommonMiddleware',
  'sessions.middleware.SessionMiddleware',
  'auth.middleware.AuthMiddleware',
  'django.middleware.transaction.TransactionMiddleware')


 Traceback:
 File "/usr/local/lib/python2.6/dist-packages/django/core/handlers/base.py"
 in get_response
   92. response = callback(request, *callback_args,
 **callback_kwargs)
 File "/home/r00t/django/rafpaneloracle2/lib/isauth.py" in wrap
   8. return f(request, *args, **kwargs)
 File "/home/r00t/django/rafpaneloracle2/lib/render.py" in wrapper
   20. output = func(request, *args, **kw)
 File "/home/r00t/django/rafpaneloracle2/company/views.py" in finance
   140. formset = FinanceSet(request.POST,
 queryset=Finance.objects.filter(company_id=company.id,
 quarter__in=quarter, year__in=year))
 File "/home/r00t/django/rafpaneloracle2/company/forms.py" in __init__
   209. super (FinanceForm,self ).__init__(*args,**kwargs) #
 populates the post
 File "/usr/local/lib/python2.6/dist-packages/django/forms/models.py" in
 __init__
   459. super(BaseModelFormSet, self).__init__(**defaults)
 File "/usr/local/lib/python2.6/dist-packages/django/forms/formsets.py" in
 __init__
   44. self._construct_forms()
 File "/usr/local/lib/python2.6/dist-packages/django/forms/formsets.py" in

Re: [Django] #11992: modelformset_factory

[Django]

#11992: modelformset_factory
-+--
  Reporter:  unk2k   | Owner:  nobody
Status:  closed  | Milestone:  1.2   
 Component:  Forms   |   Version:  1.1   
Resolution:  invalid |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by unk2k ):

  * status:  new => closed
  * needs_better_patch:  => 0
  * resolution:  => invalid
  * 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] #11481: loaddata doesn't return the proper exit code on error

[Django]

#11481: loaddata doesn't return the proper exit code on error
-+--
  Reporter:  justinlilly | Owner:  justinlilly  
Status:  new | Milestone:   
 Component:  Core framework  |   Version:  SVN  
Resolution:  |  Keywords:  loaddata commands
 Stage:  Accepted| Has_patch:  1
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Comment (by nailor):

 ...or you could raise django.core.management.CommandError and let it raise
 through the whole stack. It would make the manage.py to exit with exit
 status 1.

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

[Django] #11992: modelformset_factory

[Django]

#11992: modelformset_factory
+---
 Reporter:  unk2k   |   Owner:  nobody
   Status:  new |   Milestone:  1.2   
Component:  Forms   | Version:  1.1   
 Keywords:  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 Environment:

 Request Method: POST
 Request URL: http://panel.raf-leasing.ru:8000/company/finance/2544400/
 Django Version: 1.2 pre-alpha
 Python Version: 2.6.2
 Installed Applications:
 ['sessions', 'company', 'auth', 'lib']
 Installed Middleware:
 ('django.middleware.common.CommonMiddleware',
  'sessions.middleware.SessionMiddleware',
  'auth.middleware.AuthMiddleware',
  'django.middleware.transaction.TransactionMiddleware')


 Traceback:
 File "/usr/local/lib/python2.6/dist-packages/django/core/handlers/base.py"
 in get_response
   92. response = callback(request, *callback_args,
 **callback_kwargs)
 File "/home/r00t/django/rafpaneloracle2/lib/isauth.py" in wrap
   8. return f(request, *args, **kwargs)
 File "/home/r00t/django/rafpaneloracle2/lib/render.py" in wrapper
   20. output = func(request, *args, **kw)
 File "/home/r00t/django/rafpaneloracle2/company/views.py" in finance
   140. formset = FinanceSet(request.POST,
 queryset=Finance.objects.filter(company_id=company.id,
 quarter__in=quarter, year__in=year))
 File "/home/r00t/django/rafpaneloracle2/company/forms.py" in __init__
   209. super (FinanceForm,self ).__init__(*args,**kwargs) #
 populates the post
 File "/usr/local/lib/python2.6/dist-packages/django/forms/models.py" in
 __init__
   459. super(BaseModelFormSet, self).__init__(**defaults)
 File "/usr/local/lib/python2.6/dist-packages/django/forms/formsets.py" in
 __init__
   44. self._construct_forms()
 File "/usr/local/lib/python2.6/dist-packages/django/forms/formsets.py" in
 _construct_forms
   88. self.forms.append(self._construct_form(i))
 File "/usr/local/lib/python2.6/dist-packages/django/forms/models.py" in
 _construct_form
   475. pk = self.data[pk_key]
 File "/usr/local/lib/python2.6/dist-
 packages/django/utils/datastructures.py" in __getitem__
   203. raise MultiValueDictKeyError, "Key %r not found in %r"
 % (key, self)

 Exception Type: MultiValueDictKeyError at /company/finance/2544400/
 Exception Value: Key 'form-0-id' not found 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] #6054: PIL import error

[Django]

#6054: PIL import error
-+--
  Reporter:  nesh| Owner:  nobody
Status:  closed  | Milestone:
 Component:  Validators  |   Version:  SVN   
Resolution:  invalid |  Keywords:  PIL   
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  1 
Needs_better_patch:  0   |  
-+--
Comment (by rbanffy):

 Or, perhaps, the error message given on validate could warn about this
 issue until it's solved.

-- 
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] #11882: Documentation missing for django.contrib.admin.ModelAdmin.formfield_for_manytomany

[Django]

#11882: Documentation missing for
django.contrib.admin.ModelAdmin.formfield_for_manytomany
+---
  Reporter:  Nils L | Owner:  anonymous 
 
Status:  assigned   | Milestone:
 
 Component:  Documentation  |   Version:  1.1   
 
Resolution: |  Keywords:  formfield_for_manytomany, 
admin
 Stage:  Accepted   | Has_patch:  0 
 
Needs_docs:  0  |   Needs_tests:  0 
 
Needs_better_patch:  0  |  
+---
Changes (by Rob Hudson ):

  * status:  new => assigned
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * owner:  nobody => anonymous
  * needs_docs:  => 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] #6054: PIL import error

[Django]

#6054: PIL import error
-+--
  Reporter:  nesh| Owner:  nobody
Status:  closed  | Milestone:
 Component:  Validators  |   Version:  SVN   
Resolution:  invalid |  Keywords:  PIL   
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  1 
Needs_better_patch:  0   |  
-+--
Changes (by rbanffy):

  * keywords:  => PIL

Comment:

 The PIL docs are ambiguous. In the
 [http://www.pythonware.com/library/pil/handbook/introduction.htm
 tutorial], it uses "import Image". I would guess this is a bug in the
 tutorial, anyway, but I guess we should warn 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
-~--~~~~--~~--~--~---

Re: [Django] #10809: mod_wsgi authentication handler

[Django]

#10809: mod_wsgi authentication handler
-+--
  Reporter:  baumer1122  | Owner:  nobody  
Status:  new | Milestone:  
 Component:  Authentication  |   Version:  SVN 
Resolution:  |  Keywords:  mod_wsgi
 Stage:  Design decision needed  | Has_patch:  1   
Needs_docs:  1   |   Needs_tests:  0   
Needs_better_patch:  1   |  
-+--
Comment (by davidfischer):

 I am willing to work on this ticket, but I'm not sure it's going to work
 without some modification to mod_wsgi itself. Before the user can be
 authenticated, the `DJANGO_SETTINGS_MODULE` environment variable must be
 set. This cannot be set from inside the handler because mod_wsgi does not
 pass environment information set by `SetEnv` to the `WSGIAuthUserScript`.
 Please correct me if I am wrong.

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