Re: [Django] #19525: Regression: FileField calls validate during form validation; breaks auto_now_add date fields

[Django]

#19525: Regression: FileField calls validate during form validation; breaks
auto_now_add date fields
-+-
 Reporter:  russellm |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  File |  Version:
  uploads/storage|  1.5-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by russellm):

 @aaugustin: I've just checked with my production code, and yes,
 default=timezone.now works for the auto_now_add case. However, it won't
 address auto_now, or the pre_save conflict 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 https://groups.google.com/groups/opt_out.

Re: [Django] #19525: Regression: FileField calls validate during form validation; breaks auto_now_add date fields

[Django]

#19525: Regression: FileField calls validate during form validation; breaks
auto_now_add date fields
-+-
 Reporter:  russellm |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  File |  Version:
  uploads/storage|  1.5-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 Would this work if the `DateTimeField` was declared with
 `default=timezone.now` rather than `auto_now_add=True`?

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19525: Regression: FileField calls validate during form validation; breaks auto_now_add date fields

[Django]

#19525: Regression: FileField calls validate during form validation; breaks
auto_now_add date fields
-+-
 Reporter:  russellm |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  File |  Version:
  uploads/storage|  1.5-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by russellm):

 For the record, I discovered this by upgrading a commercial project to
 Django 1.5, so there is at least one project in the wild that will be
 affected by this change. Although I've discovered it with a auto_now_add
 FileField, it's not hard to see that this change also affects any field
 with a pre_save behaviour.

 It also has the potential to lead to incorrect validation. Consider the
 case of a field with a pre_save behavior that updates the field (auto_now
 is one example, but any denormalization/summary field would be an
 example). The call to validate occurs *before* the call to pre_save is
 made, which means that you're going to get the pre_save value used as part
 of your validation. If you then save the model, the pre_save() will be
 called, and the actual filename that is used for saving the file will be
 different to the one used for validation.

 Some initial thoughts about possible solutions:
  * Document that you can't use a field with pre-save behaviour. Not ideal
 IMHO, since it rules out an obvious use case for upload_to.
  * Roll back the fix. Also less than ideal; #9893 is an edge case bug, but
 it's something that has been seen in the wild, and isn't *too* hard to
 generate.
  * Invoke pre_save on all model fields prior to validation. Given that
 most validation doesn't need this, this approach seems a little excessive.

-- 
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 https://groups.google.com/groups/opt_out.

[Django] #19525: Regression: FileField calls validate during form validation; breaks auto_now_add date fields

[Django]

