Re: [Django] #21628: Stop using the `imp` module

2014-01-18 Thread Django
#21628: Stop using the `imp` module
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Alex Gaynor ):

 In [changeset:"9d487ae2a16d1efd501e65c78e6885c8cdcd4421"]:
 {{{
 #!CommitTicketReference repository=""
 revision="9d487ae2a16d1efd501e65c78e6885c8cdcd4421"
 Refs #21628 -- removed one usage of the imp module in the tests. It is
 deprecated in Python 3.4
 }}}

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

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


[django/django] 9d487a: Refs #21628 -- removed one usage of the imp module...

2014-01-18 Thread GitHub
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 9d487ae2a16d1efd501e65c78e6885c8cdcd4421
  
https://github.com/django/django/commit/9d487ae2a16d1efd501e65c78e6885c8cdcd4421
  Author: Alex Gaynor 
  Date:   2014-01-18 (Sat, 18 Jan 2014)

  Changed paths:
M tests/template_tests/test_loaders.py

  Log Message:
  ---
  Refs #21628 -- removed one usage of the imp module in the tests. It is 
deprecated in Python 3.4


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


[Django] #21823: Upgrade vendor'd six to latest release

2014-01-18 Thread Django
#21823: Upgrade vendor'd six to latest release
+
   Reporter:  Alex  |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Core (Other)  |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 We currently have 1.4.1 vendored, 1.5.2 is out, it's good to keep up to
 date, if for no other reason than it means less work down the road if we
 ever need a new feature from it.

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

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


Re: [Django] #21823: Upgrade vendor'd six to latest release

2014-01-18 Thread Django
#21823: Upgrade vendor'd six to latest release
--+
 Reporter:  Alex  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Alex):

 * easy:  0 => 1


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

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


Re: [Django] #21821: ORM lookup refactor broke Oracle tests

2014-01-18 Thread Django
#21821: ORM lookup refactor broke Oracle tests
-+-
 Reporter:  timo |Owner:  akaariai
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

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


Comment:

 Thanks, tests are now running. There are some errors of this type:
 {{{
 ==
 ERROR: test_unique_for_date
 (validation.test_unique.PerformUniqueChecksTest)
 --
 Traceback (most recent call last):
   File "/home/tim/code/django/tests/validation/test_unique.py", line 120,
 in test_unique_for_date
 p.full_clean()
   File "/home/tim/code/django/django/db/models/base.py", line 998, in
 full_clean
 self.validate_unique(exclude=exclude)
   File "/home/tim/code/django/django/db/models/base.py", line 808, in
 validate_unique
 date_errors = self._perform_date_checks(date_checks)
   File "/home/tim/code/django/django/db/models/base.py", line 928, in
 _perform_date_checks
 qs = model_class._default_manager.filter(**lookup_kwargs)
   File "/home/tim/code/django/django/db/models/manager.py", line 77, in
 manager_method
 return getattr(self.get_queryset(), name)(*args, **kwargs)
   File "/home/tim/code/django/django/db/models/query.py", line 685, in
 filter
 return self._filter_or_exclude(False, *args, **kwargs)
   File "/home/tim/code/django/django/db/models/query.py", line 703, in
 _filter_or_exclude
 clone.query.add_q(Q(*args, **kwargs))
   File "/home/tim/code/django/django/db/models/sql/query.py", line 1287,
 in add_q
 clause, require_inner = self._add_q(where_part, self.used_aliases)
   File "/home/tim/code/django/django/db/models/sql/query.py", line 1316,
 in _add_q
 current_negated=current_negated, connector=connector)
   File "/home/tim/code/django/django/db/models/sql/query.py", line 1186,
 in build_filter
 condition = self.build_lookup(lookups, col, value)
   File "/home/tim/code/django/django/db/models/sql/query.py", line 1091,
 in build_lookup
 next = lhs.get_lookup(lookup)
   File "/home/tim/code/django/django/db/models/sql/datastructures.py",
 line 25, in get_lookup
 return self.output_type.get_lookup(name)
   File "/home/tim/code/django/django/db/models/lookups.py", line 12, in
 get_lookup
 return self.class_lookups[lookup_name]
 TypeError: unhashable type: 'list'
 }}}
 Let me know if you need more details.

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

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


Re: [Django] #21712: Move admin.autodiscover() to AppConfig.setup()

2014-01-18 Thread Django
#21712: Move admin.autodiscover() to AppConfig.setup()
-+-
 Reporter:  aaugustin|Owner:  aaugustin
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  contrib.admin|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  app-loading  |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Aymeric Augustin ):

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


Comment:

 In [changeset:"10e0cfc0e4e77b85e8261c908baf1c4814ded3f8"]:
 {{{
 #!CommitTicketReference repository=""
 revision="10e0cfc0e4e77b85e8261c908baf1c4814ded3f8"
 Fixed #21712 -- Moved autodiscover() to AdminConfig.ready().

 Thanks Marc Tamlyn for the initial version of 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.7f6fb3f259a503fa7a3029d39fb8c68a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.


[django/django] 74d8fd: Stopped assuming that INSTALLED_APPS only contains...

2014-01-18 Thread GitHub
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 74d8fdcfa6a49cb30210c690dff08fc62b642e2a
  
https://github.com/django/django/commit/74d8fdcfa6a49cb30210c690dff08fc62b642e2a
  Author: Aymeric Augustin 
  Date:   2014-01-18 (Sat, 18 Jan 2014)

  Changed paths:
M tests/runtests.py

  Log Message:
  ---
  Stopped assuming that INSTALLED_APPS only contains app names.

While this assumption is true for the time being, it makes the code
needlessly brittle.


  Commit: 10e0cfc0e4e77b85e8261c908baf1c4814ded3f8
  
https://github.com/django/django/commit/10e0cfc0e4e77b85e8261c908baf1c4814ded3f8
  Author: Aymeric Augustin 
  Date:   2014-01-18 (Sat, 18 Jan 2014)

  Changed paths:
M django/conf/project_template/project_name/settings.py
M django/conf/project_template/project_name/urls.py
M django/contrib/admin/apps.py
M django/contrib/admin/sites.py
M docs/intro/tutorial01.txt
M docs/intro/tutorial03.txt
M docs/ref/contrib/admin/index.txt
M docs/ref/contrib/gis/tutorial.txt
M docs/ref/contrib/index.txt
M docs/releases/1.7.txt

  Log Message:
  ---
  Fixed #21712 -- Moved autodiscover() to AdminConfig.ready().

Thanks Marc Tamlyn for the initial version of the patch.


Compare: https://github.com/django/django/compare/4dc3be250662...10e0cfc0e4e7

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


[django/django] 4dc3be: Fixed typos spotted by Claude Paroz

2014-01-18 Thread GitHub
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 4dc3be250662b4132d8475fb02983a6d8f1eec23
  
https://github.com/django/django/commit/4dc3be250662b4132d8475fb02983a6d8f1eec23
  Author: Anssi Kääriäinen 
  Date:   2014-01-18 (Sat, 18 Jan 2014)

  Changed paths:
M docs/ref/models/custom-lookups.txt
M docs/releases/1.7.txt

  Log Message:
  ---
  Fixed typos spotted by Claude Paroz


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


Re: [Django] #21803: Support post-commit hooks

2014-01-18 Thread Django
#21803: Support post-commit hooks
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

 * cc: charettes (added)


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

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


Re: [Django] #21712: Move admin.autodiscover() to AppConfig.setup()

2014-01-18 Thread Django
#21712: Move admin.autodiscover() to AppConfig.setup()
-+-
 Reporter:  aaugustin|Owner:  aaugustin
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  app-loading  |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by claudep):

 I've only read the patch, but it looks good to me (except reported typos).

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

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


Re: [Django] #21821: ORM lookup refactor broke Oracle tests

2014-01-18 Thread Django
#21821: ORM lookup refactor broke Oracle tests
-+-
 Reporter:  timo |Owner:  akaariai
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Anssi Kääriäinen ):

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


Comment:

 In [changeset:"f468662e2495292356e5fd75241621563893fd4f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f468662e2495292356e5fd75241621563893fd4f"
 Fixed #21821 -- db_type argument for field_cast_sql

 The db_type argument for connection.ops.field_cast_sql wasn't correctly
 set after merge of custom lookups patch.
 }}}

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

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


[django/django] f46866: Fixed #21821 -- db_type argument for field_cast_sq...

2014-01-18 Thread GitHub
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: f468662e2495292356e5fd75241621563893fd4f
  
https://github.com/django/django/commit/f468662e2495292356e5fd75241621563893fd4f
  Author: Anssi Kääriäinen 
  Date:   2014-01-18 (Sat, 18 Jan 2014)

  Changed paths:
M django/db/models/lookups.py

  Log Message:
  ---
  Fixed #21821 -- db_type argument for field_cast_sql

