Re: [Django] #18641: Offline documentation states 1.5 when its for 1.4

[Django]

#18641: Offline documentation states 1.5 when its for 1.4
-+-
 Reporter:  burhan.khalid@…  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  Documentation|   Resolution:  needsinfo
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 What download link did you use?

 The docs at https://www.djangoproject.com/m/docs/django-docs-1.4-en.zip
 show 1.4 as expected.

-- 
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] #18641: Offline documentation states 1.5 when its for 1.4

[Django]

#18641: Offline documentation states 1.5 when its for 1.4
--+
 Reporter:  burhan.khalid@…   |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.4
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 The offline documentation download shows "Django 1.5 Documentation" but
 its for 1.4

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

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

Re: [Django] #18639: manage.py shell should have a flag to explicitly request iPython or bpython

[Django]

#18639: manage.py shell should have a flag to explicitly request iPython or 
bpython
-+-
 Reporter:  Alex |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  1.4
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by mgrouchy):

 Added Pull request for this feature here:
 https://github.com/django/django/pull/215

 Relevant documentation has been updated.

-- 
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] #18640: django.contrib.gis.gdal.DataSource fields give gibberish or segfault when accessed directly

[Django]

#18640: django.contrib.gis.gdal.DataSource fields give gibberish or segfault 
when
accessed directly
---+
 Reporter:  YenTheFirst|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 if you hold a feature in a variable, and access a field, it will give the
 correct value.

 however, if you access a feature's field by layer[][],
 it gives gibberish, or a segfault.

 this might be related to https://code.djangoproject.com/ticket/9448.
 however, given that the ticket was closed, it might be a different issue.

 script to reproduce issue:
 {{{
 import os
 import django.contrib.gis
 from django.contrib.gis.gdal import DataSource

 GIS_PATH = os.path.dirname(django.contrib.gis.__file__)
 CITIES_PATH = os.path.join(GIS_PATH, 'tests/data/cities/cities.shp')

 ds = DataSource(CITIES_PATH)
 layer = ds[0]
 feature = layer[0]
 field = feature['Name']

 print "this is valid: %r (%r)" % (field.value, list(field.value))

 field = layer[0]['Name']

 print "but this isn't: %r (%r)" % (field.value, list(field.value))

 }}}


 in python, results in segfault.
 in ipython:
 this is valid: 'Pueblo' (['P', 'u', 'e', 'b', 'l', 'o'])
 but this isn't: ':\xd5\xe2=\xb1\xb4\xb9\xb4Q' ([':', '\xd5', '\xe2', '=',
 '\xb1', '\xb4', '\xb9', '\xb4', 'Q'])

 saved as script, results in:
 this is valid: 'Pueblo' (['P', 'u', 'e', 'b', 'l', 'o'])
 but this isn't: '' ([])


 this is on an ubuntu 11.04, with django 1.4, and gdal 1.7

-- 
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] #18153: Erorneous OneToOneField for instances that have pk unset

[Django]

#18153: Erorneous OneToOneField for instances that have pk unset
-+-
 Reporter:  jbzdak@… |Owner:  dhatch
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by dhatch):

 * needs_better_patch:  1 => 0


Comment:

 Just finished the new patch matching ReverseSingleRelatedObjectDescriptor.
 Located at
 https://github.com/dhatch/django/tree/ticket_18153_backwardsincompat.

-- 
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] #18639: manage.py shell should have a flag to explicitly request iPython or bpython

[Django]

#18639: manage.py shell should have a flag to explicitly request iPython or 
bpython
-+-
   Reporter:  Alex   |  Owner:  nobody
   Type:  New| Status:  new
  feature|Version:  1.4
  Component:  Core   |   Keywords:
  (Management commands)  |  Has patch:  0
   Severity:  Normal |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  1
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 If you have both installed, sometimes you'll want one vs. another for
 various reasons.  There should be a flag to explicitly request this.

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

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

Re: [Django] #18153: Erorneous OneToOneField for instances that have pk unset

[Django]

#18153: Erorneous OneToOneField for instances that have pk unset
-+-
 Reporter:  jbzdak@… |Owner:  dhatch
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by akaariai):

 It is worth to keep the original patch also around. It might be we need to
 go that route if it turns out the backwards compatibility is likely to
 cause problems to users.

-- 
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] #18153: Erorneous OneToOneField for instances that have pk unset

[Django]

#18153: Erorneous OneToOneField for instances that have pk unset
-+-
 Reporter:  jbzdak@… |Owner:  dhatch
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by dhatch):

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

