[Django] #10029: LhzHXMJFo

[Django]

#10029: LhzHXMJFo
---+
   Reporter:  anonymous|Owner:  sYdNXlofoEzU
 Status:  new  |Milestone:  post-1.0
  Component:  Uncategorized|  Version:  1.0 
   Keywords:  XSkZVNQIqTvNSprPRIJ  |Stage:  Unreviewed  
  Has_patch:  0|   Needs_docs:  0   
Needs_tests:  0|   Needs_better_patch:  0   
---+
 iQYWMD  http://gqbjfmqqehxg.com/";>gqbjfmqqehxg,
 [url=http://pdyemibhaywz.com/]pdyemibhaywz[/url],
 [link=http://lkoqnbijqhfl.com/]lkoqnbijqhfl[/link],
 http://vkgeufknhyil.com/

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

[Changeset] r9741 - django/branches/releases/1.0.X

[noreply]

Author: gwilson
Date: 2009-01-15 00:38:27 -0600 (Thu, 15 Jan 2009)
New Revision: 9741

Modified:
   django/branches/releases/1.0.X/AUTHORS
Log:
[1.0.X] Updated name as per author's request.

Backport of r9740 from trunk.


Modified: django/branches/releases/1.0.X/AUTHORS
===
--- django/branches/releases/1.0.X/AUTHORS  2009-01-15 06:37:01 UTC (rev 
9740)
+++ django/branches/releases/1.0.X/AUTHORS  2009-01-15 06:38:27 UTC (rev 
9741)
@@ -375,7 +375,7 @@
 Johan C. Stöver 
 nowell strite
 Thomas Stromberg 
-Sundance
+Pascal Varet
 SuperJared
 Radek Švarz 
 Swaroop C H 


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

[Changeset] r9740 - django/trunk

[noreply]

Author: gwilson
Date: 2009-01-15 00:37:01 -0600 (Thu, 15 Jan 2009)
New Revision: 9740

Modified:
   django/trunk/AUTHORS
Log:
Updated name as per author's request.


Modified: django/trunk/AUTHORS
===
--- django/trunk/AUTHORS2009-01-14 20:22:25 UTC (rev 9739)
+++ django/trunk/AUTHORS2009-01-15 06:37:01 UTC (rev 9740)
@@ -378,7 +378,7 @@
 Johan C. Stöver 
 nowell strite
 Thomas Stromberg 
-Sundance
+Pascal Varet
 SuperJared
 Radek Švarz 
 Swaroop C H 


--~--~-~--~~~---~--~~
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] #4102: Allow UPDATE of only specific fields in model.save()

[Django]

#4102: Allow UPDATE of only specific fields in model.save()
+---
  Reporter:  Collin Grady   | Owner:  cgrady
Status:  new| Milestone:
 Component:  Database layer (models, ORM)   |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Design decision needed | Has_patch:  1 
Needs_docs:  1  |   Needs_tests:  0 
Needs_better_patch:  1  |  
+---
Changes (by clay):

 * cc: c...@daemons.net (added)

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

Re: [Django] #4102: Allow UPDATE of only specific fields in model.save()

[Django]

#4102: Allow UPDATE of only specific fields in model.save()
+---
  Reporter:  Collin Grady   | Owner:  cgrady
Status:  new| Milestone:
 Component:  Database layer (models, ORM)   |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Design decision needed | Has_patch:  1 
Needs_docs:  1  |   Needs_tests:  0 
Needs_better_patch:  1  |  
+---
Comment (by clay):

 Apologies for the formatting snafu above. I've uploaded the patch as
 attachment 4102.3.fix-multi-table.

-- 
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] #4102: Allow UPDATE of only specific fields in model.save()

[Django]

#4102: Allow UPDATE of only specific fields in model.save()
+---
  Reporter:  Collin Grady   | Owner:  cgrady
Status:  new| Milestone:
 Component:  Database layer (models, ORM)   |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Design decision needed | Has_patch:  1 
Needs_docs:  1  |   Needs_tests:  0 
Needs_better_patch:  1  |  
+---
Changes (by clay):

  * needs_better_patch:  0 => 1