The db_type argument for connection.ops.field_cast_sql wasn't correctly
set after merge of custom lookups 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/52dad3d61af17_1df699fd5497840%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [Django] #21800: CSRF middleware can't get POST data

2014-01-18 Thread Django
#21800: CSRF middleware can't get POST data
--+--
 Reporter:  dirigeant |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by claudep):

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


Comment:

 It is not clear for me if the issue you report is when CSRF middleware is
 or is not in the middleware list in your settings. If it is not in that
 list, you should add it and the ticket is probably invalid. Please
 clarify...

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

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


[Django] #21822: Promote the use of the app config classes for contrib apps

2014-01-18 Thread Django
#21822: Promote the use of the app config classes for contrib apps
-+-
   Reporter:  aaugustin  |  Owner:  nobody
   Type:  New feature| Status:  new
  Component:  Documentation  |Version:  master
   Severity:  Normal |   Keywords:  app-loading
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 #21675 gave all contrib apps an app config class.

 #21712 made `'django.contrib.admin.apps.AdminConfig'` the default in
 `INSTALLED_APPS`.

 We should probably to the same with all other contrib apps.

 This is mostly a documentation patch, plus a small update of the default
 project template.

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

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


Re: [Django] #21712: Move admin.autodiscover() to AppConfig.setup()

2014-01-18 Thread Django
#21712: Move admin.autodiscover() to AppConfig.setup()
-+-
 Reporter:  aaugustin|Owner:  aaugustin
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  app-loading  |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

 * stage:  Accepted => Ready for checkin


Comment:

 New PR: https://github.com/django/django/pull/2182

 I think it's good to go but I would appreciate a proof-read. It's mostly a
 documentation patch.

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

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


Re: [Django] #21712: Move admin.autodiscover() to AppConfig.setup()

2014-01-18 Thread Django
#21712: Move admin.autodiscover() to AppConfig.setup()
-+-
 Reporter:  aaugustin|Owner:  aaugustin
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  app-loading  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by aaugustin):

 It's impossible to make this change in the test suite because it relies on
 the admin autodiscovery not being run.

 The `bug8245` test app contains an invalid admin module that breaks
 autodiscovery.

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

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


Re: [Django] #21794: No warning should be raised when defining an abstract model with no app_label

2014-01-18 Thread Django
#21794: No warning should be raised when defining an abstract model with no
app_label
-+-
 Reporter:  charettes|Owner:  aaugustin
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:  fixed
  (models, ORM)  | Triage Stage:  Ready for
 Severity:  Normal   |  checkin
 Keywords:  app-loading  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Aymeric Augustin ):

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


Comment:

 In [changeset:"2f65b8e14c03a6b43c11d5de791b8d4d91721777"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2f65b8e14c03a6b43c11d5de791b8d4d91721777"
 Fixed #21794 -- Adjusted warning for abstract models.

 As far as I can tell, they don't need an app_label.

 Thanks Simon Charette for the report and 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.1952288ab5957ef165ad0c17c7ee5ab7%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.


[django/django] 2f65b8: Fixed #21794 -- Adjusted warning for abstract mode...

2014-01-18 Thread GitHub
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2f65b8e14c03a6b43c11d5de791b8d4d91721777
  
https://github.com/django/django/commit/2f65b8e14c03a6b43c11d5de791b8d4d91721777
  Author: Aymeric Augustin 
  Date:   2014-01-18 (Sat, 18 Jan 2014)

  Changed paths:
M django/db/models/base.py

  Log Message:
  ---
  Fixed #21794 -- Adjusted warning for abstract models.

As far as I can tell, they don't need an app_label.

Thanks Simon Charette for the report and 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/52dab88637980_55581301d4851183%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.


[Django] #21821: ORM lookup refactor broke Oracle tests

2014-01-18 Thread Django
#21821: ORM lookup refactor broke Oracle tests
-+-
   Reporter:  timo   |  Owner:  akaariai
   Type:  Bug| Status:  new
  Component:  Database   |Version:  master
  layer (models, ORM)|   Keywords:
   Severity:  Release|  Has patch:  0
  blocker|Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 Tests fail to run with the following traceback:
 {{{
 Traceback (most recent call last):
   File "./runtests.py", line 384, in 
 options.failfast, args)
   File "./runtests.py", line 226, in django_tests
 test_labels or get_installed(), extra_tests=extra_tests)
   File "/home/tim/code/django/django/test/runner.py", line 147, in
 run_tests
 old_config = self.setup_databases()
   File "/home/tim/code/django/django/test/runner.py", line 109, in
 setup_databases
 return setup_databases(self.verbosity, self.interactive, **kwargs)
   File "/home/tim/code/django/django/test/runner.py", line 299, in
 setup_databases
 verbosity, autoclobber=not interactive)
   File "/home/tim/code/django/django/db/backends/creation.py", line 367,
 in create_test_db
 test_database=True)
   File "/home/tim/code/django/django/core/management/__init__.py", line
 167, in call_command
 return klass.execute(*args, **defaults)
   File "/home/tim/code/django/django/core/management/base.py", line 291,
 in execute
 output = self.handle(*args, **options)
   File "/home/tim/code/django/django/core/management/commands/migrate.py",
 line 149, in handle
 emit_post_migrate_signal(created_models, self.verbosity,
 self.interactive, connection.alias)
   File "/home/tim/code/django/django/core/management/sql.py", line 244, in
 emit_post_migrate_signal
 using=db)
   File "/home/tim/code/django/django/dispatch/dispatcher.py", line 198, in
 send
 response = receiver(signal=self, sender=sender, **named)
   File "/home/tim/code/django/django/contrib/auth/management/__init__.py",
 line 85, in create_permissions
 ctype = ContentType.objects.db_manager(using).get_for_model(klass)
   File "/home/tim/code/django/django/contrib/contenttypes/models.py", line
 49, in get_for_model
 defaults={'name': smart_text(opts.verbose_name_raw)},
   File "/home/tim/code/django/django/db/models/manager.py", line 77, in
 manager_method
 return getattr(self.get_queryset(), name)(*args, **kwargs)
   File "/home/tim/code/django/django/db/models/query.py", line 416, in
 get_or_create
 return self.get(**lookup), False
   File "/home/tim/code/django/django/db/models/query.py", line 345, in get
 num = len(clone)
   File "/home/tim/code/django/django/db/models/query.py", line 121, in
 __len__
 self._fetch_all()
   File "/home/tim/code/django/django/db/models/query.py", line 962, in
 _fetch_all
 self._result_cache = list(self.iterator())
   File "/home/tim/code/django/django/db/models/query.py", line 264, in
 iterator
 for row in compiler.results_iter():
   File "/home/tim/code/django/django/db/models/sql/compiler.py", line 693,
 in results_iter
 for rows in self.execute_sql(MULTI):
   File "/home/tim/code/django/django/db/models/sql/compiler.py", line 766,
 in execute_sql
 sql, params = self.as_sql()
   File "/home/tim/code/django/django/db/backends/oracle/compiler.py", line
 43, in as_sql
 with_col_aliases=True)
   File "/home/tim/code/django/django/db/models/sql/compiler.py", line 107,
 in as_sql
 where, w_params = self.compile(self.query.where)
   File "/home/tim/code/django/django/db/models/sql/compiler.py", line 78,
 in compile
 return node.as_sql(self, self.connection)
   File "/home/tim/code/django/django/db/models/sql/where.py", line 105, in
 as_sql
 sql, params = qn.compile(child)
   File "/home/tim/code/django/django/db/models/sql/compiler.py", line 78,
 in compile
 return node.as_sql(self, self.connection)
   File "/home/tim/code/django/django/db/models/lookups.py", line 120, in
 as_sql
 lhs_sql = connection.ops.field_cast_sql(db_type, field_internal_type)
 % lhs_sql
   File "/home/tim/code/django/django/db/backends/oracle/base.py", line
 277, in field_cast_sql
 if db_type and db_type.endswith('LOB'):
 AttributeError: 'CharField' object has no attribute 'endswith'
 }}}

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

Re: [Django] #16905: Custom fields and apps should have a way to hook into BaseCommand.validate