Re: [Django] #18153: Erorneous OneToOneField for instances that have pk unset

[Django]

#18153: Erorneous OneToOneField for instances that have pk unset
-+-
 Reporter:  jbzdak@… |Owner:  dhatch
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by dhatch):

 Replying to [comment:5 akaariai]:
 > I vote for consistency with foreign key fields. It seems the right
 behavior to me. Although I have no idea how bad the breakage will be.
 There is always the possibility to claim this to be a bugfix and thus
 backwards compatibility does not apply... :)
 >
 > As for the patch, it seems good to me. The question is if that is really
 the behavior we want to commit into.
 Agreed.  Will modify the patch to be consistent with foreign keys, seems
 right to me as well.

 The behavior before was as follows:

 1) If no objects of the reverse one to one type existed in the database
 DoesNotExist was raised (regardless of null).

 2) If one object of the reverse one to one type existed in the database,
 it was returned, regardless of the fact that the field was not set.
 (Clearly this scenario is a bug)

 3) If multiple objects of the reverse type exist, MultipleObjectsReturned
 is raised.

 After the patch the behavior for all these three cases will either be to
 raise DoesNotExist or return null if the field is nullable when the pk of
 the model is not set.

-- 
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] #18153: Erorneous OneToOneField for instances that have pk unset

[Django]

#18153: Erorneous OneToOneField for instances that have pk unset
-+-
 Reporter:  jbzdak@… |Owner:  dhatch
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by akaariai):

 I vote for consistency with foreign key fields. It seems the right
 behavior to me. Although I have no idea how bad the breakage will be.
 There is always the possibility to claim this to be a bugfix and thus
 backwards compatibility does not apply... :)

 As for the patch, it seems good to me. The question is if that is really
 the behavior we want to commit into.

-- 
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] #18153: Erorneous OneToOneField for instances that have pk unset

[Django]

#18153: Erorneous OneToOneField for instances that have pk unset
-+-
 Reporter:  jbzdak@… |Owner:  dhatch
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by dhatch):

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


-- 
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] #18153: Erorneous OneToOneField for instances that have pk unset

[Django]

#18153: Erorneous OneToOneField for instances that have pk unset
-+-
 Reporter:  jbzdak@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by dhatch):

 * has_patch:  0 => 1


Comment:

 The behavior I just described would break existing regression tests.  I've
 written a patch for this such that SingleRelatedObjectDescriptor raises a
 DoesNotExist regardless of the null settings if the instance does not have
 a pk.  Note: The behavior of raising DoesNotExist even when the field is
 nullable seems inconsistent with other components of the API.

 ReverseSingleRelatedObjectDescriptor returns None when the field is null
 (see line 375 of django.db.models.fields.related).  There is another open
 issue about this problem at #10227.

 My patch is at https://github.com/dhatch/django/tree/ticket_18153.  Will
 submit a pull request once it has been reviewed.

-- 
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] #18153: Erorneous OneToOneField for instances that have pk unset

[Django]

#18153: Erorneous OneToOneField for instances that have pk unset
-+-
 Reporter:  jbzdak@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by dhatch):

 Perhaps for consistency with ForeignKeyField behavior it makes sense to
 raise a ObjectDoesNotExist unless the field is nullable, in which case
 return None.

-- 
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] #18306: Deferred models should automatically issue update_fields when saving

[Django]

#18306: Deferred models should automatically issue update_fields when saving
-+-
 Reporter:  akaariai |Owner:  akaariai
 Type:   |   Status:  reopened
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Ready for
 Severity:  Normal   |  checkin
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by akaariai):

 * needs_better_patch:  1 => 0
 * stage:  Accepted => Ready for checkin


Comment:

 I have reviewed and polished the patch written by niwi. I created
 [https://github.com/django/django/pull/213 a pull request] as I think the
 feature is now ready for commit. Please review, or at least do a cursory
 glance for obvious mistakes.

 I wonder if I should squash the two commits into one...

 I ended up getting rid of the model._state.deferred_fields and instead
 using the instance's and class' dict to check the deferred state of the
 object when saving. The idea of using ._state was mine (or at least
 encouraged by me), sorry for pushing the wrong solution.

-- 
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] #18638: Reverse OneToOne relationship does not save properly.

[Django]

#18638: Reverse OneToOne relationship does not save properly.
-+-
 Reporter:  dhatch   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   |  worksforme
 Keywords:   | Triage Stage:
Has patch:  1|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  1
 |UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 You're seeing the expected behavior. You'd need to call `tag.save()`.

 The API for 1-to-1 relationships isn't totally symmetrical -- after all it
 isn't at the SQL 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 https://groups.google.com/groups/opt_out.

Re: [Django] #5579: Trac activation mail is sent from 'webmaster@localhost'

[Django]

#5579: Trac activation mail is sent from 'webmaster@localhost'
-+-
 Reporter:  tback|Owner:  anonymous
 Type:  Bug  |   Status:  closed
Component:  Djangoproject.com|  Version:
  Web site   |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  activation email |  Needs documentation:  0
  trac   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


-- 
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] #18638: Reverse OneToOne relationship does not save properly.

[Django]

#18638: Reverse OneToOne relationship does not save properly.
-+-
 Reporter:  dhatch   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by dhatch):

 * owner:  dhatch => nobody


-- 
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] #18638: Reverse OneToOne relationship does not save properly.

[Django]

#18638: Reverse OneToOne relationship does not save properly.
-+-
 Reporter:  dhatch   |Owner:  dhatch
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by dhatch):

 * cc: dhatch (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] #18638: Reverse OneToOne relationship does not save properly.

[Django]

#18638: Reverse OneToOne relationship does not save properly.
-+-
 Reporter:  dhatch   |Owner:  dhatch
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by dhatch):

 * owner:  nobody => dhatch


-- 
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] #18638: Reverse OneToOne relationship does not save properly.

[Django]

#18638: Reverse OneToOne relationship does not save properly.
-+-
 Reporter:  dhatch   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by anonymous):

 * needs_docs:   => 0
 * needs_tests:   => 0
 * needs_better_patch:   => 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 https://groups.google.com/groups/opt_out.

Re: [Django] #5579: Trac activation mail is sent from 'webmaster@localhost'

[Django]

#5579: Trac activation mail is sent from 'webmaster@localhost'
-+-
 Reporter:  tback|Owner:  anonymous
 Type:  Bug  |   Status:  reopened
Component:  Djangoproject.com|  Version:
  Web site   |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  activation email |  Needs documentation:  0
  trac   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by anonymous):

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


-- 
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] #18638: Reverse OneToOne relationship does not save properly.

[Django]

#18638: Reverse OneToOne relationship does not save properly.
--+
 Reporter:  dhatch|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.4
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+
 When the reverse side of a one-to-one relationship is assigned to and the
 model is saved, the association is not properly written to the database.

 Example:

 Models:
 {{{
 class Tag(models.Model):
 data = models.OneToOneField("Data")

 class Data(models.Model):
 pass
 }}}

 Run:
 {{{
 data = Data()
 t = Tag.objects.create()
 data.tag = t
 data.save()
 # refresh from db
 data = Data.objects.get(pk=data.pk)
 data.tag # raises DoesNotExist
 }}}

 Attached is a patch including a test case which illustrates this issue.
 To run the test case cd to the tests directory then...

 {{{export PYTHONPATH=`pwd`:`pwd`/..; ./runtests.py --settings=test_sqlite
 one_to_one_regress}}}

 '''test_reverse_one_to_one_save''' should fail.

-- 
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] #18637: FK.limit_choices_to doc says it's for admin, but works in ModelForm

[Django]

#18637: FK.limit_choices_to doc says it's for admin, but works in ModelForm
---+
 Reporter:  Tuttle |Owner:  nobody
 Type:  Bug|   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:  1  |UI/UX:  0
---+
Changes (by aaugustin):

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


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

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

Re: [Django] #15084: Unnecessary imports lead to ImportError

[Django]

#15084: Unnecessary imports lead to ImportError
--+
 Reporter:  vanschelven   |Owner:  nobody
 Type:  Bug   |   Status:  reopened
Component:  Internationalization  |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by akaariai):

 Looking at the provided patch in this ticket - the pkgutil documentation
 says that the get_loader() will import the module if it isn't already
 imported. So, I fail to see what is the difference when using pkgutil
 compared to import_module.

 To me it seems that as long as calling ugettext leads to importing other
 apps, the importing of other apps will lead to circular imports. Is there
 a way to get the module's path without doing imports?

 I don't know Python's import mechanism well, so it is very much possible
 that I just don't understand what is happening.

-- 
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] #11154: Inconsistency with permissions for proxy models

[Django]