#19525: Regression: FileField calls validate during form validation; breaks
auto_now_add date fields
-+-
   Reporter:  russellm   |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  File   |Version:  1.5-beta-1
  uploads/storage|   Keywords:
   Severity:  Release|  Has patch:  0
  blocker|Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 As of dcd43831 (fixing #9893), a FileField will call `generate_filename()`
 as part of the validation step for a FileField on a form.  This was then
 updated in  05d333ba to address #18515.

 Unfortunately, this means that the filename function provided as an
 argument to upload_to can no longer reference any field with a pre-save
 behavior.

 The common use case for this is to organize files on disk according to
 upload date. For example:

 {{{
 def user_filename(instance, filename):
 return os.path.join('user_files',
 instance.uploaded_timestamp.strftime('%Y-%m-%d'), filename)

 class UserFile(models.Model):
 uploaded_timestamp = models.DateTimeField(auto_now_add=True)
 data = models.FileField(upload_to=user_filename)
 }}}

 Under Django 1.5, attempting to call is_valid() on a Modelform for this
 model will raise a "'NoneType' object has no attribute 'strftime'"
 exception, because instance.uploaded_timestamp hasn't been instantiated
 yet. This is despite the fact that the uploaded data has been provided,
 the generated filename would be valid, and the upload timestamp can be
 computed.

 In Django 1.4 and earlier, this works because no validation was performed
 for FileFields filenames; the uploaded_timestamp was evaluated as part of
 the model pre-save, and the persistence of the file to disk occurred after
 the model was saved.

 To my reading,
 
[https://docs.djangoproject.com/en/1.4/ref/models/fields/#django.db.models.FileField.upload_to
 the documentation is ambiguous] on whether this is  expected behavior or
 not. It says that the model may not be saved to the database yet, but
 points at AutoField as the cause for problems. However, it also explicitly
 talks about using strftime as part of file paths. A file datetimes of
 'now' would seem to be an obvious usage of this feature.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19516: Fix broken sphinx references in docs

[Django]

#19516: Fix broken sphinx references in docs
--+
 Reporter:  timo  |Owner:  timo
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"fbc06eef1af1d7ecf91fae5a94a1994f356ffd22"]:
 {{{
 #!CommitTicketReference repository=""
 revision="fbc06eef1af1d7ecf91fae5a94a1994f356ffd22"
 [1.5.X] Fixed broken links, round 3. refs #19516

 Backport of b3a8c9dab8 from master
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] fbc06e: [1.5.X] Fixed broken links, round 3. refs #19516

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: fbc06eef1af1d7ecf91fae5a94a1994f356ffd22
  
https://github.com/django/django/commit/fbc06eef1af1d7ecf91fae5a94a1994f356ffd22
  Author: Tim Graham 
  Date:   2012-12-26 (Wed, 26 Dec 2012)

  Changed paths:
M docs/conf.py
M docs/howto/error-reporting.txt
M docs/intro/tutorial02.txt
M docs/intro/tutorial04.txt
M docs/ref/contrib/comments/models.txt
M docs/ref/contrib/comments/moderation.txt
M docs/ref/contrib/contenttypes.txt
M docs/ref/forms/api.txt
M docs/ref/forms/fields.txt
M docs/ref/forms/widgets.txt
M docs/ref/models/fields.txt
M docs/ref/models/instances.txt
M docs/ref/models/querysets.txt
M docs/ref/signals.txt
M docs/ref/templates/builtins.txt
M docs/ref/utils.txt
M docs/releases/1.0-porting-guide.txt
M docs/releases/1.1.txt
M docs/releases/1.3-alpha-1.txt
M docs/releases/1.4-alpha-1.txt
M docs/releases/1.4-beta-1.txt
M docs/releases/1.4.txt
M docs/releases/1.5-alpha-1.txt
M docs/releases/1.5-beta-1.txt
M docs/releases/1.5.txt
M docs/topics/auth.txt
M docs/topics/db/queries.txt
M docs/topics/i18n/timezones.txt
M docs/topics/i18n/translation.txt
M docs/topics/python3.txt
M docs/topics/security.txt
M docs/topics/serialization.txt
M docs/topics/signals.txt
M docs/topics/testing/index.txt

  Log Message:
  ---
  [1.5.X] Fixed broken links, round 3. refs #19516

Backport of b3a8c9dab8 from master



-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19516: Fix broken sphinx references in docs

[Django]

#19516: Fix broken sphinx references in docs
--+
 Reporter:  timo  |Owner:  timo
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"b3a8c9dab87be6bc4b8096d292abe0b35c700bdd"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b3a8c9dab87be6bc4b8096d292abe0b35c700bdd"
 Fixed broken links, round 3. refs #19516
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] b3a8c9: Fixed broken links, round 3. refs #19516

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b3a8c9dab87be6bc4b8096d292abe0b35c700bdd
  
https://github.com/django/django/commit/b3a8c9dab87be6bc4b8096d292abe0b35c700bdd
  Author: Tim Graham 
  Date:   2012-12-26 (Wed, 26 Dec 2012)

  Changed paths:
M docs/conf.py
M docs/howto/error-reporting.txt
M docs/intro/tutorial02.txt
M docs/intro/tutorial04.txt
M docs/ref/contrib/comments/models.txt
M docs/ref/contrib/comments/moderation.txt
M docs/ref/contrib/contenttypes.txt
M docs/ref/forms/api.txt
M docs/ref/forms/fields.txt
M docs/ref/forms/widgets.txt
M docs/ref/models/fields.txt
M docs/ref/models/instances.txt
M docs/ref/models/querysets.txt
M docs/ref/signals.txt
M docs/ref/templates/builtins.txt
M docs/ref/utils.txt
M docs/releases/1.0-porting-guide.txt
M docs/releases/1.1.txt
M docs/releases/1.3-alpha-1.txt
M docs/releases/1.4-alpha-1.txt
M docs/releases/1.4-beta-1.txt
M docs/releases/1.4.txt
M docs/releases/1.5-alpha-1.txt
M docs/releases/1.5-beta-1.txt
M docs/releases/1.5.txt
M docs/topics/auth.txt
M docs/topics/db/queries.txt
M docs/topics/i18n/timezones.txt
M docs/topics/i18n/translation.txt
M docs/topics/python3.txt
M docs/topics/security.txt
M docs/topics/serialization.txt
M docs/topics/signals.txt
M docs/topics/testing/index.txt

  Log Message:
  ---
  Fixed broken links, round 3. refs #19516



-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19492: uWSGI how to needs to be more detailed for beginners

[Django]

#19492: uWSGI how to needs to be more detailed for beginners
---+
 Reporter:  EvilDMP|Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timo):

 * cc: timograham@… (added)
 * has_patch:  0 => 1
 * version:  1.4 => master
 * type:  Cleanup/optimization => New feature