2014-01-18 Thread Django
#16905: Custom fields and apps should have a way to hook into 
BaseCommand.validate
-+-
 Reporter:  jdunck   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by russellm):

 A [https://github.com/django/django/pull/2181 pull request] to address
 this issue is now available, and is a candidate for the 1.7 release.

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

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


[Django] #21819: How We Build Mussels Easily With Supplements

2014-01-18 Thread Django
#21819: How We Build Mussels Easily With Supplements
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 how to build muscle with the best muscle building supplements the first
 course that we have got to just its homeport are supplements you two camps
 online one camp says you don't need them in another camp which usually
 sells them that is you absolutely need them well here's think I mean
 either camp I’m in the camp what are your goals and how do we get you
 there fast enough and lot of times they real lot places with you guys
 happy you Xtreme Antler something to really should use supplements for you
 should strongly consider using supplements because they are that affected
 because they can be very helpful.
  York or the reserve for a separate the fact nonfiction and show you how
 courts of things really are because although I'm not there now hot upset
 necessary to achieve a goal they can excel are your results so let's jump
 into it what's with the old standbys so what does research proved beyond a
 shadow of a doubt if we're in the court of law we had action research in
 which supplements build muscle what is proof beyond a shadow Xtreme Antler
 of a doubter reasonable doubt personal creaky monohydrate don't get caught
 up in the Creole clings to the ethyl ester seller the liked creeping to
 the creepy teen strips creaky monohydrate works.

 This is improving time and time again do all those people usually say
 there’s no evidence about it back in a 95-94 creating first email are
 adder all and they've been proven wrong creative monody drat time and time
 again is to compare to the news create things as compared to other
 products always comes out number one its very affordable it's very cheap
 just make sure you get when they had to keep your logo on it and you're
 good those new recruiting that comes out bond with magnesium that actually
 shows a good result Xtreme Antler but I’m not to recommend not yet Press
 she male acid whey protein including together because if you're not
 familiar with that whey protein contains the three branch chain amino
 acids Lucy nice all seem Valley.


 http://www.xtrememusclerecoveryfacts.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.1605d6879889c6653b6c4ef7a763f775%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.


[Django] #21818: Wrinkle removing centre

2014-01-18 Thread Django
#21818: Wrinkle removing centre
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Botox and fillers in the answer is No I've never had any surgery know I
 probably wouldn't have the surgery as I as it stands right now question
 number two is one anti-aging tear then I should give you all and that is
 to you sunscreen is very important it helps protect your skin from the Sun
 from the UK phrase of I see a lot of young women on younger than 40 happen
 very badly damaged skin from the Sun son tries out your skin it gives you
 some spots you run the risk of developing cancer.

  I'm has been proven that some protection factor 30 or higher is very good
 for the skin it gives you a lot of protection and I also recommend that
 women have come with your skin is tea and brown all very beautifully dark
 naturally please use sunscreen brown skin tan skin and dark skin is not
 impervious to the Sun so it’s very important to use sunscreen I'm
 sunscreen volume because the Sun is out all year long question number
 three things if I could change one area aging .

 http://www.equinoxwrinklereducer.org/

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

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


[Django] #21817: Lose Your Weight With Supra Cleanse 350

2014-01-18 Thread Django
#21817: Lose Your Weight With Supra Cleanse 350
---+---
 Reporter:  anonymous  |  Owner:  nobody
 Type:  New feature| Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:  Supra Cleanse 350
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+---
 you learn the easiest way to lose eight pounds nine days if you like me
 you've probably tried many different diets they work for a while that are
 hard to maintain and eventually the way comes back and then some and then
 you back onto some new fad diet only to see the whole process start again
 why do most diets fail most diets fail because they're designed around
 marketing and buzz words rather than educating consumers about the core
 organ in the body cause you to gain or lose fat and what is that critical
 organ is the liver the liver is the key tooth rapid weight loss and long-
 term results the beauty is that by taking care of your liver properly you
 can lose eight pounds or more inane days and after that the week continues
 to come off income of easier than ever before there’s an excellent
 presentation online that explains this in more detail if you click the
 link below you have immediate access to that to that presentation in the
 presentation at the link below a doctor will detail how you can tune up
 your liver to become a fat burning machine or still in join your favorite
 foods formed.

 This has been the key to rapid long-lasting weight loss since discovering
 this better way of looking at how to approach weight loss I've been able
 to easily keep my body in the correct date so I could maintain my ideal
 weight go-ahead and click the link below and have immediate access to this
 presentation there's no requirement that you put in your email or anything
 like that you'll have immediate access to the presentation by clicking the
 link below thanks dust the hired sadly a gain from quick weightless to
 don't all many thanks watching this today’s topic is about how to stay to
 a quick weight loss diet plan the typical quick weight loss diet plan
 we’ll be the healthiest options for you most weightless plans that promise
 overnight success often require you eat nothing but greens or replace all
 your meals with fruit juices whoever if you really need to Shin of anew
 pounds or something important then there are some plans that may just be
 safe as long as you donor do it for prolonged periods of time there are
 safe ways to lose 10 to 20 pounds in a couple weeks without suffering from
 various side effects.

 http://www.supracleanse350facts.org/

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

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


[Django] #21816: Expectations of the beard

2014-01-18 Thread Django
#21816: Expectations of the beard
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 If we want to have a beard quickly expectations can be quite unreasonable.
 After a long night, you will not suddenly become a long beard on your
 face. Therefore count on at least a few days for a good beginner's beard.
 Also look for an appropriate style (see table below). Save your self the
 growth phase itchy back and hood'm not finished. So you never actually get
 that mighty beard.
 beard
 3. Working with facial hair that you have
 Focus not only on the length, but also make use of the facial hair that
 you have. For example, test the different styles and trim the beard so you
 do not get a lot of nice clit. Keeping in shape also promotes growth.
 Therefore, do not be afraid to cut back or cut shape. Invest in a quality
 trimmer. So you are prepared when it comes long hair.
 Beard Trimming
 4. Fill in the blanks
 Suffer you like many other men uneven hair growth? Consider to use the
 beard thicker and fuller look like products. You'll be surprised when you
 find out how short beards, some actually are. Special hair sprays give a
 professional result. 'm Just not overdo it, because you do not want to end
 up with an unnatural-looking beard in a wrong color.
 5. Keep your hair in good condition
 Once you're equipped with these cool beard, you have to keep it in top
 condition. If you do not do this, then there is a chance that thick that
 you have to shave off the beard again and new to begin. Use at night
 before you go to bed castor oil , and it was there the next morning from.
 Do this at the beginning of every day. See you all a successful growth?
 Then you can now take a weekly rhythm.
 Does your facial skin rough and tight on, do not get careless with your
 facial skin. Dry facial skin needs. Much care Test products used first by
 bringing under your jawline. Slightly to So you see quickly whether your
 facial skin against it can or not. 5 glasses of alcohol per week does your
 skin redder colors and leaves behind deep wrinkles. Extra care is needed.
 Moreover, drink plenty of water good for your skin. Dry skin is often a
 lack of moisture and water helps to improve., The moisture level of your
 skin Try an avocado mask on your face. Avocados have naturally high in fat
 and that you could use facial skin. Apply a half ripe, mashed avocado on
 your face and let it soak for 20 to 30 minutes. Rinse your face with
 lukewarm water.
 http://www.oxygeniusspain.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.34f10c8553d98ec462e9dbba506de54d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.


[Django] #21815: Proper nutrition is important for muscle growth !

2014-01-18 Thread Django
#21815: Proper nutrition is important for muscle growth !
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 How do you thin ? Get Free Raw Food Diary How do you thin ? If you want to
 be by adding green smoothies Permanently thinner than click here for
 digital recipe . Download directly or indoors ... If you want a good.
 Categories : Weight Loss , Buy Direct , Categories , Condition, Energy
 Boost , Exercise , Healthy Food , Running , Strength , Exercise , Products
 , Recipes , Smoothies , Sports and Exercise , Fat Burning , Nutrition ,
 Workout | Tags : Lose weight , thin , Running , kettlebell , recipe ,
 smoothies | Permalink

 by Healthy Choices No Comments
 Running for Beginners

 Running for Beginners - You're never too old to start running Running for
 beginners . Running Means positive stress to the body . A challenge for
 the promotion of your own health . If you're just starting out .


 by Healthy Choices No Comments
 Thighs workout at home

 Thighs do you train at home so .. Thighs workout at home . Perhaps you've
 heard of the kettlebell workout . This workout is multifunctional as it
 comes to work different muscle groups . So there is a Legs Program , where
 you.
 Categories : Categories, Fitness, Strength , Exercise , Sports and
 Exercise , Fat Burning | Tags : thighs workout at home , workout thighs at
 home , home workout thighs | Permalink

 by Healthy Choices No Comments
 workout at home

 Workout at home Workout at home . Training at home is becoming
 Increasingly popular . Partly Because of the crisis , this choice is easy
 Because of the costs it saved . Other benefits of a workout to do at home:
 A unique home fitness method , the most popular way of ... Continue
 reading →
 Categories : Lose weight , Categories , Sports and Exercise , Fat Burning
 Workout | Tags : kettlebell , home fit, workout at home | Permalink

 by Healthy Choices No Comments
 Training at home

 Training at home workout at home is simple and you can basically start :
 immediately ! All you need are a few tools zoals a mat or towel and maybe
 some weights to the increasement intensity . The advantage of home
 Categories : Weight Loss , Buy Direct , Categories , Condition, Products ,
 Fat Burning Workout | Tags : kettlebell , lose weight at home , home
 fitness , home workout , workout | Permalink

 by Healthy Choices No Comments
 Cheap sports

 Cheap sports do you do so! Read more soon .. Cheap sports . Cheap sports
 you can easily do it from home if you have good sport. You might think of
 running , cycling or a home fitness program . Every sport costs money .
 Just think
 Categories : Categories, Condition, Fitness, Strength , Exercise , Sports
 and Exercise , Fat Burning Workout | Tags : cheap sports | Permalink

 by Healthy Choices No Comments
 Toned body receive

 Get toned body ? Toned body . How do you get a well toned body ? This is a
 common question thats not actually very kettle to answer . Where you will
 have to work to get a toned body


 http://www.slimtrimpmfacts.org/

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

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


[Django] #21814: Weight Loss

2014-01-18 Thread Django
#21814: Weight Loss
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 The solution is not difficult. It is even quite simple! What you have done
 is very difficult. Too hard!!
 Think of it this way: what all children who are not harassed by
 bullies? Nothing? .
 Exactly! Nothing! They do nothing! Why? Because they will not be bullied!
 How can you do something against bullying if you're not being bullied!
 Only someone who is being bullied can try to stop. So to no longer be
 bullied, you must be someone who does not do anything to make it stop.
 Bullying
 Does this sound confusing? That's all right. I'm sure that you will be
 confused and taken out from the harassment.
 Instruction is given in ten simple parts. As you will see, it is the task
 of doing almost nothing. The commands are all meant to see things
 differently, then do not do what you would have done normally. You save a
 lot of energy and get what you really want. Sound good? That's right
 because it is right!
 You do not need to do right away. All ten classes at once But you would be
 able to read the first five. They are not long and well worth the time.
 The first five lessons give you what you need to stop bullying. If you
 take the other right now wants to read is good, but it's also OK if you
 read them in a week or so. Then you'll be able to see how well the first
 five lessons worked.
 Sooner you start the sooner the misery is over.

 Lesson 1: understand why you are being bullied
 , you probably do not really know why you are being bullied! You may think
 you know, but that's not really so. If you knew, you would not be bullied!
 There is really only one reason why children are bullied every time the
 spool and that is always the same reason, very simple. When you understand
 why you are being bullied bullying would stop. If you really understand at
 all, you can also do the following steps quickly.
 Why are children being bullied?
 Look wears glasses and is called "spectacle Jew." all day
 , he thinks he is so called because he wears glasses. But Look wrong. He
 carries a pair of glasses, but that's not the reason he is being bullied.
 Kim harassed by children who cry, "Your mother is a fat man."
 She thinks the kids insult her because her mother is very thick.
 But that is not so.
 Yeah, her mother is too thick, but that the children do not. Taunting her
 Markel is pushed every day as he stands in line. He does not know why they
 do it.
 The only reason he can think of is because they hate him.
 Markel but wrong.
 Maybe some kids hate him, but that's not the reason they push him.
 Erik is called by his classmates. "Gay" He likes girls and do not know why
 they call it that.
 http://www.dailyfaceliftfacts.co.uk/

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

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


[Django] #21813: Presentation on Eye!

2014-01-18 Thread Django
#21813: Presentation on Eye!
---+
 Reporter:  farialiii  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Most people have five senses. The vision to see, the ear to hear, to smell
 the smell, the taste to taste and feeling to feel. With senses you make
 contact with the world. To
 see you have two eyes. Through the eyes you can recognize people and
 things around you, you Bots example not up against a tree, and you can
 press time stand aside if a car comes at you. If you can not see, for
 example, would bike or a glass of lemonade drink are much more difficult.
 Try a sandwich ready to deal with a blindfold on, then you realize how
 hard it is when you can not see.

 The eye has the form of a sphere. The diameter is two and a half inches.
 To the eye is a solid white layer called the sclera. The front of the eye
 has a translucent layer. That is the cornea.
 Behind the pupil and the iris around it. The iris is the colored part of
 the eye. The iris consists of muscles, the pupil large and small can make.
 The pupil is actually a hole. Behind the iris is the lens.
  the lens ensures that all the light rays fall on the retina. The largest
 part of the eye's back and that is called vitreous humor. The retina
 captures all the light and sends information through the optic nerve
 to the brains. Now I show an eyeball (which I got from the biology
 classroom, where I can get to the show. Their better all things apart

 I have this picture pasted on the board, and copied onto a larger sheet,
 and appropriate things.
 How does the eye.
 iris and the pupil,
 the iris consists of muscles, if the light is pulling the muscles together
 and become the pupil smaller. In the dark, the muscles relax and become
 the pupil larger.
 The lens and the retina,
 . At the edge of the lens, the lens muscles that sphere and less bulb can
 sit The lens bends light, so your images come on the retina. If an object
 is far away, the lens is flat, to get exactly the object on the retina.
 When an object is close, the sphere lens, in order precisely to control
 the object, the retina is composed of two light-sensitive cells on the
 retina. These are rods and cones. Each eye has 120 million rods and 6 to 7
 million cones. The rods can only see black and white. If it is dark then
 you will only see the outline of something or someone. The cones make sure
 that you see colors. They also make sure that you see the little things
 and just see. Move your eyes When you move your eyes that is because the
 eyeball muscles are three pairs that make the eyes move. Both eyes always
 move together. What the eye sees.

 http://www.ecoflexjointpaincream.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.797cdecd8551f2a44a082b898460d744%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.


[Django] #21812: An overview of endurance

2014-01-18 Thread Django
#21812: An overview of endurance
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 •An overview of endurance training tips. One part is also available in:
 Tips .
 Endurance training
 •To build up stamina you need to take time. Only after a few weeks you
 will notice progress. However, endurance also slowly lost: Loss Condition
 .
 •By doing your endurance training in different tempos you train different
 energy systems.
 •Quiet endurance training (rate 1) improve your aerobic endurance,
 especially fat burning is improved and increased capillaries.
 http://www.acaiverdefacts.com/
 Duration: Beginners: 1 to 5 hours, advanced: 1 to 7 hours. Recovery
 Training: below 75% Duration: Beginners: 30 to 60 minutes , advanced: 1 to
 2 hours.
 •Average duration training (speed 2) also improved aerobic endurance
 especially cardiac, lung function and blood circulation improved.
 Duration: Beginners: 45 to 60 minutes, advanced 60 to 90 minutes.
 •Smooth endurance training (speed 3) improve your aerobic endurance and
 aerobic / anaerobic mixed energy systems, especially lactic acid tolerance
 is improved.
 •The tempos (1, 2 and 3) in the endurance training table are based on
 percentages of the anaerobic threshold. The corresponding heart rate
 values are above the rate table.
 •In the tables, the speed (km / h) and heart rate values are most
 important.
 For (much) wind and traffic, the bike speed and cycle times only give a
 good indication. Adjust depending on the wind strength your cycling speed
 and cycle time to emotionally. Or do your workout by using your heart rate
 using a heart rate monitor. If the traffic situation allows (remain
 careful!) Can be used properly. Speeds and times
 •A fairly reliable and easy method to determine the anaerobic threshold
 and a half hours as hard as cycling in a constant speed. The heart that
 you had spent most of the time is your anaerobic threshold heart rate and
 average speed your anaerobic threshold speed.
 •Over time your condition is likely going forward. You should write your
 anaerobic threshold speed (and your bike times) adjust upward. Therefore
 regularly do a test. It is not necessary to go flat. Every time one and a
 half hour It is also intuitively determine your threshold on the basis of
 a shorter test.
 •An estimate of your maximum heart rate is 220-age. This calculation is
 not reliable.
 •Your anaerobic threshold heart rate is approximately equal to 80%
 (beginner) to 90% (advanced) of the maximum heart rate.

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

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


Re: [Django] #21654: Document a use-case for `Form.errors.as_data()`

2014-01-18 Thread Django
#21654: Document a use-case for `Form.errors.as_data()`
--+
 Reporter:  selwin|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timo):

 * component:  Forms => Documentation


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

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


Re: [Django] #21654: Document a use-case for `Form.errors.as_data()`

2014-01-18 Thread Django
#21654: Document a use-case for `Form.errors.as_data()`
--+
 Reporter:  selwin|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Forms |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timo):

 * easy:  1 => 0


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

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