#11154: Inconsistency with permissions for proxy models
-+-
 Reporter:  etianen  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  proxy contenttype| Triage Stage:  Accepted
  permission |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by akaariai):

 I would really like to see a release note for this. I am currently looking
 at the pull request and wondering what exactly will change. I am going to
 close the pull request (per the policy of commit or close on review).
 Reopen with the added docs. I have a suspicious feeling I should know by
 now what this changes, but can't remember...

-- 
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] #3881: Don't mask server exception with session save exception

[Django]

#3881: Don't mask server exception with session save exception
--+
 Reporter:  hauserx@… |Owner:  adrian
 Type:  Bug   |   Status:  closed
Component:  contrib.sessions  |  Version:  1.3-beta
 Severity:  Normal|   Resolution:  fixed
 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 Anssi Kääriäinen ):

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


Comment:

 In [aeda55e6bffc3cfbf53698af398a19c1a0f02d46]:
 {{{
 #!CommitTicketReference repository=""
 revision="aeda55e6bffc3cfbf53698af398a19c1a0f02d46"
 Fixed #3881 -- skip saving session when response status is 500

 Saving session data is somewhat likely to lead into error when the
 status code is 500. It is guaranteed to lead into error if the reason
 for the 500 code is query error on 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.

[django/django] aeda55: Fixed #3881 -- skip saving session when response s...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: aeda55e6bffc3cfbf53698af398a19c1a0f02d46
  
https://github.com/django/django/commit/aeda55e6bffc3cfbf53698af398a19c1a0f02d46
  Author: Anssi Kääriäinen 
  Date:   2012-07-16 (Mon, 16 Jul 2012)

  Changed paths:
M django/contrib/sessions/middleware.py
M django/contrib/sessions/tests.py
M docs/releases/1.5.txt
M docs/topics/http/sessions.txt

  Log Message:
  ---
  Fixed #3881 -- skip saving session when response status is 500

Saving session data is somewhat likely to lead into error when the
status code is 500. It is guaranteed to lead into error if the reason
for the 500 code is query error on PostgreSQL.



-- 
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] #18637: FK.limit_choices_to doc says it's for admin, but works in ModelForm

[Django]

#18637: FK.limit_choices_to doc says it's for admin, but works in ModelForm
---+
 Reporter:  Tuttle |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Documentation  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 Using `limit_choices_to` option on a `ForeignKey` field works for me in
 the `ModelForm` too.

 I didn't test M2M field's `limit_choices_to`.

 Therefore to me, the
 
[https://docs.djangoproject.com/en/dev/ref/models/fields/#django.db.models.ForeignKey.limit_choices_to
 doc] appears to be a bit misleading mentioning "admin" twice.

-- 
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] #18635: Getting Error while added admin theam in local app --Directory indexes are not allowed here.

[Django]

#18635: Getting Error while added admin theam in local app --Directory indexes 
are
not allowed here.
---+--
 Reporter:  chhotubayas@…  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.3-alpha
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by ramiro):

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


Comment:

 TicketClosingReasons/UseSupportChannels

-- 
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/django] bebbbb: Fixed #18056 - Cleared aggregations on DateQuery.a...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: be7af096ecffc0d7585617fdfacb196bc7c2
  
https://github.com/django/django/commit/be7af096ecffc0d7585617fdfacb196bc7c2
  Author: Nuno Maltez 
  Date:   2012-07-16 (Mon, 16 Jul 2012)

  Changed paths:
M django/db/models/sql/subqueries.py
M tests/modeltests/aggregation/tests.py

  Log Message:
  ---
  Fixed #18056 - Cleared aggregations on DateQuery.add_date_select

Cleared aggregations on add_date_select method so only distinct dates
are returned when dealing with a QuerySet that contained aggregations.
That would cause the query set to return repeated dates because it
would look for distinct (date kind, aggregation) pairs.



-- 
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] #18056: query_set.dates('field_name', 'years') does not return distinct elements

[Django]

#18056: query_set.dates('field_name', 'years') does not return distinct elements
-+-
 Reporter:  framazz@…|Owner:  nmfm
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Anssi Kääriäinen ):

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


Comment:

 In [be7af096ecffc0d7585617fdfacb196bc7c2]:
 {{{
 #!CommitTicketReference repository=""
 revision="be7af096ecffc0d7585617fdfacb196bc7c2"
 Fixed #18056 - Cleared aggregations on DateQuery.add_date_select

 Cleared aggregations on add_date_select method so only distinct dates
 are returned when dealing with a QuerySet that contained aggregations.
 That would cause the query set to return repeated dates because it
 would look for distinct (date kind, aggregation) pairs.
 }}}

