date:20130627

Re: [Django] #15363: get_queryset & get_query_set

2013-06-27 Thread Django

#15363: get_queryset & get_query_set
--+
 Reporter:  sorl  |Owner:  loic84
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Other)  |  Version:  master
 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
--+

Comment (by loic84):

 I'm not sure why you would use this temporary metaclass, could you try the
 following:

 {{{
 def __call__(self, base_manager, *args, **kwargs):
 return type(
 self.__class__.__name__,
 (self.__class__, base_manager),
 {'use_for_related_fields': True}
 )
 }}}

 Note that I didn't manage to run your test suite, even with the old
 `TEST_RUNNER` so it's just a guess.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.5ea5947e622c0d71615a6b8fcd58%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20656: test db spatial extentsion not created when using new postgis 2.0 "CREATE EXTENSION postgis; " method

2013-06-27 Thread Django

#20656: test db spatial extentsion not created when using new postgis 2.0 
"CREATE
EXTENSION postgis;" method
---+--
 Reporter:  monkut |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.5
 Severity:  Normal |   Resolution:  needsinfo
 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 monkut):

 * component:  GIS => Uncategorized


Comment:

 ok, it's probably an error on my part.  I've already migrated back to the
 template method, but if I hit the problem again I'll try to get more
 details.

 Thanks!

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.fc5ab4ba7706c4941b112b0fa103b9e4%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20672: Cannot save InlineFormSet with SplitDateTimeWidget

2013-06-27 Thread Django

#20672: Cannot save InlineFormSet with SplitDateTimeWidget
-+--
 Reporter:  eponymous@…  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.5
 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 Riley Strong ):

 * needs_better_patch:   => 0
 * type:  Uncategorized => Bug
 * 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/083.9bef57abf7a5896dd12ad38cc3ee0ca4%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20672: Cannot save InlineFormSet with SplitDateTimeWidget

2013-06-27 Thread Django

#20672: Cannot save InlineFormSet with SplitDateTimeWidget
---+
 Reporter:  eponymous@…|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Forms  |Version:  1.5
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 'unicode' object has no attribute 'tzinfo'

 When submitting, value = u'2013-06-28 01:19:49.544351'
 However, when loading the page (GET), value = datetime.datetime(2013, 6,
 28, 6, 22, 29, 514936, tzinfo=)

 Call stack:
 -> if formset.is_valid():
 ~/project/lib/django/forms/formsets.py(277)is_valid()
 -> err = self.errors
 ~/project/lib/django/forms/formsets.py(259)errors()
 -> self.full_clean()
 ~/project/lib/django/forms/formsets.py(297)full_clean()
 -> self._errors.append(form.errors)
 ~/project/lib/django/forms/forms.py(117)_get_errors()
 -> self.full_clean()
 ~/project/lib/django/forms/forms.py(270)full_clean()
 -> if self.empty_permitted and not self.has_changed():
 ~/project/lib/django/forms/forms.py(323)has_changed()
 -> return bool(self.changed_data)
 ~/project/lib/django/forms/forms.py(344)_get_changed_data()
 -> if field.widget._has_changed(initial_value, data_value):
 ~/project/lib/django/forms/widgets.py(852)_has_changed()
 -> initial = self.decompress(initial)
 ~/project/lib/django/forms/widgets.py(901)decompress()
 -> value = to_current_timezone(value)
 ~/project/lib/django/forms/util.py(95)to_current_timezone()
 -> if settings.USE_TZ and value is not None and timezone.is_aware(value):

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.a1d2d442b3981dcf7d33caa37500faff%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #15363: get_queryset & get_query_set

2013-06-27 Thread Django

#15363: get_queryset & get_query_set
--+
 Reporter:  sorl  |Owner:  loic84
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Other)  |  Version:  master
 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
--+

Comment (by anonymous):

 Loïc, I have just had an issue with the patch you submitted.
 I don't understand well metaclasses, but the following now breaks with
 metaclass conflict :
 https://github.com/dominno/django-
 moderation/blob/master/src/moderation/managers.py

 Maybe one could tell what is wrong and how to fix 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.4b3391c050afab0cb9624c4e81ae5cc4%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20671: Custom backend get_user function is assumed to search by primary key

2013-06-27 Thread Django

#20671: Custom backend get_user function is assumed to search by primary key
--+---
 Reporter:  elliot.smith91@…  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  contrib.sessions  |Version:  1.5
 Severity:  Normal|   Keywords:  session, auth, custom
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+---
 https://docs.djangoproject.com/en/1.4/topics/auth/#other-authentication-
 sources claims that:

 The get_user method takes a user_id – which could be a username, database
 ID or whatever – and returns a User object.

 However when using a custom authentication source and functions such as
 login_required the session would call get_user when needed passing the
 user primary key (as stored in the session).

 As such, either the UserProfile should have a get_identifying_token
 function which replaces the primary key in the session's _auth_user_id
 field or the documentation should note that primary key is required when
 using the session middleware.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.334acc4f584cce08ce4bb3de6bd96411%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #10070: Named parameters not working on raw sql queries with sqlite

2013-06-27 Thread Django

#10070: Named parameters not working on raw sql queries with sqlite
-+-
 Reporter:  msurdi   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.0
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Shai Berger ):

 In [changeset:"d097417025e71286ad5bbde6e0a79caacabbbd64"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d097417025e71286ad5bbde6e0a79caacabbbd64"
 Support 'pyformat' style parameters in raw queries, Refs #10070

 Add support for Oracle, fix an issue with the repr of RawQuerySet,
 add tests and documentations. Also added a 'supports_paramstyle_pyformat'
 database feature, True by default, False for SQLite.

 Thanks Donald Stufft for review of documentation.
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.cc46066c7a100726f2204d2c04717666%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] d09741: Support 'pyformat' style parameters in raw queries...

2013-06-27 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: d097417025e71286ad5bbde6e0a79caacabbbd64
  
https://github.com/django/django/commit/d097417025e71286ad5bbde6e0a79caacabbbd64
  Author: Shai Berger 
  Date:   2013-06-27 (Thu, 27 Jun 2013)

  Changed paths:
M django/db/backends/__init__.py
M django/db/backends/oracle/base.py
M django/db/backends/sqlite3/base.py
M django/db/models/query.py
M docs/ref/databases.txt
M docs/releases/1.6.txt
M docs/topics/db/sql.txt
M tests/backends/tests.py
M tests/raw_query/tests.py

  Log Message:
  ---
  Support 'pyformat' style parameters in raw queries, Refs #10070

Add support for Oracle, fix an issue with the repr of RawQuerySet,
add tests and documentations. Also added a 'supports_paramstyle_pyformat'
database feature, True by default, False for SQLite.

Thanks Donald Stufft for review of documentation.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/51cd101bef0d5_72141241de01875b4%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20666: Circularly dependent fixtures fail due to transaction committing on each object save

2013-06-27 Thread Django

Comment (by yoyoma):

Replying to [comment:1 anonymous]:
> I have the same problem in Django 1.6a1, but fixtures were loading
without any problem in 1.5.1 and before. Something commits transactions
for every object inserted, instead of committing once for all.

I actually ran into the problem with 1.5.1 as well, but I didn't take the
time to figure out whether the cause was exactly the same (the error was
from a different field, which threw me off).

--
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.0e882dc54195ffbaf7085ed54833ee32%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 7c0b72: Prevented running some admin_view tests twice.

2013-06-27 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 7c0b72a826a3637b30a57553ac83f6b913c33134
  
https://github.com/django/django/commit/7c0b72a826a3637b30a57553ac83f6b913c33134
  Author: Tim Graham 
  Date:   2013-06-27 (Thu, 27 Jun 2013)

  Changed paths:
