[Django] #22042: confused in tutorial 03 about location of mysite/urls.py

[Django]

#22042: confused in tutorial 03 about location of mysite/urls.py
--+-
 Reporter:  jason@…   |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.6
 Severity:  Normal|   Keywords:  tutorial 03
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+-
 Working through the tutorials, I got stuck for a while in this section:

 https://docs.djangoproject.com/en/1.6/intro/tutorial03/#write-your-first-
 view

 Where it asks you to create mysite/urls.py   I made the mistake of
 creating it at the top level of mysite rather than in
 mysite/mysite/urls.py   this led to lots of 404 errors and head
 scratching.

 For a novice like me, it was not clear which mysite directory to put the
 file in. Please consider making it a little more explicit

 thanks.

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

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

[django/django] 007c5c: Updated docs that misreported django.apps.apps.rea...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 007c5cd36762c125102d4f6c48d7e7f42dbfdcff
  
https://github.com/django/django/commit/007c5cd36762c125102d4f6c48d7e7f42dbfdcff
  Author: Simon Meers 
  Date:   2014-02-13 (Thu, 13 Feb 2014)

  Changed paths:
M docs/ref/applications.txt

  Log Message:
  ---
  Updated docs that misreported django.apps.apps.ready as being a method.


-- 
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/52fd769ac2d51_254170bd408597c%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #22041: LayerMapError: Django cannot import shapefile into postgresql

[Django]

#22041: LayerMapError: Django cannot import shapefile into postgresql
---+
 Reporter:  klopycira  |  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 am working on a web-based gis project using geodjango under django 1.6
 framework. . I have using postgresql 9.1 and python 2.7
 while following the tutorial on installing and making first apps in
 django, i have worked on the sample (world, as presented in tutorial) and
 it worked properly. As soon as i have created my own apps using
 srid=32651, I have this error:

 LayerMapError: Could not retrieve geometry from feature

 below are my codes, and i don't know i got my mistake. .
 thanks in advance for helping out. .
 cheers!

 models.py
 {{{
 from django.db import models
 from django.contrib.gis.db import models as gismodels


 class Butuan_Parcel(gismodels.Model):
 newpin = models.CharField(max_length=35)
 geometry = gismodels.MultiPolygonField(srid=32651)
 objects = gismodels.GeoManager()

 def __unicode__(self):
 return self.newpin
 # Create your models here.

 }}}


 settings.py
 {{{
 import os
 from django.contrib.gis.utils import LayerMapping
 from models import Butuan_Parcel

 bound_mapping = {
 'newpin': 'NEWPIN',
 'geometry': 'MULTIPOLYGON',
 }

 bound_shp =
 os.path.abspath(os.path.join(os.path.dirname(__file__),'data/parcels.shp'))

 def run(verbose=True):
 lm = LayerMapping(Butuan_Parcel, bound_shp, bound_mapping,
   transform=False, encoding='iso-8859-1')
 lm.save(strict=True, verbose=verbose)

 }}}




 load.py
 {{{
 import os
 from django.contrib.gis.utils import LayerMapping
 from models import Butuan_Parcel

 bound_mapping = {
 'newpin': 'NEWPIN',
 'geometry': 'MULTIPOLYGON',
 }

 bound_shp =
 os.path.abspath(os.path.join(os.path.dirname(__file__),'data/parcels.shp'))

 def run(verbose=True):
 lm = LayerMapping(Butuan_Parcel, bound_shp, bound_mapping,
   transform=False, encoding='iso-8859-1')
 lm.save(strict=True, verbose=verbose)

 }}}

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

[Django] #22040: RadioSelect options no longer available

[Django]

#22040: RadioSelect options no longer available
---+
 Reporter:  chad@… |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Documentation  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 https://docs.djangoproject.com/en/dev/ref/forms/widgets/#radioselect

 "That included the  tags. To get more granular, you can use each
 radio button’s tag, choice_label and id_for_label attributes. For example,
 this template..."

 id_for_label is no longer present in the code. Or it's returning blank.

 Might want to add that choice_value and index are also available.

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

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

Re: [Django] #20915: Remove django.test.client dependency on django.contrib.auth (and .sessions?)

[Django]