Re: [Django] #21659: password_change_form.html does not use admin_static

2014-01-18 Thread Django
#21659: password_change_form.html does not use admin_static
---+
 Reporter:  mcella |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.6
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"8a34d35696927e1eafce3fdfdd87246b3f189268"]:
 {{{
 #!CommitTicketReference repository=""
 revision="8a34d35696927e1eafce3fdfdd87246b3f189268"
 Fixed #21659 -- Modified the registration/password_change_form.html admin
 template to use {% admin_static %}.

 Thanks mcella.
 }}}

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

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


[django/django] 8a34d3: Fixed #21659 -- Modified the registration/password...

2014-01-18 Thread GitHub
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 8a34d35696927e1eafce3fdfdd87246b3f189268
  
https://github.com/django/django/commit/8a34d35696927e1eafce3fdfdd87246b3f189268
  Author: Tim Graham 
  Date:   2014-01-18 (Sat, 18 Jan 2014)

  Changed paths:
M django/contrib/admin/templates/registration/password_change_form.html

  Log Message:
  ---
  Fixed #21659 -- Modified the registration/password_change_form.html admin 
template to use {% admin_static %}.

Thanks mcella.


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


Re: [Django] #21601: Broken encoding in German translation

2014-01-18 Thread Django
#21601: Broken encoding in German translation
--+
 Reporter:  lfaraone  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Translations  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timo):

 * easy:  1 => 0


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

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