Comment:

 Patch 4102.3 does not work correctly with multi-table inheritance --
 child._modified_attrs is not visible by the parent, so a modified parent
 field is not updated. Something like this fixes it:

 Index: third-party/Django-1.0.2-final+4102.3+2705/django/db/models/base.py
 ===
 --- third-party/Django-1.0.2-final+4102.3+2705/django/db/models/base.py
 (revision 3362)
 +++ third-party/Django-1.0.2-final+4102.3+2705/django/db/models/base.py
 (working copy)
 @@ -358,7 +358,10 @@
  non_pks = [f for f in meta.local_fields if not f.primary_key]
  modified_attrs = self._modified_attrs
  non_pks = [f for f in non_pks if (f.name in modified_attrs or
 f.attname in modified_attrs)]
 -self._reset_modified_attrs()
 +
 +# Reset modified attribute accumulator after parent fields have
 been updated
 +if cls == self.__class__:
 +self._reset_modified_attrs()

  # First, try an UPDATE. If that doesn't update anything, do an
 INSERT.
  pk_val = self._get_pk_val(meta)

-- 
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] #10028: no objects found

[Django]

#10028: no objects found
--+-
 Reporter:  brian |   Owner:  mtredinnick
   Status:  new   |   Milestone: 
Component:  Database layer (models, ORM)  | Version:  1.0
 Keywords:|   Stage:  Unreviewed 
Has_patch:  0 |  
--+-
 Continued from 

 Python 2.5.2 (r252:60911, Oct  5 2008, 19:24:49)
 [GCC 4.3.2] on linux2
 Type "help", "copyright", "credits" or "license" for more information.
 (InteractiveConsole)
 >>> import inventory.models as models
 >>> object=models.software.objects.get(id=267)
 >>> print
 models.software_installation.objects.filter(software=object).count()
 10
 >>> print models.software_installation.objects.filter(software=object)
 []
 >>> print
 models.software_installation.objects.filter(software=object).query.as_sql()
 ('SELECT `inventory_software_installation`.`id`,
 `inventory_software_installation`.`software_id`,
 `inventory_software_installation`.`license_key_id` FROM
 `inventory_software_installation` INNER JOIN `inventory_software` ON
 (`inventory_software_installation`.`software_id` =
 `inventory_software`.`id`) LEFT OUTER JOIN `inventory_license_key` ON
 (`inventory_software_installation`.`license_key_id` =
 `inventory_license_key`.`id`) INNER JOIN `inventory_software` T4 ON
 (`inventory_license_key`.`software_id` = T4.`id`) INNER JOIN
 `inventory_license` ON (`inventory_license_key`.`license_id` =
 `inventory_license`.`id`) INNER JOIN `inventory_software` T6 ON
 (`inventory_license`.`software_id` = T6.`id`) WHERE
 `inventory_software_installation`.`software_id` = %s  ORDER BY
 `inventory_software`.`name` ASC, T4.`name` ASC, T6.`name` ASC,
 `inventory_license`.`vendor_id` ASC, `inventory_license_key`.`key` ASC',
 (267,))
 >>> quit()

 --- cut ---

 class software(models.Model):
 name = models.CharField(max_length=100)
 class Meta:
 ordering = ('name',)

 class license(models.Model):
 software = models.ForeignKey(software)
 vendor_id = models.CharField(max_length=10,null=True,blank=True)
 class Meta:
 ordering = ('software','vendor_id')

 class license_key(models.Model):
 software = models.ForeignKey(software)
 license  = models.ForeignKey(license)
 key = models.CharField(max_length=50,null=True,blank=True)
 class Meta:
 ordering = ('software','license','key')

 class software_installation(models.Model):
 software = models.ForeignKey(software)
 license_key = models.ForeignKey(license_key,null=True,blank=True)
 class Meta:
 ordering = ('software','license_key')

 --- cut ---

 The ordering Meta tag is important; if I remove the appropriate meta tags
 (I haven't worked out which ones yet), then everything works fine.

 Brian May

 PS Thanks for the very prompt response.

-- 
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] #9672: timeuntil filters doesn't work with DateField since [8579]

