[Django] #19778: csrf middleware report BAD_REFERER when HTTP_HOST contains port

[Django]

#19778: csrf middleware report BAD_REFERER when HTTP_HOST contains port
+
 Reporter:  jens.tinfors@…  |  Owner:  nobody
 Type:  Uncategorized   | Status:  new
Component:  contrib.csrf|Version:  1.4
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 For a given request with the HTTP_HOST header set to 'www.example.com:443'
 and the HTTP_REFERER set to 'https://www.example.com/somepage' the
 same_origin check will report REASON_BAD_REFERER due to fact that HOST has
 port and REFERER does not. Perhaps, as in my case, a less competent
 firewall has tampered with the request on its way to the server.

 Here's a failing test (that I added to
 tests/regressiontests/csrf_tests/tests.py):

 {{{
def test_https_good_referer_with_port(self):
 req = self._get_POST_request_with_token()
 req._is_secure_override = True
 req.META['HTTP_HOST'] = 'www.example.com:443'
 req.META['HTTP_REFERER'] = 'https://www.example.com/somepage'
 req2 = CsrfViewMiddleware().process_view(req, post_form_view, (),
 {})
 self.assertEqual(None, req2)
 }}}

 I know the port is a valid part of the same_origin check but I'm thinking
 that if it's missing from REFERER, the scheme is https and HTTP_HOST uses
 the default port, maybe we can skip the port from the same_origin check.

 What do you think?

 Incidentally, if I set a port number on the HTTP_REFERER the test still
 fails:
 {{{
def test_https_good_referer_with_port(self):
 req = self._get_POST_request_with_token()
 req._is_secure_override = True
 req.META['HTTP_HOST'] = 'www.example.com:443'
 req.META['HTTP_REFERER'] = 'https://www.example.com/somepage:443'
 req2 = CsrfViewMiddleware().process_view(req, post_form_view, (),
 {})
 self.assertEqual(None, req2)
 }}}

 kind regards /jens

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19749: Documentation needed: stdout.write line endings in management commands changed.

[Django]

#19749: Documentation needed: stdout.write line endings in management commands
changed.
-+-
 Reporter:  xian@…   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Core (Management |  1.5-beta-1
  commands)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by claudep):

 Is this one better?

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #15363: get_queryset & get_query_set

[Django]

#15363: get_queryset & get_query_set
--+
 Reporter:  sorl  |Owner:  loic84
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by charettes):

 Added a new patch that doesn't solve the mixin issue described by
 @akaariai but provide a generic of dealing with method rename
 deprecations.

 It should be easier now to use it for the `get_prefetch_query_set` ->
 `get_prefetch_queryset` and `queryset` -> `get_queryset` migration if it
 should ever happen.

 Will wait for another core developer to chime in about whether or not it's
 worth the trouble to go forward with this.

 Personally I think the change is worth it for the sake on consistency.
 Pushing the first rename (`get_query_set` -> `get_queryset`) early into
 the 1.6 life cycle should give us a clear view over the viability of this
 kind of refactoring.

 @loic84, I won't have time to work on this in next few weeks. Feel free to
 tackle the `__mro__` issues :)

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19753: Custom user system shouldn't be dependent on all installed apps

[Django]

#19753: Custom user system shouldn't be dependent on all installed apps
---+--
 Reporter:  abraham@…  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  contrib.auth   |  Version:  1.5-beta-1
 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
---+--

Comment (by anonymous):

 To be more clear... it looks like admin.autodiscover() is executed before
 the models are imported. The guardian/models.py and guardian/admin.py.
 files are dependent on compat.py. I guess get_user_model() should not be
 called when importing any models.py files.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19753: Custom user system shouldn't be dependent on all installed apps

[Django]

#19753: Custom user system shouldn't be dependent on all installed apps
---+--
 Reporter:  abraham@…  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  contrib.auth   |  Version:  1.5-beta-1
 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
---+--

Comment (by abraham@…):

 Just tried it.

 It seems like it has nothing to do with the foreign key reference. More to
 do with the importing using get_user_model() and inclusion of admin module
 (autodiscover maybe?).

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django]

[GitHub]

  Branch: refs/tags/1.5c1
  Home:   https://github.com/django/django

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django]

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19777: Casting a SimpleLazyObject to an int fails

[Django]

#19777: Casting a SimpleLazyObject to an int fails
-+-
 Reporter:  mattrobenolt |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  functional   | Triage Stage:
  simplelazyobject   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by jacob):

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


Comment:

 Closing after IRC discussion:

 {{{
 jacobkm: mattrobenolt: I'm a bit confused: why are you passing a user into
 something that expects an int?
 jacobkm: I don't think it really has anything to do with the lazy object;
 if you did that with a non-lazy object you'd just get something like "
 int() argument must be a string or a number, not 'User'"
 mattrobenolt: jacobkm: So we've been staring at this.
 mattrobenolt: There's a bug in our code which causes us to pass in an
 AnonymousUser to our filter.
 mattrobenolt: Which uncovered the SimpleLazyObject bug.
 mattrobenolt: Inside Django's RelatedField._pk_trace, it's looking for a
 model's pk to get around the coersion.
 mattrobenolt: If it's an Anonymous user, there is none of that, so it
 fails ugly.
 mattrobenolt: So I guess we've uncovered a couple issues. 1) A bug in our
 code.
 mattrobenolt: 2) A bug in coercing any SimpleLazyObject to an int with
 __int__.
 mattrobenolt: 3) Should passing an AnonymousUser to a filter yield a
 better error?
 jacobkm: I'd say no to 3 since that would basically require special-casing
 AnonymousUser somewhere nasty.
 mattrobenolt: I agree on that.
 jacobkm: I'm trying to think through why you'd need __int__ on the lazy
 object. It's not really a public API, it's just used within Django in a
 few places, and we never need it in an int context.
 jacobkm: So I'm inclined to say "no"
 mattrobenolt: Yeah, after uncovering our bug, it wouldn't have solved it
 since it's still a bug on our end.
 mattrobenolt: Err, that didn't make much sense, but yeah.
 mattrobenolt: I'm trying to think of a better way to solve this. At least
 in terms of a better error message.
 mattrobenolt: Because this was terrible to track down considering we
 pinned it on that. :)
 fhahn left the chat room. (Ping timeout: 248 seconds)
 jacobkm: Yeah I think I'm gonna close this; if you come up with a way to
 make better error messages I'm all about that.
 }}}

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19777: Casting a SimpleLazyObject to an int fails

[Django]

#19777: Casting a SimpleLazyObject to an int fails
--+-
 Reporter:  mattrobenolt  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Core (Other)  |Version:  master
 Severity:  Normal|   Keywords:  functional simplelazyobject
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+-
 Should be pretty self explanatory. We noticed the bug when passing
 `request.user` into a filter like:

 {{{
 Model.objects.filter(user=request.user)
 }}}

 Since Django is attempting to coerce the object to an int, it fails on the
 SimpleLazyObject yielding:

 {{{
 TypeError: int() argument must be a string or a number, not
 'SimpleLazyObject'
 }}}

 The error can be reproduced simple by doing:

 {{{
 class Foo(object):
   __int__ = lambda self: 1

 int(SimpleLazyObject(Foo)))
 }}}

 See https://github.com/django/django/pull/706 for 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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19776: test fails in git stable/1.5.x branch

[Django]

#19776: test fails in git stable/1.5.x branch
---+
 Reporter:  robvdl |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Testing framework  |Version:  1.5-beta-1
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 This test wasn't failing just the other day, so probably only just
 introduced.

 ERROR: test_authenticate
 
(django.contrib.auth.tests.auth_backends.CustomUserModelBackendAuthenticateTest)
 --
 Traceback (most recent call last):
   File "/home/rob/Projects/django15-env/eve/venv/local/lib/python2.7/site-
 packages/django/contrib/auth/tests/auth_backends.py", line 205, in
 test_authenticate
 authenticated_user = authenticate(email='t...@example.com',
 password='test')
 NameError: global name 'authenticate' is not defined

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19775: database configuration without "default" not supported

[Django]