[Django] #21811: 10 tips for your face to clean properly

2014-01-18 Thread Django
#21811: 10 tips for your face  to clean properly
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Everyone knows that it is important to wash your face well, but the
 chances are that you're doing it all wrong. Dr. Macrene Alexiades-
 Armenakas of Yale University points out the biggest mistakes and explains
 how you can solve them.

 1. Choose the right product
 A facial cleanser to clean your skin and prepare for other skin products
 such as lotions or ointments. Therefore, choose a mild, moisturizing
 cleanser that removes oil and debris without making your skin dry., Tense
 or flaky 2. First wash your hands for you to clean your face begins, you
 should thoroughly wash your hands first. You do not want the bacteria are
 transmitted to your hands. 3. Use lukewarm water , it is a myth that you
 have to wash with cold water to close your pores. your face Too cold or
 too hot will make your skin only scare and irritate, with broken
 capillaries result. 4. Soothe your facial cleanser Never apply a facial
 cleanser before you have your face moist. Most cleaners are too hard and
 should be diluted with water. Use a knijpje of your product and create a
 soapy water with your fingers. Apply with a gentle, circular motion to
 dislodge the dirt. 5. Rinse and repeat Retarded product leftovers will dry
 out your skin and clog pores. Keep therefore rinse the cleanser completely
 from your skin away. Do not forget to rinse. Your hairline, neck and the
 sides of your nose These spots are often forgotten, leaving your skin
 becomes irritated there.













 6. Scrub too often
 the ingredients in products should scrub the skin softening by removing
 dead skin cells, but too much scrubbing can remove the new layer and dried
 up. Thereby weakens the natural barrier of the skin. 7. Dump your
 washcloth Your fingertips are always the best choice. If you still can not
 do without washcloth, then you should certainly ensure that it is clean
 and you should not rub it too hard. The skin on your face is very
 delicate, so scrubbing can cause abrasions and wrinkles. 8. Keep the
 moisture Apply a moisturizer if your skin is still damp. This helps ensure
 that the humidity in the balance remains. 9. Trop is too much , your face
 two to three times daily washing is healthy, but too much cleaning
 disrupts your natural barrier. That can create problems such as acne and
 rosacea worse. 10. The evening is crucial Never go to sleep without a
 complete facial cleansing. Pollutants that continue to sit overnight, can
 lead to the build up of mold, redness and other skin problems.


 http://www.tonadermantiaging.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.32fbc32ddb47620a69ac54b5f55d4607%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.


[Django] #21810: Beautiful Skin

2014-01-18 Thread Django
#21810: Beautiful Skin
---+
 Reporter:  alicewmoore@…  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Economy I scan object and your pocket that release casts a shadow
 rejuvenating skin care recipes fight Craig do it yourself skincare track
 formulas okay quite catch ox hair was thrust of that box smart I so
 obviously tech test sure out site speck I have website ask are healthcare
 stocks speck OK Qantas scratch stick trash spank ice’s yes I was telling
 box quite as well of cost s such second choice space I popular I of scrap
 okay at quite ok says hack all properties I hi finally crowd of which hi
 price quality X all ask of happy actual fight cop I got all crime %ah some
 work I just how spot hi of I tackles I crowd of watch finally crowd I
 products CAPREIT sculpture of carry fine re: that where hi II choose how I
 some ask powerful I fact stock caps this is quite for OSC ice how often I
 epic score quiet act crash I crowd Castro x-Pac okay Shyster cry all-star
 I carrots well I quite I'll call knots stride kaka fast all pack starts
 scat I kaka oil whole I'll crossed sick ass also I scary I'll sacked
 hearts.

 http://www.zinncollectionskincare.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.5b440ab7fc53db396a35285f175a7b5b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.


[Django] #21809: Get Skin Care

2014-01-18 Thread Django
#21809: Get Skin Care
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 What makes came McDowell but it should be suited to any irritation or
 leading recommend something like that safety checks on speeds everyday
 birthdays I’m and then I went to use this warning day this is the new
 paradigm of the polo_ and video that's why I’ve been using recently just
 desperate skin and takes off condition quite expensive but neither is
 commander actually and high-performance burned and looted stereotypes and
 cheese this is the extended time x tiny micro particles diamonds murder in
 as with no expenditure it's really find it very powerful Clements muses in
 fifteen minutes using activator it kind of little bit and help six seven
 eight omits way or something about the anyway it's brilliant neighbor I
 don't have any problems with so nasty things in their products and some
 other united because they’re very high winds button saying and acquainted
 with a vengeance so that’s the very nice indeed man I’ve been using a lot
 sofa and he's got a bit of a hundred following the sun he's campaign and
 this is a must mass and just kind of Slavic on and texting tried so a type
 that you caught me if you’re facing she's quite amazing it's extremely
 expanded to much mobs him yeah it has to know quite honestly thought about
 that synthesize at least is four times and if you can see that not
 actually that much missing sank expensive pet there is a man timed at that
 if you've got your concerts are the faces of both quite expensive all
 right we'll stand up in the southbound man treatment last unjustly that's
 unfair eighteen thirty seconds networks and bravery strong and that's not
 expensive at all so that's a really good budget option for you now you say
 you need to use it creates more stress as I’ve got this is the governments
 cannot return power to brings as you can see remedies finally catches this
 again and again scrutinizes like just very energizing explains in my
 skills really bright Southwick so that's the point animus landslides and
 published a selection handed this is the rent Weizmann decreeing quite
 like that something is that the owner under the American presently
 products exhibit greed your home maintenance on the ballot compassion
 which tries to explain introducing dates skin Bernie nothing alike when
 dots that I thought gee products that you could put some as a base not
 necessary as a primer that's instead of more stressor all just off to a
 stressor this is a basket at the second day very nice and it is a credit
 paralyzed facts Spanish in any lights the justice and very succinctly same
 effect that one I’m not will not have is if you've got lazy there is no
 reason moments and memories of many leading satiny bit time that is very
 effective this is the icily radiance immediately put me back to normal
 rituals can really.
 [http://www.dailyfaceliftfacts.co.uk/]

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

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


[Django] #21808: How To Weight Loss?

2014-01-18 Thread Django
#21808: How To Weight Loss?
---+
 Reporter:  ruthmire   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I'm dinner early breakfast or something especially like breakfast really
 helps you lose weight loss don't make it into desert cut I don’t and eat
 um you're foolish are you at lunch first and then there is the only have
 happily when and but not only to see eat your food before you have your
 meal kid irony.

 I don't know let us do it with alternating but I'm pretty sure I'm so sure
 that this is very good for how its stake in general because they if you
 eat your fruits after your meal in your group will have like the function
 religious the oranges you wait and hear something it’s not going to give
 you a much.

 It should have giving you what he did Happy Meal visible have improved
 before your meal and then because then it would-be even in education that
 they're supposed to give you don't skip breakfast

 http://www.zencleansedetoxify.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/051.6ca8184a87b775756be7655830a0707e%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.


[Django] #21807: How to lose weight fast

2014-01-18 Thread Django
#21807: How to lose weight fast
--+---
 Reporter:  anonymous |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  contrib.admin |Version:  1.3-alpha
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+---
 '''I think that really is the secret toot being on a diet and to not
 gaining weight back is recognizing that''' we just take the empty calories
 out a large Diet we don't even have to worry about counting calories at
 all so vegetables there's sweet potatoes eats spinach past Swiss chard
 kale there are a whole green ball hole vegetables for you to try as
 explained in the white refined flour that's used in white bread pasta and
 tortillas is completely stripped all of its fiber its nutrients and this
 refined white flour is Paul love empty calories this means those calories
 turned straight into fat without giving your body in New in nutrition it
 also means that this white bread and white flour products are going to
 significantly spike your blood sugar basically it's like having here we
 find sugar every time.

 '''Now yesterday's the week cars are going to be lower in fat city hires a
 concert down vaster up these days''' where you get into year alternate
 currency last year at Target cardio because this is how we're going to
 need toot was like in love most target lower stomach fat out the last days
 that speeds cheap date now we know the importance as I recovery with you
 saw go into details just understand this is crucial of people think they
 can just skip the Chi better results statute the sketch at its going to
 hit that wall exercised I adaptation you can hit plateau feels fat so make
 sure to incorporate GK section 103 is a seven-step proven formula this all
 about mental tactics in this the same exact formula used by locals ass
 actually built at into their lives it's one thing is for 14 days it’s
 another thing to make it on your lifestyle that's why I seven-step present
 from docent skip this section you dressy a fat loss Catholic a question is
 mental and this Sat step room for me is good teaching I don't know how to
 lose the weight but do keep it off for the long haul not put it to both
 sexes for you the first one scientifically approving unique yes and tricks
 and techniques to the results display..For more details at

 http://www.garciniacambogiapureselectfacts.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.a3822ccd7ca4311b4731aeacdea9835b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.


[Django] #21806: How We Skin Care Easily With Supplements

2014-01-18 Thread Django
#21806: How We Skin Care Easily With Supplements
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 You just need got favors but up well here and also because Apple has wife
 Nancy is that they owe something plastic spool a dollar for this phone
 audience at this point I let the cat have a cupcake tablespoon lunch
 followed disposable details for because it has top I just that makes it
 SEC its it even though I'm it it's going to be already have to keep it on
 your skin right because it just got to find themyeah they have a is simple
 solution for that you can't just squeeze that can just squeaked that just
 got this but they keep us apart a cup just pick other cop piece of clothes
 here and put and blend apple and cut on that piece of clothes just take it
 that's quickly just love it they easy and fast.
 All you can just you just got it's very hard to all plant in just said P
 so I all of this stuff cats of this is a they are can just read it this
 message from that piece of glass and after what to do is this just you get
 there any club got on bus and just keep it inside at but your face father
 and at is less your face got right like this you gonnakeep this often but
 this is not going to travel down on you up-close and their but you just
 got did that got to go inside and but your face you also can do is wait us
 you have to do is find that stuff forget about the necklace to say but
 because nick gets older faster than that face can't and you know on your
 skin to look younger neck has some problems.

 There are really simple steps that you can do to help prevent damage and
 improve eighteen scanned most of the negative changes that we see her skin
 party to external factors like some exposure sifymail secret is preventing
 damage which you can do and say to any age sky hath no the region and
 thanks thriller I know you're good about ten years simple clumsy manure my
 straightening sunscreen and max perfect it's a great foundation ok but to
 find an active part I think about protecting skin anti-oxidants in
 addition to your sunscreen you want to keep the foundation desk in strand
 by stimulating collagen production and you know it's fully are extremely
 bad drag enough content and styles okay Tim smith a brighter skin sensibly
 simple sake.

 http://www.aktivepmantiwrinkle.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.9296f6cce15b9c052381cc34b0c94040%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.


[Django] #21805: Skin Care With Lumanelle

2014-01-18 Thread Django
#21805: Skin Care With Lumanelle
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 The micro or nay from this genetically modified plants it generated our
 DNA in yes we’re becoming pesticide factories you still want to meet the
 GF most of what’s in most grades out there but look the bottom line is it
 raises glucose you know to fix the hormone receptors in the fix the cell.

 We have to get rid of all grains and sugar I spell that out in my book the
 cellular healing diet you know it is an absolute major point it’s the
 800-pound gorilla in anti-aging you better take my advisedly settee organ
 is the next secret is a good one we’re going to break the fat myth because
 the fat myth so many of you.

 http://www.lumanelleskinfacts.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.471a06c06ff71d75fc2979b2ff25cfa9%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [Django] #21794: No warning should be raised when defining an abstract model with no app_label

2014-01-18 Thread Django
#21794: No warning should be raised when defining an abstract model with no
app_label
-+-
 Reporter:  charettes|Owner:  aaugustin
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Ready for
 Severity:  Normal   |  checkin
 Keywords:  app-loading  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by charettes):

 * stage:  Accepted => Ready for checkin


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

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