[Django]

#9672: timeuntil filters doesn't work with DateField since [8579]
--+-
  Reporter:  anonymous| Owner:  nobody 
Status:  new  | Milestone: 
 Component:  Template system  |   Version:  SVN
Resolution:   |  Keywords:  timeuntil timesince
 Stage:  Unreviewed   | Has_patch:  1  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by rossp):

 * cc: r...@rossp.org (added)
  * needs_tests:  1 => 0

Comment:

 In my attachment I have moved the anonymous fix into the `timesince` block
 rather than `timeuntil`, so that any use of `timesince` from other places
 (eg direct usage in a view) will also pick up the same change. It also has
 the impact of causing `timesince` with a `now` input of type `date`
 (rather than `datetime`) to work correctly.

 I've also added some unit tests to the patch, hopefully they are
 sufficient for checkin.

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

Re: [Django] #10027: include a link to "Form and Field Validation" from "Working with Forms"

[Django]

#10027: include a link to "Form and Field Validation" from "Working with Forms"
+---
  Reporter:  john_fries | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by john_fries):

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

Comment:

 The "Form and Field Validation" document is at
 http://docs.djangoproject.com/en/dev/ref/forms/validation/

-- 
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] #10027: include a link to "Form and Field Validation" from "Working with Forms"

[Django]

#10027: include a link to "Form and Field Validation" from "Working with Forms"
---+
 Reporter:  john_fries |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 We should include a link to the "Form and Field Validation" document in
 the "further topics" section of the "Working with Forms" document
 (http://docs.djangoproject.com/en/dev/topics/forms/).  I had a very hard
 time finding the "Form and Field Validation" material, and it's pretty
 essential to know about it when you are learning how to use Django forms.

 Thanks,
 John

-- 
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] #9858: Add POSTGIS_TEMPLATE setting for GIS Test Runner

[Django]

#9858: Add POSTGIS_TEMPLATE setting for GIS Test Runner
+---
  Reporter:  Aryeh Leib Taurog   | Owner:  
jbronn 
Status:  assigned   | Milestone:  
post-1.0   
 Component:  GIS|   Version:  
1.0
Resolution: |  Keywords:  
test template_postgis create_spatial_db
 Stage:  Accepted   | Has_patch:  1 
 
Needs_docs:  0  |   Needs_tests:  0 
 
Needs_better_patch:  0  |  
+---
Changes (by jbronn):

  * status:  new => assigned
  * summary:  pg test database not created with postgis template, tests
  fail => Add POSTGIS_TEMPLATE setting for GIS
  Test Runner
  * milestone:  => post-1.0

Comment:

 Alright, I think I've figured this one out.  On Windows you have specify
 an extra permission for the database superuser to be able to import the
 PostGIS files this is "Can modify data objects."  Attached is a screen
 shot from PGAdmin III that shows this permission checked in the create new
 role gui.

 Regardless, I'm not gonna "wontfix" this, and I'm repurposing the ticket
 to add support for a `POSTGIS_TEMPLATE` setting.

-- 
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] #10026: Possible error in django.contrib.auth.views.password_reset_confirm

[Django]

#10026: Possible error in django.contrib.auth.views.password_reset_confirm
+---
 Reporter:  jwmayfield  |   Owner:  nobody
   Status:  new |   Milestone:
Component:  Authentication  | Version:  SVN   
 Keywords:  password reset  |   Stage:  Unreviewed
Has_patch:  1   |  
+---
 Was getting this error:

 {{{

 [Django] Error (EXTERNAL IP): /reset/a6-29j-f7bb4a0b3867c9d3024a/

 Traceback (most recent call last):

  File "/usr/local/src/django/django/core/handlers/base.py", line 86, in
 get_response
response = callback(request, *callback_args, **callback_kwargs)

  File "/usr/local/src/django/django/contrib/auth/views.py", line 122, in
 password_reset_confirm
context_instance['validlink'] = True

  File "/usr/local/src/django/django/template/context.py", line 36, in
 __setitem__
self.dicts[0][key] = value

 TypeError: 'str' object does not support item assignment

 }}}

 Quick and dirty fix attached.

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