#20915: Remove django.test.client dependency on django.contrib.auth (and
.sessions?)
--+
 Reporter:  ramiro|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Testing framework |  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 carljm):

 Replying to [comment:11 russellm]:
 > I'm thinking of the case where there are *other* apps that need to
 inject functionality into the test client. I'm following the "special
 cases are never *that* special" logic. Auth has a need to inject some
 extra functionality into the test client (however it's done). There's no
 reason to believe that other apps won't have the same need.
 >
 > That said, to my knowledge, there isn't a huge community of 3rd party
 apps waiting to inject functionality into the test client. There's a
 possibility that this is a case of YAGNI.

 It's possible there might be other apps that would use it, but I haven't
 seen the demand. I mean, if people want to add special features to the
 test client they already can subclass it (or monkeypatch it themselves); I
 haven't seen so many people doing that as to justify a new feature
 specifically to support it.

 And what the Zen has to say about special cases is "special cases aren't
 special enough to break the rules", which I think weighs in the opposite
 direction :-)

 > And regardless, this could also be done with subclassing (or mixins).
 >
 > This only gets complicated if there are two or more apps that provide a
 useful mixin - at that point, the end user doesn't have a prey-a-porter
 TestClient class; they need to have a testing utility library that
 composes the TestClient out of all the bits they need.

 True. I guess I don't find that three-liner composition a problematic
 burden, for what I think would be an unusual case.

 > I'm not especially invested in either approach; I don't have the same
 visceral reaction against contribute_to_class, but I can appreciate where
 that reaction comes from.

 `Contribute_to_class` (as its currently used anyway) only touches a class
 that you've already attached something to explicitly. This proposal is for
 outright action-at-a-distance where-the-heck-did-that-come-from
 monkeypatching, which feels quite different to me.

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

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

Re: [Django] #20915: Remove django.test.client dependency on django.contrib.auth (and .sessions?)

[Django]

#20915: Remove django.test.client dependency on django.contrib.auth (and
.sessions?)
--+
 Reporter:  ramiro|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Testing framework |  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 russellm):

 Replying to [comment:10 carljm]:
 > I have trouble seeing the rationale for inventing our own magical
 monkeypatching framework for this specific case, when ordinary Python has
 the tools to solve the problem.

 I'm thinking of the case where there are *other* apps that need to inject
 functionality into the test client. I'm following the "special cases are
 never *that* special" logic. Auth has a need to inject some extra
 functionality into the test client (however it's done). There's no reason
 to believe that other apps won't have the same need.

 That said, to my knowledge, there isn't a huge community of 3rd party apps
 waiting to inject functionality into the test client. There's a
 possibility that this is a case of YAGNI.

 And regardless, this could also be done with subclassing (or mixins).

 This only gets complicated if there are two or more apps that provide a
 useful mixin - at that point, the end user doesn't have a prey-a-porter
 TestClient class; they need to have a testing utility library that
 composes the TestClient out of all the bits they need.

 I'm not especially invested in either approach; I don't have the same
 visceral reaction against contribute_to_class, but I can appreciate where
 that reaction comes from.

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

Re: [Django] #20915: Remove django.test.client dependency on django.contrib.auth (and .sessions?)

[Django]

#20915: Remove django.test.client dependency on django.contrib.auth (and
.sessions?)
--+
 Reporter:  ramiro|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Testing framework |  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 carljm):

 Replying to [comment:9 mjtamlyn]:
 > Russell's approach might be nice if there are other third party apps who
 wish to push utilities into the API. I could imagine a situation where
 something like contrib.admin or an API framework or CMS system could have
 utility assertions for common patterns of testing your configuration of
 them, which might feel appropriate to be client methods.
 >
 > The issue with Carl's suggestion is that if auth provides a subclass and
 any other third party API provides a subclass merging them quickly gets
 boring, although it is the more explicit approach and it would remove the
 dependency more cleanly.

 Boring perhaps, but also trivially easy, takes advantage of ordinary
 Python programming techniques, and has all the flexibility of ordinary
 Python. Especially if the extra features are provided both as a mixin
 class and then as a Client subclass using the mixin.

 I have trouble seeing the rationale for inventing our own magical
 monkeypatching framework for this specific case, when ordinary Python has
 the tools to solve the problem.

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

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

Re: [Django] #20915: Remove django.test.client dependency on django.contrib.auth (and .sessions?)

[Django]