Re: [Django] #21529: url tag urlencodes arguments irreversibly

2014-01-18 Thread Django
#21529: url tag urlencodes arguments irreversibly
-+-
 Reporter:  leo@…|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.6
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  url tag urlencode|  Needs documentation:  0
  javascript js  |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by timo):

 For the record, this was
 [https://docs.djangoproject.com/en/dev/releases/1.6/#quoting-in-reverse
 introduced in Django 1.6].

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

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


Re: [Django] #21791: RelatedFieldWidgetWrapper object has no attribute decompress

2014-01-18 Thread Django
#21791: RelatedFieldWidgetWrapper object has no attribute decompress
---+--
 Reporter:  DylannCordel   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.6
 Severity:  Normal |   Resolution:  worksforme
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by DylannCordel):

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


Comment:

 Hi,

 The problem seems to be in cmsplugin_filer_image in class FilerImagePlugin
 where "page_link"  is missing from raw_id_fields.
 Maybe RelatedFieldWidgetWrapper really should have his own decompress
 method but I'll investiguate latter (currently, I rush to finish the
 project...).
 I resolve this ticket as "worksforme" and will reopen it if it's necessary
 when I'll be sure there is something to do in Django :).

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

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


[Django] #21804: Gain Strong Muscles

2014-01-18 Thread Django
#21804: Gain Strong Muscles
---+---
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:  xtreme antler
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+---
 You well just busted ability to take this information you do a bit of well
 you want to do patch lasts pal look at this mom 3 scheme freaking huge
 home norm local to that nothing the I'm you math level personal trainer
 Alex. it's a bit new gym is going to be asking a massive certified
 personal trainer number for team Xtreme Antler with him so let's talk
 about don 18 by Tim car which one should I'd be taking for muscle growth
 mass and strength right now right now I’m using full-time full time even
 though.
 I'd even if I don't ring B-fifty time release by me and held my sum what
 does he mean by time-release imp who so you take are the 50 which to the
 complex would be six and 12 I believe and I believe it does it have been
 you want to I could be wrong by I'm sure that must be fifties have band
 own arm if he only has be six to twelve their admin be one into to help
 with break down carbohydrates and proteins for energy are so you good too
 few you work out you know be six and 12 if you're nervous system in for
 and you're going out into production of red blood cells. for more info
 please visit the page below.
 [http://www.xtremeantleraustralia.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.20f45bc53a2803dc7b0509da0c139571%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [Django] #21712: Move admin.autodiscover() to AppConfig.setup()

2014-01-18 Thread Django
#21712: Move admin.autodiscover() to AppConfig.setup()
-+-
 Reporter:  aaugustin|Owner:  aaugustin
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  app-loading  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


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

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


Re: [Django] #21712: Move admin.autodiscover() to AppConfig.setup()

2014-01-18 Thread Django
#21712: Move admin.autodiscover() to AppConfig.setup()
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admin |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  app-loading   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by aaugustin):

 Yes, we must change the default project template. We should also copy-
 paste the usual warnings in the tutorial for people who don't check
 properly what version they're using.

 We've decided to always use `apps.py`. Let's stick with 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.46adf630278b5ce47d731d4c32fbb2c1%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [Django] #21794: No warning should be raised when defining an abstract model with no app_label

2014-01-18 Thread Django
#21794: No warning should be raised when defining an abstract model with no
app_label
-+-
 Reporter:  charettes|Owner:  aaugustin
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  app-loading  |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * easy:  1 => 0
 * stage:  Unreviewed => Accepted


Comment:

 I'm attaching a patch that keeps a warning for abstract models (because
 the behavior will change) but uses a different message.

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

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


Re: [Django] #21794: No warning should be raised when defining an abstract model with no app_label

2014-01-18 Thread Django
#21794: No warning should be raised when defining an abstract model with no
app_label
-+-
 Reporter:  charettes|Owner:  aaugustin
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:  app-loading  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by aaugustin):

 This deprecation aims at getting rid of the legacy "look one level up from
 the package or module named 'models'" behavior. (In the face of ambiguity,
 refuse the temptation to guess.)

 app_label is primarily used to determine which application the model
 should be attached to in the app registry. Since abstract models aren't
 registered, they may work without one, although I'm not sure if there are
 other consequences.

 When this logic goes away, what app_label do we set for abstract models
 that aren't in an installed app and don't have an explicit app_label?
 `Options` has a default value of `None`. I assume we can use 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.17dbfd981141b3a3e6f885b99312e934%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [Django] #21802: Add empty __init__ files to documentaion of custom commands

2014-01-18 Thread Django
#21802: Add empty __init__ files to documentaion of custom commands
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.5
 Severity:  Normal |   Resolution:  wontfix
 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 russellm):

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


Comment:

 I can appreciate that this was probably frustrating, but it reflects a
 fundamental feature of the Python language itself. There's a limit to how
 much of a Python tutorial we can embed into every section of our docs and
 maintain readability.

 For that reason, I'm marking this wontfix.

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

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


Re: [Django] #14051: Signals for transaction commit/rollback