Re: [Django] #10025: Docstring typo in django.contrib.auth.tokens

[Django]

#10025: Docstring typo in django.contrib.auth.tokens
-+--
  Reporter:  Tarken  | Owner:  nobody
Status:  new | Milestone:
 Component:  Authentication  |   Version:  1.0   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by Tarken):

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

Comment:

 I just notice, line 21 also contains a typo:
 # Parse the tokem
 Should read:
 # Parse the token

-- 
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] #10025: Docstring typo in django.contrib.auth.tokens

[Django]

#10025: Docstring typo in django.contrib.auth.tokens
+---
 Reporter:  Tarken  |   Owner:  nobody
   Status:  new |   Milestone:
Component:  Authentication  | Version:  1.0   
 Keywords:  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 Very minor, but line 7 of django.contrib.auth.tokens begins with:
 "Stratgy object..."

 Obviously a typo for "Strategy".

-- 
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] #10024: Moving to a new host

[Django]

#10024: Moving to a new host
+---
  Reporter:  dagny  | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.0   
Resolution:  wontfix|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by jacob):

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

Comment:

 This is out of scope for Django. There's plenty of sysadmin documentation
 out there, and a good hosting provider ought to give you this
 documentation 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] #8138: Switch django tests to use transactions

[Django]

#8138: Switch django tests to use transactions
+---
  Reporter:  mremolt| Owner:  nobody  
Status:  new| Milestone:  post-1.0
 Component:  Testing framework  |   Version:  SVN 
Resolution: |  Keywords:  
 Stage:  Accepted   | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Comment (by kmtracey):

 I've updated the patch in response to comments on the dev list:
 http://groups.google.com/group/django-
 developers/browse_thread/thread/1e4f4c840b180895/b1ed88f5ace403b4#

 The test suite is now reordered so that all the tests that are going to
 use rollback are run first.  That way they can count on a clean DB, just
 as they could when they did the flush/syncdb to begin.

 Consensus seems to be to leave the doctest running outside of any
 transaction, so changes made by doctests may bleed over into other tests
 (as they can today).

 I removed the commit of the timezone setting for postgres since it is not
 necessary to avoid the fixtures doctest error when doctests are not
 enclosed in a transaction.  If it can be observed in other tests, though,
 I'd be interested in hearing about it.  Having the timezone setting
 vulnerable to rollback seems odd to me.

-- 
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] #10024: Moving to a new host

[Django]

#10024: Moving to a new host
---+
 Reporter:  dagny  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Documentation is needed on how to backup and move to a new hosting
 service.

-- 
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] #3460: Allow configuration of postgresql_psycopg2 isolation level

[Django]

#3460: Allow configuration of postgresql_psycopg2 isolation level
+---
  Reporter:  Jack Moffitt   | Owner:  
Richard Davies 
Status:  new| Milestone:
  
 Component:  Database layer (models, ORM)   |   Version:  SVN   
  
Resolution: |  Keywords:
  
 Stage:  Accepted   | Has_patch:  1 
  
Needs_docs:  0  |   Needs_tests:  0 
  
Needs_better_patch:  0  |  
+---
Comment (by iamseb):

 I've made it behave the same way as the native_autocommit setting for now,
 due to previous disquiet about changing the default behaviour. If there's
 general agreement that this is the correct method for retrieving inserted
 pk values then I'd be very happy for it to become the default.

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

[Changeset] r9738 - in django/branches/releases/1.0.X: . django/contrib/comments django/contrib/comments/templates/comments django/contrib/comments/views docs/ref/contrib/comments

[noreply]

Author: jacob
Date: 2009-01-14 11:00:15 -0600 (Wed, 14 Jan 2009)
New Revision: 9738