#19775: database configuration without "default" not supported
---+-
 Reporter:  monkut |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Documentation  |Version:  1.4
 Severity:  Normal |   Keywords:  multipledbs
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+-
 For version 1.4 and dev documentation on multiple databases the text seems
 to imply that you can choose not to define a "default" db

 https://docs.djangoproject.com/en/1.4/topics/db/multi-db/#defining-your-
 databases

 """
 ... Django uses the database with the alias of default when no other
 database has been selected. If you don’t have a default database, you need
 to be careful to always specify the database that you want to use.

 """

 However, when you actually remove, or do not include a "default" and
 attempt to syncdb with Postgresql, you get the following error that
 explicitly tells you, that you *must* define a "default" database:

 >python manage.py syncdb
 Traceback (most recent call last):
   File "manage.py", line 16, in 
 execute_manager(settings)
   File "C:\Python27\lib\site-packages\django\core\management\__init__.py",
 line 459, in execute_manager
 utility.execute()
   File "C:\Python27\lib\site-packages\django\core\management\__init__.py",
 line 382, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "C:\Python27\lib\site-packages\django\core\management\__init__.py",
 line 261, in fetch_command
 klass = load_command_class(app_name, subcommand)
   File "C:\Python27\lib\site-packages\django\core\management\__init__.py",
 line 69, in load_command_class
 module = import_module('%s.management.commands.%s' % (app_name, name))
   File "C:\Python27\lib\site-packages\django\utils\importlib.py", line 35,
 in import_module
 __import__(name)
   File "C:\Python27\lib\site-
 packages\django\core\management\commands\syncdb.py", line 8, in 
 from django.core.management.sql import custom_sql_for_model,
 emit_post_sync_signal
   File "C:\Python27\lib\site-packages\django\core\management\sql.py", line
 6, in 
 from django.db import models
   File "C:\Python27\lib\site-packages\django\db\__init__.py", line 12, in
 
 raise ImproperlyConfigured("You must define a '%s' database" %
 DEFAULT_DB_ALIAS)
 django.core.exceptions.ImproperlyConfigured: You must define a 'default'
 database

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19385: Add support for multiple-column join

[Django]

#19385: Add support for multiple-column join
-+-
 Reporter:  cseibert |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  join |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by akaariai):

 I have done some testing, and this is looking excellent. You have
 convinced me that the ForeignObject is a good idea. I tried the
 ForeignObject with ActiveTranslationField (a "reverse foreign key"
 fetching current active language's translations). There is need for couple
 of simple additions to ForeignObject, but otherwise things seems to just
 work.

 The tests & changes for translation fields are here:
 
https://github.com/akaariai/django/commit/790fc1693744fe3a8f407080527a0c70b1f4a759.
 This is not intended for inclusion in your patch as is, but I would like
 to add the ability to do the reverse joining stuff at some point. Only
 minor changes.

 The get_extra_join_sql() method could likely be replaced with
 get_extra_filter(). The get_extra_filter() could work for both the
 descriptor and extra_join_restriction cases. In addition this would be
 much better than generating raw SQL for custom backend support. This is
 not needed in this ticket, but definitely something to think about for
 future work.

 Unfortunately it seems I will be very busy still for the couple next
 weeks, so I can't promise a full review & commit soon. What I have managed
 to review so far suggests that there isn't much work to do.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 660f80: [1.5.x] Fixed #19662 -- alter auth modelbackend to...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 660f80c3d60083ecba26c83c0670ccca7fc56e09
  
https://github.com/django/django/commit/660f80c3d60083ecba26c83c0670ccca7fc56e09
  Author: Preston Holmes 
  Date:   2013-02-07 (Thu, 07 Feb 2013)

  Changed paths:
M django/contrib/auth/backends.py
M django/contrib/auth/tests/auth_backends.py
M docs/ref/contrib/auth.txt

  Log Message:
  ---
  [1.5.x] Fixed #19662 -- alter auth modelbackend to accept custom username 
fields

Thanks to Aymeric and Carl for the review.



-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19662: Explain correct `authenticate` usage with custom user model.

[Django]

#19662: Explain correct `authenticate` usage with custom user model.
-+--
 Reporter:  tomchristie  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  1.5-beta-1
 Severity:  Release blocker  |   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 Preston Holmes ):

 In [changeset:"660f80c3d60083ecba26c83c0670ccca7fc56e09"]:
 {{{
 #!CommitTicketReference repository=""
 revision="660f80c3d60083ecba26c83c0670ccca7fc56e09"
 [1.5.x] Fixed #19662 -- alter auth modelbackend to accept custom username
 fields

 Thanks to Aymeric and Carl for the review.
 }}}

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19662: Explain correct `authenticate` usage with custom user model.

[Django]

#19662: Explain correct `authenticate` usage with custom user model.
-+--
 Reporter:  tomchristie  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  1.5-beta-1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by Preston Holmes ):

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


Comment:

 In [changeset:"c44d748272d1d39e7cd48b625c526f532703aa29"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c44d748272d1d39e7cd48b625c526f532703aa29"
 Fixed #19662 -- alter auth modelbackend to accept custom username fields

 Thanks to Aymeric and Carl for the review.
 }}}

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] c44d74: Fixed #19662 -- alter auth modelbackend to accept ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c44d748272d1d39e7cd48b625c526f532703aa29
  
https://github.com/django/django/commit/c44d748272d1d39e7cd48b625c526f532703aa29
  Author: Preston Holmes 
  Date:   2013-02-07 (Thu, 07 Feb 2013)

  Changed paths:
M django/contrib/auth/backends.py
M django/contrib/auth/tests/auth_backends.py
M docs/ref/contrib/auth.txt

  Log Message:
  ---
  Fixed #19662 -- alter auth modelbackend to accept custom username fields

Thanks to Aymeric and Carl for the review.



-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 112c6e: Typo in i18n docs.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 112c6e987dbe789c8eb1889852f6056131c8d4d6
  
https://github.com/django/django/commit/112c6e987dbe789c8eb1889852f6056131c8d4d6
  Author: Ramiro Morales 
  Date:   2013-02-07 (Thu, 07 Feb 2013)

  Changed paths:
M docs/topics/i18n/translation.txt

  Log Message:
  ---
  Typo in i18n 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17600: Error in encapsulates filters (Q)

[Django]

#17600: Error in encapsulates filters (Q)
-+-
 Reporter:  pmartin  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by akaariai):

 #13198 is related (if not duplicate). Tests from that ticket should be
 added at least. I reopened that ticket so that adding the tests will not
 be forgotten.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #13198: exclude() bug when used with Q() objects

[Django]

#13198: exclude() bug when used with Q() objects
-+-
 Reporter:  mucisland|Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.1
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  exclude Q|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by akaariai):

 * status:  closed => new
 * resolution:  duplicate =>
 * stage:  Unreviewed => Accepted


Comment:

 I tried this with master, one of the tests pass, the other doesn't. After
 the patch to #17600 this one would be fixed this.

 I'm reopening this one so that proper test will be added in #17600.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #13198: exclude() bug when used with Q() objects

[Django]

#13198: exclude() bug when used with Q() objects
-+-
 Reporter:  mucisland|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.1
  (models, ORM)  |   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:
 Keywords:  exclude Q|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by jedediah@…):

 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


Comment:

 Still seeing this in Django 1.4, so either it was erroneously marked as a
 dupe or it snuck back in. It's pretty simple to reproduce:
 {{{
 MyModel.objects.exclude(nullable_field=123)   => includes rows with
 nullable_field=null
 MyModel.objects.exclude(Q(nullable_field=123))   => excludes rows with
 nullable_field=null
 }}}

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19772: Redirects don't honor APPEND_SLASH

[Django]

#19772: Redirects don't honor APPEND_SLASH
---+
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.redirects  |  Version:  1.4
 Severity:  Normal |   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 Aymeric Augustin ):

 In [changeset:"64623a2e115d781c99c7df4dbb67a1e576c0165a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="64623a2e115d781c99c7df4dbb67a1e576c0165a"
 Fixed #19772 -- Handled APPEND_SLASH correctly in the redirects app.
 }}}

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 64623a: Fixed #19772 -- Handled APPEND_SLASH correctly in ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 64623a2e115d781c99c7df4dbb67a1e576c0165a
  
https://github.com/django/django/commit/64623a2e115d781c99c7df4dbb67a1e576c0165a
  Author: Aymeric Augustin 
  Date:   2013-02-07 (Thu, 07 Feb 2013)

  Changed paths:
M django/contrib/redirects/middleware.py
M django/contrib/redirects/tests.py

  Log Message:
  ---
  Fixed #19772 -- Handled APPEND_SLASH correctly in the redirects app.



-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19772: Redirects don't honor APPEND_SLASH

[Django]

#19772: Redirects don't honor APPEND_SLASH
---+
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.redirects  |  Version:  1.4
 Severity:  Normal |   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:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"833ccd4b5b4b294e7ca8d32faa4461be7fafb13c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="833ccd4b5b4b294e7ca8d32faa4461be7fafb13c"
 [1.5.x] Fixed #19772 -- Handled APPEND_SLASH correctly in the redirects
 app.

 Backport of 64623a2.
 }}}

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 833ccd: [1.5.x] Fixed #19772 -- Handled APPEND_SLASH corre...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 833ccd4b5b4b294e7ca8d32faa4461be7fafb13c
  
https://github.com/django/django/commit/833ccd4b5b4b294e7ca8d32faa4461be7fafb13c
  Author: Aymeric Augustin 
  Date:   2013-02-07 (Thu, 07 Feb 2013)

  Changed paths:
M django/contrib/redirects/middleware.py
M django/contrib/redirects/tests.py

  Log Message:
  ---
  [1.5.x] Fixed #19772 -- Handled APPEND_SLASH correctly in the redirects app.

Backport of 64623a2.



-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19772: Redirects don't honor APPEND_SLASH

[Django]