-- 
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 https://groups.google.com/groups/opt_out.

[Django] #19524: DoesNotExist exception when adding object in admin with inline object

[Django]

#19524: DoesNotExist exception when adding object in admin with inline object
---+
 Reporter:  qcwxezdas@…|  Owner:  nobody
 Type:  Bug| Status:  new
Component:  contrib.admin  |Version:  1.5-beta-1
 Severity:  Normal |   Keywords:  admin,DoesNotExist,inlines
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 '''models.py'''
 {{{
 class Service(models.Model):
 provider = models.ForeignKey("services.ServiceProvider",
  verbose_name=_("Service provider"),
  related_name="services")
 title = models.CharField(_("Title"), max_length=150)
 # ... other fields ...

 class EntertainmentType(models.Model):
 title = models.CharField(max_length=150, unique=True)

 def __unicode__(self):
 return self.title

 class Meta:
 ordering = ('title',)


 class Entertainment(Service):
 types = models.ManyToManyField(EntertainmentType,
 verbose_name=_("Types"),
related_name="entertainments")

 description = models.TextField(_("Description"), blank=True)
 # ... other fields ...

 def __unicode__(self):
 return self.title

 class Meta:
 ordering = ('title',)


 class EntertainmentPhoto(models.Model):
 entertainment = models.ForeignKey(Entertainment,
 related_name="photos")
 description = models.TextField(_("Description"), max_length=1000,
blank=True)
 photo = ImageWithThumbsField(_("Photo"), sizes=(),
 upload_to="services/photos/entertainment")
 is_main = models.BooleanField(verbose_name=_("Main"), default=False)

 class Meta:
 ordering = ('-is_main',)
 verbose_name = _("Photo")
 verbose_name_plural = _("Photos")
 }}}

 '''admin.py'''


 {{{
 from django.contrib import admin
 from services.entertainment.models import Entertainment,
 EntertainmentType, EntertainmentPhoto

 class EntertainmentTypeAdmin(admin.ModelAdmin):
 pass

 class EntertainmentPhotoInline(admin.TabularInline):
 model = EntertainmentPhoto

 class EntertainmentAdmin(admin.ModelAdmin):
 filter_horizontal = ["types"]
 list_display = Entertainment.list_display
 list_filter = ["provider", "types", ]
 inlines = [EntertainmentPhotoInline]

 admin.site.register(Entertainment, EntertainmentAdmin)
 admin.site.register(EntertainmentType, EntertainmentTypeAdmin)
 }}}

 If I add the Entertainment object without any EntertainmentPhoto inlines
 then everything wents correct. I am ABLE to add inline photos when editing
 created instance.

 However, if I add photos when instance is not created (in add view), I get
 the following:


 {{{
 Environment:


 Request Method: POST
 Request URL:
 http://77.79.59.184:8000/admin/entertainment/entertainment/add/?provider=1

 Django Version: 1.5b2
 Python Version: 2.7.2
 Installed Applications:
 ['south',
  'gunicorn',
  'django_extensions',
  'django.contrib.databrowse',
  'django.contrib.contenttypes',
  'django.contrib.sessions',
  'django.contrib.sites',
  'django.contrib.messages',
  'django.contrib.staticfiles',
  'django.contrib.admin',
  'authentication',
  'framework',
  'framework.menu',
  'services',
  'maps',
  'services.entertainment',
  'services.otherservices']
 Installed Middleware:
 ('django.middleware.common.CommonMiddleware',
  'django.contrib.sessions.middleware.SessionMiddleware',
  'django.middleware.csrf.CsrfViewMiddleware',
  'django.contrib.auth.middleware.AuthenticationMiddleware',
  'django.contrib.messages.middleware.MessageMiddleware',
  'django.middleware.clickjacking.XFrameOptionsMiddleware')


 Traceback:
 File "/Users/aemdy/virtualenvs/django1.5/lib/python2.7/site-
 packages/django/core/handlers/base.py" in get_response
   116. response = callback(request,
 *callback_args, **callback_kwargs)
 File "/Users/aemdy/virtualenvs/django1.5/lib/python2.7/site-
 packages/django/contrib/admin/options.py" in wrapper
   370. return self.admin_site.admin_view(view)(*args,
 **kwargs)
 File "/Users/aemdy/virtualenvs/django1.5/lib/python2.7/site-
 packages/django/utils/decorators.py" in _wrapped_view
   91. response = view_func(request, *args, **kwargs)
 File "/Users/aemdy/virtualenvs/django1.5/lib/python2.7/site-
 packages/django/views/decorators/cache.py" in _wrapped_view_func
   89. response = view_func(request, *args, **kwargs)
 File "/Users/aemdy/virtualenvs/django1.5/lib/python2.7/site-
 packages/django/contrib/admin/sites.py" in inner
   202. return view(request, *args, **kwargs)
 File "/Users/aemdy/virtualenvs/django1.5/lib/python2.7/site-
 packages/django/utils/decorators.py" in _wrapper
   25. return bound_func(*

Re: [Django] #19172: test_poisoned_http_host* tests failing when having ADMINS settings populated

[Django]

#19172: test_poisoned_http_host* tests failing when having ADMINS settings
populated
-+-
 Reporter:  bernardofontes   |Owner:  claudep
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  1.4
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  unit tests, auth,| Triage Stage:  Accepted
  admin, mail|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by anonymous):

 ok. thanks for your reply.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19522: ModelForm and BooleanField

[Django]

#19522: ModelForm and BooleanField
---+---
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Forms  |  Version:  1.5-alpha-1
 Severity:  Normal |   Resolution:  invalid
 Keywords:  modelform  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+---
Changes (by timo):

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


-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19522: ModelForm and BooleanField

[Django]

#19522: ModelForm and BooleanField
---+---
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Forms  |  Version:  1.5-alpha-1
 Severity:  Normal |   Resolution:
 Keywords:  modelform  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+---

Comment (by anonymous):

 Must user _(u'Кириллица')

 Remove this ticket, please.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19522: ModelForm and BooleanField

[Django]

#19522: ModelForm and BooleanField
---+---
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Forms  |  Version:  1.5-alpha-1
 Severity:  Normal |   Resolution:
 Keywords:  modelform  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+---

Comment (by anonymous):

 # -*- coding: utf-8 -*-
 from django.utils.translation import ugettext_lazy as _


  class TestModel(models.Model):
  b = models.BooleanField(db_index=True, default=True,
 verbose_name=_('Кириллица'))


  class TestModelForm(forms.ModelForm):
  class Meta:
  model = TestModel

  f = TestModelForm()

  {{ f }} -- no view form

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19523: improve performance of django's bash completion

[Django]

#19523: improve performance of django's bash completion
-+-
 Reporter:  rhertzog |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.4
Component:  Core (Management |   Resolution:
  commands)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * component:  Uncategorized => Core (Management commands)


-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19523: improve performance of django's bash completion

[Django]

#19523: improve performance of django's bash completion
--+
 Reporter:  rhertzog  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Uncategorized |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by aaugustin):

 * 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 https://groups.google.com/groups/opt_out.

Re: [Django] #19523: improve performance of django's bash completion

[Django]

#19523: improve performance of django's bash completion
-+-
 Reporter:  rhertzog |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.4
Component:  Uncategorized|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by lfaraone):

 * cc: luke@… (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 https://groups.google.com/groups/opt_out.

Re: [Django] #19522: ModelForm and BooleanField

[Django]

#19522: ModelForm and BooleanField
---+---
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Forms  |  Version:  1.5-alpha-1
 Severity:  Normal |   Resolution:
 Keywords:  modelform  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+---
Changes (by anonymous):

 * needs_docs:   => 0
 * version:  1.4-alpha-1 => 1.5-alpha-1
 * 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 https://groups.google.com/groups/opt_out.

[Django] #19523: improve performance of django's bash completion

[Django]

#19523: improve performance of django's bash completion
--+
 Reporter:  rhertzog  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Uncategorized |Version:  1.4
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+
 In http://bugs.debian.org/695811 Anders Kaseorg  reported
 that the usage of the basename command was severly impacting the
 performances of Django's bash completion script.

 The attached patch gets rid of "basename" in favor of some bash internal
 pattern substitution and improves the perfornance by a factor of 5
 according to its author.

-- 
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 https://groups.google.com/groups/opt_out.

[Django] #19522: ModelForm and BooleanField

[Django]

#19522: ModelForm and BooleanField
+-
 Reporter:  anonymous   |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Forms   |Version:  1.4-alpha-1
 Severity:  Normal  |   Keywords:  modelform
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+-
 class TestModel(models.Model):
 b = models.BooleanField(db_index=True, default=True)
 class Meta:
 db_table = 'test'
 app_label = 'test'


 class TestModelForm(forms.ModelForm):
 class Meta:
 model = TestModel

 f = TestModelForm()

 {{ f }} -- no view form

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19521: Querying __day__gte (or any other comparison) not allowed

[Django]

#19521: Querying __day__gte (or any other comparison) not allowed
-+-
 Reporter:  batment@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:  queryset |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 `__day` is a lookup, and you cannot chain lookups.

-- 
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 https://groups.google.com/groups/opt_out.

[Django] #19521: Querying __day__gte (or any other comparison) not allowed

[Django]

#19521: Querying __day__gte (or any other comparison) not allowed
--+--
 Reporter:  batment@… |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.4
 Severity:  Normal|   Keywords:  queryset
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+--
 Filter on field_name__day__gte returns "FieldError: Join on field
 'field_name' not permitted. Did you misspell 'day' for the lookup type?"

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19482: django.contrib.localflavor in INSTALLED_APPS raises DeprecationWarning

[Django]

#19482: django.contrib.localflavor in INSTALLED_APPS raises DeprecationWarning
-+--
 Reporter:  andreas_pelme|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.5-beta-1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  localflavor  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by aaugustin):

 * easy:  1 => 0
 * stage:  Design decision needed => 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 https://groups.google.com/groups/opt_out.

Re: [Django] #19482: django.contrib.localflavor in INSTALLED_APPS raises DeprecationWarning

[Django]

#19482: django.contrib.localflavor in INSTALLED_APPS raises DeprecationWarning
-+-
 Reporter:  andreas_pelme|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:
 Severity:  Release blocker  |  1.5-beta-1
 Keywords:  localflavor  |   Resolution:  fixed
Has patch:  0| Triage Stage:  Design
  Needs tests:  0|  decision needed
Easy pickings:  1|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 I wrapped up the documentation.

 Thank you Simon and Claude -- you did all the hard work 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 https://groups.google.com/groups/opt_out.

Re: [Django] #19482: django.contrib.localflavor in INSTALLED_APPS raises DeprecationWarning

[Django]

#19482: django.contrib.localflavor in INSTALLED_APPS raises DeprecationWarning
-+-
 Reporter:  andreas_pelme|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:
 Severity:  Release blocker  |  1.5-beta-1
 Keywords:  localflavor  |   Resolution:
Has patch:  0| Triage Stage:  Design
  Needs tests:  0|  decision needed
Easy pickings:  1|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"e2396bf1220c543ee8d15c7640481889caace61d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e2396bf1220c543ee8d15c7640481889caace61d"
 [1.5.x] Updated documentation on localflavor translations

 to account for the deprecation of django.contrib.localflavor in 1.5.

 Refs #19482.
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] e2396b: [1.5.x] Updated documentation on localflavor trans...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: e2396bf1220c543ee8d15c7640481889caace61d
  