Modified:
   django/branches/releases/1.0.X/
   django/branches/releases/1.0.X/django/contrib/comments/admin.py
   django/branches/releases/1.0.X/django/contrib/comments/forms.py
   django/branches/releases/1.0.X/django/contrib/comments/managers.py
   django/branches/releases/1.0.X/django/contrib/comments/models.py
   
django/branches/releases/1.0.X/django/contrib/comments/templates/comments/approve.html
   
django/branches/releases/1.0.X/django/contrib/comments/templates/comments/delete.html
   
django/branches/releases/1.0.X/django/contrib/comments/templates/comments/flag.html
   django/branches/releases/1.0.X/django/contrib/comments/urls.py
   django/branches/releases/1.0.X/django/contrib/comments/views/utils.py
   django/branches/releases/1.0.X/docs/ref/contrib/comments/index.txt
   django/branches/releases/1.0.X/docs/ref/contrib/comments/upgrade.txt
Log:
A handful of fixes to django.contrib.comments:

  * Fixed #9143, #9429, and #9439 (was r9730 on trunk)
  * Fixed #9959: comment preview documentation example (was r9731 on trunk)
  * Fixed #9346: comment upgrade SQL in documentation. (was r9732 on trunk).


Property changes on: django/branches/releases/1.0.X
___
Name: svnmerge-integrated
   - 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691,9693-9699,9703-9706,9709-9713,9716-9723,9725-9726,9733
   + 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691,9693-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9733

Modified: django/branches/releases/1.0.X/django/contrib/comments/admin.py
===
--- django/branches/releases/1.0.X/django/contrib/comments/admin.py 
2009-01-14 16:02:59 UTC (rev 9737)
+++ django/branches/releases/1.0.X/django/contrib/comments/admin.py 
2009-01-14 17:00:15 UTC (rev 9738)
@@ -1,5 +1,4 @@
 from django.contrib import admin
-from django.conf import settings
 from django.contrib.comments.models import Comment
 from django.utils.translation import ugettext_lazy as _
 

Modified: django/branches/releases/1.0.X/django/contrib/comments/forms.py
===
--- django/branches/releases/1.0.X/django/contrib/comments/forms.py 
2009-01-14 16:02:59 UTC (rev 9737)
+++ django/branches/releases/1.0.X/django/contrib/comments/forms.py 
2009-01-14 17:00:15 UTC (rev 9738)
@@ -1,11 +1,9 @@
-import re
 import time
 import datetime
 
 from django import forms
 from django.forms.util import ErrorDict
 from django.conf import settings
-from django.http import Http404
 from django.contrib.contenttypes.models import ContentType
 from models import Comment
 from django.utils.encoding import force_unicode

Modified: django/branches/releases/1.0.X/django/contrib/comments/managers.py
===
--- django/branches/releases/1.0.X/django/contrib/comments/managers.py  
2009-01-14 16:02:59 UTC (rev 9737)
+++ django/branches/releases/1.0.X/django/contrib/comments/managers.py  
2009-01-14 17:00:15 UTC (rev 9738)
@@ -1,5 +1,4 @@
 from django.db import models
-from django.dispatch import dispatcher
 from django.contrib.contenttypes.models import ContentType
 from django.utils.encoding import force_unicode
 