-- 
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] #56: MySQL id columns should be UNSIGNED

[Django]

#56: MySQL id columns should be UNSIGNED
-+-
 Reporter:  Manuzhai |Owner:
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  mysql|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by akaariai):

 To me the alternate approach seems fine. It does need some tests though,
 mainly to make sure the related field type matching works properly.

 The alternate approach doesn't directly resolve this ticket's issue
 though. Unsigned is different than bigint. I wonder if adding also
 unsigned flag should be done?

-- 
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] #13844: Errors when using character fields for aggregation

[Django]

#13844: Errors when using character fields for aggregation
-+-
 Reporter:  zegrep@… |Owner:  wogan
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.2
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by akaariai):

 * needs_better_patch:  1 => 0
 * needs_tests:  1 => 0
 * stage:  Accepted => Ready for checkin


Comment:

 There is a comment in Oracle's convert_values() which says that because
 to_python() is meant for validation, it should not be used for converting
 values. At least one possible problem is that the to_python() method
 raises `ValidationError` on problematic input, and that error doesn't fit
 here.

 I am proposing (and I am going to likely commit)
 
[https://github.com/akaariai/django/commit/fe1e4f4e3ca3a70cdc3d327f9021b349fa75b431
 a patch] which just removes the non-necessary float(value) from
 convert_values. This fixes PostgreSQL and MySQL. Oracle and SQLite already
 override the convert_values() method, and return the bare value in the
 "unknown field type" case.

 In addition, the suggestion made in the comments of this ticket that the
 conversion should be done by the field, not by the backend gets a +1 from
 me. It might be as straightforward as defining to_python() to do the
 conversion, but IMO it needs separate ticket and some more investigation.

-- 
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] #15053: Make templates more reusable by Improving template loading algorithm to avoid extending infinite recursion

[Django]

#15053: Make templates more reusable by Improving template loading algorithm to
avoid extending infinite recursion
-+
 Reporter:  pmartin  |Owner:  nobody
 Type:  New feature  |   Status:  reopened
Component:  Template system  |  Version:  1.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+

Comment (by pmartin):

 Now works with the last version of
 
[https://github.com/goinnn/django/commit/ddb9fc152422743c18c1336413ad3255b5305385
 django]. I want to write comments, analize the code and I will try to
 clean the code. I coded this 18 month ago...

-- 
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] #18636: django-admin.py startproject mysite

[Django]

#18636: django-admin.py startproject mysite
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.3
 Severity:  Normal |   Resolution:  worksforme
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by aaugustin):

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


Comment:

 This peculiarity of Ubuntu is explained exactly two lines below the
 command, in "Script name may differ in distribution packages".

-- 
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] #18636: django-admin.py startproject mysite

[Django]

#18636: django-admin.py startproject mysite
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.3
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 Hi,

 Thanks for the good work.

 "django-admin.py startproject mysite" should read "django-admin
 startproject mysite" at least on my machine (Ubuntu 12.04)

 this is where the django-admin resides /usr/bin/django-admin

 Best

-- 
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] #5725: Inspectdb makes too long CharFields

[Django]

#5725: Inspectdb makes too long CharFields
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  introspection mysql  |  checkin
  inspectdb  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by jedie):

 * cc: django@… (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] #18635: Getting Error while added admin theam in local app --Directory indexes are not allowed here.

[Django]

#18635: Getting Error while added admin theam in local app --Directory indexes 
are
not allowed here.
---+--
 Reporter:  chhotubayas@…  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.3-alpha
 Severity:  Normal |   Resolution:
 Keywords: | 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_better_patch:   => 0
 * version:  1.4 => 1.3-alpha
 * 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] #18635: Getting Error while added admin theam in local app --Directory indexes are not allowed here.

[Django]

#18635: Getting Error while added admin theam in local app --Directory indexes 
are
not allowed here.
---+
 Reporter:  chhotubayas@…  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  contrib.admin  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Page not found (404)
 Request Method: GET
 Request URL:http://localhost:8080/static/grappelli/

 Directory indexes are not allowed here.

 You're seeing this error because you have DEBUG = True in your Django
 settings file. Change that to False, and Django will display a standard
 404 page.

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

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

Re: [Django] #18212: GenericIPAddressField does not handle verbose_name and name args like other field types

[Django]