#19772: Redirects don't honor APPEND_SLASH
---+
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.redirects  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by aaugustin):

 * stage:  Unreviewed => Accepted


Comment:

 I'm selfishly going to backport this to 1.5 because it breaks
 djangoproject.com...

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19749: Documentation needed: stdout.write line endings in management commands changed.

[Django]

#19749: Documentation needed: stdout.write line endings in management commands
changed.
-+-
 Reporter:  xian@…   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Core (Management |  1.5-beta-1
  commands)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by xian@…):

 I don't think it addresses the issue correctly. The fact that newlines are
 added is part of it, but I had to dig through the code to figure out how
 to _stop_ having newlines.

 `self.stdout.write("A message.\n")` still works exactly the same after the
 change. But `self.stdout.write("A message.")` gets a \n tacked on.

 The problem for me came because I was using `self.stdout.write(".")` to
 show progress on a single line like a progress bar.  I had to replace that
 with: `self.stdout.write(".", ending="")` to fix 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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19774: contentypes generic module has core functionality plus admins-specific one

[Django]

#19774: contentypes generic module has core functionality plus admins-specific 
one
+
   Reporter:  ramiro|  Owner:  nobody
   Type:  Bug   | Status:  new
  Component:  contrib.contenttypes  |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 (Copied from https://code.djangoproject.com/ticket/16368#comment:16)

 The django/contrib/contenttypes/generic.py modules contains both the
 definitions of the model-related generic stuff (!GenericForeignKey, etc.)
 AND the admin app-related specialized inlines (!GenericInlineModelAdmin,
 !GenericStackedInline, !GenericTabularInline.)

 So, for example, if you import `django.contrib.contenttypes.generic` from
 your models.py because you need !GenericForeignKey then the
 !GenericXInlineY sutff imports django.contrib.admin and it in its own turn
 imports contrib.sites causing the reported failure (see below). Again, the
 Sites framework isn't listed in INSTALLED_APPS and what is worse: The
 admin app isn't either (!).

 Maybe it's time we move !GenericInlineModelAdmin, !GenericStackedInline,
 !GenericTabularInline from django.contrib.contenttypes.generic to, say,
 django.contrib.contenttypes.generic_admin? (of course this would need a
 deprecation process)

 {{{
 from django.contrib.contenttypes import generic
   File "django/contrib/contenttypes/generic.py", line 14, in 
 from django.contrib.admin.options import InlineModelAdmin,
 flatten_fieldsets
   File "django/contrib/admin/__init__.py", line 6, in 
 from django.contrib.admin.sites import AdminSite, site
   File "django/contrib/admin/sites.py", line 4, in 
 from django.contrib.admin.forms import AdminAuthenticationForm
   File "django/contrib/admin/forms.py", line 4, in 
 from django.contrib.auth.forms import AuthenticationForm
   File "django/contrib/auth/forms.py", line 10, in 
 from django.contrib.sites.models import get_current_site
   File "/django/contrib/sites/models.py", line 5, in 
 raise Exception
 }}}

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19773: Moving the response after a popup submission to a template so that it can be overwritten.

[Django]

#19773: Moving the response after a popup submission to a template so that it 
can
be overwritten.
--+
 Reporter:  jimmylam@…|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  contrib.admin |Version:  1.4
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Currently, after a popup submission (e.g. adding another User thur the "+"
 link in django admin), the response is

 ''
 'opener.dismissAddAnotherPopup(window,
 "%s", "%s");' % \
 # escape() calls force_unicode.
 (escape(pk_value), escapejs(obj)))

 Can this be changed so that it is loaded from a template file?  And so,
 the template file can then be overwritten.

 Since most browsers are having more strict cross-site pop-up windows
 security checking and my site are being loaded from different subdomains.
 In order to make them work together, i have to add the javascript
 'document.domain = 'mydomain.com' in the templates, including the admin
 templates.

 However, the above response can't be modified or overwritten because it's
 part of the code within the response_add method of ModelAdmin.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] b53915: Changed test assertion strategy used in 04d9730.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b5391515cd9b3f2608ca41fa61471a04b771389a
  
https://github.com/django/django/commit/b5391515cd9b3f2608ca41fa61471a04b771389a
  Author: Ramiro Morales 
  Date:   2013-02-07 (Thu, 07 Feb 2013)

  Changed paths:
M tests/regressiontests/generic_relations_regress/tests.py

  Log Message:
  ---
  Changed test assertion strategy used in 04d9730.



-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #13137: GenericForeignKey does not allow content type PK 0

[Django]

#13137: GenericForeignKey does not allow content type PK 0
-+-
 Reporter:  devesine |Owner:  woodlee
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  master
  contrib.contenttypes   |   Resolution:
 Severity:  Normal   | Triage Stage:  Design
 Keywords:  contenttype  |  decision needed
  genericforeignkey  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by ramiro):

 The one that changed triage state to DDN was me. Sorry

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #13137: GenericForeignKey does not allow content type PK 0

[Django]

#13137: GenericForeignKey does not allow content type PK 0
-+-
 Reporter:  devesine |Owner:  woodlee
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  master
  contrib.contenttypes   |   Resolution:
 Severity:  Normal   | Triage Stage:  Design
 Keywords:  contenttype  |  decision needed
  genericforeignkey  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by anonymous):

 * stage:  Accepted => Design decision needed


-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #13137: GenericForeignKey does not allow content type PK 0

[Django]

#13137: GenericForeignKey does not allow content type PK 0
-+-
 Reporter:  devesine |Owner:  woodlee
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  master
  contrib.contenttypes   |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  contenttype  |  Needs documentation:  0
  genericforeignkey  |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by ramiro):

 I'd say close this ticket as ''wontfix'' because ContentType is an
 'internal' model over which the user has no control so its IntegerField id
 PK follows the usual semantics of a Django model regarding it having a
 value of 0 meaning the model has no corresponding DB record.
 So the only scenario in which CT could have a 0 PK is an edge-case one and
 IMHO it's not worth to special-case PK semantics of CT for 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19758: Password reset form should not leak information

[Django]

#19758: Password reset form should not leak information
--+--
 Reporter:  anonymous |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  master
 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 anonymous):

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


Comment:

 I think this is fixed in a pull request now:
 https://github.com/django/django/pull/703

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19753: Custom user system shouldn't be dependent on all installed apps

[Django]

#19753: Custom user system shouldn't be dependent on all installed apps
---+--
 Reporter:  abraham@…  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  contrib.auth   |  Version:  1.5-beta-1
 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
---+--

Comment (by abraham@…):

 I'll give this a shot after work!

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #13085: GenericForeignKey.get_content_type fails if `object` or `id` evaluate to False. Should use 'is not None' test.

[Django]

#13085: GenericForeignKey.get_content_type fails if `object` or `id` evaluate to
False.  Should use 'is not None' test.
-+-
 Reporter:  benreynwar   |Owner:  Ramiro
 Type:  Bug  |  Morales 
Component:   |   Status:  closed
  contrib.contenttypes   |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 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 Ramiro Morales ):

 * owner:   => Ramiro Morales 
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"04d9730b127c689b8eda01cbc913efa6e2eb230b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="04d9730b127c689b8eda01cbc913efa6e2eb230b"
 Fixed #13085 -- Don't fail on creation of model with GFK to a model with
 __len__() returning zero.

 Also, according to the comments on the ticket and its duplicates, added
 tests execising saving an instance of a model with a GFK to:

 * An unsaved object -- This actually doesn't generate the same failure
   but another ORM-level exception. The test verifies it's the case.

 * An instance of a model with a __nonzero__() method thant returns False
   for it. This doesn't fail because that code path isn't executed.

 * An instance of a model with a CharField PK and an empty value for it.
   This doesn't fail.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 04d973: Fixed #13085 -- Don't fail on creation of model wi...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 04d9730b127c689b8eda01cbc913efa6e2eb230b
  
https://github.com/django/django/commit/04d9730b127c689b8eda01cbc913efa6e2eb230b
  Author: Ramiro Morales 
  Date:   2013-02-07 (Thu, 07 Feb 2013)

  Changed paths:
M django/contrib/contenttypes/generic.py
M tests/regressiontests/generic_relations_regress/models.py
M tests/regressiontests/generic_relations_regress/tests.py

  Log Message:
  ---
  Fixed #13085 -- Don't fail on creation of model with GFK to a model with 
__len__() returning zero.

Also, according to the comments on the ticket and its duplicates, added
tests execising saving an instance of a model with a GFK to:

* An unsaved object -- This actually doesn't generate the same failure
  but another ORM-level exception. The test verifies it's the case.

* An instance of a model with a __nonzero__() method thant returns False
  for it. This doesn't fail because that code path isn't executed.

* An instance of a model with a CharField PK and an empty value for it.
  This doesn't fail.



-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19772: Redirects don't honor APPEND_SLASH

[Django]

#19772: Redirects don't honor APPEND_SLASH
---+--
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.redirects  |  Version:  1.4
 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
---+--