#20915: Remove django.test.client dependency on django.contrib.auth (and
.sessions?)
--+
 Reporter:  ramiro|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Testing framework |  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 mjtamlyn):

 Russell's approach might be nice if there are other third party apps who
 wish to push utilities into the API. I could imagine a situation where
 something like contrib.admin or an API framework or CMS system could have
 utility assertions for common patterns of testing your configuration of
 them, which might feel appropriate to be client methods.

 The issue with Carl's suggestion is that if auth provides a subclass and
 any other third party API provides a subclass merging them quickly gets
 boring, although it is the more explicit approach and it would remove the
 dependency more cleanly.

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

Re: [Django] #20916: Provide a "simple_login" feature for the test client

[Django]

#20916: Provide a "simple_login" feature for the test client
---+
 Reporter:  mjtamlyn   |Owner:  alasdair
 Type:  New feature|   Status:  assigned
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  auth   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by timo):

 I wonder if it might be nice to complete #20915 (remove django.test.client
 dependency on django.contrib.auth) before adding this which is more of
 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/066.994b2bbc4904cbfcc5d4244dc719ec2e%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #22039: Inline Model Admin DatePicker Bug

[Django]

#22039: Inline Model Admin DatePicker Bug
---+--
 Reporter:  smg247 |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Uncategorized  |Version:  1.4
 Severity:  Normal |   Keywords:  Admin Inline
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+--
 In Django 1.4.10. In a TabluarInline, with a datefield or a timefield,
 when extra is set to 0, the DatePicker and TimePicker do not work on any
 new model instances.  They do not input the value chosen into the field.
 If extra is set to 1 or more, the pickers do work, but only on the
 instances that were initially provided; clicking add another 
 and then trying to use a picker on that instance will not work.

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

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

[django/django] 83a3ad: Removed _actions_icnt declaration from local scope...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 83a3add4bed8d8d49f93b30c817c66908b0a26ba
  
https://github.com/django/django/commit/83a3add4bed8d8d49f93b30c817c66908b0a26ba
  Author: Bas Peschier 
  Date:   2014-02-13 (Thu, 13 Feb 2014)

  Changed paths:
M django/contrib/admin/static/admin/js/actions.js

  Log Message:
  ---
  Removed _actions_icnt declaration from local scope in admin JS.

Commit 4523fcd introduces _actions_icnt to the local scope,
which overrides the value set in the HTML.

The admin would incorrectly show selected rows in a change list
as "1 of undefined selected".


-- 
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/52fd1d81a1ee1_2485113dd40108294%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22038: Admin shows selected rows as " of undefined selected"

[Django]

#22038: Admin shows selected rows as " of undefined selected"
---+
 Reporter:  bpeschier  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by bmispelon):

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


Comment:

 Hi,

 Th PR looks good but it'd be better with some tests.
 I was also thinking it might be wise to add a comment on the line where
 `_actions_icnt` is used to indicate that the lack of declaration is on
 purpose.

 I'll mark this as `release blocker` as well so that it doesn't slip
 through the cracks.

 Thanks for catching this.

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

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

[Django] #22038: Admin shows selected rows as " of undefined selected"

[Django]

#22038: Admin shows selected rows as " of undefined selected"
---+
 Reporter:  bpeschier  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  contrib.admin  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  0  |  UI/UX:  0
---+
 Commit
 
https://github.com/django/django/commit/4523fcd60101124a307bd4026296337087b66884
 introduces ```_actions_icnt``` to the local scope, which overrides the
 value set in the HTML.

 The admin will show selected rows in a change list as "1 of undefined
 selected".

 PR under https://github.com/django/django/pull/2274; looking into a test.

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

Re: [Django] #19869: Make changing the active language inside `LiveTestServerCase` possible

[Django]

#19869: Make changing the active language inside `LiveTestServerCase` possible
-+-
 Reporter:  void |Owner:
 Type:  New feature  |  unaizalakain