2014-01-18 Thread Django
#14051: Signals for transaction commit/rollback
-+-
 Reporter:  Ask Solem |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Design
 Keywords:   |  decision needed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 I've created a new ticket that asks for the ability to run code after the
 transaction is committed: #21803.

 As far as I understand, that was the original use case here.

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

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


[Django] #21803: Support post-commit hooks

2014-01-18 Thread Django
#21803: Support post-commit hooks
-+-
   Reporter:  aaugustin  |  Owner:  nobody
   Type:  New| Status:  new
  feature|Version:  master
  Component:  Database   |   Keywords:
  layer (models, ORM)|  Has patch:  0
   Severity:  Normal |Needs tests:  0
   Triage Stage: |  Easy pickings:  0
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 We should merge https://github.com/carljm/django-transaction-hooks once it
 has stabilized.

 It looks robust and correctly builds on top of the transaction management
 code.

 See also #14051.

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

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


Re: [Django] #9596: Comparing a DateTimeField to a date is too hard

2014-01-18 Thread Django
#9596: Comparing a DateTimeField to a date is too hard
-+-
 Reporter:  django@… |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  lookup_type date |  Needs documentation:  0
  datetimefield compare comparison   |  Patch needs improvement:  1
  query_term field lookup|UI/UX:  0
Has patch:  1|
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by akaariai):

 Now that #16187 is fixed this should be relatively easy to implement:

 {{{
 class DateTransform(Transform):
 lookup_name = 'as_date'  # or just date, implementer's choice
 output_type = DateField()

 def as_sql(self, qn, connection):
 lhs, lhs_params = qn.compile(self.lhs)
 # Biggest problem is the following line - implement date cast
 template
 # for different backends. MySQL seems to be date(%s), PostgreSQL
 %s::date.
 date_cast_sql = connection.ops.date_cast_template
 return date_cast_template % lhs, lhs_params
 DateTimeField.register_lookup(DateTransform)
 }}}

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

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


Re: [Django] #16187: Refactor lookup system

2014-01-18 Thread Django
#16187: Refactor lookup system
-+-
 Reporter:  UloPe|Owner:  akaariai
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:  fixed
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by Anssi Kääriäinen ):

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