Comment (by carljm):

 Yes, that's what I was about to say.

 But I still agree with you that it seems like `RedirectFallbackMiddleware`
 ought to be trying with an added slash, not a removed one, in this case,
 since `APPEND_SLASH` would never actually have appended a slash in this
 situation. IOW `RedirectFallbackMiddleware` needs to have its own
 implementation of `APPEND_SLASH`, not reverse its effect like the current
 code seems to be trying to do.

 Unfortunately adding a slash while retaining querystring is a bit uglier
 than removing, but doable.

 I have no idea how this would have broken with the recent dp.com changes.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19772: Redirects don't honor APPEND_SLASH

[Django]

#19772: Redirects don't honor APPEND_SLASH
---+--
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.redirects  |  Version:  1.4
 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
---+--

Comment (by aaugustin):

 I just understood the current construct -- it's probably designed to
 handle querystrings.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #15039: The current download link redirection breaks wget making Linux download inconvenient

[Django]

#15039: The current download link redirection breaks wget making Linux download
inconvenient
-+-
 Reporter:  jonathanberger   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Djangoproject.com|  Version:  1.2
  Web site   |   Resolution:
 Severity:  Normal   | Triage Stage:  Design
 Keywords:   |  decision needed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by carljm):

 I think changing the URLs for future releases to include the filename at
 the end is the most sensible/compatible solution. It doesn't seem to me
 that much is gained by leaving it 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19753: Custom user system shouldn't be dependent on all installed apps

[Django]

#19753: Custom user system shouldn't be dependent on all installed apps
---+--
 Reporter:  abraham@…  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  contrib.auth   |  Version:  1.5-beta-1
 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
---+--

Comment (by charettes):

 This [https://github.com/lukaszb/django-
 guardian/blob/master/guardian/models.py#L54 `ForeignKey`] should reference
 `getattr(django.conf.settings, 'AUTH_USER_MODEL', 'auth.User')`. This
 looks like the [https://github.com/lukaszb/django-
 guardian/commit/2a78307e40b427d7ef0bdebb8787358ef686bc6f culprit].

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19772: Redirects don't honor APPEND_SLASH

[Django]

#19772: Redirects don't honor APPEND_SLASH
---+--
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.redirects  |  Version:  1.4
 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
---+--

Comment (by aaugustin):

 I've provisionally applied this change on the server.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19772: Redirects don't honor APPEND_SLASH

[Django]

#19772: Redirects don't honor APPEND_SLASH
-+
   Reporter:  aaugustin  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  contrib.redirects  |Version:  1.4
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 seanbrant reports on IRC that the following command no longer works.
 {{{
 pip install https://www.djangoproject.com/download/1.5c1/tarball/
 }}}

 `/download/1.5c1/tarball/` is a URL in the redirect table. But pip strips
 the trailing slash, and despite `APPEND_SLASH = True`, Django doesn't
 restore it.

 It could be a side effect of the upgrade of djangoproject.com to 1.4 this
 morning but I haven't found a corresponding change.

 

 I don't understand how
 
[https://github.com/django/django/blob/master/django/contrib/redirects/middleware.py#L16
 RedirectFallbackMiddleware deals with APPEND_SLASH]. APPEND_SLASH tests if
 the resulting URL exists, and if not, it doesn't add a slash. Since
 RedirectFallbackMiddleware only handles 404, it can never operate on an
 URL processed by APPEND_SLASH.

 Therefore, I believe the fallback lookup should be:
 {{{
 Redirect.objects.get(site__id__exact=current_site.id, old_path=path + '/')
 }}}
 rather than:
 {{{
 Redirect.objects.get(site__id__exact=current_site.id,
 old_path__exact=path[:path.rfind('/')]+path[path.rfind('/')+1:])
 }}}
 (which doesn't make any sense to me, actually).

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19662: Explain correct `authenticate` usage with custom user model.

[Django]

#19662: Explain correct `authenticate` usage with custom user model.
-+--
 Reporter:  tomchristie  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  Version:  1.5-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by mjtamlyn):

 I'm inclined to agree with Carl - I'd rather things had the "correct"
 signature and it shouldn't be massively difficult to update external
 backends. Any pluggable app providing auth is likely to require updating
 for custom user models in any case.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19662: Explain correct `authenticate` usage with custom user model.

[Django]

#19662: Explain correct `authenticate` usage with custom user model.
-+--
 Reporter:  tomchristie  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  Version:  1.5-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by carljm):

 Replying to [comment:7 shaneallgeier@…]:
 > I believe that `authenticate()` should be left as is (only expecting
 `username`). Otherwise, all DRY/pluggable authentication backends would
 have to first check the `USERNAME_FIELD` from the user model every time
 someone tries to authenticate. It would also require pluggable backends to
 check the Django version to figure out if it even needs to check for a
 possible `USERNAME_FIELD`. I know it won't be a difference in speed or
 anything, but it would still be annoying to write.

 You mean "all DRY/pluggable authentication backends that use essentially
 the same authentication scheme as ModelBackend but for some reason
 reimplement it themselves"? How big a category of reusable authentication
 backends is this? The `authenticate()` method of authentication backends
 has always been documented to accept `**credentials` precisely so custom
 auth backends can accept any authentication credentials that make sense
 for them, not be limited to what `ModelBackend` does. So I don't think
 changing `ModelBackend` to use more sensible credential names with custom
 User classes is enforcing any changes on custom auth backends in general.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19693: truncatewords_html closes tags

[Django]

#19693: truncatewords_html closes   tags
-+--
 Reporter:  sneawo   |Owner:  reecelong
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  1.4
 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
-+--

Comment (by aaugustin):

 The report isn't accurate; to reproduce on master:
 {{{
 >>> from django.template.defaultfilters import truncatewords_html
 >>> truncatewords_html('testtest test', 2)
 u'testtest ...'
 }}}

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19757: syncdb untranslated prompts for creating superuser

[Django]

#19757: syncdb untranslated prompts for creating superuser
-+--
 Reporter:  eukreign |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by Florian Apolloner ):

 In [changeset:"2b916895a1cea39de3280a6910e2886aebfcfc64"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2b916895a1cea39de3280a6910e2886aebfcfc64"
 Updated createsuperuser to use unicode_literals. Refs #19757.
 }}}

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 2b9168: Updated createsuperuser to use unicode_literals. R...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2b916895a1cea39de3280a6910e2886aebfcfc64
  
https://github.com/django/django/commit/2b916895a1cea39de3280a6910e2886aebfcfc64
  Author: Florian Apolloner 
  Date:   2013-02-07 (Thu, 07 Feb 2013)

  Changed paths:
M django/contrib/auth/management/commands/createsuperuser.py

  Log Message:
  ---
  Updated createsuperuser to use unicode_literals. Refs #19757.



-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19706: Tutorial amendments

[Django]

#19706: Tutorial amendments
-+-
 Reporter:  EvilDMP  |Owner:  timo
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Documentation|  1.5-beta-1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"ad2311dfc68fb10710093c5b8c827249852402dd"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ad2311dfc68fb10710093c5b8c827249852402dd"
 [1.5.x] Fixed #19706 - Tweaks to the tutorial.

 Thanks Daniele Procida.

 Backport of aa85ccf8ce 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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] ad2311: [1.5.x] Fixed #19706 - Tweaks to the tutorial.

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: ad2311dfc68fb10710093c5b8c827249852402dd
  
https://github.com/django/django/commit/ad2311dfc68fb10710093c5b8c827249852402dd
  Author: Tim Graham 
  Date:   2013-02-07 (Thu, 07 Feb 2013)

  Changed paths:
M docs/intro/reusable-apps.txt
M docs/intro/tutorial01.txt
M docs/intro/tutorial02.txt
M docs/intro/tutorial03.txt
M docs/intro/tutorial04.txt

  Log Message:
  ---
  [1.5.x] Fixed #19706 - Tweaks to the tutorial.

Thanks Daniele Procida.

Backport of aa85ccf8ce 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19706: Tutorial amendments

[Django]

#19706: Tutorial amendments
-+-
 Reporter:  EvilDMP  |Owner:  timo
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Documentation|  1.5-beta-1
 Severity:  Normal   |   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"aa85ccf8ce11c4b8374c74fd9dfe72647be49ada"]:
 {{{
 #!CommitTicketReference repository=""
 revision="aa85ccf8ce11c4b8374c74fd9dfe72647be49ada"
 Fixed #19706 - Tweaks to the tutorial.

 Thanks Daniele Procida.
 }}}

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] aa85cc: Fixed #19706 - Tweaks to the tutorial.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: aa85ccf8ce11c4b8374c74fd9dfe72647be49ada
  
https://github.com/django/django/commit/aa85ccf8ce11c4b8374c74fd9dfe72647be49ada
  Author: Tim Graham 
  Date:   2013-02-07 (Thu, 07 Feb 2013)

  Changed paths:
M docs/intro/reusable-apps.txt
M docs/intro/tutorial01.txt
M docs/intro/tutorial02.txt
M docs/intro/tutorial03.txt
M docs/intro/tutorial04.txt

  Log Message:
  ---
  Fixed #19706 - Tweaks to the tutorial.