Component:  Testing framework|   Status:  assigned
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by unaizalakain):

 Well, it surely isn't the most elegant way of doing it but defining some
 special functions for changing the active language when those functions
 already exist doesn't seem right to me either.

 I think disabling the language thread-local in the testing environment
 isn't too bad, after all, it's not needed.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.b5db82d4798e761b8775a3bd7f8a6223%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()`

[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:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by loic84):

 * has_patch:  0 => 1


Comment:

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

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

Re: [Django] #20916: Provide a "simple_login" feature for the test client

[Django]

#20916: Provide a "simple_login" feature for the test client
---+
 Reporter:  mjtamlyn   |Owner:  alasdair
 Type:  New feature|   Status:  assigned
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  auth   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Alasdair):

 That's a good point about the duplication. I'll factor out the common
 functionality.

 There is already documentation and an entry in the release notes in my
 patch. I can work on these if they need improvement.

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

Re: [Django] #21454: Ignoring certain fields on INSERT and UPDATE queries

[Django]

#21454: Ignoring certain fields on INSERT and UPDATE queries
-+-
 Reporter:  mpessas  |Owner:  mpessas
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  oracle   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * needs_better_patch:  0 => 1


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

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

Re: [Django] #19869: Make changing the active language inside `LiveTestServerCase` possible

[Django]

#19869: Make changing the active language inside `LiveTestServerCase` possible
-+-
 Reporter:  void |Owner:
 Type:  New feature  |  unaizalakain
Component:  Testing framework|   Status:  assigned
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by apollo13):

 * cc: apollo13 (added)


Comment:

 I'd very much prefer a method which just sets the active language in the
 other thread as suggested by julien. While the PR might work, it makes me
 run away in fear.

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

[django/django] 474eec: Fixed a typo (I guess).

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 474eeccb52416c24ed375c0026af54e586a67ff3
  
https://github.com/django/django/commit/474eeccb52416c24ed375c0026af54e586a67ff3
  Author: Florian Apolloner 
  Date:   2014-02-13 (Thu, 13 Feb 2014)

  Changed paths:
M django/test/client.py

  Log Message:
  ---
  Fixed a typo (I guess).


-- 
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/52fcf4bd49331_29989dbd40269f6%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16521: Provide keyboard shortcuts in admin

[Django]

#16521: Provide keyboard shortcuts in admin
---+---
 Reporter:  coolRR |Owner:  anonymous
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  1.7-alpha-1
 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:  1
---+---
Changes (by N):

 * version:  1.3 => 1.7-alpha-1


Comment:

 http://www.cheerfulgivers.org/media/#gjch>go to website ambien
 show up urine drug screen - ambien selling price

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

[Django] #22037: Allow testing and dumping legacy database without enabling syncdb

[Django]

#22037: Allow testing and dumping legacy database without enabling syncdb
--+
 Reporter:  ellisd23@…|  Owner:  nobody
 Type:  New feature   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.6
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 I've run into an issue with multiple databases that seems like it could be
 a common enough use case to warrant taking a look at.  I have a legacy
 database that I am using a database router for.  I have reading enabled,
 but I would prefer not to allow syncdb since writing and changing
 structures are handled by the legacy application.

 Still, for basic read operations such as dumpdata, ``allow_syncdb`` is
 checked, as well as when creating test databases.  My Django app depends
 on the working legacy database, thus a test database needs to be created
 as well.

 For now I'm overriding this will a custom setting that is modified at run
 time to indicate whether ``syncdb`` should be allowed, but this is
 obviously not a good long-term solution.

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

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

[django/django] e86aa8: Fixed a link in the 1.7 release notes.

[GitHub]

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

  Changed paths:
M docs/releases/1.7.txt

  Log Message:
  ---
  Fixed a link in the 1.7 release notes.


-- 
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/52fce5b039c74_247c6dfd441052dc%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] f94f46: Fixed #19496 -- Added truncatechars_html filter.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: f94f466cd3461527fb76a3e8951039a3c2388829
  
https://github.com/django/django/commit/f94f466cd3461527fb76a3e8951039a3c2388829
  Author: Jeremy 
  Date:   2014-02-13 (Thu, 13 Feb 2014)

  Changed paths:
M django/template/defaultfilters.py
M django/utils/text.py
M docs/ref/templates/builtins.txt
M docs/releases/1.7.txt
M tests/defaultfilters/tests.py

  Log Message:
  ---
  Fixed #19496 -- Added truncatechars_html filter.

Thanks esevece for the suggestion and  Nick Sandford and Martin Warne
for the inital work on the patch.


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

Re: [Django] #19496: truncatechars_html

[Django]

#19496: truncatechars_html
-+
 Reporter:  esevece  |Owner:  EvilDMP
 Type:  New feature  |   Status:  closed
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  truncatechars| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"f94f466cd3461527fb76a3e8951039a3c2388829"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f94f466cd3461527fb76a3e8951039a3c2388829"
 Fixed #19496 -- Added truncatechars_html filter.

 Thanks esevece for the suggestion and  Nick Sandford and Martin Warne
 for the inital work on 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/065.cc4176dc03afc96869f08c8809f3c0b2%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22035: makemigrations when adding field with a unique_together constraint should create fields before constraints

[Django]

#22035: makemigrations when adding field with a unique_together constraint 
should
create fields before constraints
-+
 Reporter:  SmileyChris  |Owner:  bak1an
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  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 bak1an):

 * has_patch:  0 => 1
 * version:  1.7-alpha-1 => master


Comment:

 [https://github.com/django/django/pull/2272 pull request]

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

Re: [Django] #21952: Deadlock while dispatching signals

[Django]

#21952: Deadlock while dispatching signals
-+
 Reporter:  edevil   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Other) |  Version:  1.6
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  signal deadlock  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by apollo13):

 * cc: apollo13 (added)


Comment:

 I just tried backporting it, but it caused quite a few failures in the
 dispatch tests which I really don't want to debug again :). Since this
 only appears to affect gevent (which Django is completely untested on
 anyways -- although in theory this should affect CPython too) I'll not put
 any further work into this. If you want to give the backporting a shot and
 get the tests passing, I'll happily commit 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/064.f6aa464f21aa0b65b40be8594ea985c0%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #6595: Use the TEST-NET (192.0.2.0/24) IP address block in examples (nit)

[Django]

#6595: Use the TEST-NET (192.0.2.0/24) IP address block in examples (nit)
-+-
 Reporter:  superjudge   |Owner:
 Type:  Bug  |  superjudge
Component:  Database layer   |   Status:  closed
  (models, ORM)  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  RFC5735  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by anonymous):

 * severity:   => Normal
 * component:  Documentation => Database layer (models, ORM)
 * needs_tests:  0 => 1
 * easy:   => 0
 * keywords:   => RFC5735
 * needs_docs:  0 => 1
 * ui_ux:   => 0
 * type:   => Bug
 * stage:  Unreviewed => Accepted


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

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

[django/django] 32a880: [1.6.x] Added a missing import in staticfiles test...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 32a880ae95fe19f0c6383571d4aab58f03044686
  
https://github.com/django/django/commit/32a880ae95fe19f0c6383571d4aab58f03044686
  Author: Tim Graham 
  Date:   2014-02-13 (Thu, 13 Feb 2014)

  Changed paths:
M tests/staticfiles_tests/tests.py

  Log Message:
  ---
  [1.6.x] Added a missing import in staticfiles tests.


-- 
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/52fcc2e1b3ae1_6d6ddfdd386667%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22004: Allow session.modified with an explicit False value to override SESSION_SAVE_EVERY_REQUEST

[Django]

#22004: Allow session.modified with an explicit False value to override
SESSION_SAVE_EVERY_REQUEST
--+--
 Reporter:  bruth |Owner:  johngian
 Type:  Uncategorized |   Status:  assigned
Component:  contrib.sessions  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+--
Changes (by johngian):

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


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

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

Re: [Django] #22004: Allow session.modified with an explicit False value to override SESSION_SAVE_EVERY_REQUEST

[Django]

#22004: Allow session.modified with an explicit False value to override
SESSION_SAVE_EVERY_REQUEST
--+--
 Reporter:  bruth |Owner:  johngian
 Type:  Uncategorized |   Status:  assigned
Component:  contrib.sessions  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+--
Changes (by johngian):

 * cc: johngiannelos@… (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/063.4007fac1081f5f93e0ab85175f5bf5e0%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22035: makemigrations when adding field with a unique_together constraint should create fields before constraints

[Django]

#22035: makemigrations when adding field with a unique_together constraint 
should
create fields before constraints
-+---
 Reporter:  SmileyChris  |Owner:  bak1an
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-alpha-1
 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 bak1an):

 * status:  new => assigned
 * cc: antonbaklanov@… (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * owner:   => bak1an
 * needs_docs:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 I can confirm this on current master.
 Will try to write test+patch for this now.

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

Re: [Django] #21064: The add_view and change_view code in contrib.admin.options share the same code and need to be refactored

[Django]

#21064: The add_view and change_view code in contrib.admin.options share the 
same
code and need to be refactored
--+
 Reporter:  kamni |Owner:  kamni
 Type:  Cleanup/optimization  |   Status:  closed
Component:  contrib.admin |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:  admin | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"390001ce52802a7fa1fceeabfb646e6b32911fb9"]:
 {{{
 #!CommitTicketReference repository=""
 revision="390001ce52802a7fa1fceeabfb646e6b32911fb9"
 Fixed #21064 -- Refactored common logic in ModelAdmin.add_view and
 change_view.
 }}}

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

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

[django/django] 390001: Fixed #21064 -- Refactored common logic in ModelAd...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 390001ce52802a7fa1fceeabfb646e6b32911fb9
  
https://github.com/django/django/commit/390001ce52802a7fa1fceeabfb646e6b32911fb9
  Author: Adam Avramov 
  Date:   2014-02-13 (Thu, 13 Feb 2014)

  Changed paths:
M django/contrib/admin/options.py

  Log Message:
  ---
  Fixed #21064 -- Refactored common logic in ModelAdmin.add_view and 
change_view.


-- 
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/52fcbb279f598_2dcd79dd44590d8%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21952: Deadlock while dispatching signals

[Django]

#21952: Deadlock while dispatching signals
-+
 Reporter:  edevil   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Other) |  Version:  1.6
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  signal deadlock  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by edevil):

 Ping.

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

[Django] #22036: weight loss 12 00

[Django]

#22036: weight loss 12 00
---+-
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:  Super Cleanse Total
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+-
 back in controlto you do next now you'll see them year of her life it
 won't be easy yeah you'll see her two things she neverdreamed she could
 fired leading up to a fine way 365 days Ste alright so I'm 21 and I am 220
 poundsevery way it makes me think honestly because I feel like I'm a
 disappointment no one else in my family is there a wayI am would really be
 of an early I am the one who sticks out here and think home when we sit
 down to eat I eat with the family eats we don't talkabout how morbidly
 obese [http://supercleansetotalfacts.com/ Super Cleanse Total] I am like
 if I didever go away myself out a lot of parents I ever wanted tospoil
 appearance I feel like my whole entire life is adisplay miss like nothing
 mad do I won homecoming queen 01 valedictorian I have a trophy case for
 trophies not that even seems like a true ever compensatefor the fact that
 I am a disappointment because I'll waitand I don't think I could ever
 really make appears crowd until Oct do lose this weight yeah Viet are you
 down white boxy 3 by my you 3 I a.m. the PT sir we're not I want to see TN
 perfect jumpin Jack's ok I get out there at 220 pounds overweight and I
 get outthere talking about access and they are you ready set go why I
 could hear you paint this process takes are against methere's so many
 obese people that passed away because thecomplications because they're
 away I christophe music for this because Idon't wanna be a statistic I
 want this and I need this more than anything where outside Regional School
 where sheteaches a little first-graders PE and she has she has no idea
 that I'mhere some now is bringing yeah Fri Jul she's she's the
 proverbialoverachiever she does everything so well and the one thing that
 she just has notbeen able to conquer is your way she struggled with it all
 her life andshe brought it to me and I read a letter I just knew miss you
 be a perfecttransformation nah class today oh yeah his name Chris grit but
 guess what and choose you yeah I flew all the way across thecountry to get
 yes gonna for yeah Sarah this means that I have a future thatmeans that I
 am sure and I'm until ready for Hannah I in the year many spending a lot
 oftime together over the next year and she's going to go on a lot to be
 and I i now got twelve months your life is going to change for aastarted
 Evans Saturday Iran yeah I guess you might now that I surprise Rachel the
 next stepis due camp I within 24 hours wonderfully LosAngeles one week you
 ready your alright you camp is aone-week crash course where quarter
 individual out to theenvironment which they got past in fewer
 completelyneutral environment where I can keeps them everything that
 theywill need to know to transform all welcome to the California
 healthlongevity Institute well gary phelan I'm feeling good goodI'm ready
 to get ago and I'm ready to get started by growth goes through this so
 much I ready to get started so alongthose lines are I need to know what
 I'm working with I need to a UN so when I want to do iswe're upstairs it
 change damage in the back alrightsounds good our end richard is realize
 yet but just due toher size the city doesn't have a scale that wayon and
 so we need to do on the fates guess and no I'm obese but for me to have
 tostay in their on a scale in a loading dock in Weymouthself boom as some
 believe what I ready to face the scale yes I ambecause I'm ready way for
 I'm on gone on things on on on me on could depress huh 369 helms as
 unbelievable S three people right there no one should ever wear thatmuch
 this is not a lot its own
 http://supercleansetotalfacts.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.cd99890fcf8f97a5ac0d4a4d494b0277%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21951: Docs should assume Python 3 first for __str__/__unicode__ methods

[Django]

#21951: Docs should assume Python 3 first for __str__/__unicode__ methods
--+
 Reporter:  timo  |Owner:  alasdair
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"8aa1efff6d6cb1589a1977f3e68f4c26eb6adc74"]:
 {{{
 #!CommitTicketReference repository=""
 revision="8aa1efff6d6cb1589a1977f3e68f4c26eb6adc74"
 Fixed #21951 -- Updated docs to use __str__ for Python 3

 Thanks Tim Graham for the report and recommendations
 }}}

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

[django/django] 8aa1ef: Fixed #21951 -- Updated docs to use __str__ for Py...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 8aa1efff6d6cb1589a1977f3e68f4c26eb6adc74
  
https://github.com/django/django/commit/8aa1efff6d6cb1589a1977f3e68f4c26eb6adc74
  Author: Alasdair Nicol 
  Date:   2014-02-13 (Thu, 13 Feb 2014)

  Changed paths:
M docs/howto/custom-model-fields.txt
M docs/intro/tutorial01.txt
M docs/ref/contrib/admin/actions.txt
M docs/ref/contrib/admin/index.txt
M docs/ref/contrib/contenttypes.txt
M docs/ref/contrib/gis/commands.txt
M docs/ref/contrib/gis/layermapping.txt
M docs/ref/contrib/gis/tutorial.txt
M docs/ref/forms/api.txt
M docs/ref/forms/fields.txt
M docs/ref/models/instances.txt
M docs/ref/models/querysets.txt
M docs/topics/auth/customizing.txt
M docs/topics/class-based-views/generic-display.txt
M docs/topics/db/examples/many_to_many.txt
M docs/topics/db/examples/many_to_one.txt
M docs/topics/db/examples/one_to_one.txt
M docs/topics/db/models.txt
M docs/topics/db/queries.txt
M docs/topics/forms/modelforms.txt

  Log Message:
  ---
  Fixed #21951 -- Updated docs to use __str__ for Python 3

Thanks Tim Graham for the report and recommendations


-- 
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/52fcb7d17ac0d_29989dbd4020717%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22030: AttributeError: 'CharField' object has no attribute 'swappable_setting'

[Django]

#22030: AttributeError: 'CharField' object has no attribute 'swappable_setting'
-+---
 Reporter:  bmispelon|Owner:
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-alpha-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+---
Changes (by bmispelon):

 * has_patch:  0 => 1


Comment:

 Failing test case and tentative fix there:
 https://github.com/django/django/pull/2270

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

[Django] #22035: makemigrations when adding field with a unique_together constraint should create fields before constraints

[Django]

#22035: makemigrations when adding field with a unique_together constraint 
should
create fields before constraints
-+-
 Reporter:  SmileyChris  |  Owner:
 Type:  Bug  | Status:  new
Component:  Migrations   |Version:  1.7-alpha-1
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 Added a slug field to a Tag model, and a unique_together constraint of
 [('site', 'slug')]

 Running makemigrations resulted in a migration with the operations ordered
 like this:

 {{{
 operations = [
 migrations.AlterUniqueTogether(
 name='tag',
 unique_together=set([(u'site', u'slug')]),
 ),
 migrations.AddField(
 model_name='tag',
 name='slug',
 field=models.SlugField(default=''),
 preserve_default=False,
 ),
 migrations.AlterField(
 model_name='tag',
 name='name',
 field=models.CharField(max_length=20),
 ),
 ]
 }}}

 That choked when running the migration, but manually changing the
 constraint to happen after the field addition worked fine. Apart from the
 fact that I should probably have made this two migrations, would it be
 sensible to order the AlterUniqueTogether operations last?

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

Re: [Django] #10933: Avoid " TypeError: Cannot convert Decimal("0.0000") to Decimal " when the decimal module has been reloaded

[Django]

#10933: Avoid " TypeError: Cannot convert Decimal("0.") to Decimal  " when 
the
decimal module has been reloaded
-+-
 Reporter:  gagravarr|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  dceu2011 |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by anonymous):

 I found this bug in Django 1.6.1, using runserver and sqlite3.

 The model is:

 {{{
 class Car(models.Model):
   price = models.DecimalField(max_digits=7, decimal_places=2)
   maker = models.ForeignKey(CarMaker, null=True, blank=True,
 related_name="%(app_label)s_%(class)s_result")
 }}}

 And the piece of code that raised the exception:

 {{{
 try:
   car1.maker = maker1
   car1.save()
 except:
   # manage error
 }}}

 It raised:

 {{{
 Cannot convert Decimal('3.03') to Decimal
 }}}

 Can provide the whole traceback if needed.

 Can someone change the bug version to 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/067.b481f370efba833406482e6731dadcc3%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22023: .values() followed by defer() or only() results invalid data or crash

[Django]

#22023: .values() followed by defer() or only() results invalid data or crash
-+-
 Reporter:  jtiai|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  orm  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by akaariai):

 I wonder if we should just disallow .only() and .defer() after .values().
 Deferred loading for .values() doesn't seem sensible to me.

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

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

Re: [Django] #22023: .values() followed by defer() or only() results invalid data or crash

[Django]

#22023: .values() followed by defer() or only() results invalid data or crash
-+-
 Reporter:  jtiai|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  orm  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Lauxley):

 woops

 {{{
 --- db/models/query.py
 +++ db/models/query.py
 @@ -956,7 +956,14 @@
  def iterator(self):
 }}}

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

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

[Django] #22034: Checks for ModelAdmin ForeignKeys fail with GenericInlineModelAdmin

[Django]

#22034: Checks for ModelAdmin ForeignKeys fail with GenericInlineModelAdmin
---+
 Reporter:  jwa|  Owner:  nobody
 Type:  Bug| Status:  new
Component:  contrib.admin  |Version:  master
 Severity:  Normal |   Keywords:  checks
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Checks `admin.E202` fail when trying to detect a `ForeignKey` from a
 `GenericInlineModelAdmin`:

 The following setup yields this error:

 {{{
 : (admin.E202) 'app.Bar' has no ForeignKey to
 'app.Foo'.
 }}}

 `models.py`
 {{{
 class Foo(models.Model):
 """Foo may have some Bars."""
 text = models.TextField()

 class Bar(models.Model):
 text = models.TextField()

 content_type = models.ForeignKey(ContentType)
 object_id = models.PositiveIntegerField()
 content_object = generic.GenericForeignKey('content_type',
 'object_id')
 }}}

 `admin.py`
 {{{
 class BarInline(GenericStackedInline):
 model = Bar

 @admin.register(Foo)
 class FooAdmin(admin.ModelAdmin):
 inlines = [BarInline]
 }}}

 I think this will require an exception in `_check_fk_name` for generic
 InlineAdmin classes here:
 
https://github.com/django/django/blob/06bd181f97e5e5561ae7e80efae4c38ee670773f/django/contrib/admin/checks.py#L866

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

[django/django] c3434f: Removed test for migration check forgotten in 7e94...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c3434fed5bb223b2765a85f88053d42b70d81ad9
  
https://github.com/django/django/commit/c3434fed5bb223b2765a85f88053d42b70d81ad9
  Author: Baptiste Mispelon 
  Date:   2014-02-13 (Thu, 13 Feb 2014)

  Changed paths:
R tests/migrations/test_checks.py

  Log Message:
  ---
  Removed test for migration check forgotten in 
7e941ba67ceab8a74ba50509d13ed4298f8305cd.


-- 
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/52fc84523e610_76ed8f9d3c2566%40hookshot-fe7-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22015: Hide relationships with related_name='+' in contrib.admindocs

[Django]

#22015: Hide relationships with related_name='+' in contrib.admindocs
---+
 Reporter:  motiejus   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admindocs  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  1
---+

Comment (by claudep):

 Note that there are also tests in `tests/admin_docs`, notably
 `admin_docs.tests.AdminDocViewTests.test_model_detail`. We'd need a new
 `models.py`, though.

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