Comment:

 In [changeset:"20bab2cf9d02a5c6477d8aac066a635986e0d3f3"]:
 {{{
 #!CommitTicketReference repository=""
 revision="20bab2cf9d02a5c6477d8aac066a635986e0d3f3"
 Fixed #16187 -- refactored ORM lookup system

 Allowed users to specify which lookups or transforms ("nested lookus")
 are available for fields. The implementation is now class based.

 Squashed commit of the following:

 commit fa7a7195f1952a9c8dea7f6e89ee13f81757eda7
 Author: Anssi Kääriäinen 
 Date:   Sat Jan 18 10:53:24 2014 +0200

 Added lookup registration API docs

 commit eb1c8ce164325e0d8641f14202e12486c70efdb6
 Author: Anssi Kääriäinen 
 Date:   Tue Jan 14 18:59:36 2014 +0200

 Release notes and other minor docs changes

 commit 11501c29c9352d17f22f3a0f59d3b805913dedcc
 Author: Anssi Kääriäinen 
 Date:   Sun Jan 12 20:53:03 2014 +0200

 Forgot to add custom_lookups tests in prev commit

 commit 83173b960ea7eb2b24d573f326be59948df33536
 Author: Anssi Kääriäinen 
 Date:   Sun Jan 12 19:59:12 2014 +0200

 Renamed Extract -> Transform

 commit 3b18d9f3a1bcdd93280f79654eba0efa209377bd
 Author: Anssi Kääriäinen 
 Date:   Sun Jan 12 19:51:53 2014 +0200

 Removed suggestion of temporary lookup registration from docs

 commit 21d0c7631c161fc0c67911480be5d3f13f1afa68
 Merge: 2509006 f2dc442
 Author: Anssi Kääriäinen 
 Date:   Sun Jan 12 09:38:23 2014 -0800

 Merge pull request #2 from mjtamlyn/lookups_3

 Reworked custom lookups docs.

 commit f2dc4429a1da04c858364972eea57a35a868dab4
 Author: Marc Tamlyn 
 Date:   Sun Jan 12 13:15:05 2014 +

 Reworked custom lookups docs.

 Mostly just formatting and rewording, but also replaced the example
 using ``YearExtract`` to  use an example which is unlikely to ever be
 possible directly in the ORM.

 commit 250900650628d1f11beadb22814abd666029fb81
 Author: Anssi Kääriäinen 
 Date:   Sun Jan 12 13:19:13 2014 +0200

 Removed unused import

 commit 4fba5dfaa022653ffa72497258ffd8f8b7476f92
 Author: Anssi Kääriäinen 
 Date:   Sat Jan 11 22:34:41 2014 +0200

 Added docs to index

 commit 6d53963f375c77a1f287833b19b976d23f36c30b
 Author: Anssi Kääriäinen 
 Date:   Sat Jan 11 22:10:24 2014 +0200

 Dead code removal

 commit f9cc0390078e21f1ea5a7bc1f15b09f8f6b0904d
 Author: Anssi Kääriäinen 
 Date:   Sat Jan 11 19:00:43 2014 +0200

 A new try for docs

 commit 33aa18a6e3c831930bda0028222a26f9c1d96e66
 Author: Anssi Kääriäinen 
 Date:   Sat Jan 11 14:57:12 2014 +0200

 Renamed get_cols to get_group_by_cols

 commit c7d5f8661b7d364962bed2e6f81161c1b4f1bcc3
 Author: Anssi Kääriäinen 
 Date:   Sat Jan 11 14:45:53 2014 +0200

 Altered query string customization for backends vendors

 The new way is trying to call first method 'as_' + connection.vendor.
 If that doesn't exist, then call as_sql().

 Also altered how lookup registration is done. There is now
 RegisterLookupMixin class that is used by Field, Extract and
 sql.Aggregate. This allows one to register lookups for extracts and
 aggregates in the same way lookup registration is done for fields.

 commit 90e7004ec14e15503f828cc9bde2a7dab593814d
 Merge: 66649ff f7c2c0a
 Author: Anssi Kääriäinen 
 Date:   Sat Jan 11 13:21:01 2014 +0200

 Merge branch 'master' into lookups_3

 commit 66649ff891c7c73c7eecf6038c9a6802611b5d8a
 Author: Anssi Kääriäinen 
 Date:   Sat Jan 11 13:16:01 2014 +0200

 Some rewording in docs

 commit 31b8faa62714b4b6b6057a9f5cc106c4dd73caab
 Author: Anssi Kääriäinen 
 Date:   Sun Dec 29 15:52:29 2013 +0200

 Cleanup based on review comments

 commit 1016159f34674c0df871ed891cde72be8340bb5d
 Author: Anssi Kääriäinen 
 Date:   Sat Dec 28 18:37:04 2013 +0200

 

Re: [Django] #11722: Query lookups that reference an F() expression produce invalid sql

2014-01-18 Thread Django
#11722: Query lookups that reference an F() expression produce invalid sql
-+-
 Reporter:  plandry@…|Owner:  Anssi
 Type:  Bug  |  Kääriäinen 
Component:  Database layer   |   Status:  closed
  (models, ORM)  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  F() expression   | Triage Stage:  Ready for
  query sql  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Anssi Kääriäinen ):

 * status:  new => closed
 * owner:   => Anssi Kääriäinen 
 * resolution:   => fixed


Comment:

 In [changeset:"20bab2cf9d02a5c6477d8aac066a635986e0d3f3"]:
 {{{
 #!CommitTicketReference repository=""
 revision="20bab2cf9d02a5c6477d8aac066a635986e0d3f3"
 Fixed #16187 -- refactored ORM lookup system

 Allowed users to specify which lookups or transforms ("nested lookus")
 are available for fields. The implementation is now class based.

 Squashed commit of the following:

 commit fa7a7195f1952a9c8dea7f6e89ee13f81757eda7
 Author: Anssi Kääriäinen 
 Date:   Sat Jan 18 10:53:24 2014 +0200

 Added lookup registration API docs

 commit eb1c8ce164325e0d8641f14202e12486c70efdb6
 Author: Anssi Kääriäinen 
 Date:   Tue Jan 14 18:59:36 2014 +0200

 Release notes and other minor docs changes

 commit 11501c29c9352d17f22f3a0f59d3b805913dedcc
 Author: Anssi Kääriäinen 
 Date:   Sun Jan 12 20:53:03 2014 +0200

 Forgot to add custom_lookups tests in prev commit

 commit 83173b960ea7eb2b24d573f326be59948df33536
 Author: Anssi Kääriäinen 
 Date:   Sun Jan 12 19:59:12 2014 +0200

 Renamed Extract -> Transform

 commit 3b18d9f3a1bcdd93280f79654eba0efa209377bd
 Author: Anssi Kääriäinen 
 Date:   Sun Jan 12 19:51:53 2014 +0200

 Removed suggestion of temporary lookup registration from docs

 commit 21d0c7631c161fc0c67911480be5d3f13f1afa68
 Merge: 2509006 f2dc442
 Author: Anssi Kääriäinen 
 Date:   Sun Jan 12 09:38:23 2014 -0800

 Merge pull request #2 from mjtamlyn/lookups_3

 Reworked custom lookups docs.

 commit f2dc4429a1da04c858364972eea57a35a868dab4
 Author: Marc Tamlyn 
 Date:   Sun Jan 12 13:15:05 2014 +

 Reworked custom lookups docs.

 Mostly just formatting and rewording, but also replaced the example
 using ``YearExtract`` to  use an example which is unlikely to ever be
 possible directly in the ORM.

 commit 250900650628d1f11beadb22814abd666029fb81
 Author: Anssi Kääriäinen 
 Date:   Sun Jan 12 13:19:13 2014 +0200

 Removed unused import

 commit 4fba5dfaa022653ffa72497258ffd8f8b7476f92
 Author: Anssi Kääriäinen 
 Date:   Sat Jan 11 22:34:41 2014 +0200

 Added docs to index

 commit 6d53963f375c77a1f287833b19b976d23f36c30b
 Author: Anssi Kääriäinen 
 Date:   Sat Jan 11 22:10:24 2014 +0200

 Dead code removal

 commit f9cc0390078e21f1ea5a7bc1f15b09f8f6b0904d
 Author: Anssi Kääriäinen 
 Date:   Sat Jan 11 19:00:43 2014 +0200

 A new try for docs

 commit 33aa18a6e3c831930bda0028222a26f9c1d96e66
 Author: Anssi Kääriäinen 
 Date:   Sat Jan 11 14:57:12 2014 +0200

 Renamed get_cols to get_group_by_cols

 commit c7d5f8661b7d364962bed2e6f81161c1b4f1bcc3
 Author: Anssi Kääriäinen 
 Date:   Sat Jan 11 14:45:53 2014 +0200

 Altered query string customization for backends vendors

 The new way is trying to call first method 'as_' + connection.vendor.
 If that doesn't exist, then call as_sql().

 Also altered how lookup registration is done. There is now
 RegisterLookupMixin class that is used by Field, Extract and
 sql.Aggregate. This allows one to register lookups for extracts and
 aggregates in the same way lookup registration is done for fields.

 commit 90e7004ec14e15503f828cc9bde2a7dab593814d
 Merge: 66649ff f7c2c0a
 Author: Anssi Kääriäinen 
 Date:   Sat Jan 11 13:21:01 2014 +0200

 Merge branch 'master' into lookups_3

 commit 66649ff891c7c73c7eecf6038c9a6802611b5d8a
 Author: Anssi Kääriäinen 
 Date:   Sat Jan 11 13:16:01 2014 +0200

 Some rewording in docs

 commit 31b8faa62714b4b6b6057a9f5cc106c4dd73caab
 Author: Anssi Kääriäinen 
 Date:   Sun Dec 29 15:52:29 2013 +0200

 Cleanup based on review comments

 commit 

[django/django] 20bab2: Fixed #16187 -- refactored ORM lookup system

2014-01-18 Thread GitHub
  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 20bab2cf9d02a5c6477d8aac066a635986e0d3f3
  
https://github.com/django/django/commit/20bab2cf9d02a5c6477d8aac066a635986e0d3f3
  Author: Anssi Kääriäinen 
  Date:   2014-01-18 (Sat, 18 Jan 2014)

  Changed paths:
M django/contrib/contenttypes/generic.py
M django/contrib/gis/db/backends/mysql/operations.py
M django/contrib/gis/db/backends/oracle/operations.py
M django/contrib/gis/db/backends/postgis/operations.py
M django/contrib/gis/db/backends/spatialite/operations.py
A django/contrib/gis/db/models/constants.py
M django/contrib/gis/db/models/fields.py
A django/contrib/gis/db/models/lookups.py
M django/contrib/gis/db/models/sql/query.py
M django/db/backends/__init__.py
M django/db/backends/postgresql_psycopg2/base.py
M django/db/backends/sqlite3/base.py
M django/db/models/__init__.py
M django/db/models/aggregates.py
M django/db/models/fields/__init__.py
M django/db/models/fields/related.py
A django/db/models/lookups.py
M django/db/models/sql/aggregates.py
M django/db/models/sql/compiler.py
M django/db/models/sql/datastructures.py
M django/db/models/sql/expressions.py
M django/db/models/sql/query.py
M django/db/models/sql/subqueries.py
M django/db/models/sql/where.py
M docs/howto/custom-model-fields.txt
M docs/index.txt
A docs/ref/models/custom-lookups.txt
M docs/ref/models/fields.txt
M docs/ref/models/index.txt
M docs/ref/models/querysets.txt
M docs/releases/1.7.txt
M tests/aggregation/tests.py
A tests/custom_lookups/__init__.py
A tests/custom_lookups/models.py
A tests/custom_lookups/tests.py
M tests/expressions/tests.py
M tests/null_queries/tests.py
M tests/queries/tests.py

  Log Message:
  ---
  Fixed #16187 -- refactored ORM lookup system

Allowed users to specify which lookups or transforms ("nested lookus")
are available for fields. The implementation is now class based.

Squashed commit of the following:

commit fa7a7195f1952a9c8dea7f6e89ee13f81757eda7
Author: Anssi Kääriäinen 
Date:   Sat Jan 18 10:53:24 2014 +0200

Added lookup registration API docs

commit eb1c8ce164325e0d8641f14202e12486c70efdb6
Author: Anssi Kääriäinen 
Date:   Tue Jan 14 18:59:36 2014 +0200

Release notes and other minor docs changes

commit 11501c29c9352d17f22f3a0f59d3b805913dedcc
Author: Anssi Kääriäinen 
Date:   Sun Jan 12 20:53:03 2014 +0200

Forgot to add custom_lookups tests in prev commit

commit 83173b960ea7eb2b24d573f326be59948df33536
Author: Anssi Kääriäinen 
Date:   Sun Jan 12 19:59:12 2014 +0200

Renamed Extract -> Transform

commit 3b18d9f3a1bcdd93280f79654eba0efa209377bd
Author: Anssi Kääriäinen 
Date:   Sun Jan 12 19:51:53 2014 +0200

Removed suggestion of temporary lookup registration from docs

commit 21d0c7631c161fc0c67911480be5d3f13f1afa68
Merge: 2509006 f2dc442
Author: Anssi Kääriäinen 
Date:   Sun Jan 12 09:38:23 2014 -0800

Merge pull request #2 from mjtamlyn/lookups_3

Reworked custom lookups docs.

commit f2dc4429a1da04c858364972eea57a35a868dab4
Author: Marc Tamlyn 
Date:   Sun Jan 12 13:15:05 2014 +

Reworked custom lookups docs.

Mostly just formatting and rewording, but also replaced the example
using ``YearExtract`` to  use an example which is unlikely to ever be
possible directly in the ORM.

commit 250900650628d1f11beadb22814abd666029fb81
Author: Anssi Kääriäinen 
Date:   Sun Jan 12 13:19:13 2014 +0200

Removed unused import

commit 4fba5dfaa022653ffa72497258ffd8f8b7476f92
Author: Anssi Kääriäinen 
Date:   Sat Jan 11 22:34:41 2014 +0200

Added docs to index

commit 6d53963f375c77a1f287833b19b976d23f36c30b
Author: Anssi Kääriäinen 
Date:   Sat Jan 11 22:10:24 2014 +0200

Dead code removal

commit f9cc0390078e21f1ea5a7bc1f15b09f8f6b0904d
Author: Anssi Kääriäinen 
Date:   Sat Jan 11 19:00:43 2014 +0200

A new try for docs

commit 33aa18a6e3c831930bda0028222a26f9c1d96e66
Author: Anssi Kääriäinen 
Date:   Sat Jan 11 14:57:12 2014 +0200

Renamed get_cols to get_group_by_cols

commit c7d5f8661b7d364962bed2e6f81161c1b4f1bcc3
Author: Anssi Kääriäinen 
Date:   Sat Jan 11 14:45:53 2014 +0200

Altered query string customization for backends vendors

The new way is trying to call first method 'as_' + connection.vendor.
If that doesn't exist, then call as_sql().

Also altered how lookup registration is done. There is now
RegisterLookupMixin class that is used by Field, Extract and
sql.Aggregate. This allows one to register lookups for extracts and
aggregates in the same way lookup registration is 

[Django] #21802: Add empty __init__ files to documentaion of custom commands

2014-01-18 Thread Django
#21802: Add empty __init__ files to documentaion of custom commands
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.5
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Hi There
 I got stucked while creating a custom command on django because I forgot
 to add __init__ files on management and commands directories.

 A nice comment telling us to create those files will be nice
 Best Regards
 Zvi Schutz

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

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