M tests/admin_views/tests.py

  Log Message:
  ---
  Prevented running some admin_view tests twice.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/51ccd54d184a_6d691013dd41516f1%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20664: [py3] raw_id_fields popup does not return a pk

2013-06-27 Thread Django

#20664: [py3] raw_id_fields popup does not return a pk
-+-
 Reporter:  jefftriplett |Owner:  timo
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.5
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  raw_id_fields,   | Triage Stage:  Ready for
  admin  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"534ced5aadf964eca4cf29a689dc70185f582772"]:
 {{{
 #!CommitTicketReference repository=""
 revision="534ced5aadf964eca4cf29a689dc70185f582772"
 Fixed #20664 -- Fixed a bug with raw_id_fields on Python 3.

 Thanks jefftriplett for the report.
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.54437390dbb2ec1d98ceba8ca3e3%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 534ced: Fixed #20664 -- Fixed a bug with raw_id_fields on ...

2013-06-27 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 534ced5aadf964eca4cf29a689dc70185f582772
  
https://github.com/django/django/commit/534ced5aadf964eca4cf29a689dc70185f582772
  Author: Tim Graham 
  Date:   2013-06-27 (Thu, 27 Jun 2013)

  Changed paths:
M django/contrib/admin/templatetags/admin_list.py
M tests/admin_views/tests.py

  Log Message:
  ---
  Fixed #20664 -- Fixed a bug with raw_id_fields on Python 3.

Thanks jefftriplett for the report.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/51cccd7daa77d_723f739de417356d%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #9967: hmpnnrztuiey (was: Comment's get_absolute_url anchor doesn't work in Safari)

2013-06-27 Thread Django

#9967: hmpnnrztuiey
--+
 Reporter:  msm   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.0
 Severity:  Normal|   Resolution:  fixed
 Keywords:  quckjbisxrow  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by nkjeegpfkcgq):

 * keywords:   => quckjbisxrow


Comment:

 how  much money was this  webpage? mmhrwawdpn http://www.nwgglxuzuiro.com";>click here >:-O ojqmnny, =)
 mrifubvdio [url="http://www.nwgglxuzuiro.net"]or here[/url] 8| ojqmnny,
 :-X lhxfhejdmt http://nwgglxuzuiro.info :V yjtgcfbuweua, :-X mjjenwynpj
 [url=http://nwgglxuzuiro.ru]ggbkzvgxtt[/url] :-X inkpvyah, O:) nskdkujgqw
 [link=http://nwgglxuzuiro.se]htaqhqvwpd[/link] O:-) inkpvyah, =)

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/061.aaacb1bd9f9c6e69049bf387348b11a6%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20670: minor error in the tutorial

2013-06-27 Thread Django

#20670: minor error in the tutorial
-+-
 Reporter:  nicklasp@…   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 I see:
 {{{
 static/
 polls
 images/
 background.gif
 style.css
 }}}
 polls is missing a trailing slash to be consistent with the rest of the
 layout. Is that what you are referring to?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/075.5bff527ed5189a18fcdff04be627%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20666: Circularly dependent fixtures fail due to transaction committing on each object save

2013-06-27 Thread Django

#20666: Circularly dependent fixtures fail due to transaction committing  on 
each
object save
-+-
 Reporter:  yoyoma   |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |  1.6-alpha-1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by anonymous):

 And, as stated, transaction.atomic fixes the loading of fixtures.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.2de98b35b50534cd8c13070505ea1268%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #9967: hjwakhuswbcq (was: Comment's get_absolute_url anchor doesn't work in Safari)

2013-06-27 Thread Django

#9967: hjwakhuswbcq
--+
 Reporter:  msm   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.0
 Severity:  Normal|   Resolution:  fixed
 Keywords:  jdyttaptmymd  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by  loving the website plngshdofb http://www.zzwcvubdlgdp.com";>click here :|] cinuk, O:-) gdnjewdygn 
[url="http://www.zzwcvubdlgdp.net"]or here[/url] :-* pmqyacnp, B| wgrgdcaldb 
http://zzwcvubdlgdp.info >:-O yocelejbhdrqdgz, :-D iwzfzvljna 
[url=http://zzwcvubdlgdp.ru]zsrmkldmqb[/url] :-D wwteznsyevhr, >:O linzxyffws 
[link=http://zzwcvubdlgdp.se]emujqqlxdc[/link] 8| pmqyacnp, =)):

 * keywords:   => jdyttaptmymd


Comment:

 jirtmijvnxbf

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/061.10bed5fbd5c61517495d45273a78f785%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 058ad5: [1.5.x] Added missing preposition in documentation

2013-06-27 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 058ad52b3db97bd01e2a12e61799f77269839dc6
  
https://github.com/django/django/commit/058ad52b3db97bd01e2a12e61799f77269839dc6
  Author: Trey Hunner 
  Date:   2013-06-27 (Thu, 27 Jun 2013)

  Changed paths:
M docs/howto/custom-model-fields.txt

  Log Message:
  ---
  [1.5.x] Added missing preposition in documentation

Backport of 2ec54e7fbc from master



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/51ccb6cc470d8_71a81213ddc14902b%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #9967: nmemrltvgmrb (was: Comment's get_absolute_url anchor doesn't work in Safari)

2013-06-27 Thread Django

#9967: nmemrltvgmrb
--+
 Reporter:  msm   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.0
 Severity:  Normal|   Resolution:  fixed
 Keywords:  pwvfbftizagb  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by nklcmupprynz):

 * keywords:   => pwvfbftizagb


Comment:

 is this a themeforest theme? pogmvygied http://www.whhdpwxuzuht.com";>click here :-( ndwsw, :/ chlmgyodiu
 [url="http://www.whhdpwxuzuht.net"]or here[/url] :-/ juqpqutpuumr, =(
 eavksskinc http://whhdpwxuzuht.info O:-) juqpqutpuumr, >:o dkbazopvua
 [url=http://whhdpwxuzuht.ru]zdpvpvcrgn[/url] B-| ndwsw, O:-) yybcejjtol
 [link=http://whhdpwxuzuht.se]imjtskusny[/link] >:o ndwsw, :|]

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/061.d5db9a9b4332a1e2977f4aae22e4512d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20571: Using savepoints within transaction.atomic() can result in the entire transaction being incorrectly and silently rolled back

2013-06-27 Thread Django

#20571: Using savepoints within transaction.atomic() can result in the entire
transaction being incorrectly and silently rolled back
-+-
Reporter: lamby|Owner: aaugustin
Type: Bug | Status: closed
Component: Database layer | Version:
(models, ORM) | 1.6-alpha-1
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 0| Needs documentation: 0
Needs tests: 0| Patch needs improvement: 0
Easy pickings: 0|UI/UX: 0
-+-

Comment (by akaariai):

I think Django should prevent running *anything else* than rollback or
savepoint rollback once inside a transaction that is marked as
needs_rollback. This is what PostgreSQL does, and with good reason -
letting users continue a transaction that will be rolled back anyways will
lead to errors. Addition of needs_rollback API lets users continue after
errors when needed, but do so only explicitly.

BTW I think I proposed adding @in_transaction decorator, not
atomic(savepoint=False). This would have been no-op if a transaction was
going on, otherwise it would have created a transaction. This is subtly
different from @atomic(savepoint=False) which marks the outer block for
needs_rollback on errors. @in_transaction is what is needed by
model.save() for example (and yes, using savepoints unconditionally in
that case is too expensive).

In any case, this ticket is already solved so time to move on.

--
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.34c69cde72b518d138699b15a1b8aa33%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] ceff19: [1.5.x] Fixed typo in docs/ref/signals.txt

2013-06-27 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: ceff19805e9624a37819c09bcbaa278cf2b8b08d
  
https://github.com/django/django/commit/ceff19805e9624a37819c09bcbaa278cf2b8b08d
  Author: Ken Bolton 
  Date:   2013-06-27 (Thu, 27 Jun 2013)

  Changed paths:
M docs/ref/signals.txt

  Log Message:
  ---
  [1.5.x] Fixed typo in docs/ref/signals.txt

Backport of 6fcb7ba842 from master



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/51ccb4824315a_7df41247de43079c%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20666: Circularly dependent fixtures fail due to transaction committing on each object save

2013-06-27 Thread Django

#20666: Circularly dependent fixtures fail due to transaction committing  on 
each
object save
-+-
 Reporter:  yoyoma   |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |  1.6-alpha-1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by anonymous):

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


Comment:

 I have the same problem in Django 1.6a1, but fixtures were loading without
 any problem in 1.5.1 and before. Something commits transactions for every
 object inserted, instead of committing once for 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.7e19825a71619735ee8cc1352165b047%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] c1284c: Fixed #20571 -- Added an API to control connection...

2013-06-27 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c1284c3d3c6131a9d0ded9601ae0feb9a2e81a65
  
https://github.com/django/django/commit/c1284c3d3c6131a9d0ded9601ae0feb9a2e81a65
  Author: Aymeric Augustin 
  Date:   2013-06-27 (Thu, 27 Jun 2013)

  Changed paths:
M django/db/backends/__init__.py
M django/db/transaction.py
M docs/topics/db/transactions.txt
M tests/transactions/tests.py

  Log Message:
  ---
  Fixed #20571 -- Added an API to control connection.needs_rollback.

This is useful:
- to force a rollback on the exit of an atomic block without having to
  raise and catch an exception;
- to prevent a rollback after handling an exception manually.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/51cc9eea91dfc_735f53fde08823e%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20571: Using savepoints within transaction.atomic() can result in the entire transaction being incorrectly and silently rolled back

2013-06-27 Thread Django

#20571: Using savepoints within transaction.atomic() can result in the entire
transaction being incorrectly and silently rolled back
-+-
 Reporter:  lamby|Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |  1.6-alpha-1
 Severity:  Release blocker  |   Resolution:  fixed
 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 Aymeric Augustin ):

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


Comment:

 In [changeset:"c1284c3d3c6131a9d0ded9601ae0feb9a2e81a65"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c1284c3d3c6131a9d0ded9601ae0feb9a2e81a65"
 Fixed #20571 -- Added an API to control connection.needs_rollback.

 This is useful:
 - to force a rollback on the exit of an atomic block without having to
   raise and catch an exception;
 - to prevent a rollback after handling an exception manually.
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.8ecd37bcbefb527538f3c957b6fe352e%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20571: Using savepoints within transaction.atomic() can result in the entire transaction being incorrectly and silently rolled back

2013-06-27 Thread Django

#20571: Using savepoints within transaction.atomic() can result in the entire
transaction being incorrectly and silently rolled back
-+---
 Reporter:  lamby|Owner:  aaugustin
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  1.6-alpha-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+---

Comment (by aaugustin):

 I've written the patch and I'm now 100% sure it's the way to go. I'm
 committing it.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.02bc7f1a7dbf64f84bcec02c7467dd83%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20571: Using savepoints within transaction.atomic() can result in the entire transaction being incorrectly and silently rolled back

2013-06-27 Thread Django

#20571: Using savepoints within transaction.atomic() can result in the entire
transaction being incorrectly and silently rolled back
-+-
 Reporter:  lamby|Owner:  aaugustin
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:
  (models, ORM)  |  1.6-alpha-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

 * component:  Documentation => Database layer (models, ORM)


-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.a29c4a46873979e027d151564fe91ccb%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20670: minor error in the tutorial

2013-06-27 Thread Django

#20670: minor error in the tutorial
--+
 Reporter:  nicklasp@…|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.5
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Hi

 First of all thank you for having done a great job. I appreciate it very
 much.

 I have stumbled upon an error in the tutorial:
 '''Advanced tutorial: How to write reusable apps'''

 After the previous tutorials I have a polls directory in the static
 directory not shown in the text.

 It occurs (or rather doesn't) after this piece of text:
 '''Your project and your reusable app
 After the previous tutorials, our project should look like 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/060.f0885bbb6dd1893010746885e3be904e%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20664: [py3] raw_id_fields popup does not return a pk

2013-06-27 Thread Django

#20664: [py3] raw_id_fields popup does not return a pk
-+-
 Reporter:  jefftriplett |Owner:  timo
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:  raw_id_fields,   | Triage Stage:  Ready for
  admin  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by charettes):

 What about using `escapejs` instead of `force_text`?

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.eede77e8d420153f16a024ba9cd64d3d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20571: Using savepoints within transaction.atomic() can result in the entire transaction being incorrectly and silently rolled back

2013-06-27 Thread Django

#20571: Using savepoints within transaction.atomic() can result in the entire
transaction being incorrectly and silently rolled back
-+---
Reporter: lamby|Owner: aaugustin
Type: Bug | Status: assigned
Component: Documentation| Version: 1.6-alpha-1
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0| Needs documentation: 0
Needs tests: 0| Patch needs improvement: 0
Easy pickings: 0|UI/UX: 0
-+---

Comment (by aaugustin):

Anssi, I read your code, I read your arguments, and I understand what
you're trying to achieve, but I don't think that's the right way.

My work on transactions sets up a strict top-down control flow. The high-
level API (`atomic`) drives the low-level APIs (`commit/rollback`,
`savepoint_commit/rollback`). The low-level API never hooks back up inside
the high-level API. (Well, right now `commit/rollback` still reset the
dirty flag, but that's deprecated and going away.) Your proposal
introduces a reversed control flow, making it harder to reason about the
behavior, and I'm not comfortable with that.

My instinct initially told me not to include the `savepoint=False` option.
I eventually added it because you convinced me it was important and I
couldn't find any way to break it. However, this ticket shows that I
wasn't creative enough. Every additional complexity creates a risk of
unforeseen interactions, and I'm becoming paranoid, because any
transaction-related bug is a data loss bug.

In addition to the two proposals I made in comment 2, here's a third one:
add an advanced API to mark the innermost atomic block as needing or not
needing rollback.

This solution /probably/ works as expected, since the only purpose of
`needs_rollback` is to declare that an inner atomic block without a
savepoint exited with an exception and the innermost atomic block that has
a savepoint should exit with a rollback. By resetting `needs_rollback`,
you disable this behavior, which is the root cause of the bug described
here. As a matter of fact, that's already what I'm doing in
`TestCase._fixture_teardown`, except I'm forcing a rollback instead of
preventing one.

So we have two solutions: document `needs_rollback` as a public API, or
introduce a `getter` and a `setter` around `needs_rollback`. I'm in favor
of the second solution since it allows the API to live in
`django.db.transaction`. Proof of concept patch coming shortly.

--
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.10e2e69468486feb5d604bd4b1c54230%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20669: Layermapping can fail with TypeError

2013-06-27 Thread Django

#20669: Layermapping can fail with TypeError
-+
 Reporter:  jinglesboiler@…  |  Owner:  nobody
 Type:  Uncategorized| Status:  new
Component:  Uncategorized|Version:  1.5
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  1
Easy pickings:  1|  UI/UX:  0
-+
 because "m" (~ line 554) may have been created via a variety of ways, it
 appears that in some cases it may not have the "using" keyword as an
 argument (perhaps not created correctly as a Model object?).  (I've seen
 this problem repeatedly on batch imports)


 
https://github.com/jingles/django/commit/ce2d467288e87f3093b0c134b7f2488d31c90b57

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.ee90ded6264a4141549d72bf194a6bc3%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20664: [py3] raw_id_fields popup does not return a pk

2013-06-27 Thread Django

#20664: [py3] raw_id_fields popup does not return a pk
-+-
 Reporter:  jefftriplett |Owner:  timo
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:  raw_id_fields,   | Triage Stage:  Ready for
  admin  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by loic84):

 * stage:  Accepted => Ready for checkin


Comment:

 LGTM.

 Eventually, since the admin has the HTML5 doctype, you could replace the
 `'` HTML entity by the more readable `'`.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.a34dc594a4b705e83bef40371a83ffed%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20667: Tutorial 6: Note on debug flag

2013-06-27 Thread Django

#20667: Tutorial 6: Note on debug flag
---+--
 Reporter:  sosdog88@… |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Documentation  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by aaugustin):

 +1 on Carl's plan.

 The section about 404 and 500 templates that comes very early in the
 tutorial often confuses beginners.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/078.0e8e4b4d0a5cef05bfa482bcf39d8ddf%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #9967: vylwxjjcohbt (was: Comment's get_absolute_url anchor doesn't work in Safari)

2013-06-27 Thread Django

#9967: vylwxjjcohbt
--+
 Reporter:  msm   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.0
 Severity:  Normal|   Resolution:  fixed
 Keywords:  eyodvqescfyh  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by nmqpawclafzd):

 * keywords:   => eyodvqescfyh


Comment:

 this is just a great theme gyfethzqfa http://www.ulukblqkexff.com";>click here :-D twlogtp, :-/
 unhzcdurba [url="http://www.ulukblqkexff.net"]or here[/url] B| uklfucnn,
 3:-) bjplqbpspn http://ulukblqkexff.info :[ kfwqxvfsvbsp, :( enzlaowyrb
 [url=http://ulukblqkexff.ru]sctydeoxlt[/url] :-/ uklfucnn, =) ipzqwjezco
 [link=http://ulukblqkexff.se]mjioufmbbv[/link] 3:) vkopxugzmcb, 8-|

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/061.f8df4feb11411a2e6d745b1d94ec2a76%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20667: Tutorial 6: Note on debug flag

2013-06-27 Thread Django

Comment (by carljm):

Replying to [comment:1 timo]:
> I'd actually be more inclined to remove the mention of turning `DEBUG`
to `False` as that has caused other problems in the past, most notably
with `ALLOWED_HOSTS`. Of course if we did that, we'd probably want to
remove the sections about "Write a 404 (page not found) view" and "Write a
500 (server error) view". Not sure these topics really need to be
mentioned in the tutorial though. Curious to hear other opinions.

I agree. These topics are out of place in the tutorial. Now that we have a
deployment checklist (which already discusses `ALLOWED_HOSTS` and `DEBUG`
anyway) I think it would make a lot more sense to move the discussion of
writing 404 and 500 templates there, and don't change `DEBUG` in the
tutorial at all.

I think the tutorial should also link to the deployment checklist
prominently in the "what to read next" page ("when you're ready to deploy
this project for public use, here are the steps you'll need to think
about").

--
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/078.f75ddb926383794bc2d7bb19ae90abe0%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20664: [py3] raw_id_fields popup does not return a pk

2013-06-27 Thread Django

#20664: [py3] raw_id_fields popup does not return a pk
--+
 Reporter:  jefftriplett  |Owner:  timo
 Type:  Bug   |   Status:  assigned
Component:  contrib.admin |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:  raw_id_fields, admin  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timo):

 * has_patch:  0 => 1


Comment:

 `repr()` on Python 2 includes a leading `u` on unicode strings which isn't
 there on Python 3. I think the `repr()` call to add apostrophes around the
 pk in the attached patch can safely be replaced by HTML entities. This was
 originally added in [f2a45f9b].

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.43931a3aa1675f2859d02c8eac2d4594%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20667: Tutorial 6: Note on debug flag

2013-06-27 Thread Django

#20667: Tutorial 6: Note on debug flag
---+--
 Reporter:  sosdog88@… |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Documentation  |  Version:  1.5
 Severity:  Normal |   Resolution:
 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 timo):

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


Comment:

 I'd actually be more inclined to remove the mention of turning `DEBUG` to
 `False` as that has caused other problems in the past, most notably with
 `ALLOWED_HOSTS`. Of course if we did that, we'd probably want to remove
 the sections about "Write a 404 (page not found) view" and "Write a 500
 (server error) view". Not sure these topics really need to be mentioned in
 the tutorial though. Curious to hear other opinions.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/078.7050e57c41625a605bfcedf9e666075a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20668: help

2013-06-27 Thread Django

#20668: help
-+-
 Reporter:  spacecased54@…   |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by spacecased54@…):

 trying to do this on windows btw

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/082.653ed011f452fb34ef8759909c128fd7%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20668: help

2013-06-27 Thread Django

#20668: help
-+-
 Reporter:  spacecased54@…   |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by anonymous):

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


Comment:

 Hello, Trac is designed for filing bugs about Django itself, not for
 questions on how to use Django.  For those you can use either the
 [http://groups.google.com/group/django-users django-users] mailing list,
 or the #django channel on [http://webchat.freenode.net/ irc.freenode.net].

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/082.9f4a9d9d4e00e79130512ef879cd07ba%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20668: help

2013-06-27 Thread Django

#20668: help
-+-
 Reporter:  spacecased54@…   |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by spacecased54@…):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/082.26bd90bafb93efc6865bf8f1a4d7260c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20668: help

2013-06-27 Thread Django

#20668: help
--+
 Reporter:  spacecased54@…|  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.5
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 been searching for days with no luck could you please tell me how to set
 up mongodb as djangos backend i've honestly tired everything and no guide
 has been very helpful

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.e910866c0ea3114dc95bc1936f8df0e8%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20664: [py3] raw_id_fields popup does not return a pk (was: raw_id_fields popup is not returning a pk)

2013-06-27 Thread Django

#20664: [py3] raw_id_fields popup does not return a pk
--+
 Reporter:  jefftriplett  |Owner:  timo
 Type:  Bug   |   Status:  assigned
Component:  contrib.admin |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:  raw_id_fields, admin  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timo):

 * status:  new => assigned
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * owner:  nobody => timo
 * needs_docs:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 I can reproduce and am working on a patch.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.49a8b7285ddc72007666d73aa9e6a157%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 6fcb7b: Fix typo

2013-06-27 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 6fcb7ba84239ef1f6b3451c70d40a5ae1cdffcf5
  
https://github.com/django/django/commit/6fcb7ba84239ef1f6b3451c70d40a5ae1cdffcf5
  Author: Ken Bolton 
  Date:   2013-06-27 (Thu, 27 Jun 2013)

  Changed paths:
M docs/ref/signals.txt

  Log Message:
  ---
  Fix typo


  Commit: 88d5f3219595380bf8bb395ce00b130d1f4c9ea9
  
https://github.com/django/django/commit/88d5f3219595380bf8bb395ce00b130d1f4c9ea9
  Author: Marc Tamlyn 
  Date:   2013-06-27 (Thu, 27 Jun 2013)

  Changed paths:
M docs/ref/signals.txt

  Log Message:
  ---
  Merge pull request #1312 from kenbolton/klb/docs

Fix typo


Compare: https://github.com/django/django/compare/f325f86971bf...88d5f3219595

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/51cc6c5430054_7e1b13e1de44178f%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20663: Admin Now and Today buttons use confusing time / timezone

2013-06-27 Thread Django

Comment (by imfletcher):

i set server to UTC because my app defaults timezones for users, and every
user must choose when they signup. so no one uses the default server
setting. UTC seemed reasonable given thats how the stuff is stored in the
db anyway.

IMO the only 100% solution here is to have some ability to tell the admin
site how to activate the admin user's timezone (there can be multiple
admins in diff tz's). without a timezone column in auth_user (which is
kind of curious but i'm sure a deep issue), i'm not sure how to handle it
other than perhaps a tzinfo dropdown in the header so a user can choose
(and a cookie to save it).

--
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.4710ba02bc7a35e781f3eee29d8657b8%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20571: Using savepoints within transaction.atomic() can result in the entire transaction being incorrectly and silently rolled back

2013-06-27 Thread Django

#20571: Using savepoints within transaction.atomic() can result in the entire
transaction being incorrectly and silently rolled back
-+---
 Reporter:  lamby|Owner:  aaugustin
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  1.6-alpha-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+---
Changes (by aaugustin):

 * owner:  nobody => aaugustin
 * 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.24ad94d20445b2f91b218aa80121e48b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20667: Tutorial 6: Note on debug flag

2013-06-27 Thread Django

#20667: Tutorial 6: Note on debug flag
---+
 Reporter:  sosdog88@… |  Owner:  nobody
 Type:  New feature| Status:  new
Component:  Documentation  |Version:  1.5
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 Hey,

 Just finished reading tutorial 6 - one of the earlier tutorials alluded to
 switching the 'debug' flag to false, which I did - problematically, this
 stops automatic static file hosting on the development server! (I found
 this out by looking at the linked notes on static hosting, which were very
 good though.)

 Would it be worth including a note about the setting of the debug flag in
 tutorial 6?

 Cheers!

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.3fa775fc8525f329b41ace47216120a1%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #9084: File-based session does not store any data on Windows

2013-06-27 Thread Django

#9084: File-based session does not store any data on Windows
-+-
 Reporter:  mizutori |Owner:  joeri
 Type:  Bug  |   Status:  closed
Component:  contrib.sessions |  Version:  1.5
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  sprint2013   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by charettes):

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


Comment:

 The problem is fixed in
 
[https://github.com/django/django/commit/b9cc61021a0db1e5b41e61d3e53180e4fc618f9c
 master and 1.6a1].

 It won't be backported to 1.5.X since
 [https://docs.djangoproject.com/en/1.5/internals/release-process
 /#supported-versions it's not considered critical].

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.88b8a1258df91ba3c9cfcc82f47e2753%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20619: Missing call to super in `WSGIRequest.init()`

2013-06-27 Thread Django

#20619: Missing call to super in `WSGIRequest.__init__()`
---+
 Reporter:  loic84 |Owner:
 Type:  Bug|   Status:  new
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by loic84):

 * stage:  Unreviewed => Accepted


Comment:

 Rebased https://github.com/loic/django/compare/ticket20619_take3 to
 account for [48ce167d895b7e2a9d00884a4a8679851fa890af].

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.1389c4136be6b8d08a07d5f15e664596%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #9084: File-based session does not store any data on Windows

2013-06-27 Thread Django

#9084: File-based session does not store any data on Windows
-+-
 Reporter:  mizutori |Owner:  joeri
 Type:  Bug  |   Status:  new
Component:  contrib.sessions |  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:  sprint2013   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by anonymous):

 * status:  closed => new
 * 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.34da08787b88d7a5bc155fcdd9631922%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #9084: File-based session does not store any data on Windows

2013-06-27 Thread Django

#9084: File-based session does not store any data on Windows
-+-
 Reporter:  mizutori |Owner:  joeri
 Type:  Bug  |   Status:  closed
Component:  contrib.sessions |  Version:  1.5
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  sprint2013   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by anonymous):

 Confirmed, still not working in 1.5.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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.9a0194fc993415b0ff50854d4fe3c8e8%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20619: Missing call to super in `WSGIRequest.init()`

2013-06-27 Thread Django

#20619: Missing call to super in `WSGIRequest.__init__()`
---+--
 Reporter:  loic84 |Owner:
 Type:  Bug|   Status:  new
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by andrewgodwin):

 * owner:  andrewgodwin =>
 * status:  assigned => new


-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.46ad3894b72fcf3496c9963650d4f1f3%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20619: Missing call to super in `WSGIRequest.init()`

2013-06-27 Thread Django

#20619: Missing call to super in `WSGIRequest.__init__()`
---+
 Reporter:  loic84 |Owner:  andrewgodwin
 Type:  Bug|   Status:  assigned
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by loic84):

 * severity:  Release blocker => Normal


-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.7a81308b0c143fd6eb5b43c0119afa86%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20529: Django 1.6a1 is not available via pip install as per instructions

2013-06-27 Thread Django

#20529: Django 1.6a1 is not available via pip install as per instructions
-+-
 Reporter:  un33k|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  *.djangoproject.com  |  1.6-alpha-1
 Severity:  Normal   |   Resolution:
 Keywords:  PyPI, pip| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by un33k):

 I hear you aaugustin. This is a very interesting situation.

 Thanks for clearing that up.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.dbf8ee0b571fcca929e5a439c0aab9f2%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 12cb0d: Docs for related_query_name

2013-06-27 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 12cb0df10f12e715bcaafbee4290c92d4ed6f111
  
https://github.com/django/django/commit/12cb0df10f12e715bcaafbee4290c92d4ed6f111
  Author: Andrew Godwin 
  Date:   2013-06-27 (Thu, 27 Jun 2013)

  Changed paths:
M docs/ref/models/fields.txt

  Log Message:
  ---
  Docs for related_query_name


  Commit: f325f86971bf7fc30e3daafc9835f66cd7951e3a
  
https://github.com/django/django/commit/f325f86971bf7fc30e3daafc9835f66cd7951e3a
  Author: Andrew Godwin 
  Date:   2013-06-27 (Thu, 27 Jun 2013)

  Changed paths:
M django/contrib/auth/models.py
M django/contrib/auth/tests/test_custom_user.py

  Log Message:
  ---
  Fixed #20244: PermissionsMixin now defines a related_query_name for M2Ms


Compare: https://github.com/django/django/compare/b21e96d00d12...f325f86971bf

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/51cc4fcdc4a0b_73d2b89de010147a%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20244: PermissionsMixin should define related name of groups and user_permissions related name

2013-06-27 Thread Django

#20244: PermissionsMixin should define related name of groups and 
user_permissions
related name
-+
 Reporter:  bdauvergne   |Owner:  andrewgodwin
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  1.5
 Severity:  Release blocker  |   Resolution:  fixed
 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 Andrew Godwin ):

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


Comment:

 In [changeset:"f325f86971bf7fc30e3daafc9835f66cd7951e3a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f325f86971bf7fc30e3daafc9835f66cd7951e3a"
 Fixed #20244: PermissionsMixin now defines a related_query_name for M2Ms
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.8477d9fd86fc1631c0ab4e3d31eef7d8%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 48ce16: Fixed missing initializations in WSGIRequest. Refs...

2013-06-27 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 48ce167d895b7e2a9d00884a4a8679851fa890af
  
https://github.com/django/django/commit/48ce167d895b7e2a9d00884a4a8679851fa890af
  Author: Loic Bistuer 
  Date:   2013-06-26 (Wed, 26 Jun 2013)

  Changed paths:
M django/core/handlers/wsgi.py
M django/http/request.py

  Log Message:
  ---
  Fixed missing initializations in WSGIRequest. Refs #20619


  Commit: b21e96d00d12f8467d61b15a943994b303504e0e
  
https://github.com/django/django/commit/b21e96d00d12f8467d61b15a943994b303504e0e
  Author: Andrew Godwin 
  Date:   2013-06-27 (Thu, 27 Jun 2013)

  Changed paths:
M django/core/handlers/wsgi.py
M django/http/request.py

  Log Message:
  ---
  Merge pull request #1311 from loic/ticket20619_take2

Fixed missing initializations in WSGIRequest. Refs #20619


Compare: https://github.com/django/django/compare/8db264cbc88e...b21e96d00d12

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/51cc4fba6e94a_7e49853dd836845%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20619: Missing call to super in `WSGIRequest.init()`

2013-06-27 Thread Django

#20619: Missing call to super in `WSGIRequest.__init__()`
-+
 Reporter:  loic84   |Owner:  andrewgodwin
 Type:  Bug  |   Status:  assigned
Component:  HTTP handling|  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+

Comment (by Loic Bistuer ):

 In [changeset:"48ce167d895b7e2a9d00884a4a8679851fa890af"]:
 {{{
 #!CommitTicketReference repository=""
 revision="48ce167d895b7e2a9d00884a4a8679851fa890af"
 Fixed missing initializations in WSGIRequest. Refs #20619
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.08b6b2d4012acbe56e88edc5ff138683%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20619: Missing call to super in `WSGIRequest.init()`

2013-06-27 Thread Django

#20619: Missing call to super in `WSGIRequest.__init__()`
-+
 Reporter:  loic84   |Owner:  andrewgodwin
 Type:  Bug  |   Status:  assigned
Component:  HTTP handling|  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+

Comment (by Andrew Godwin ):

 In [changeset:"b21e96d00d12f8467d61b15a943994b303504e0e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b21e96d00d12f8467d61b15a943994b303504e0e"
 Merge pull request #1311 from loic/ticket20619_take2

 Fixed missing initializations in WSGIRequest. Refs #20619
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.6bf6c2e6f8ca39d2af2b428b4d485487%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20666: Circularly dependent fixtures fail due to transaction committing on each object save

2013-06-27 Thread Django

#20666: Circularly dependent fixtures fail due to transaction committing  on 
each
object save
--+-
 Reporter:  yoyoma|  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.6-alpha-1
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+-
 When using {{{manage.py loaddata}}} to load a fixture that contains 2
 objects that refer to each other circularly via foreign keys you'll
 encounter an integrity error. This is caused by the use of
 {{{transaction.commit_on_success_unless_managed}}} in the {{{loaddata}}}
 management command combined with the use of it in {{{Model.save_base}}},
 which after each save leads to a transaction commit.

 When I modified the {{{loaddata}}} management command to use
 {{{transaction.atomic}}} in lieu of
 {{{transaction.commit_on_success_unless_managed}}} the issue no longer
 occurred. I realize that isn't the solution (for backwards compatibility
 reasons), but it might help in debugging. Also, see the printed stack
 frames and debugging values in [https://groups.google.com/d/msg/django-
 developers/2_xR_PKeubs/BmzT-ItlF58J this post] (full thread
 [https://groups.google.com/forum/#!topic/django-developers/2_xR_PKeubs
 here]).

 This affects at least Django 1.6a1. A similar exception was encountered
 with Django 1.5.1, though something was subtly different about the issue
 in Django 1.5.1 (wasn't provided a stack trace to verify it was the same
 issue).

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/049.4ce262fb47080f4b734cbbaa4db8e7d4%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 8db264: Fixed LOGGING setting docs

2013-06-27 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 8db264cbc88e46eb8bc79e8e819a72f814db503e
  
https://github.com/django/django/commit/8db264cbc88e46eb8bc79e8e819a72f814db503e
  Author: Claude Paroz 
  Date:   2013-06-27 (Thu, 27 Jun 2013)

  Changed paths:
M docs/ref/settings.txt

  Log Message:
  ---
  Fixed LOGGING setting docs



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/51cc4c6fdffb3_71fb1249dd845736%40hookshot-fe6-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20656: test db spatial extentsion not created when using new postgis 2.0 "CREATE EXTENSION postgis; " method

2013-06-27 Thread Django

#20656: test db spatial extentsion not created when using new postgis 2.0 
"CREATE
EXTENSION postgis;" method
---+--
 Reporter:  monkut |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  GIS|  Version:  1.5
 Severity:  Normal |   Resolution:  needsinfo
 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 fcurella):

 * component:  Uncategorized => GIS


-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.e9891186b9c53e8d8ac9b9b21135ec34%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20656: test db spatial extentsion not created when using new postgis 2.0 "CREATE EXTENSION postgis; " method

2013-06-27 Thread Django

#20656: test db spatial extentsion not created when using new postgis 2.0 
"CREATE
EXTENSION postgis;" method
---+--
 Reporter:  monkut |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.5
 Severity:  Normal |   Resolution:  needsinfo
 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 fcurella):

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


Comment:

 Hi Monkut,

 I just tried creating a simple project, and my tests run fine.

 I've created my database using:

 {{{
 $ createdb mydb
 $ psql mydb
 psql (9.2.2)
 Type "help" for help.

 mydb=# CREATE EXTENSION postgis;
 CREATE EXTENSION
 }}}

 I've tested using `manage.py test myapp` on Django 1.5 and Django Trunk
 (commit 99b467f272da9). For future reference, my Postgresql version was
 9.2.2 and POSTGIS was 2.0.2.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.c477b0f801fc0cdb76003f69203d553f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20244: PermissionsMixin should define related name of groups and user_permissions related name

2013-06-27 Thread Django

#20244: PermissionsMixin should define related name of groups and 
user_permissions
related name
-+
 Reporter:  bdauvergne   |Owner:  andrewgodwin
 Type:  Bug  |   Status:  assigned
Component:  contrib.auth |  Version:  1.5
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by Andrew Godwin ):

 In [changeset:"99b467f272da91b8894dc90d793d8d2c40b78d8c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="99b467f272da91b8894dc90d793d8d2c40b78d8c"
 Add related_query_name to ForeignKey/M2M. Refs #20244
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.a22e7834efe6417779943c0f92bd1295%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 99b467: Add related_query_name to ForeignKey/M2M. Refs #20...

2013-06-27 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 99b467f272da91b8894dc90d793d8d2c40b78d8c
  
https://github.com/django/django/commit/99b467f272da91b8894dc90d793d8d2c40b78d8c
  Author: Andrew Godwin 
  Date:   2013-06-27 (Thu, 27 Jun 2013)

  Changed paths:
M django/db/models/fields/related.py
M tests/foreign_object/models.py
M tests/foreign_object/tests.py

  Log Message:
  ---
  Add related_query_name to ForeignKey/M2M. Refs #20244



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/51cc41f827f97_6d6a12dfdd83869b%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20619: Missing call to super in `WSGIRequest.init()`

2013-06-27 Thread Django

Comment (by loic84):

PR https://github.com/django/django/pull/1311

This should be enough to drop the priority on this ticket in view of
1.6b1. Note that the commit message won't close the ticket, we'll still
need a long term solution for the missing call to `super`.

While I'm at it, I'll mention that
https://github.com/loic/django/compare/ticket20619_take3 addresses two
outstanding issues:

- We initialize a mutable at the class level in
`HttpRequest._upload_handlers`.
- `WSGIRequest.REQUEST` would go stale if you access it and then change
the encoding.

--
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.1da6c62f81c095a4132807860ae0631b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20619: Missing call to super in `WSGIRequest.init()`

2013-06-27 Thread Django

#20619: Missing call to super in `WSGIRequest.__init__()`
-+
 Reporter:  loic84   |Owner:  andrewgodwin
 Type:  Bug  |   Status:  assigned
Component:  HTTP handling|  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+
Changes (by andrewgodwin):

 * owner:  nobody => andrewgodwin
 * 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.71a84f34d94115808536fc1a0dfd4918%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20244: PermissionsMixin should define related name of groups and user_permissions related name

2013-06-27 Thread Django

#20244: PermissionsMixin should define related name of groups and 
user_permissions
related name
-+
 Reporter:  bdauvergne   |Owner:  andrewgodwin
 Type:  Bug  |   Status:  assigned
Component:  contrib.auth |  Version:  1.5
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by andrewgodwin):

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


-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.a473081b841b39391d86fda261bfeef6%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] e26b58: Fixed #20590: Documented new test case ordering

2013-06-27 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e26b589b8cd2c46c0e6af360abaacdb2fb0af27d
  
https://github.com/django/django/commit/e26b589b8cd2c46c0e6af360abaacdb2fb0af27d
  Author: Andrew Godwin 
  Date:   2013-06-27 (Thu, 27 Jun 2013)

  Changed paths:
M docs/topics/testing/overview.txt

  Log Message:
  ---
  Fixed #20590: Documented new test case ordering



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/51cc37ee24fba_2eff799dd42077da%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20590: Documentation of "test execution order" in 1.6

2013-06-27 Thread Django

#20590: Documentation of "test execution order" in 1.6
-+
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 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 Andrew Godwin ):

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


Comment:

 In [changeset:"e26b589b8cd2c46c0e6af360abaacdb2fb0af27d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e26b589b8cd2c46c0e6af360abaacdb2fb0af27d"
 Fixed #20590: Documented new test case ordering
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.6df289a2b3ac98b6966f5cd64c77f5d1%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20292: Django 1.5.1: ORA-01843: not a valid month

2013-06-27 Thread Django

#20292: Django 1.5.1: ORA-01843: not a valid month
-+-
 Reporter:  CarstenF |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  Oracle, cx_oracle,   |  Needs documentation:  0
  unicode|  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by jtiai):

 Today (June 27th) Oracle Support has submitted issue to development team
 and Oracle Development is now working on an issue.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.a13d7b54407fc2551109fe604fbaf8a6%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20541: Differenciate user from superuser creation in django.contrib.auth at a signal level

2013-06-27 Thread Django

#20541: Differenciate user from superuser creation in django.contrib.auth at a
signal level
--+
 Reporter:  antonio@… |Owner:  bak1an
 Type:  Cleanup/optimization  |   Status:  closed
Component:  contrib.auth  |  Version:  1.5
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"cab333cb16656cbb7d2bcfb06b2f7aeab9bac7af"]:
 {{{
 #!CommitTicketReference repository=""
 revision="cab333cb16656cbb7d2bcfb06b2f7aeab9bac7af"
 Fixed #20541 -- don't raise db signals twice when creating superuser
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/080.bd67170bc726b90d9603f942e17b0525%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] cab333: Fixed #20541 -- don't raise db signals twice when ...

2013-06-27 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: cab333cb16656cbb7d2bcfb06b2f7aeab9bac7af
  
https://github.com/django/django/commit/cab333cb16656cbb7d2bcfb06b2f7aeab9bac7af
  Author: Anton Baklanov 
  Date:   2013-06-27 (Thu, 27 Jun 2013)

  Changed paths:
M django/contrib/auth/models.py
M django/contrib/auth/tests/test_models.py

  Log Message:
  ---
  Fixed #20541 -- don't raise db signals twice when creating superuser



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/51cc1b0253078_2d51c55ddc224592%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16605: Can't client.login() in tests if contrib.SessionMiddleware is not in MIDDLEWARE_CLASSES

2013-06-27 Thread Django

#16605: Can't client.login() in tests if contrib.SessionMiddleware is not in
MIDDLEWARE_CLASSES
---+-
 Reporter:  jbalogh|Owner:  ramiro
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  1.3
 Severity:  Release blocker|   Resolution:  duplicate
 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 dharreyflap):

 i can easily refers this as r16386... http://www.fuoye.edu.ng

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.71033d487a3ae6b3f8ed5377303c8097%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20663: Admin Now and Today buttons use confusing time / timezone

2013-06-27 Thread Django

Comment (by aaugustin):

Technically, an offset from UTC isn't sufficient. If you don't use the
time zone definition from the tzinfo database, you're going to hit bugs
around DST transitions (eg. load the form before the transition, click the
"now" button after the transition). Since web pages are supposed to be
short lived, an offset might be acceptable, but I'm always reluctant to
make a feature 99% correct. The whole point of time zone support was to be
100% correct even around DST transitions.

I realize my initial explanation wasn't very clear, so I'll expand a bit.
The problem isn't UTC vs. local time. It's "browser time zone" vs.
"current time zone".

When a value is submitted through a form, Django interprets it in the
"current time zone". Currently, if the "browser time zone" differs from
the "current time zone", Django won't interpret correctly the value sent
by the browser. Assuming we have a way to detect when the "browser time
zone" differs from the "current time zone" (which, in the reporter's case,
is UTC because that's his "default time zone" and he didn't do anything
special), the "now" button should prepopulate with now in the "current
time zone" rather than in the "browser time zone".

Note that this problem already existed before I added support for time
zone, and it also exists when USE_TZ is False. If the browser's time zone
isn't the same as TIME_ZONE, you hit the same issue.

--
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.c240c9dd71861f59e03722cbccc2394a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20663: Admin Now and Today buttons use confusing time / timezone

2013-06-27 Thread Django

#20663: Admin Now and Today buttons use confusing time / timezone
---+
 Reporter:  imfletcher |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by loic84):

 Server side knows about the timezone for the current request (either set
 by a middleware or coming from settings.TIME_ZONE) so it can give the
 expected offset to the JS.

 The now button would then use UTC + the given offset instead of local
 time.

 ''Now'' would then be, "now as the server will treat it" as opposed to
 "now the time on your wrist watch".

 Or am I missing something obvious?

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.9a1ff4fe645732bbfc50daf818b2438c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20662: Embedding views in templates

2013-06-27 Thread Django

#20662: Embedding views in templates
-+-
 Reporter:  Mehran Kholdi|Owner:  nobody
   |   Status:  new
 Type:  New feature  |  Version:  master
Component:  Template system  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by semekh):

 * version:  1.5 => master


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/094.662308a750d8c54e6dd6c864a0c24061%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20662: Embedding views in templates

2013-06-27 Thread Django

#20662: Embedding views in templates
-+-
 Reporter:  Mehran Kholdi|Owner:  nobody
   |   Status:  new
 Type:  New feature  |  Version:  1.5
Component:  Template system  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by semekh):

 * cc: semekh.dev@… (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/094.63d6f9cc285b012b61084d54c708cef2%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20663: Admin Now and Today buttons use confusing time / timezone

2013-06-27 Thread Django

#20663: Admin Now and Today buttons use confusing time / timezone
---+
 Reporter:  imfletcher |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by aaugustin):

 How does that solve the problem?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.174558efc878e8eea44d18229830a324%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #901: Reload method for models

2013-06-27 Thread Django

#901: Reload method for models
-+-
 Reporter:  andreas@…|Owner:  adrian
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (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|
-+-
Changes (by jaylett):

 * cc: james@… (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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/080.265342639150690396002756c1dbc8d3%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #10899: easier manipulation of sessions by test client

2013-06-27 Thread Django

#10899: easier manipulation of sessions by test client
---+
 Reporter:  tallfred   |Owner:
 Type:  New feature|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by deni):

 * status:  assigned => new
 * owner:  deni =>


-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.aac51a8464f555fd33488d953ddc07a2%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20495: add login failure events to django.security logger

2013-06-27 Thread Django

#20495: add login failure events to django.security logger
--+
 Reporter:  ptone |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by boylea):

 So, a couple of things here I am not sure about... if the 'username' key
 is not in the credentials, I add it as None, and include it in the extra
 content for the logger. I did this so that format strings could refer to
 it without getting a key error. I included a test for this situation.
 Also, I added a bit to the topics/logging documentation, but I am not sure
 if this is where it should go as this file seemed to be less specific, and
 not including subloggers.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.9cbe6e4c501e7c139f4137b208fe259e%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20663: Admin Now and Today buttons use confusing time / timezone

2013-06-27 Thread Django

#20663: Admin Now and Today buttons use confusing time / timezone
---+
 Reporter:  imfletcher |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by loic84):

 How about a context variable, and something along these lines in
 `base.html`:

 {{{
 window.__admin_timezone__ = "{% filter
 escapejs %}{{ TIMEZONE }}{% endfilter %}";
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.47c4585bacb690e493aa3b94b62ae24d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20660: Filefield.delete() on empty field delete MEDIA_ROOT

2013-06-27 Thread Django

#20660: Filefield.delete() on empty field delete MEDIA_ROOT
--+
 Reporter:  stanislas.guerra@…|Owner:  claudep
 Type:  Bug   |   Status:  assigned
Component:  File uploads/storage  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  FileField delete  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

 * has_patch:  0 => 1


Comment:

 https://github.com/django/django/pull/1310

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/084.66f2c00ee645f688aba544d4e68b5ecf%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20663: Admin Now and Today buttons use confusing time / timezone

2013-06-27 Thread Django

* stage: Unreviewed => Accepted

Comment:

I'm a bit surprised that you set TIME_ZONE = 'UTC'. I suppose your
application is used by users in multiple time zones, and UTC is the least
controversial choice?

The admin buttons should use the "current time zone". Then it's up to
developers to ensure that their users have the correct "current time
zone". This is how Django supports multiple time zones. If you don't do
anything special, the "current time zone" is the same as the "default time
zone" defined by the TIME_ZONE setting.

Then all we need is a way to determine the current time in an arbitrary
time zone in JavaScript. Unfortunately, I'm not aware of a JavaScript
library to access the tzinfo database. If there's one, I'm not sure how to
maintain it up to date. This is an open problem!

I'm accepting the ticket because it's clearly an UX bug. Now, we need a
plan to fix it, and such a plan should be discussed on the
DevelopersMailingList first.

--
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.2d06299da663cbebdfa38f5c68551328%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20660: Filefield.delete() on empty field delete MEDIA_ROOT

2013-06-27 Thread Django

#20660: Filefield.delete() on empty field delete MEDIA_ROOT
--+
 Reporter:  stanislas.guerra@…|Owner:  claudep
 Type:  Bug   |   Status:  assigned
Component:  File uploads/storage  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  FileField delete  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

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


-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/084.8149f7b76f936452dee3e158fd863789%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20660: Filefield.delete() on empty field delete MEDIA_ROOT

2013-06-27 Thread Django

#20660: Filefield.delete() on empty field delete MEDIA_ROOT
--+
 Reporter:  stanislas.guerra@…|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  File uploads/storage  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  FileField delete  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

 * version:  1.4 => master
 * stage:  Unreviewed => Accepted


Comment:

 I could reproduce this. And yes, the deletion succeeds only when
 MEDIA_ROOT is a symlink (when it's a real directory, it will fail with
 `OSError: [Errno 21] Is a directory: ...` at least on Linux).

 I tend to think there are two bugs:
  * `FieldFile` should not call `storage.delete` when `self._file` is None
  * `FileSystemStorage` should not try to remove a path when its `delete`
 method receives `''` as argument.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/084.252c75e2cfa48ef4ac156bc5b6b983e4%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20665: Sitemaps documentation example pattern missing backslash

2013-06-27 Thread Django

#20665: Sitemaps documentation example pattern missing backslash
---+
 Reporter:  roman  |  Owner:  nobody
 Type:  Bug| Status:  closed
Component:  Documentation  |Version:  master
 Severity:  Normal | Resolution:  fixed
 Keywords:  sitemap, patterns  |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  1
UI/UX:  0  |
---+

Comment (by Baptiste Mispelon ):

 In [changeset:"165cc1dc2f1cda87f7da65e8a6483318d3ca12be"]:
 {{{
 #!CommitTicketReference repository=""
 revision="165cc1dc2f1cda87f7da65e8a6483318d3ca12be"
 [1.4.x] Fixed #20665 -- Missing backslash in sitemaps documentation

 Backport of 5005303ae7919eef26dab9f8ba279696966ebf1d from master.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.db7636448b66aff11e75c63d246918f6%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20665: Sitemaps documentation example pattern missing backslash

2013-06-27 Thread Django

#20665: Sitemaps documentation example pattern missing backslash
---+
 Reporter:  roman  |  Owner:  nobody
 Type:  Bug| Status:  closed
Component:  Documentation  |Version:  master
 Severity:  Normal | Resolution:  fixed
 Keywords:  sitemap, patterns  |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  1
UI/UX:  0  |
---+

Comment (by Baptiste Mispelon ):

 In [changeset:"20295f278815598858ada0096324f77088a0df52"]:
 {{{
 #!CommitTicketReference repository=""
 revision="20295f278815598858ada0096324f77088a0df52"
 [1.5.x] Fixed #20665 -- Missing backslash in sitemaps documentation

 Backport of 5005303ae7919eef26dab9f8ba279696966ebf1d from master.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.b891c10c3207c62375068e0f6d5e89b7%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 20295f: [1.5.x] Fixed #20665 -- Missing backslash in sitem...

2013-06-27 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 20295f278815598858ada0096324f77088a0df52
  
https://github.com/django/django/commit/20295f278815598858ada0096324f77088a0df52
  Author: Baptiste Mispelon 
  Date:   2013-06-27 (Thu, 27 Jun 2013)

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

  Log Message:
  ---
  [1.5.x] Fixed #20665 -- Missing backslash in sitemaps documentation

Backport of 5005303ae7919eef26dab9f8ba279696966ebf1d from master.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/51cbee2956a6_2d4d533dd8232234%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 165cc1: [1.4.x] Fixed #20665 -- Missing backslash in sitem...

2013-06-27 Thread GitHub

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: 165cc1dc2f1cda87f7da65e8a6483318d3ca12be
  
https://github.com/django/django/commit/165cc1dc2f1cda87f7da65e8a6483318d3ca12be
  Author: Baptiste Mispelon 
  Date:   2013-06-27 (Thu, 27 Jun 2013)

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

  Log Message:
  ---
  [1.4.x] Fixed #20665 -- Missing backslash in sitemaps documentation

Backport of 5005303ae7919eef26dab9f8ba279696966ebf1d from master.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/51cbee47b0fcb_4c768c3de015104b%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 500530: Fixed #20665 -- Missing backslash in sitemaps docu...

2013-06-27 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 5005303ae7919eef26dab9f8ba279696966ebf1d
  
https://github.com/django/django/commit/5005303ae7919eef26dab9f8ba279696966ebf1d
  Author: Baptiste Mispelon 
  Date:   2013-06-27 (Thu, 27 Jun 2013)

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

  Log Message:
  ---
  Fixed #20665 -- Missing backslash in sitemaps documentation

Thanks to roman for the report.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/51cbee06a6f08_578d96dde0135f1%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20665: Sitemaps documentation example pattern missing backslash

2013-06-27 Thread Django

#20665: Sitemaps documentation example pattern missing backslash
---+
 Reporter:  roman  |  Owner:  nobody
 Type:  Bug| Status:  closed
Component:  Documentation  |Version:  master
 Severity:  Normal | Resolution:  fixed
 Keywords:  sitemap, patterns  |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  1
UI/UX:  0  |
---+
Changes (by Baptiste Mispelon ):

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


Comment:

 In [changeset:"5005303ae7919eef26dab9f8ba279696966ebf1d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5005303ae7919eef26dab9f8ba279696966ebf1d"
 Fixed #20665 -- Missing backslash in sitemaps documentation

 Thanks to roman for the report.
 }}}

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.256e2be66153be218040be9395c2f921%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

90 matches

Mail list logo