Modified: django/branches/releases/1.0.X/django/contrib/comments/models.py
===
--- django/branches/releases/1.0.X/django/contrib/comments/models.py
2009-01-14 16:02:59 UTC (rev 9737)
+++ django/branches/releases/1.0.X/django/contrib/comments/models.py
2009-01-14 17:00:15 UTC (rev 9738)
@@ -140,7 +140,7 @@
 Return this comment as plain text.  Useful for emails.
 """
 d = {
-'user': self.user,
+'user': self.user or self.name,
 'date': self.submit_date,
 'comment': self.comment,
 'domain': self.site.domain,

Modified: 
django/branches/releases/1.0.X/django/contrib/comments/templates/comments/approve.html
===
--- 
django/branches/releases/1.0.X/django/contrib/comments/templates/comments/approve.html
  2009-01-14 16:02:59 UTC (rev 9737)
+++ 
dja

Re: [Django] #3460: Allow configuration of postgresql_psycopg2 isolation level

[Django]

#3460: Allow configuration of postgresql_psycopg2 isolation level
+---
  Reporter:  Jack Moffitt   | Owner:  
Richard Davies 
Status:  new| Milestone:
  
 Component:  Database layer (models, ORM)   |   Version:  SVN   
  
Resolution: |  Keywords:
  
 Stage:  Accepted   | Has_patch:  1 
  
Needs_docs:  0  |   Needs_tests:  0 
  
Needs_better_patch:  0  |  
+---
Comment (by Richard Davies ):

 Thanks - looks good to me. I imagine that you want
 "self.features.can_return_id_from_insert = True", not False, on new line
 70 of backends/postgresql_psycopg2/base.py? I'd assume this is a postgres
 feature which is always available regardless of isolation level?

-- 
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] #3460: Allow configuration of postgresql_psycopg2 isolation level

[Django]

#3460: Allow configuration of postgresql_psycopg2 isolation level
+---
  Reporter:  Jack Moffitt   | Owner:  
Richard Davies 
Status:  new| Milestone:
  
 Component:  Database layer (models, ORM)   |   Version:  SVN   
  
Resolution: |  Keywords:
  
 Stage:  Accepted   | Has_patch:  1 
  
Needs_docs:  0  |   Needs_tests:  0 
  
Needs_better_patch:  0  |  
+---
Comment (by iamseb):

 I've added an updated patch that implements a safe version of the
 transaction isolation patch for database connections that implement
 transaction pooling, whilst sticking with the implementation approach in
 Richard's combined patch. Transaction isolation can return incorrect data
 when retrieving PKs after insert operations without this addition.

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

[Changeset] r9737 - django/branches/releases/1.0.X

[noreply]

Author: kmtracey
Date: 2009-01-14 10:02:59 -0600 (Wed, 14 Jan 2009)
New Revision: 9737

Modified:
   django/branches/releases/1.0.X/
Log:
[1.0.X] Bring svnmerge metadata up to date with what's actually been merged to 
the branch.



Property changes on: django/branches/releases/1.0.X
___
Name: svnmerge-integrated
   - 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691,9695-9696,9698,9709,9713
   + 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691,9693-9699,9703-9706,9709-9713,9716-9723,9725-9726,9733


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

[Changeset] r9736 - django/branches/releases/1.0.X

[noreply]

Author: kmtracey
Date: 2009-01-14 09:37:23 -0600 (Wed, 14 Jan 2009)
New Revision: 9736

Modified:
   django/branches/releases/1.0.X/
Log:
[1.0.X] Block two more revisions fumblefingers missed in the last attempt.



Property changes on: django/branches/releases/1.0.X
___
Name: svnmerge-blocked
   - 
/django/trunk:9098,9103,9110,9112,9145,9152,9157,9160,9188,9248,9263,9278,9299-9300,9303-9304,9332,9344,9346,9348-9349,9353-9354,9397-9398,9463-9465,9470,9489-9490,9527-9528,9530-9532,9537-9538,9551-9555,9558,9561,9569,9592-9594,9620,9625,9637,9643,9646,9690,9700-9702,9714-9715,9724,9727-9729
   + 
/django/trunk:9098,9103,9110,9112,9145,9152,9157,9160,9188,9248,9263,9278,9299-9300,9303-9304,9332,9344,9346,9348-9349,9353-9354,9397-9398,9463-9465,9470,9489-9490,9527-9528,9530-9532,9537-9538,9551-9555,9558,9561,9569,9592-9594,9620,9625,9637,9643,9646,9690,9700-9702,9707-9708,9714-9715,9724,9727-9729


--~--~-~--~~~---~--~~
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] #8055: Transaction error when doing loaddata

[Django]

#8055: Transaction error when doing loaddata
+---
  Reporter:  Erik Allik   | Owner:  ramiro
   
Status:  new| Milestone:  post-1.0  
   
 Component:  Serialization  |   Version:  SVN   
   
Resolution: |  Keywords:  loaddata 
fixtures print_exc 2.3 traceback
 Stage:  Accepted   | Has_patch:  1 
   
Needs_docs:  0  |   Needs_tests:  0 
   
Needs_better_patch:  0  |  
+---
Changes (by ramiro):

  * keywords:  => loaddata fixtures print_exc 2.3 traceback
  * owner:  nobody => ramiro
  * has_patch:  0 => 1
  * status:  reopened => new

Comment:

 tom_payne didn't report what version of Python he was using, but from what
 he describes he could be using Python 2.3. Uploaded a patch based in his
 findings.

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

[Changeset] r9735 - django/branches/releases/1.0.X

[noreply]

Author: kmtracey
Date: 2009-01-14 09:33:07 -0600 (Wed, 14 Jan 2009)
New Revision: 9735

Modified:
   django/branches/releases/1.0.X/
Log:
[1.0.X] Block trunk new function commits from svnmerge.py consideration.



Property changes on: django/branches/releases/1.0.X
___
Name: svnmerge-blocked
   - 
/django/trunk:9098,9103,9110,9112,9145,9152,9157,9160,9188,9248,9263,9278,9299-9300,9303-9304,9332,9344,9346,9348-9349,9353-9354,9397-9398,9463-9465,9470,9489-9490,9527-9528,9530-9532,9537-9538,9551-9555,9558,9561,9569,9592-9594,9620,9625,9637,9643,9646,9690
   + 
/django/trunk:9098,9103,9110,9112,9145,9152,9157,9160,9188,9248,9263,9278,9299-9300,9303-9304,9332,9344,9346,9348-9349,9353-9354,9397-9398,9463-9465,9470,9489-9490,9527-9528,9530-9532,9537-9538,9551-9555,9558,9561,9569,9592-9594,9620,9625,9637,9643,9646,9690,9700-9702,9714-9715,9724,9727-9729


--~--~-~--~~~---~--~~
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] #3460: Allow configuration of postgresql_psycopg2 isolation level

[Django]

#3460: Allow configuration of postgresql_psycopg2 isolation level
+---
  Reporter:  Jack Moffitt   | Owner:  
Richard Davies 
Status:  new| Milestone:
  
 Component:  Database layer (models, ORM)   |   Version:  SVN   
  
Resolution: |  Keywords:
  
 Stage:  Accepted   | Has_patch:  1 
  
Needs_docs:  0  |   Needs_tests:  0 
  
Needs_better_patch:  0  |  
+---
Comment (by nicferrier):

 It's vital that the returning patch be in there as well. Without that it
 is entirely possible to get inconsistent data by naive (non-transaction
 protected) use of the ORM.

 WITH the patch it is NOT possible to get inconsistent data simply be being
 naive.

-- 
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] #3460: Allow configuration of postgresql_psycopg2 isolation level

[Django]

#3460: Allow configuration of postgresql_psycopg2 isolation level
+---
  Reporter:  Jack Moffitt   | Owner:  
Richard Davies 
Status:  new| Milestone:
  
 Component:  Database layer (models, ORM)   |   Version:  SVN   
  
Resolution: |  Keywords:
  
 Stage:  Accepted   | Has_patch:  1 
  
Needs_docs:  0  |   Needs_tests:  0 
  
Needs_better_patch:  0  |  
+---
Changes (by Richard Davies ):

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

Comment:

 I've updated nicferrier's patch to make it configurable - hopefully this
 can now go in for 1.1 by tomorrow.

 The revised patch uses the same basic mechanism that nicferrier suggested.
 It is typically inactive, and is switched on with
 DATABASE_OPTIONS={'native_autocommit':True}, which I have documented. With
 this patch, SVN Django passes the full test suite using sqlite3,
 postgresql_psycopg2 (plain default) and postgresql_psycopg2
 (native_autocommit turned on).

 I fixed two bugs to get the full test suite to pass (both mentioned in
 various patches earlier in this ticket): savepoints are not supported in
 isolation level 0, and I've moved the call to the new
 connection._enter_transaction_management() inside
 transaction.enter_transaction_management() so that it also applies to
 fixtures loaddata.py, etc.

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