https://github.com/django/django/commit/e2396bf1220c543ee8d15c7640481889caace61d
  Author: Aymeric Augustin 
  Date:   2012-12-26 (Wed, 26 Dec 2012)

  Changed paths:
M docs/ref/contrib/localflavor.txt

  Log Message:
  ---
  [1.5.x] Updated documentation on localflavor translations

to account for the deprecation of django.contrib.localflavor in 1.5.

Refs #19482.



-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19482: django.contrib.localflavor in INSTALLED_APPS raises DeprecationWarning

[Django]

#19482: django.contrib.localflavor in INSTALLED_APPS raises DeprecationWarning
-+-
 Reporter:  andreas_pelme|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:
 Severity:  Release blocker  |  1.5-beta-1
 Keywords:  localflavor  |   Resolution:
Has patch:  0| Triage Stage:  Design
  Needs tests:  0|  decision needed
Easy pickings:  1|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"e2ec7b47b3acb0338d971942ca7ffd36c2a4d8f4"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e2ec7b47b3acb0338d971942ca7ffd36c2a4d8f4"
 Updated documentation on localflavor translations

 to account for the removal of django.contrib.localflavor in 1.6.

 Refs #19482.
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] e2ec7b: Updated documentation on localflavor translations

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e2ec7b47b3acb0338d971942ca7ffd36c2a4d8f4
  