Thanks Daniele Procida.



-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 056b2b: [1.4.x] Fixed #19756 - Corrected a ManyToMany exam...

[GitHub]

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: 056b2b5f65e6b12c609dbd064cbe1e44a8730bf7
  
https://github.com/django/django/commit/056b2b5f65e6b12c609dbd064cbe1e44a8730bf7
  Author: Tim Graham 
  Date:   2013-02-07 (Thu, 07 Feb 2013)

  Changed paths:
M docs/topics/db/examples/many_to_many.txt

  Log Message:
  ---
  [1.4.x] Fixed #19756 - Corrected a ManyToMany example and added some links 
and markup.

Backport of 43efefae69 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19756: .add or .create on ManyToManyField doc page

[Django]

#19756: .add or .create on ManyToManyField doc page
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  closed
Component:  Documentation  |Version:  1.4
 Severity:  Normal | Resolution:  fixed
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  1
UI/UX:  0  |
---+

Comment (by Tim Graham ):

 In [changeset:"056b2b5f65e6b12c609dbd064cbe1e44a8730bf7"]:
 {{{
 #!CommitTicketReference repository=""
 revision="056b2b5f65e6b12c609dbd064cbe1e44a8730bf7"
 [1.4.x] Fixed #19756 - Corrected a ManyToMany example and added some links
 and markup.

 Backport of 43efefae69 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19756: .add or .create on ManyToManyField doc page

[Django]

#19756: .add or .create on ManyToManyField doc page
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  closed
Component:  Documentation  |Version:  1.4
 Severity:  Normal | Resolution:  fixed
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  1
UI/UX:  0  |
---+

Comment (by Tim Graham ):

 In [changeset:"a81363d85accfe09fe6885b255355dfb108e25af"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a81363d85accfe09fe6885b255355dfb108e25af"
 [1.5.x] Fixed #19756 - Corrected a ManyToMany example and added some links
 and markup.

 Backport of 43efefae69 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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] a81363: [1.5.x] Fixed #19756 - Corrected a ManyToMany exam...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: a81363d85accfe09fe6885b255355dfb108e25af
  
https://github.com/django/django/commit/a81363d85accfe09fe6885b255355dfb108e25af
  Author: Tim Graham 
  Date:   2013-02-07 (Thu, 07 Feb 2013)

  Changed paths:
M docs/topics/db/examples/many_to_many.txt

  Log Message:
  ---
  [1.5.x] Fixed #19756 - Corrected a ManyToMany example and added some links 
and markup.

Backport of 43efefae69 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19756: .add or .create on ManyToManyField doc page

[Django]

#19756: .add or .create on ManyToManyField doc page
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  closed
Component:  Documentation  |Version:  1.4
 Severity:  Normal | Resolution:  fixed
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  1
UI/UX:  0  |
---+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"43efefae692729925c0f75c55e93bd1f33f42bfd"]:
 {{{
 #!CommitTicketReference repository=""
 revision="43efefae692729925c0f75c55e93bd1f33f42bfd"
 Fixed #19756 - Corrected a ManyToMany example and added some links and
 markup.
 }}}

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 43efef: Fixed #19756 - Corrected a ManyToMany example and ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 43efefae692729925c0f75c55e93bd1f33f42bfd
  
https://github.com/django/django/commit/43efefae692729925c0f75c55e93bd1f33f42bfd
  Author: Tim Graham 
  Date:   2013-02-07 (Thu, 07 Feb 2013)

  Changed paths:
M docs/topics/db/examples/many_to_many.txt

  Log Message:
  ---
  Fixed #19756 - Corrected a ManyToMany example and added some links and markup.



-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19771: eBay Why You Must Have A Postage Scale If You happen to be Going To Sell Anything###

[Django]

#19771: eBay Why You Must Have A Postage Scale If You happen to be Going To Sell
Anything###
-+
 Reporter:  beschconliancid1972  |  Owner:  nobody
 Type:  Uncategorized| Status:  new
Component:  Uncategorized|Version:  1.4
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 No matter what you sell on eBay having a digital scale is possibly the
 second most essential item you will need in order to be successful (a
 digital camera is the 1st). If you've ever shipped a package you know that
 you need to have to have the appropriate weight so that you have the
 appropriate postage on it. If you estimate the weight you are either going
 to spend also a lot for postage or your package will be returned for not
 having adequate postage. With the cost of stamps these days you cannot
 afford to pay also substantially for shipping. If you happen to be an eBay
 seller you currently have sufficient costs to take into consideration
 devoid of having to be concerned about postage also. Sometimes sellers
 will provide a flat price shipping charge. This is okay to do after in a
 when depending on what you're selling, but most of the time you require to
 charge close to actual shipping (a tiny handling fee is okay) so that your
 purchasers [http://www.youtube.com/watch?v=hjYz6gKjjwU continue reading]
 will want to obtain from you. Think me, they know if you're overcharging
 and will click away from your auction and go on to the next. Also, it is
 against eBays rules to charge excessive shipping, if you attempt to do so
 your auction will get pulled and you will threat losing your account.

 So, to resolve this situation (and to make your life so a great deal less
 complicated) you need to have to get postage scale. There are a large
 number of sorts of scales offered but the top for weighing the most
 accurately is a digital scale. The next factor you will need to make a
 decision is how a great deal weight capacity you require for the digital
 scale you get. This will rely on what you are selling. If you are selling
 anything heavy then you will require a heavy duty scale, but if you are
 promoting mostly lighter weight products such as clothes or books then you
 will most likely only want up to a five lb. capacity scale.

 You will probably be asking, why do I want a scale when I can just take my
 packages to the post workplace and have them weighed for me? The situation
 with that is :

 #1 You have to have to know the weight of your package ahead of you list
 the item on eBay. Unless you package it up and take it to the post office
 prior to you list it you will not know the precise weight. And even then
 you do not know who's purchasing your item which implies you do not know
 where it's getting shipped. If your package is more than a certain weight
 this does matter depending on the shipping zone. You need to have to know
 what you happen to be going to charge for shipping just before you list
 the item and your bidders require to know what they will have to spend. If
 you do not list your shipping charges you will drop bids.

 #two You just made an additional trip to the post workplace. Can you
 consider obtaining to stand in line behind ten many people just to get the
 weight of your package and then right after it sells you will have to go
 back down there and stand in line again to spend to have it shipped? You
 do not have time for that.

 And the #3 purpose why you need to have a cale is as a result of you have
 no explanation not to get 1. Did you know you can get one particular for
 totally free shipped to you?

 Just think, If you have your personal scale you can start printing your
 own postage at residence, all you need to have is a printer & paper. You
 never require anything unique just a common printer that prints legibly.
 All you will need to do to ship your package from home and by no means
 have to go to the post office once again is #1 Weigh it - make positive
 you keep in mind to include things like the entire package which means the
 item you're selling, the box you're shipping it in and the packing
 material. #2 Print the postage proper from your pc and tape it to your
 package. #three Schedule a no cost choose-up from USPS straight from your
 doorstep. Yes, your postal carrier will pick up your package for you, all
 you need to have to do is go internet and schedule a choose-up at least a
 day in advance.

 Think about under no circumstances having to go to the post office again!
 How a great deal time & gas will you save? And don't overlook your sanity
 - if you have kids and you've ever had to stand in line at the post office
 for 20 minutes with them and a handful of packages then you know what I'm
 speaking about. So join 

Re: [Django] #19749: Documentation needed: stdout.write line endings in management commands changed.

[Django]

#19749: Documentation needed: stdout.write line endings in management commands
changed.
-+-
 Reporter:  xian@…   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Core (Management |  1.5-beta-1
  commands)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by claudep):

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


Comment:

 Does the attached patch seem sufficient?

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19770: cheap rolex watches!

[Django]

#19770: cheap rolex watches!
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 http://cheap-rolex.com

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19769: Seo ###

[Django]

#19769: Seo ###
+
 Reporter:  teucenrale1982  |  Owner:  nobody
 Type:  Uncategorized   | Status:  new
Component:  Uncategorized   |Version:  1.4
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 A major perk to applying An additional advantage of making use of spend
 per click search engines to advertise your product is that you are in
 manage of how a lot you want to invest on an advertising camp...

 Even if you are running a smaller organization you can take advantage of a
 pay per click system. Pay per click search engine marketing offers any
 variety of online business a low cost type of promotion. The beauty is
 that a pay per click ad campaign is that it can also guide bring acquiring
 client not just surfers

 A massive perk to employing One more advantage of making use of spend per
 click search engines to advertise your product is that you are in manage
 of how considerably you want to devote on an marketing campaign. This is
 not necessarily accurate of other types of marketing. You are in control
 of how a great deal income you want to deposit into your pay per click
 marketing account and you can also identify exactly where and on what
 keyword it is basically spent. You also ascertain how and when the
 advertisements were run and just how a great deal you are prepared to
 spend every single time an interested surfer clicks on your ad. This is a
 great deal less costly than letting an agency do this for you. It also
 locations all accountability for your errors into a single lap  yours!

 If you want to make dollars on the World-wide-web, then you need to
 [http://www.justiciaparaputis.org/ read more] be managing a spend per
 click advertising campaign (or 'sponsored listing' as they are
 occasionally called) on at least one of the most preferred search engines.

 One other amazing advantage to using pay-per-click search engines that can
 not be overlooked as a search engine optimization tactic is that you have
 the potential to provide your item knowledge only to these who are
 interested. Thanks to the keyword search technique you can automate your
 ad so that it is targeted to these who are already likely prospects. In
 essence the search engine itself is building leads and performing
 marketplace study for you. However one other large perk is that this
 naturally raises your rankings in the search engine pages as well because
 the search engines adore ads and links that are focused!

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19768: 40s Night And An Amiable Game Of Poker ###

[Django]

#19768: 40s Night And An Amiable Game Of Poker ###
---+
 Reporter:  allofider1984  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Within my early post-college years several select friends, Sam and Pete,
 shared exactly the same interests that used to do older women and poker.
 We started going out on Thursday nights to a particular bar that could
 usually have ladies in their 40s lately divorced or single for other
 reasons. We called it 40s night. We would often reach the club around 8
 pm, after the gymnasium and after a couple of beers. Some nights were
 dead; others
 
[http://www.purevolume.com/couchlute7/posts/3589385/Gemstones+-+The+Crowning+Glory+Of+Ornaments
 buy here] were a little more exciting. On this a particular night we ran
 into three other women, Dawn, Melissa and Kelly. Melissa was sporting a
 tshirt nevertheless Double N scrawled on with a sharpie gun. First
 instincts were, I suppose she must need you to definitely ask. Thinking it
 had regarding her structure we went over to strike up a conversation.
 Turns out the Double D, intended Delightfully Divorced, maybe not what we
 were thinking.

 Several buddies and Melissa were out celebrating her recent divorce which
 been finalized that morning. After where we were headed too exchanging
 pleasantries and drinking until closing with them, they asked. My on again
 off again girlfriend was at our home (I was with Sam and Pete for moral
 support) and therefore these two areas were from the picture Sam was
 living with his Aunt. Petes girlfriend was out of town visiting her
 parents and wasn't due back before next morning, so we headed there.

 After offering the poker case and the nice stuff to drink and chips, the
 tip of a friendly game of strip poker came out. All agreed it was just for
 fun. Well after hrs of drinking and poker, we found ourselves down
 seriously to our boxers and Melissas interesting Double N shirt draped
 over a chair. Whilst the rest of us did plenty of looking, the girls were
 really playing. At about 3:00 in the morning there was a jiggling at the
 leading door, then a gasp, then a scream. Petes partner had gotten in
 early and desired to surprise him a day later. She was hoping to climb in
 to bed and have him awaken to her smiling face.

 Alternatively she was treated a number of half naked women alongside her
 very nearly naked partner. Next evening, my on again off again girlfriend
 got a call and turned my never again girlfriend. And Pete, well, Pete
 ended up being forced to go to the er to obtain some reconstructive work
 performed on his little Pete.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19767: Option Options for a Healthy Lifestyle How Viatmins and Other Supplments Can Help You Stay Healthy ###

[Django]

#19767: Option Options for a Healthy Lifestyle How Viatmins and Other Supplments
Can Help You Stay Healthy ###
+
 Reporter:  gravatawin1981  |  Owner:  nobody
 Type:  Uncategorized   | Status:  new
Component:  Uncategorized   |Version:  1.4
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 Vitamins  could help  manage  diet  requirements,  keep energy and
 potentially  reduce medication in take. They must be taken carefully and
 with moderation in order to be effective. If too many are ingested, many
 of the  important nutrients will simply  go through the body without being
 used. Natural vitamins like Solaray calcium citrate or Source natural
 multidophilus 12  could help keep your body in balance so you can continue
 about your day without worrying about disease or straining yourself.
 Cleanses can also be  helpful when taken  properly. By taking them
 moderately and with caution, your body can be free of
 [http://www.sodapopsurvey.com/?p=97 solaray supplements] toxins.  All
 these  choices  ought to be researched and  reviewed with a  medical
 professional  prior to you begin your vitamin regiment.
 Solaray supplements and other Solaray products are  brand source with a
 range of probiotics, vitamins and  natural herbs to keep your body
 healthy. Probiotics are a natural  means to  present  microbes into your
 digestive system in order to  correctly break down  meals so you  could
 keep the nutrients without harming your body. Solaray probiotics are a
 natural option that many use  due to the fact that it is gentle and
 reliable. Herbs are  an additional  helpful  method to keep your body in
 check.  Using tinctures,  pills and teas to  offer your body with natural
 supplements that have been used for hundreds of years. With herbs you
 must go to a trusted herbalist or  natural herb  company before using
 natural herbs in your  diet plan. This  could ensure they are all-natural,
 fair trade and  reputable. Vitamins should be  managed the same. By
 visiting a site that is a  relied on distributer of vitamins, you  could
 guarantee their quality.
 Cleanses should  additionally be well  looked into  prior to starting a
 cleansing  program. By  speaking with your  medical professional about
 your  choice before starting cleanses, it will be safer and will be
 effective  because you are using cleanses tailored to your body type.
 There is a  variety of cleansing  choices. While some are trends (such as
 drinking water with lemon juice and chili flakes for a week) that are
 extremely  efficient in making you  drop weight  however not in  keeping
 the  fat loss or cleanliness.  Using cleanses such as Solaray yeast
 cleanses or Solaray super digestaway you  could  adhere to a  program
 without  compromising your diet or  daily life. By using supplements it
 will  additionally keep you from depriving yourself from a healthy diet.
 While some trends  urge you to only eat a few meals a day, using a
 supplement will keep you full and active throughout the cleanse.
 By using these  choices, you  might  have the ability to cut down on
 medicines. By using  natural herbs such as red clover or garlic, you can
 cut down on  diet plan  tablets.  Natural herbs are more dependable for
 slimming down and your metabolism will not  reduce  as soon as you are
 done taking them unlike  lots of  diet plan  tablets. Solaray vitamins or
 Source natural vitamins will keep your body balanced when used with
 regular  workout and diet. After consulting a  doctor and making a
 routine that  deals with your  demands, you can be able to keep your body
 in check and  might be able  minimize  specific  medicines. Cleanses are a
 fantastic way to keep your digestive system regular but you  should take a
 dependable cleanse in order to be effective while still keeping your  day-
 to-day caloric  consumption  routine.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19766: Acne Remedy Item Data###

[Django]

#19766: Acne Remedy Item Data###
---+
 Reporter:  marmondblocex1981  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 In spite of all the scientific understanding right now, folks nevertheless
 believe that acne is triggered by...

 Latest research have concluded roughly 90% of all teenagers, 50% of all
 adult ladies and 25% of all adults had suffered from acne, either as a
 chronic skin disease or at some point in their lives. Although there is no
 universal remedy, acne is absolutely less complicated to treat now than it
 used to be. Nonetheless, finding the right acne remedy product is still a
 mystery for several of the sufferers.

 In spite of all the scientific expertise today, men and women still feel
 that acne is triggered by distinct issues we do. Truly
 [http://www.solutionsforscars.com/ the infographic], it is mostly a
 mixture of aspects underneath our skin that lead to acne. The good news
 that there are acne remedy items that can eradicate it entirely in about
 95% of all situations.

 Your skin has several great functions that aid it recover totally even
 from significant acne if treated correctly:

 * It is self healing.

 * It is very elastic.

 * It registers and remembers sensations extremely exactly.

 * It is really resilient.

 * It is self-cleaning and hardly ever suffers any severe infection.

 * It lets in some elements and protects you from others.

 * It holds in the complete quantity of liquid that flows through your
 body.

 Salicylic Acid

 There's a lot of evidence that salicylic acid is a single of the most
 effective approach on acne difficulties. It decreases the quantity of
 principal acne lesions, as effectively as the number and severity of all
 lesions related with acne. Salicylic acid is protected to use even on dark
 skin and provides great and quick final results.

 Glycolic Acid

 Among common alpha hydroxyl acids, glycolic acid is one of the most
 commonly utilized. It has similar outcomes with a chemical peel. Even when
 used in strong concentrations, glycolic acid has only couple of damaging
 side effects. Long-phrase day to day use may possibly also have a helpful
 impact on acne scars.

 Glycolic acid is also efficient in escalating skin resistance to
 ultraviolet light, enhancing moisture retention, as well as the basic skin
 situation. Nevertheless, even though it is rather productive and has only
 minor side effects, it is greater to use as component of a more
 complicated skin care technique.

 Benzoyl Peroxide

 Benzoyl peroxide is a broadly utilized ingredient in acne therapy
 merchandise. It used to be really well-known in the 1930s, but given that
 then, healthcare science has come up with new and far more successful
 treatments. Nevertheless, a lot of dermatologists are nevertheless
 pleading for the benefits of acne remedy items that include Benzoyl
 peroxide.

 In addition to its antibacterial effect, Benzoyl peroxide apparently has
 an anti-oxidant action as properly. Amongst its most common side effects
 is dry and irritated skin.

 A lot of acne remedy items available on the industry right now use 1 of
 the ingredients mentioned above in mixture with other substances. Some of
 the most well-known and successful products against acne are ProAcrive,
 ZENMED Derma Cleanse System, Accutane and Benzoyl Peroxide. Nonetheless,
 when purchasing an acne remedy product, you have to search through the
 side effects thoroughly, as some of them could be worse than your acne
 itself.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19765: Style Guidelines For Enhancing Your Style Savvy###

[Django]

#19765: Style Guidelines For Enhancing Your Style Savvy###
---+
 Reporter:  ipdeveso1977   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Looking your ideal is valuable in discovering a partner, employment and a
 good number of other really important factors in life. All the same,
 various people never know basic fashion tips and hints that would make
 them appear considerably far better in their day to day lives. Study on
 for some very easy and usable style helpful hints to hold your self
 hunting superb.

 A single nice style tip is to take into consideration the type of care
 that a garment needs ahead of getting it. This is a great concept for the
 reason that if you get anything that is dry clean only or hand wash only,
 you could either end up ruining it or in no way working with it.

 Invest in clothes with your close friends and trade garments with them.
 This is a good quality way to expand your wardrobe and for you and your
 good friends to maintain up with the latest fashion trends. Individuals
 trade garments all the time, so do not hesitate to trade clothing with
 your closest mates.

 It is not rather uncomplicated to put on plaid, especially when you are
 searching to adopt a appear that is softer than you normally have. If you
 must put on plaid, make confident that you pair it with a thing that is
 feminine like skinny jeans or a bag that has ruffles on it.

 Invest money on your shoes. You may very well be tempted to purchase
 footwear as cheaply as you can, in particular if they look decent. Still,
 purchasing a top quality [http://www.jacketsinside.com/ the jackets for
 men] pair of footwear suggests that they will final a lengthy time and
 will not fall apart right after just a handful of wearings. They are also
 made of improved components and are even more comfortable on your feet.

 If you are a mother, fashion is possibly the last thing on your mind, But
 know that it is potential to appear fantastic and practical at the exact
 same time. Irrespective of whether taking the youngsters to the park,
 sporting events or any other event, spruce up your appear with a nice
 T-Shirt, knee-length skirt and a pair of flat sandals!

 Are you a woman with lots of curves? If so, then aim to put on skirts that
 will catch the eye. Stay away from wearing eye-catching tops that will
 draw the eye up. Instead, wear extended jackets that will draw eyes down.
 Also, you should certainly put on a single color due to the fact it
 produces a slimming impact.

 The very best time to apply body moisturizer is straight immediately after
 you shower. Use it prior to you dry off, or after a gently towel drying.
 This will support to lock the moisture from the shower into your skin,
 doubling the positive aspects of the moisturizer. It will also require
 that you use much less of the item.

 Skinny jeans are what is in style now. These kinds of jeans are snug
 around all areas of your physique, from you waist and rear end, all the
 way down to your ankles. The perfect element of these jeans is that they
 appear good quality with quite a great deal any pair of shoes!

 Dipped hem dresses are in the style ideal now. These dresses dip down in
 both the front of the dress and back, although they do not dip also
 significantly. Dipped hem dresses are a wonderful way to show off your
 shoulders and when worn with a pair of heels, is the perfect appear!

 If you have thick or tremendously curly hair, working with a gel item will
 enable you to produce the style you want. Function the product into towel-
 dried hair and then style it as you want. You can let it to dry naturally,
 or use a hair drier. This is especially beneficial in humid climate.

 One style tip to give some thought to is to have at least one item that is
 leopard print. While this might possibly look odd, this style has been
 popular throughout the ages and could be just the factor to add some spice
 to your outfit. Typically just a belt or purse could do the trick.

 When hemming your pants, take the height of your shoes into account. The
 hem of your pants need to constantly be half to three fourths of an inch
 off the floor. Hold two lengths of pants. Have pants that you can wear
 heels with and ones you can wear with flat footwear.

 If you like form fitting clothes, it is especially very important to know
 what supplies and colors blend with each other, and will hold their form
 the leading. This is important mainly because if you get the wrong blend,
 not only the outfit will possibly go out of shape, but it could possibly
 be uncomfortable as nicely.

 Wear cropped pants in a more flattering way by choosing capris, pedal
 

Re: [Django] #19764: Homeschooling: You Can Teach Your Kids At Home ###

[Django]

#19764: Homeschooling: You Can Teach Your Kids At Home ###
---+--
 Reporter:  tiranhina1985  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.4
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by oinopion):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19764: Homeschooling: You Can Teach Your Kids At Home ###

[Django]

#19764: Homeschooling: You Can Teach Your Kids At Home ###
---+
 Reporter:  tiranhina1985  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Surely you've known some one that's property schooled their children.
 You've probably considered it, but you might have decided that you could
 not do it. The wrong idea has been got by you about homeschooling if that
 is your mindset. Your children can be provided by you with the proper
 education. All you have to is the proper structure.

 Homeschooling can be time consuming. Make sure you put aside additional
 time to make your meals or discover how you can make bigger
 [http://www.newswire.net/newsroom/local/california/70209-Lindero-Learning-
 Center-Offers-Free-SAT-and-ACT-Practice-Tests.html purchase free sat
 practice] meals once a to be frozen for quick dinners throughout the
 month. You will be very happy to have that freezing spagehetti sauce in
 the freezer!

 During homeschooling time, your youngster needs to see you as their
 teacher. Likewise, when you are not teaching the course you have to change
 of teacher function. Parents that also teach their children have many
 advantages over a normal teacher, as long as they cannot allow their love
 for his or her child to disrupt educational goals.

 Remember that you don't need certainly to follow any guidelines when you
 are the teacher, while you want your house schooled student( s) to master
 just as much or maybe more as their traditionally schooled alternatives.
 Decide to try different teaching and learning techniques to see what is
 most effective for the student. Also, consider using a incentive system to
 produce learning more interesting.

 There could be many people out there which will try to discourage you from
 teaching your young ones in the home. You must make it clear to them that
 this can be a decision that you have made as a parent and they want to
 regard it, while there is nothing wrong with listening to the opinion of
 the others.

 Then make certain that your homeschooling program prepares them for that,
 if you ultimately plan to shift your young ones back into an everyday
 college program. If you can obtain a copy of the school program for the
 entire year the system will be re-entered by them to make sure that
 they'll be on course with or before their course see. Moreover, ask them
 to study on the traditional school schedule, meals and all.

 If you have just gotten started, and you are not sure how things must be
 going, contact other parents who are teaching their kids at home. Use the
 Internet to find other parents in your town and question them tons of
 questions until you are certain that this really is something that you're
 more comfortable with.

 Visit zoos and other sights to increase what you are teaching the kids.
 Discuss the animals and their habitats. A geography lesson could be
 supplemented by this. In addition, it may seem about endangered animals
 and what's happened to diminish their numbers. There are many applications
 to the, including seeing the visitors!

 You can put the education of one's kids first in a way that no-one else
 can. With the proper direction and right understanding, you can give them
 the training that they need. It can be one of the most rewarding, while
 it's definitely not the easiest thing in the world.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19763: LocaleMiddleware should check for supported languages in settings.LANGUAGE_CODE too

[Django]

#19763: LocaleMiddleware should check for supported languages in
settings.LANGUAGE_CODE too
--+
 Reporter:  kozz  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Translations  |Version:  1.4
 Severity:  Normal|   Keywords:  locale
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+
 We have a Django project with the setting:
 LANGUAGE_CODE = 'en-us'
 LANGUAGES = (
 ('en', 'English'),
 ('sv', 'Swedish'),
 )

 These settings should be correct according to the documentation
 https://docs.djangoproject.com/en/dev/ref/settings/#language-code.

 We also have the middleware django.middleware.locale.LocaleMiddleware
 enabled.

 However, in django.utils.translation.trans_real.py in the method
 get_language_from_request(...) it simply falls back to
 settings.LANGUAGE_CODE without any validation. I expected it to check
 whether the language is supported or not in the same manner as for what it
 done for the URL, the cookie and the HTTP header.

 This can easily be tested with curl (for example).

 {{{
 $ curl -v -H "Accept-Language: asd" http://localhost:8000/ -o /dev/null
 * About to connect() to localhost port 8000 (#0)
 *   Trying 127.0.0.1...
   % Total% Received % Xferd  Average Speed   TimeTime Time
 Current
  Dload  Upload   Total   SpentLeft
 Speed
   0 00 00 0  0  0 --:--:-- --:--:-- --:--:--
 0* connected
 * Connected to localhost (127.0.0.1) port 8000 (#0)
 > GET / HTTP/1.1
 > User-Agent: curl/7.27.0
 > Host: localhost:8000
 > Accept: */*
 > Accept-Language: asd
 >
 * additional stuff not fine transfer.c:1037: 0 0
 * additional stuff not fine transfer.c:1037: 0 0
   0 00 00 0  0  0 --:--:--  0:00:01 --:--:--
 0* HTTP 1.0, assume close after body
 < HTTP/1.0 302 FOUND
 < Date: Thu, 07 Feb 2013 08:45:28 GMT
 < Server: WSGIServer/0.1 Python/2.7.3
 < Vary: Cookie
 < Content-Type: text/html; charset=utf-8
 < Location: http://localhost:8000/en-us/
 <
 { [data not shown]
   0 00 00 0  0  0 --:--:--  0:00:01 --:--:--
 0
 * Closing connection #0
 }}}

 Here the client sends a totally unknown language and the server responds
 with redirecting to http://localhost:8000/en-us/ when I expect it to
 redirect to http://localhost:8000/en/

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 720888: Fixed #15808 -- Added optional HttpOnly flag to th...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 720888a14699a80a6cd07d32514b9dcd5b1005fb
  
https://github.com/django/django/commit/720888a14699a80a6cd07d32514b9dcd5b1005fb
  Author: Aymeric Augustin 
  Date:   2013-02-07 (Thu, 07 Feb 2013)

  Changed paths:
M django/conf/global_settings.py
M django/middleware/csrf.py
M docs/ref/contrib/csrf.txt
M docs/ref/settings.txt
M docs/releases/1.6.txt
M tests/regressiontests/csrf_tests/tests.py

  Log Message:
  ---
  Fixed #15808 -- Added optional HttpOnly flag to the CSRF Cookie.

Thanks Samuel Lavitt for the report and Sascha Peilicke for the patch.



-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #15808: CSRF token cookie does not utilize the "Secure" or "HttpOnly" flag

[Django]

#15808: CSRF token cookie does not utilize the "Secure" or "HttpOnly" flag
--+
 Reporter:  Samuel.Lavitt@…   |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  contrib.csrf  |  Version:  1.3
 Severity:  Normal|   Resolution:  fixed
 Keywords:  CSRF Secure HttpOnly  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Aymeric Augustin ):

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


Comment:

 In [changeset:"720888a14699a80a6cd07d32514b9dcd5b1005fb"]:
 {{{
 #!CommitTicketReference repository=""
 revision="720888a14699a80a6cd07d32514b9dcd5b1005fb"
 Fixed #15808 -- Added optional HttpOnly flag to the CSRF Cookie.

 Thanks Samuel Lavitt for the report and Sascha Peilicke for the 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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19762: The Origin Of Tennis And Polo Shirts###

[Django]

#19762: The Origin Of Tennis And Polo Shirts###
-+
 Reporter:  justmitlodo1975  |  Owner:  nobody
 Type:  Uncategorized| Status:  new
Component:  Uncategorized|Version:  1.4
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 Throughout the nineteenth to early twentieth century, tennis players
 usually wore long-sleeved shirts, trousers, and...

 A tennis shirt or also commonly recognized as a polo shirt or a golf
 shirt, is a variety of t-shirt with a collar, normally with some buttons
 down a slit beneath the collar, two modest slits on the bottom of either
 side, and an optional pocket. These shirts are usually created of knitted
 cloth specifically pique cotton or, less typically, silk, merino wool, or
 synthetic fibers.

 During the nineteenth to early twentieth century, tennis players typically
 wore extended-sleeved shirts, trousers, and ties Attire appropriate for
 workplace perform in our modern day society. These formal clothes
 presented a number of troubles for ease of play and comfort on the court.
 The French 7-time Grand Slam tennis champion Ren Lacoste felt that the
 stiff dress shirts and ties of the day have been just too heavy and
 uncomfortable for the tennis court. He began his own line of apparel,
 named Lacoste soon after his namesake and made a loosely-knit pique cotton
 shirt with an un-starched, flat protruding collar and a longer shirt-tail
 in back than in front. The function of the thick pique collar was to
 defend the neck from getting sunburned by the sun. Preceeding Lacostes
 1929 invention of the tennis shirt, polo players generally wore thick
 extended-sleeve shirts created of Oxford-cloth cotton. It is exciting to
 note that this shirt was the very first to have a button-down collar,
 which polo players invented in the late nineteenth century to preserve
 [http://www.youtube.com/watch?v=dWFpOsXhca0 human resources manager] their
 collars from flapping in the wind. Nevertheless, those clothing presented
 a discomfort on the field, and when polo players became conscious of
 Lacostes invention in the 1930s they readily adopted it for use in polo.

 Just before extended, the style of polo shirt and tennis shirt became the
 very same. By the 1950s, polo shirts had been deemed as part of the common
 tennis attire in America. It was hugely sought following. In fact, the
 tennis players also cite their court uniform as a polo shirt, even though
 in reality, the t-shirt was initially designed for tennis and was only
 taken on by polo players a excellent many years later.

 Then Ralph Lauren started a new line of polo shirts and incorporated it
 into his current collection referred to as Polo, in 1967. As a outcome,
 polo shirts became even more popular. Laurens polo shirts were not
 genuinely created for the game, but its design was equivalent to what the
 polo players were wearing at that time.

 Just before long, golfers became aware of the positive aspects of Lacostes
 tennis shirt. As a outcome, when golfs customary put on grew much more
 relaxed and informal some time in the twentieth century, golfers did not
 consider twice about adopting the tennis shirt. Until today, most golfers
 wear absolutely nothing else. For the ladies, they can have their tennis
 shirt custom produced in colors that they like. The only difference is
 that the monicker golf shirts have a variety of golf cuts necessary to
 incorporate into the normal tennis shirts. Nowadays, the tennis shirts
 popularity is so widespread that it has a line of style of its own. Most
 of the principal clothing producers have a version or variation of
 Lacostes tennis shirt given that it is worn extensively by both men and
 girls right now and not necessarily for athletic purposes. Tennis shirts
 are regarded as wise casual put on. A lot of semi-expert and retail
 workers wear tennis shirts to work since round collar t-shirts are deemed
 as well informal and however business suits are also formal.

 Its rough and prepared style also tends to make it a favored shirt for
 these working outdoors, such as field guides and labourers. For the
 duration of the 1990s, the tennis shirt became the standard organization
 informal/casual attire for the higher tech business and then spread to
 other industries. Company logos are often printed on these tennis shirts
 to be utilised as custom corporate apparel. Some government officials in
 India wear tennis shirts as common work attire.

 Tennis shirts are with no doubt very fashionable in sports. Officials such
 as caddies, some retired golf pros, umpires and sports announcers put on
 tennis shirts on a typical basis. In addition to that, tennis shirts are
 also well-liked in several schools, especially junior schools. Each boys
 and girls wear 

[Django] #19761: Home Credit Repair How You Can Take Action All On Your Own ###

[Django]

#19761: Home Credit Repair How You Can Take Action All On Your Own ###
-+
 Reporter:  nexsmitbestbanp1988  |  Owner:  nobody
 Type:  Uncategorized| Status:  new
Component:  Uncategorized|Version:  1.4
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 Self credit repair is actually the only path you can repair your bad
 credit. Although they can give you advice, no one can take action for you.
 You've to really sit back and get a great look at your credit repair and
 then opt for yourself how you want to start tackling the issue. Home
 credit repair isn't that difficult to do, however you do need to make a
 conscientious effort. Home credit restoration works.

 There are instances when everybody else overextends themselves and finds
 [http://rv-hire-florida.atlbusiness.net/rv-rentals-in-orlando-florida/
 company website] that they are short of money. You might have to postpone
 paying double the next and paying one bill this month. But, this results
 in a diminished credit rating and turns up unfavourably on your own credit
 report. It's not too detrimental, bit each month if it occurs, then you do
 have to focus on means of doing self credit repair, if there are only 1 or
 2 items of this nature on your credit report. Focus on your credit report
 and correct it yourself by having a good look at your finances.

 To begin with, begin oneself credit restoration by organizing a monthly
 budget. List them your income and your entire payments. You've to
 incorporate groceries and emergency funds in the list of costs. If your
 expenses amount to a lot more than what you are getting, then you could
 need to avail of professional guidance in the place of doing the credit
 file fix yourself. A counsellor will review the credit report and sit back
 with you. Advice will be offered by he/she about what you can certainly do
 to begin repairing your credit.

 Debt consolidation reduction is one of the ways you can certainly do home
 credit repair. You might say you dont wish to sign up for another mortgage
 and have significantly more funds, but when you pay off all the expenses,
 you're left with one payment. More than likely, the amount is less than
 the total you're spending. Cutting up your credit cards is another means
 of doing credit record repair yourself. Once the temptation to utilize
 them isn't there, most of your payments go to lowering your debt. on time
 even if you make all your payments, it is not just a good strategy to have
 your credit report show that you have used all your available credit. But,
 you can hold one card, in the event a crisis occurs while you're along the
 way of self credit repair.

 Self credit repair is the greatest credit repair, so long as you know very
 well what you're doing.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.