#18212: GenericIPAddressField does not handle verbose_name and name args like 
other
field types
-+-
 Reporter:  toofishes|Owner:
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:  fields   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by net147):

 * cc: net147 (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] #18634: Escaping in the startproject command

[Django]

#18634: Escaping in the startproject command
-+-
 Reporter:  mjtamlyn |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


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

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

[Django] #18634: Escaping in the startproject command

[Django]

#18634: Escaping in the startproject command
+
 Reporter:  mjtamlyn|  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Core (Management commands)  |Version:  master
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 The startproject command uses the template language, and seems to be html-
 escaping various things. For example aviraldg reported on IRC getting a
 SECRET_KEY with several instances of & in the middle of the string.

 In this context it's harmless, but it may break other places where & or <
 are legitimate characters. We should probably render the whole template
 with escaping disabled.

-- 
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] #15932: related_name='+' ignored in ManyToManyField validation

[Django]

#15932: related_name='+' ignored in ManyToManyField validation
---+--
 Reporter:  Fredde |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.4-beta-1
 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
---+--

Comment (by akaariai):

 I don't think the patch is correct.

 To me it seems the related_name must be unique in the __related model__,
 not in the originating model. And, as the '+' implies the related name is
 hidden in the related model, I don't see why it should be unique in this
 case even in the related model. It doesn't need to be unique, as it
 shouldn't exists at all. Maybe this is not a documentation issue after
 all?

-- 
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] #13161: Ticked 2514 and 5171, solution for using Django with other psycopg2 applications.

[Django]

#13161: Ticked 2514 and 5171, solution for using Django with other psycopg2
applications.
-+-
 Reporter:  spoksss  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  psycopg2, unicode|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by aaugustin):

 Replying to [comment:10 anonymous]:
 > What else can be done to commit it to trunk?

 The patch is still marked as needing tests.

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

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

Re: [Django] #15932: related_name='+' ignored in ManyToManyField validation

[Django]

#15932: related_name='+' ignored in ManyToManyField validation
---+--
 Reporter:  Fredde |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.4-beta-1
 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
---+--

Comment (by anonymous):

 The statement that related_name has to be unique within a model is not
 true for the following cases:
  * The relation fields refers till different models
  * The related_name is "+" for a ForeignKey field

-- 
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] #13161: Ticked 2514 and 5171, solution for using Django with other psycopg2 applications.

[Django]

#13161: Ticked 2514 and 5171, solution for using Django with other psycopg2
applications.
-+-
 Reporter:  spoksss  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  psycopg2, unicode|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by anonymous):

 * version:  1.2-beta => 1.4


Comment:

 Now (version 1.4 of Django) there is only one supported backend (psycopg2)
 for postgresql, so it is possible, that this patch will be in trunk.
 What else can be done to commit it to trunk?

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

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

Re: [Django] #18629: Adding methods/attributes to date-based views (was: Adding methods/attributes to editing views)

[Django]

#18629: Adding methods/attributes to date-based views
--+
 Reporter:  pydanny   |Owner:  donigian
 Type:  Cleanup/optimization  |   Status:  reopened
Component:  Documentation |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:  cbv   | 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):

 4

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

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

Re: [Django] #15932: related_name='+' ignored in ManyToManyField validation

[Django]

#15932: related_name='+' ignored in ManyToManyField validation
---+--
 Reporter:  Fredde |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.4-beta-1
 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
---+--

Comment (by claudep):

 Attached a patch with updated documentation about related_name. Please
 check the wording.

-- 
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] #18632: Cleanup on methods/attributes associated with editing views

[Django]

#18632: Cleanup on methods/attributes associated with editing views
--+
 Reporter:  pydanny   |Owner:  pydanny
 Type:  Cleanup/optimization  |   Status:  reopened
Component:  Documentation |  Version:  1.4
 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
--+
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16011: Improve Django documentation search engine results relevancy

[Django]

#16011: Improve Django documentation search engine results relevancy
-+-
 Reporter:  info.ksamuel@…   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.3
Component:  Djangoproject.com|   Resolution:
  Web site   | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  search-engine|  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by aaugustin):

 See also #18633

-- 
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] #18633: Can't use parenthesis in Documentation search bar

[Django]

#18633: Can't use parenthesis in Documentation search bar
-+-
 Reporter:  kevinlondon  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Djangoproject.com|  Version:  1.4
  Web site   |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  website, search, |  Needs documentation:  0
  documentation  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  1
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * stage:  Unreviewed => Accepted


Comment:

 Related: #16011

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