https://github.com/django/django/commit/e2ec7b47b3acb0338d971942ca7ffd36c2a4d8f4
  Author: Aymeric Augustin 
  Date:   2012-12-26 (Wed, 26 Dec 2012)

  Changed paths:
M docs/ref/contrib/localflavor.txt

  Log Message:
  ---
  Updated documentation on localflavor translations

to account for the removal of django.contrib.localflavor in 1.6.

Refs #19482.



-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19518: Deprecation of localflavor not documented

[Django]

#19518: Deprecation of localflavor not documented
-+
 Reporter:  aaugustin|  Owner:  nobody
 Type:  Bug  | Status:  closed
Component:  Documentation|Version:  master
 Severity:  Release blocker  | Resolution:  fixed
 Keywords:   |   Triage Stage:  Unreviewed
Has patch:  0|  Easy pickings:  0
UI/UX:  0|
-+

Comment (by Aymeric Augustin ):

 In [changeset:"0c79e5e347e3c5d3f942d4338bb5476f0277cd21"]:
 {{{
 #!CommitTicketReference repository=""
 revision="0c79e5e347e3c5d3f942d4338bb5476f0277cd21"
 [1.5.x] Fixed #19518 -- Documented the deprecation of localflavor.

 Also moved the contrib deprecations at the top of their section and made
 minor markup fixes.

 Backport of 4500d35 from master.
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] 0c79e5: [1.5.x] Fixed #19518 -- Documented the deprecation...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 0c79e5e347e3c5d3f942d4338bb5476f0277cd21
  
https://github.com/django/django/commit/0c79e5e347e3c5d3f942d4338bb5476f0277cd21
  Author: Aymeric Augustin 
  Date:   2012-12-26 (Wed, 26 Dec 2012)

  Changed paths:
M docs/internals/deprecation.txt
M docs/ref/contrib/localflavor.txt
M docs/releases/1.5.txt

  Log Message:
  ---
  [1.5.x] Fixed #19518 -- Documented the deprecation of localflavor.

Also moved the contrib deprecations at the top of their section and made
minor markup fixes.

Backport of 4500d35 from master.



-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19518: Deprecation of localflavor not documented

[Django]

#19518: Deprecation of localflavor not documented
-+
 Reporter:  aaugustin|  Owner:  nobody
 Type:  Bug  | Status:  closed
Component:  Documentation|Version:  master
 Severity:  Release blocker  | Resolution:  fixed
 Keywords:   |   Triage Stage:  Unreviewed
Has patch:  0|  Easy pickings:  0
UI/UX:  0|
-+
Changes (by Aymeric Augustin ):

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


Comment:

 In [changeset:"4500d3522defd7df869756e8ee2c876a747a8fa9"]:
 {{{
 #!CommitTicketReference repository=""
 revision="4500d3522defd7df869756e8ee2c876a747a8fa9"
 Fixed #19518 -- Documented the deprecation of localflavor.

 Also moved the contrib deprecations at the top of their section and made
 minor markup fixes.
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] 4500d3: Fixed #19518 -- Documented the deprecation of loca...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 4500d3522defd7df869756e8ee2c876a747a8fa9
  
https://github.com/django/django/commit/4500d3522defd7df869756e8ee2c876a747a8fa9
  Author: Aymeric Augustin 
  Date:   2012-12-26 (Wed, 26 Dec 2012)

  Changed paths:
M docs/internals/deprecation.txt
M docs/ref/contrib/localflavor.txt
M docs/releases/1.5.txt

  Log Message:
  ---
  Fixed #19518 -- Documented the deprecation of localflavor.

Also moved the contrib deprecations at the top of their section and made
minor markup fixes.



-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #11688: verbose_name should allow dynamical translation based on a number

[Django]

#11688: verbose_name should allow dynamical translation based on a number
--+
 Reporter:  mitar |Owner:  nobody
 Type:  New feature   |   Status:  reopened
Component:  Internationalization  |  Version:  1.1
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by anonymous):

 * cc: 4glitch@… (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 https://groups.google.com/groups/opt_out.

Re: [Django] #18549: Admin should not use verbose_name_plural for OneToOne field

[Django]

#18549: Admin should not use verbose_name_plural for OneToOne field
---+
 Reporter:  RoySmith   |Owner:  vanessagomes
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by anonymous):

 * cc: 4glitch@… (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 https://groups.google.com/groups/opt_out.

Re: [Django] #14844: i18n blocktrans tag pluralization feature limited by gettext constraints and unique local tag context

[Django]

#14844: i18n blocktrans tag pluralization feature limited by gettext constraints
and unique local tag context
--+
 Reporter:  ramiro|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Internationalization  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by anonymous):

 * cc: 4glitch@… (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 https://groups.google.com/groups/opt_out.

Re: [Django] #16408: Query result types not being converted with Spatialite

[Django]

#16408: Query result types not being converted with Spatialite
-+-
 Reporter:  Antonio Eugenio  |Owner:  jbronn
  Burriel   |   Status:  closed
 Type:  Bug  |  Version:
Component:  GIS  |  1.5-beta-1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  regression   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"4f67ab63761a949a4ee8dab5ae38f23b32dc56e5"]:
 {{{
 #!CommitTicketReference repository=""
 revision="4f67ab63761a949a4ee8dab5ae38f23b32dc56e5"
 [1.5.x] Fixed #16408 -- Re-fixed value conversion with Spatialite backend

 Backport of 0907d3c6f from master.
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] 4f67ab: [1.5.x] Fixed #16408 -- Re-fixed value conversion ...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 4f67ab63761a949a4ee8dab5ae38f23b32dc56e5
  
https://github.com/django/django/commit/4f67ab63761a949a4ee8dab5ae38f23b32dc56e5
  Author: Claude Paroz 
  Date:   2012-12-26 (Wed, 26 Dec 2012)

  Changed paths:
M django/contrib/gis/db/models/sql/query.py
M django/contrib/gis/tests/geoapp/test_regress.py

  Log Message:
  ---
  [1.5.x] Fixed #16408 -- Re-fixed value conversion with Spatialite backend

Backport of 0907d3c6f from master.



-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #16408: Query result types not being converted with Spatialite

[Django]

#16408: Query result types not being converted with Spatialite
-+-
 Reporter:  Antonio Eugenio  |Owner:  jbronn
  Burriel   |   Status:  closed
 Type:  Bug  |  Version:
Component:  GIS  |  1.5-beta-1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  regression   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"0907d3c6f511ef3dc68d381389a32b9b54ae4be7"]:
 {{{
 #!CommitTicketReference repository=""
 revision="0907d3c6f511ef3dc68d381389a32b9b54ae4be7"
 Fixed #16408 -- Re-fixed value conversion with Spatialite backend
 }}}

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

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

[django/django] 0907d3: Fixed #16408 -- Re-fixed value conversion with Spa...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 0907d3c6f511ef3dc68d381389a32b9b54ae4be7
  
https://github.com/django/django/commit/0907d3c6f511ef3dc68d381389a32b9b54ae4be7
  Author: Claude Paroz 
  Date:   2012-12-26 (Wed, 26 Dec 2012)

  Changed paths:
M django/contrib/gis/db/models/sql/query.py
M django/contrib/gis/tests/geoapp/test_regress.py

  Log Message:
  ---
  Fixed #16408 -- Re-fixed value conversion with Spatialite backend



-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19172: test_poisoned_http_host* tests failing when having ADMINS settings populated

[Django]

#19172: test_poisoned_http_host* tests failing when having ADMINS settings
populated
-+-
 Reporter:  bernardofontes   |Owner:  claudep
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  1.4
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  unit tests, auth,| Triage Stage:  Accepted
  admin, mail|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by claudep):

 Only security fixes do reach the 1.3.x branch of Django. You will have to
 live with these errors in Django 1.3, or patch the installed Django
 version yourself.

-- 
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 https://groups.google.com/groups/opt_out.