date:20140210

[Django] #22007: Mixed import styles (possible OCD on my part)

2014-02-10 Thread Django

#22007: Mixed import styles (possible OCD on my part)
-+-
 Reporter:  kinjal.dixit@…   |  Owner:  nobody
 Type:   | Status:  new
  Cleanup/optimization   |Version:  1.6
Component:  Documentation|   Keywords:  import module, import
 Severity:  Normal   |  script
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  1|  UI/UX:  0
-+-
 I am getting thrown by the documentation
 (https://docs.djangoproject.com/en/1.6/topics/class-based-views/intro
 /#using-class-based-views), when they give this example:

 from django.http import HttpResponse
 from django.views.generic.base import View

 class MyView(View):
 def get(self, request):
 # 
 return HttpResponse('result')

 For the first import, they are specifying only the folder names and
 omitting the actual python script which contains the definition of `class
 HttpResponse`, which is `response.py`.  Here they are relying on the
 `__init__.py` to work.

 For the second import, they are not relying on the `__init__.py` and going
 all the way to specify the python script in which the `class View` is
 defined, which is `base.py`.

 If the first way is preferred, then the second import should be written
 as:

 from django.views.generic import View

 If the second way is preferred, then the first import should be written
 as:

 from django.http.request import HttpRequest

 I know that both are acceptable.  I am just wondering why both are being
 used and not just one style.  I think this is important because this will
 be what people will be writing in the code.

 I would very much love to see this (and other occurrences of this) to be
 identified and cleaned up.

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

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

[Django] #22006: DRY login_required method should be documented

2014-02-10 Thread Django

#22006: DRY login_required method should be documented
---+
 Reporter:  django@…   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 See https://code.djangoproject.com/ticket/16626 for the discussion.

 Currently, the docs suggest decorating each class separately, they should
 also suggest the mixin as recommended in the ticket above, for setting
 `login_required` (or others) on multiple classes.

 Note: Creating a `ProtectedView` superclass and subclassing doesn't work
 for the reason as specified in the `Note` in the current docs:
 https://docs.djangoproject.com/en/dev/topics/class-based-views/intro
 /#decorating-the-class

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

[Django] #22005: PendingDeprecationWarning with management commands.

2014-02-10 Thread Django

#22005: PendingDeprecationWarning with management commands.
-+
 Reporter:  loic84   |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Uncategorized|Version:  master
 Severity:  Release blocker  |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 These happen on a fresh `startproject` created for the occasion and with
 any management command.

 {{{
 $ python -Wall ./manage.py validate
 /Users/loic/Dev/django/django/contrib/contenttypes/models.py:131:
 PendingDeprecationWarning: Model class
 django.contrib.contenttypes.models.ContentType doesn't declare an explicit
 app_label and either isn't in an application in INSTALLED_APPS or else was
 imported before its application was loaded. This will no longer be
 supported in Django 1.9.
   class ContentType(models.Model):
 /Users/loic/Dev/django/django/contrib/auth/models.py:40:
 PendingDeprecationWarning: Model class
 django.contrib.auth.models.Permission doesn't declare an explicit
 app_label and either isn't in an application in INSTALLED_APPS or else was
 imported before its application was loaded. This will no longer be
 supported in Django 1.9.
   class Permission(models.Model):
 /Users/loic/Dev/django/django/contrib/auth/models.py:95:
 PendingDeprecationWarning: Model class django.contrib.auth.models.Group
 doesn't declare an explicit app_label and either isn't in an application
 in INSTALLED_APPS or else was imported before its application was loaded.
 This will no longer be supported in Django 1.9.
   class Group(models.Model):
 /Users/loic/Dev/django/django/contrib/auth/models.py:191:
 PendingDeprecationWarning: Model class
 django.contrib.auth.models.AbstractBaseUser doesn't declare an explicit
 app_label and either isn't in an application in INSTALLED_APPS or else was
 imported before its application was loaded. Its app_label will be set to
 None in Django 1.9.
   class AbstractBaseUser(models.Model):
 /Users/loic/Dev/django/django/contrib/auth/models.py:278:
 PendingDeprecationWarning: Model class
 django.contrib.auth.models.PermissionsMixin doesn't declare an explicit
 app_label and either isn't in an application in INSTALLED_APPS or else was
 imported before its application was loaded. Its app_label will be set to
 None in Django 1.9.
   class PermissionsMixin(models.Model):
 /Users/loic/Dev/django/django/contrib/auth/models.py:353:
 PendingDeprecationWarning: Model class
 django.contrib.auth.models.AbstractUser doesn't declare an explicit
 app_label and either isn't in an application in INSTALLED_APPS or else was
 imported before its application was loaded. Its app_label will be set to
 None in Django 1.9.
   class AbstractUser(AbstractBaseUser, PermissionsMixin):
 /Users/loic/Dev/django/django/contrib/auth/models.py:405:
 PendingDeprecationWarning: Model class django.contrib.auth.models.User
 doesn't declare an explicit app_label and either isn't in an application
 in INSTALLED_APPS or else was imported before its application was loaded.
 This will no longer be supported in Django 1.9.
   class User(AbstractUser):
 System check identified no issues (0 silenced).
 }}}

 fb1e3435a4d7e0265f19a1a9f130c9485fb8dfe9 is a "bad" commit,
 ab922c5cd84d3bde09917b72cfddd8c6a4985f26 is a "good" commit, bisect blames
 d4a5019bef116028edb6e66eac9156da96a3d704. Sadly, since bisect unveils a
 docs-only commit, it may be one of those issue that is hard to reproduce.

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

Re: [Django] #20373: Simple Multi-DB read replica unit test raises TransactionManagementError

2014-02-10 Thread Django

#20373: Simple Multi-DB read replica unit test raises TransactionManagementError
---+--
 Reporter:  TTimo  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by anonymous):

 Also this captcha like math equation for spam often fails here if the
 result is supposed to be a negative number.

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

Re: [Django] #20373: Simple Multi-DB read replica unit test raises TransactionManagementError

2014-02-10 Thread Django

#20373: Simple Multi-DB read replica unit test raises TransactionManagementError
---+--
 Reporter:  TTimo  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by anonymous):

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


Comment:

 I've experienced the same bug on both django 1.5 and django 1.6  I too am
 using multi-db read replica with TEST_MIRROR set.  If I remove the slave
 and the db router the test runs fine.

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

Re: [Django] #22002: AppConfig.ready() and tests

2014-02-10 Thread Django

#22002: AppConfig.ready() and tests
--+
 Reporter:  mjtamlyn  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Release blocker   |   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by russellm):

 Is there a use case driving this? I'm having difficulty thinking of any
 sort of database activity that you would need to do in a ready() method.
 Of course, that's probably due to a lack of imagination on my part.

 Agreed that at the very least, there needs to be docs, even if those docs
 are "don't do 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.e8fa2207040889f0f835553bca0ae4f8%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16617: URLField with min_length or max_length reports wrong length in validation messages

2014-02-10 Thread Django

#16617: URLField with min_length or max_length reports wrong length in 
validation
messages
-+
 Reporter:  frasern  |Owner:  version2beta
 Type:  Bug  |   Status:  new
Component:  Forms|  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
-+

Comment (by sperrygrove):

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

 Makes value available to BaseValidator types for use in the validator
 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/065.a97b653ed4e7aeab3786ba734c804369%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

2014-02-10 Thread 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
---+
Changes (by mjtamlyn):

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


Comment:

 The patch is a good approach, but there is now a large amount of
 duplication between `login` and `simple_login`. Also, the new
 functionality needs both documentation and release notes.

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

Re: [Django] #21942: document Form.clean() in "Forms API" docs

2014-02-10 Thread Django

#21942: document Form.clean() in "Forms API" docs
-+-
 Reporter:  cjerdonek|Owner:  lkitchner
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.6
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
  forms,clean,validation |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-
Changes (by lkitchner):

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


-- 
Ticket URL: 
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.e7dfed112c75984dc9f64fa4d2c8986a%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 (was: Allow session.modified with an explicitl False value to override SESSION_SAVE_EVER

2014-02-10 Thread Django

#22004: Allow session.modified with an explicit False value to override
SESSION_SAVE_EVERY_REQUEST
--+--
 Reporter:  bruth |Owner:  nobody
 Type:  Uncategorized |   Status:  new
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 bruth):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * needs_tests:   => 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/063.1a0e78557ba747841cf0887782ee7cfa%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

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

2014-02-10 Thread Django

#22004: Allow session.modified with an explicitl False value to override
SESSION_SAVE_EVERY_REQUEST
--+
Reporter: bruth | Owner: nobody
Type: Uncategorized | Status: new
Component: contrib.sessions |Version: master
Severity: Normal| Keywords:
Triage Stage: Unreviewed| Has patch: 0
Easy pickings: 1 | UI/UX: 0
--+
This line checks precludes a view that attempts to explicitly set the
`session.modified` attribute to False. The use case I have is have a view
that serves as a "ping" endpoint for session timeouts. The problem is that
if the project setting has the SESSION_SAVE_EVERY_REQUEST set to true,
that view continually reset the session expiry time.

The changes required are to set

[https://github.com/django/django/blob/master/django/contrib/sessions/backends/base.py#L42
this line] to None and

[https://github.com/django/django/blob/master/django/contrib/sessions/middleware.py#L31
this line] to `if modified or (modified is None and
settings.SESSION_SAVE_EVERY_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/048.6eae66f098e0736587fc4f8eb4d812c6%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #22003: LiveServerTestCase with ATOMIC_REQUESTS leaves Postgres connections open after socket error

2014-02-10 Thread Django

#22003: LiveServerTestCase with ATOMIC_REQUESTS leaves Postgres connections open
after socket error
---+
 Reporter:  garron |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Testing framework  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 When using LiveServerTestCase with ATOMIC_REQUESTS, a socket error
 happening in LiveServerThread can result in Postgres connections being
 left open. This results in the removal of the test database failing due to
 those open connections.

 I've attached a sample test which exhibits this issue (when using postgres
 and ATOMIC_REQUESTS). In order for the test to exhibit the issue, there
 must be a view behind the targeted url.

 I've also attached a patch to LiveServerThread that fixes this for 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/049.8301d8b5c807fb3c24225804828d314f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #22002: AppConfig.ready() and tests

2014-02-10 Thread Django

#22002: AppConfig.ready() and tests
+
   Reporter:  mjtamlyn  |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Documentation |Version:  master
   Severity:  Release blocker   |   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 If you do something with the database in AppConfig.ready(), then during
 test runs it runs against the production db as it happens before django
 knows it's testing. I don't think there's any way to change this, but it
 should be documented.

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

Re: [Django] #22001: GeoDjango (contrib.gis) does not create geometry columns in 1.7a2

2014-02-10 Thread Django

#22001: GeoDjango (contrib.gis) does not create geometry columns in 1.7a2
-+
 Reporter:  steko|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  GIS  |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by mjtamlyn):

 * severity:  Normal => Release blocker
 * stage:  Unreviewed => Accepted


Comment:

 I haven't verified this, but assuming it is the case then it's definitely
 a release blocker.

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

Re: [Django] #22001: GeoDjango (contrib.gis) does not create geometry columns in 1.7a2

2014-02-10 Thread Django

#22001: GeoDjango (contrib.gis) does not create geometry columns in 1.7a2
+--
 Reporter:  steko   |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  GIS |  Version:  master
 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 steko):

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


Comment:

 Something went wrong with my submission: apologies.

 sqlmigrate output with PostGIS (index but no column):

 {{{
 CREATE TABLE "elisapp_location" ("id" serial NOT NULL PRIMARY KEY, "name"
 varchar(100) NOT NULL);
 CREATE INDEX "elisapp_location_geom_id" ON "elisapp_location" USING GIST
 ("geom" );
 }}}

 Forgot to add that I am using Python 2.7.5 and Django is installed in a
 virtualenv.

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

[Django] #22001: GeoDjango (contrib.gis) does not create geometry columns in 1.7a2

2014-02-10 Thread Django

#22001: GeoDjango (contrib.gis) does not create geometry columns in 1.7a2
+
 Reporter:  steko   |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  GIS |Version:  master
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 I am testing Django 1.7a2 on a very small project+app.

 So far, with both PostGIS and SpatiaLite I have found the following
 problem. Basically the geometry column is included in the migration.py
 file, but not in the SQL migration.

 models.py:


 {{{
 from django.contrib.gis.db import models

 # Create your models here.

 class Location(models.Model):
 name = models.CharField(max_length=100)
 geom = models.PointField(srid=2100)
 objects = models.GeoManager()

 def __unicode__(self):
 return self.name

 }}}

 0001 myapp/0001_initial.py:

 {{{
 # encoding: utf8
 from django.db import models, migrations
 import django.contrib.gis.db.models.fields


 class Migration(migrations.Migration):

 dependencies = [
 ]

 operations = [
 migrations.CreateModel(
 name='Location',
 fields=[
 (u'id', models.AutoField(verbose_name=u'ID',
 serialize=False, auto_created=True, primary_key=True)),
 ('name', models.CharField(max_length=100)),
 ('geom',
 django.contrib.gis.db.models.fields.PointField(srid=2100)),
 ],
 options={
 },
 bases=(models.Model,),
 ),
 ]
 }}}

 Output from sqlmigrate:

 {{{
 (venv)[steko@ogma myproject]$ python manage.py sqlmigrate myapp 0001
 CREATE TABLE "myapp_location" ("id" integer NOT NULL PRIMARY KEY
 AUTOINCREMENT, "name" varchar(100) NOT NULL);
 }}}

 This happens both with PostGIS and SpatiaLite. Perhaps obvious: it works
 well with Django 1.6. My current system is Fedora 20.

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

Re: [Django] #21661: Password reset part of django.auth isn't documented

2014-02-10 Thread Django

#21661: Password reset part of django.auth isn't documented
--+
 Reporter:  cortex@…  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.6
 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
--+

Comment (by mrchrisadams):

 Hi Timo, thanks for letting me know about the reset instructions with the
 admin.

 I think I have enough to have a stab this week at fleshing this out and
 submitting a PR.

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

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

Re: [Django] #21661: Password reset part of django.auth isn't documented

2014-02-10 Thread Django

#21661: Password reset part of django.auth isn't documented
-+-
 Reporter:  cortex@… |Owner:
 Type:   |  mrchrisadams
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.6
 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 mrchrisadams):

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


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

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

Re: [Django] #21996: UnicodeDecodeError when calling GeoIP.country

2014-02-10 Thread Django

#21996: UnicodeDecodeError when calling GeoIP.country
-+-
 Reporter:  Florent Messa|Owner:  claudep
    |   Status:  closed
 Type:  Bug  |  Version:  1.6
Component:  GIS  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Claude Paroz ):

 In [changeset:"76700c5437d4b5187f58a3f99104f45002d1524e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="76700c5437d4b5187f58a3f99104f45002d1524e"
 [1.6.x] Fixed #21996 -- Used proper encoding for GeoIP content

 Thanks Florent Messa for the report.
 Backport of fb1e3435a4 from master.
 }}}

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

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

Re: [Django] #7835: Provide the ability for model definitions that are only availably during testing

2014-02-10 Thread Django

#7835: Provide the ability for model definitions that are only availably during
testing
-+
 Reporter:  russellm |Owner:  kkubasik
 Type:  New feature  |   Status:  new
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  feature test models  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by JocelynD):

 However, I don't know why but when using south, the "Test Models in
 tests.py" trick does not work (table is not created), so you have to put
 in your ''settings.py'' the following :


 {{{
 SOUTH_TESTS_MIGRATE = False
 }}}


 to disable the south migrations for the test db.

 (which will anyway save you some cpu time...)

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

[django/django] e9ffe7: [1.6.x] Added 1.6.3 release notes stub

2014-02-10 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: e9ffe7e3c8e8fefa1f5675a30016740d6c812cca
  
https://github.com/django/django/commit/e9ffe7e3c8e8fefa1f5675a30016740d6c812cca
  Author: Claude Paroz 
  Date:   2014-02-10 (Mon, 10 Feb 2014)

  Changed paths:
A docs/releases/1.6.3.txt

  Log Message:
  ---
  [1.6.x] Added 1.6.3 release notes stub


  Commit: 76700c5437d4b5187f58a3f99104f45002d1524e
  
https://github.com/django/django/commit/76700c5437d4b5187f58a3f99104f45002d1524e
  Author: Claude Paroz 
  Date:   2014-02-10 (Mon, 10 Feb 2014)

  Changed paths:
M django/contrib/gis/geoip/prototypes.py
M django/contrib/gis/geoip/tests.py
M docs/releases/1.6.3.txt

  Log Message:
  ---
  [1.6.x] Fixed #21996 -- Used proper encoding for GeoIP content

Thanks Florent Messa for the report.
Backport of fb1e3435a4 from master.


Compare: https://github.com/django/django/compare/dbb9819360bc...76700c5437d4

-- 
You received this message because you 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/52f8ec97f16c_7b759d9d3825091%40hookshot-fe11-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21996: UnicodeDecodeError when calling GeoIP.country

2014-02-10 Thread Django

#21996: UnicodeDecodeError when calling GeoIP.country
-+-
 Reporter:  Florent Messa|Owner:  claudep
    |   Status:  closed
 Type:  Bug  |  Version:  1.6
Component:  GIS  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"fb1e3435a4d7e0265f19a1a9f130c9485fb8dfe9"]:
 {{{
 #!CommitTicketReference repository=""
 revision="fb1e3435a4d7e0265f19a1a9f130c9485fb8dfe9"
 Fixed #21996 -- Used proper encoding for GeoIP content

 Thanks Florent Messa for the report.
 }}}

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

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

[django/django] ee9fcb: Fixed #17673 -- Forbid field shadowing.

2014-02-10 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ee9fcb1672ddf5910ed8c45c37a00f32ebbe2bb1
  
https://github.com/django/django/commit/ee9fcb1672ddf5910ed8c45c37a00f32ebbe2bb1
  Author: Christopher Medrela 
  Date:   2014-02-10 (Mon, 10 Feb 2014)

  Changed paths:
M django/db/models/base.py
M django/db/models/fields/__init__.py
M docs/releases/1.7.txt
M tests/invalid_models_tests/test_models.py
M tests/model_inheritance/models.py
M tests/model_inheritance/tests.py

  Log Message:
  ---
  Fixed #17673 -- Forbid field shadowing.

Thanks Anssi Kääriäinen for the suggestion.


-- 
You received this message because you 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/52f8eb02bdcb2_14217ddd401027d1%40hookshot-fe12-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] c3dd38: Added 1.6.3 release notes stub

2014-02-10 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c3dd38c57427f2d51222b4789137848f5a3194e7
  
https://github.com/django/django/commit/c3dd38c57427f2d51222b4789137848f5a3194e7
  Author: Claude Paroz 
  Date:   2014-02-10 (Mon, 10 Feb 2014)

  Changed paths:
A docs/releases/1.6.3.txt

  Log Message:
  ---
  Added 1.6.3 release notes stub


  Commit: fb1e3435a4d7e0265f19a1a9f130c9485fb8dfe9
  
https://github.com/django/django/commit/fb1e3435a4d7e0265f19a1a9f130c9485fb8dfe9
  Author: Claude Paroz 
  Date:   2014-02-10 (Mon, 10 Feb 2014)

  Changed paths:
M django/contrib/gis/geoip/prototypes.py
M django/contrib/gis/geoip/tests.py
M docs/releases/1.6.3.txt

  Log Message:
  ---
  Fixed #21996 -- Used proper encoding for GeoIP content

Thanks Florent Messa for the report.


Compare: https://github.com/django/django/compare/ee9fcb1672dd...fb1e3435a4d7

-- 
You received this message because you 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/52f8ebb2a2b75_555f23d3410283a%40hookshot-fe8-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17673: Forbid field shadowing in model multi-inheritance

2014-02-10 Thread Django

#17673: Forbid field shadowing in model multi-inheritance
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  validation   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"ee9fcb1672ddf5910ed8c45c37a00f32ebbe2bb1"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ee9fcb1672ddf5910ed8c45c37a00f32ebbe2bb1"
 Fixed #17673 -- Forbid field shadowing.

 Thanks Anssi Kääriäinen for the suggestion.
 }}}

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

Re: [Django] #6630: Fieldsets for newforms

2014-02-10 Thread Django

#6630: Fieldsets for newforms
-+-
 Reporter:  Petr Marhoun |Owner:  nobody
     |   Status:  new
 Type:  New feature  |  Version:  master
Component:  Forms|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  feature  |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  1
Easy pickings:  0|
-+-
Changes (by rm_):

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

Re: [Django] #17301: Defining fieldsets in a form class

2014-02-10 Thread Django

#17301: Defining fieldsets in a form class
-+-
 Reporter:  msiedlarek   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  form, forms, | Triage Stage:  Accepted
  fieldsets  |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by rm_):

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

Re: [Django] #18714: Add an option to compilemessages to compile fuzzy translations

2014-02-10 Thread Django

#18714: Add an option to compilemessages to compile fuzzy translations
-+-
 Reporter:  rasca|Owner:  bak1an
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  compilemessages  |  Needs documentation:  0
  fuzzy msgfmt   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by bak1an):

 * needs_better_patch:  1 => 0


Comment:

 [https://github.com/django/django/pull/2259 new, rebased 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/063.8e3282ebb721eadc5cb693f997684865%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #3254: [patch] experimental fulltext search support for postgres, oracle and mssql

2014-02-10 Thread Django

#3254: [patch] experimental fulltext search support for postgres, oracle and 
mssql
-+-
 Reporter:  Ronny Pfannschmidt   |Owner:  mjtamlyn
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  oracle fulltext  |  Needs documentation:  1
  search |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-
Changes (by mjtamlyn):

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


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

[Django] #22000: 'ModelChoiceField' object has no attribute 'to_field_name'

2014-02-10 Thread Django

#22000: 'ModelChoiceField' object has no attribute 'to_field_name'
+
 Reporter:  anonymous   |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Forms   |Version:  1.6
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 Hello,

 I am getting the error, [ 'ModelChoiceField' object has no attribute
 'to_field_name' ],
 when I try to use the following model (from an open source library) in the
 ModelChoiceField with python 2.7.3

 This is the model in question.
 https://sourcegraph.com/github.com/celery/django-
 celery/symbols/python/djcelery/models/IntervalSchedule#examples

 This is the code that causes the error in a form. (The original code was a
 form that inherited from the ModelChoiceField, but ModelChoiceField itself
 also gives the error. )
 {{{#!python
 widgets={'interval': ModelChoiceField(
 queryset=IntervalSchedule.objects.all(), empty_label=" :-( ")}
 }}}
 The modelform, based on PeriodicTask in which the widget is changed, is
 called by modelformset_factory.
 (from djcelery.models import PeriodicTask, IntervalSchedule )

 /usr/local/lib/python2.7/dist-packages/django/forms/models.py in
 prepare_value

   {{{#!python
 def prepare_value(self, value):
 if hasattr(value, '_meta'):
 if self.to_field_name:
 return value.serializable_value(self.to_field_name)
 else:
 return value.pk
 return super(ModelChoiceField, self).prepare_value(value)
 }}}

 Django Version: 1.6
 Exception Type: AttributeError
 Exception Value:
 'ModelChoiceField' object has no attribute 'to_field_name'
 Exception Location: /usr/local/lib/python2.7/dist-
 packages/django/forms/models.py in prepare_value, line 1115
 Python Executable:  /usr/bin/python
 Python Version: 2.7.3

 I do see the to_field_name in the code on
 https://github.com/django/django/blob/stable/1.6.x/django/forms/models.py
 but it is initialized on init.

 So could this be race condition bug?
 (Since I don't get the error with the roughly same code if the widget is
 not changed. )

 (Am not clicking easy pickings due to the possibility of it being a race
 bug. Getting the to_field_name out of the init and into the class would be
 easy enough to fix this bug, but if something else is going on... )

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

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

[django/django] f5123c: Fixed #21371 -- Added the block.super to admin bod...

2014-02-10 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: f5123c7291e855713b59e739bad0e50a1d50d3ef
  
https://github.com/django/django/commit/f5123c7291e855713b59e739bad0e50a1d50d3ef
  Author: julien 'pouete' Godin 
  Date:   2014-02-10 (Mon, 10 Feb 2014)

  Changed paths:
M django/contrib/admin/templates/admin/app_index.html
M django/contrib/admin/templates/admin/auth/user/change_password.html
M django/contrib/admin/templates/admin/change_form.html
M django/contrib/admin/templates/admin/change_list.html
M django/contrib/admin/templates/admin/delete_confirmation.html
M django/contrib/admin/templates/admin/delete_selected_confirmation.html
M django/contrib/admin/templates/admin/index.html
M django/contrib/admin/templates/admin/login.html
A tests/admin_views/templates/admin/base_site.html
M tests/admin_views/tests.py

  Log Message:
  ---
  Fixed #21371 -- Added the block.super to admin bodyclass blocks.

Thanks Keryn Knight for the report.


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

Re: [Django] #21371: Admin templates use a `bodyclass` block without ever calling super.

2014-02-10 Thread Django

#21371: Admin templates use a `bodyclass` block without ever calling super.
-+-
 Reporter:  Keryn Knight |Owner:  resry
   |   Status:  closed
 Type:   |  Version:  master
  Cleanup/optimization   |   Resolution:  fixed
Component:  contrib.admin| Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"f5123c7291e855713b59e739bad0e50a1d50d3ef"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f5123c7291e855713b59e739bad0e50a1d50d3ef"
 Fixed #21371 -- Added the block.super to admin bodyclass blocks.

 Thanks Keryn Knight for the report.
 }}}

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

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

[Django] #21999: have filter_horizontal / filter_vertical work with ForeignKey

2014-02-10 Thread Django

#21999: have filter_horizontal / filter_vertical work with ForeignKey
---+--
 Reporter:  rm_|  Owner:  nobody
 Type:  New feature| Status:  new
Component:  contrib.admin  |Version:  master
 Severity:  Normal |   Keywords:  admin FilteredSelectMultiple
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+--
 When you have many values for a ForeignKey the ability to filter it comes
 very handy.

 From a quick look at the code this is what is required:
 - update contrib/admin/checks.py, contrib/admin/validation.py,
 contrib/admin/options.py to permit filter_* on ForeignKeys
 - make FilteredSelectMultiple accept a max_entries limit so that a
 ForeignKey is limited to 1 filtered entry but a ManyToMany may have any
 limit > 1
 - have the javascript work accordingly with the aforementioned limit

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

[django/django] 59d9b2: Fixed #21190 -- Added a new ePub theme for documen...

2014-02-10 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 59d9b264745bb1a4736bb6df4dafb83049835483
  
https://github.com/django/django/commit/59d9b264745bb1a4736bb6df4dafb83049835483
  Author: Markus Amalthea Magnuson 
  Date:   2014-02-10 (Mon, 10 Feb 2014)

  Changed paths:
A docs/_theme/djangodocs-epub/epub-cover.html
A docs/_theme/djangodocs-epub/static/docicons-behindscenes.png
A docs/_theme/djangodocs-epub/static/docicons-note.png
A docs/_theme/djangodocs-epub/static/docicons-philosophy.png
A docs/_theme/djangodocs-epub/static/docicons-warning.png
A docs/_theme/djangodocs-epub/static/epub.css
A docs/_theme/djangodocs-epub/theme.conf
M docs/conf.py

  Log Message:
  ---
  Fixed #21190 -- Added a new ePub theme for documentation.


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

Re: [Django] #21190: Fix broken ePub documentation by adding a proper theme for it

2014-02-10 Thread Django

#21190: Fix broken ePub documentation by adding a proper theme for it
-+
 Reporter:  giuliettamasina  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Documentation|  Version:  1.5
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"59d9b264745bb1a4736bb6df4dafb83049835483"]:
 {{{
 #!CommitTicketReference repository=""
 revision="59d9b264745bb1a4736bb6df4dafb83049835483"
 Fixed #21190 -- Added a new ePub theme for 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/073.d9a6c8dcd9fd975e07f602aba176b4a9%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 9a4ee8: Fixed #21994 -- Added form_dict argument to calls ...

2014-02-10 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 9a4ee8ddb858ae07ff42be0261c867aa3d2eb53c
  
https://github.com/django/django/commit/9a4ee8ddb858ae07ff42be0261c867aa3d2eb53c
  Author: Julian Wachholz 
  Date:   2014-02-10 (Mon, 10 Feb 2014)

  Changed paths:
M django/contrib/formtools/tests/wizard/namedwizardtests/forms.py
M django/contrib/formtools/tests/wizard/namedwizardtests/tests.py
M django/contrib/formtools/wizard/views.py
M docs/ref/contrib/formtools/form-wizard.txt
M docs/releases/1.7.txt

  Log Message:
  ---
  Fixed #21994 -- Added form_dict argument to calls of WizardView.done()

Added an additional keyword argument ``form_dict`` to calls of
WizardView.done() implementations which allows easier access to validated
forms by their step name.


-- 
You received this message because you 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/52f8c675ad2a8_6f691465d382912d%40hookshot-fe10-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21994: Pass a dict of forms to WizardView.done()

2014-02-10 Thread Django

#21994: Pass a dict of forms to WizardView.done()
---+
 Reporter:  jwa|Owner:  jwa
 Type:  New feature|   Status:  closed
Component:  contrib.formtools  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords:  formtools wizard   | 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:"9a4ee8ddb858ae07ff42be0261c867aa3d2eb53c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="9a4ee8ddb858ae07ff42be0261c867aa3d2eb53c"
 Fixed #21994 -- Added form_dict argument to calls of WizardView.done()

 Added an additional keyword argument ``form_dict`` to calls of
 WizardView.done() implementations which allows easier access to validated
 forms by their step name.
 }}}

-- 
Ticket URL: 
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.9ff2a7635aa3dee614af4e3342a4227f%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

2014-02-10 Thread 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:  assigned
Component:  contrib.admin |  Version:  master
 Severity:  Normal|   Resolution:
 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 timo):

 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1


Comment:

 Comments for improvement on the
 [https://github.com/django/django/pull/2256 PR].

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

Re: [Django] #21597: (2006, 'MySQL server has gone away') in django1.6 when wait_timeout passed

2014-02-10 Thread Django

#21597: (2006, 'MySQL server has gone away') in django1.6 when wait_timeout 
passed
-+-
 Reporter:  ekeydar@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  mysql|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by andreis):

 Hi,
 to me it seems to be a bug. Old django would close every connection right
 away, django 1.6 checks with CONN_MAX_AGE:
 1. It gets CONN_MAX_AGE from DATABASES, sets close_at:

 {{{
 max_age = self.settings_dict['CONN_MAX_AGE']
 self.close_at = None if max_age is None else time.time() + max_age
 }}}

 2. Actually the code above affects close_if_unusable_or_obsolete, which
 closes the connection if 'self.close_at is not None and time.time() >=
 self.close_at'
 3. close_if_unusable_or_obsolete itself is being called by
 close_old_connections, which in turn is a request handler for
 signals.request_started and signals.request_finished.

 We have a worker, which is effectively a django app but but it doesn't
 process any HTTP requests. In fact that makes all connections persistent
 because close_old_connections never gets called.

 Please advise.

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

Re: [Django] #20083: Fix for #18985 makes it impossible to filter deprecation warnings

2014-02-10 Thread Django

#20083: Fix for #18985 makes it impossible to filter deprecation warnings
--+
 Reporter:  aaugustin |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by guettli):

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

[Django] #21998: weight loss doctor plan

2014-02-10 Thread Django

#21998: weight loss doctor plan
--+
 Reporter:  anonymous |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Uncategorized |Version:  1.6
 Severity:  Normal|   Keywords:  Cleanse Ultimo
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 guys so yeah check in with your team members yeah our on this together
 it's not it’s not easy and I know you know it just median and his group
 and coaching you guys keeps me going on ohm its me working out and eating
 healthy in I'm so we need you guys as much as you guys need asks Obama's
 CIA I guess I see a guy s calls are getting shorter and you get sick you
 can buy cell ohm oh I one other thing yeah we're still voting on the on
 when are the other poster and Dom I need to take my photo I guess make
 that poster but omega will get that[http://cleanseultimoadvice.com/
 Cleanse Ultimo] done this week and I will announce the winner this week
 cell and getting out argue not tear gas on her right that's all I got many
 guys up RI yetis d crush it have a great week ohm and 08 arts at me said
 when does oxide up well I can do it I got to happen every thanks I'll damn
 alright guys have a great week man II later here
 my name is doctor Rothmans board-certified in internal medicine an
 emergency medicine and I have a practice in east brunswickit's named Andy
 wellness and spa import certified in both the specialties my practice
 however is really geared towards wellness and helping people discover why
 it is that they get sick as opposed to treating their symptoms with drugs
 a lot of people and maybe that's one reason why you're here tonight and
 they're looking for answers to their health problems sometimes .
 http://cleanseultimoadvice.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.bb8b61b5bb0f9bf70b3fbfb156721c9c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #7835: Provide the ability for model definitions that are only availably during testing

2014-02-10 Thread Django

#7835: Provide the ability for model definitions that are only availably during
testing
-+
 Reporter:  russellm |Owner:  kkubasik
 Type:  New feature  |   Status:  new
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  feature test models  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by JocelynD):

 Replying to [comment:32 adrian_lc]:

 > With 1.6 and the new discovery-runner the models in `tests.py` are not
 being installed anymore, so this feature would be way more useful now.

 I don't get it, I did a minimal test case (attached) with django 1.6:

 * a "buggy" project
 * a "tested" app
 * tested/models.py contains a single abstract model `AbstractTestStat`
 * tested/tests.py contains a `TestStat` model inheriting from
 `AbstractTestStat`
 * tested/tests.py contains a single test testing TestStat

 Either

 ./manage.py test


 or

 ./manage.py test tested

 Works fine, populating the test db and succeeding test as expected.

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

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

Re: [Django] #21996: UnicodeDecodeError when calling GeoIP.country

2014-02-10 Thread Django

#21996: UnicodeDecodeError when calling GeoIP.country
-+-
 Reporter:  Florent Messa|Owner:  claudep
    |   Status:  assigned
 Type:  Bug  |  Version:  1.6
Component:  GIS  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Florent Messa ):

 Good for me, thank you for your quick 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/097.60b5b5d4e781663b21ddfc830a9e9880%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21994: Pass a dict of forms to WizardView.done()

2014-02-10 Thread Django

#21994: Pass a dict of forms to WizardView.done()
---+
 Reporter:  jwa|Owner:  jwa
 Type:  New feature|   Status:  new
Component:  contrib.formtools  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  formtools wizard   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by jwa):

 Pull request is here:

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

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

Re: [Django] #21986: The documentation provides no indication as to why you might want to use indexes

2014-02-10 Thread Django

#21986: The documentation provides no indication as to why you might want to use
indexes
--+
 Reporter:  django-issues@…   |Owner:  bbaja42
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timo):

 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1


Comment:

 As noted on the PR, I think we can probably do a bit better than just a
 link to Wikipedia's entry on database indexes. I wouldn't want to go into
 too much detail since indexing is a complex topic and is often database
 dependent, but some idea of where to start looking would be helpful.

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

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

Re: [Django] #21795: preserve_filter doesn't work on production server

2014-02-10 Thread Django

#21795: preserve_filter doesn't work on production server
---+--
 Reporter:  honyczek   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.6
 Severity:  Normal |   Resolution:  needsinfo
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  1
---+--

Comment (by timo):

 Ping me (timograham) in #django-dev if you like, it will be easier than
 communicating via this ticket.

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

Re: [Django] #20784: RegexValidator should accept a new parameter to perform reversed validation

2014-02-10 Thread Django

#20784: RegexValidator should accept a new parameter to perform reversed 
validation
+
 Reporter:  devfeng |Owner:  nobody
 Type:  New feature |   Status:  closed
Component:  Core (Other)|  Version:  master
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  RegexValidator  | 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:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"b102c27ff4d21ea6262e600227530f75337a5df2"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b102c27ff4d21ea6262e600227530f75337a5df2"
 Fixed #20784 -- Added inverse_match parameter to RegexValidator.
 }}}

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

Re: [Django] #21795: preserve_filter doesn't work on production server

2014-02-10 Thread Django

#21795: preserve_filter doesn't work on production server
---+--
 Reporter:  honyczek   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.6
 Severity:  Normal |   Resolution:  needsinfo
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  1
---+--

Comment (by honyczek):

 Ok, I'd like to do it, but I haven't any knowledge how to debug this.
 Could you give me some recommendations what to use and where to look?

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

[django/django] b102c2: Fixed #20784 -- Added inverse_match parameter to R...

2014-02-10 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b102c27ff4d21ea6262e600227530f75337a5df2
  
https://github.com/django/django/commit/b102c27ff4d21ea6262e600227530f75337a5df2
  Author: Si Feng 
  Date:   2014-02-10 (Mon, 10 Feb 2014)

  Changed paths:
M django/core/validators.py
M docs/ref/validators.txt
M docs/releases/1.7.txt
M tests/validators/tests.py

  Log Message:
  ---
  Fixed #20784 -- Added inverse_match parameter to RegexValidator.


-- 
You received this message because you 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/52f8ac60b6ccd_30fd8dd44508d3%40hookshot-fe8-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21795: preserve_filter doesn't work on production server

2014-02-10 Thread Django

#21795: preserve_filter doesn't work on production server
---+--
 Reporter:  honyczek   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.6
 Severity:  Normal |   Resolution:  needsinfo
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  1
---+--

Comment (by anonymous):

 Ok, I'd like to do it, but I haven't any knowledge how to debug this.
 Could you give me some recommendations what to use and where to look?

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

Re: [Django] #18586: Rewrite unit tests migrated from doctests

2014-02-10 Thread Django

#18586: Rewrite unit tests migrated from doctests
--+
 Reporter:  konk  |Owner:  judy2k
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Testing framework |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  unit tests| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"0d98422b1365ae1e75051036936aab31248d5ee1"]:
 {{{
 #!CommitTicketReference repository=""
 revision="0d98422b1365ae1e75051036936aab31248d5ee1"
 Refactored RecursiveM2MTests into smaller pieces, refs #18586.
 }}}

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

[django/django] c5395e: Allowed a message to be passed to assertQuerysetEq...

2014-02-10 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c5395eef7693e1ae222cbfd81d031237c1802c7f
  
https://github.com/django/django/commit/c5395eef7693e1ae222cbfd81d031237c1802c7f
  Author: Chris Bailey 
  Date:   2014-02-10 (Mon, 10 Feb 2014)

  Changed paths:
M django/test/testcases.py
M docs/topics/testing/tools.txt

  Log Message:
  ---
  Allowed a message to be passed to assertQuerysetEqual to make it consistent 
with other assert methods.


  Commit: 0d98422b1365ae1e75051036936aab31248d5ee1
  
https://github.com/django/django/commit/0d98422b1365ae1e75051036936aab31248d5ee1
  Author: Chris Bailey 
  Date:   2014-02-10 (Mon, 10 Feb 2014)

  Changed paths:
M tests/m2m_recursive/tests.py

  Log Message:
  ---
  Refactored RecursiveM2MTests into smaller pieces, refs #18586.


Compare: https://github.com/django/django/compare/21f034165c73...0d98422b1365

-- 
You received this message because you 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/52f8a999e8bd0_7b759d9d38142e5%40hookshot-fe11-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21996: UnicodeDecodeError when calling GeoIP.country

2014-02-10 Thread Django

#21996: UnicodeDecodeError when calling GeoIP.country
-+-
 Reporter:  Florent Messa|Owner:  claudep
    |   Status:  assigned
 Type:  Bug  |  Version:  1.6
Component:  GIS  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by claudep):

 * has_patch:  0 => 1


Comment:

 Could you please test the attached 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/097.ef74bdd226842c90806127dea0857da0%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #14832: Impossible to create inline objects if form validates but is unchanged

2014-02-10 Thread Django

#14832: Impossible to create inline objects if form validates but is unchanged
---+
 Reporter:  julien |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords:  sprintdec2010  | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  1
---+
Changes (by wim@…):

 * version:  1.2 => 1.4


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

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

Re: [Django] #14832: Impossible to create inline objects if form validates but is unchanged

2014-02-10 Thread Django

#14832: Impossible to create inline objects if form validates but is unchanged
---+
 Reporter:  julien |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords:  sprintdec2010  | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  1
---+

Comment (by anonymous):

 The problem still exists in Django 1.4.10

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

Re: [Django] #21996: UnicodeDecodeError when calling GeoIP.country

2014-02-10 Thread Django

#21996: UnicodeDecodeError when calling GeoIP.country
-+-
 Reporter:  Florent Messa|Owner:  claudep
    |   Status:  assigned
 Type:  Bug  |  Version:  1.6
Component:  GIS  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by claudep):

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


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

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

Re: [Django] #21994: Pass a dict of forms to WizardView.done()

2014-02-10 Thread Django

#21994: Pass a dict of forms to WizardView.done()
---+
 Reporter:  jwa|Owner:  jwa
 Type:  New feature|   Status:  new
Component:  contrib.formtools  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  formtools wizard   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by jezdez):

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


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

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

[Django] #21997: weight loss permantly

2014-02-10 Thread Django

#21997: weight loss permantly
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:  Cleanse Ultimo
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I want to share with you some the amazing success stories I get posted on
 my Face book page every day we have which Bonded at the age of 64 who went
 from 327 pounds to 200 87pounds on the program that's a loss of forty
 pounds I personally email which a few times and he says the biggest reward
 was knowing that will be [http://cleanseultimoadvice.com/ Cleanse Ultimo]
 around longer to see his grandkids grow up James Penne porn is 43 years
 old and was once 199 pounds says he's almost on the 160 pounds now for the
 first time since he was in his 20s his course to be in good enough shape
 tout his all swimsuit on first next family vacation and then weave two
 more success stories from the ladies for you christen Monson from
 Australia said she has never had a weight problem but when she weighed in
 at 84 kilograms she decided to do something about it in just one week on
 the program she’s already down four kilograms and the last story I has
 from Martha Taurus Street whose fifty-six years or in doing the low impact
 workout from the program mother says she's on her fourth day as already
 lost four pounds on the program and cannot believe it now not only does
 the 31 Day Fat Loss Cure get everyday men and women incredible results but
 it’s also were the only fat loss programs in the world endorsed by one of
 the world's top weight loss surgeons check out what doctor Ron heck you're
 world-leading weight loss surgeon from Texas has to say about the program
 the 31 Day Fat Loss Cure offers a fantastic approach to fat loss use in a
 variety of effective techniques including fun bodyweight exercises you can
 do write your own living room with no equipment whether you're beginner or
 advanced fitness nut this program a short produce great results doctor on
 her cure MD had weight loss surgeon for the Bariatric Surgery Center Texas
 here's a few the secrets you’ll discover in the 31 Day Fat Loss Cure on
 page 15 you learn the number one mistake ninety-seven percent of people
 make when trying to lose fat that keeps them soft and flabby simply
 understanding this one mistake will give you an unfair advantage over
 every other person on page 19 you learn the six little-known exercises
 that skyrocket your metabolism through the roof allowing you to burn more
 fat than doing crunches or cardio workouts on page 47 you learn for angry
 is that you absolutely must stay away from if you want to lose stubborn
 belly fat food company secretly Heidi’s four ingredients in eighty percent
 the food you eat and if you don't know how to look for them you always try
 to lose your belly fat on page 45 you learn two more so-called health
 foods that are secretly making you fat already told you about a whole
 grains but there are two more health foods that almost every person eats
 that are doing nothing but and infect your waistline on page 15 you learn
 a unique trick foresting up your workout so that you'll never miss another
 workout district work for me even when I was working 14-hour days on page
 38 you'll see might infamous15-minute workout that burn up to nine times
 more belly fat than traditional cardio on page 44 you learn 7 little-known
 foods that burn belly fat quicker than any diet pill or supplement on
 earth on page 17 you learn a weird mindset trip that won’t guarantee that
 the fact you lose will last forever most people don't understand this and
 this is the main reason why they lose weight but
 http://cleanseultimoadvice.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.c16036ed7c7c9eaf3f5b7ca86f066b7c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21996: UnicodeDecodeError when calling GeoIP.country

2014-02-10 Thread Django

#21996: UnicodeDecodeError when calling GeoIP.country
-+
 Reporter:  Florent Messa   |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  GIS  |Version:  1.6
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 GeoIP.country('IP') raises an UnicodeDecodeError when dealing with
 countries with accents.

 For example:

 {{{
 g = GeoIP()
 g.country('200.7.49.81')
 }}}

 Should returns "Curaçao" instead:

 {{{
 In [2]: g = GeoIP()

 In [3]: g.country('200.7.49.81')
 ---
 UnicodeDecodeErrorTraceback (most recent call
 last)
  in ()
 > 1 g.country('200.7.49.81')

 /Users/thoas/Sites/Python/Ulule/.ven/ulule/lib/python2.7/site-
 packages/django/contrib/gis/geoip/base.pyc in country(self, query)
 193 # Returning the country code and name
 194 return {'country_code' : self.country_code(query),
 --> 195 'country_name' : self.country_name(query),
 196 }
 197

 /Users/thoas/Sites/Python/Ulule/.ven/ulule/lib/python2.7/site-
 packages/django/contrib/gis/geoip/base.pyc in country_name(self, query)
 179 if self._country:
 180 if ipv4_re.match(query):
 --> 181 return GeoIP_country_name_by_addr(self._country,
 enc_query)
 182 else:
 183 return GeoIP_country_name_by_name(self._country,
 enc_query)

 /Users/thoas/Sites/Python/Ulule/.ven/ulule/lib/python2.7/site-
 packages/django/contrib/gis/geoip/prototypes.pyc in _err_check(result,
 func, cargs)
 103 def _err_check(result, func, cargs):
 104 if result:
 --> 105 return result.decode()
 106 return result
 107 func.restype = c_char_p
 }}}

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

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

Re: [Django] #21905: Add check for default=now() on Date/Time/DateTimeFields

2014-02-10 Thread Django

#21905: Add check for default=now() on Date/Time/DateTimeFields
--+---
 Reporter:  taishi@…  |Owner:  mamun
 Type:  New feature   |   Status:  assigned
Component:  Core (Other)  |  Version:  1.7-alpha-1
 Severity:  Normal|   Resolution:
 Keywords:  check | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+---
Changes (by mamun):

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


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

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

Re: [Django] #21881: Clarify that `{% ssi ... parsed %}` has the same limitations as `{% include %}`

2014-02-10 Thread Django

#21881: Clarify that `{% ssi ... parsed %}` has the same limitations as `{% 
include
%}`
---+
 Reporter:  nagyv  |Owner:  mamun
 Type:  Bug|   Status:  assigned
Component:  Documentation  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords:  ssi block  | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by mamun):

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


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

Re: [Django] #21553: InterfaceError in Postgres

2014-02-10 Thread Django

#21553: InterfaceError in Postgres
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.6
  (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
-+-

Comment (by KyleMac):

 I just ran into this as well.

 For some reason postmaster killed a process and so all of postgres
 restarted to avoid corruption. Postgres was down for only a few seconds
 and normal service should have resumed.

 However, all the persistent db connections in Django were now dead and
 needed to reconnect. But is_usable was throwing "InterfaceError:
 connection already closed" and so Django would never reconnect and only
 served error 500 pages until I manually restarted 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/067.50c1978cd29783bda4cca0deea799101%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21995: GenericForeignKey import wrong

2014-02-10 Thread Django

#21995: GenericForeignKey import wrong
-+--
 Reporter:  helberg.andre@…  |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Documentation|  Version:  1.6
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by mjtamlyn):

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


Comment:

 This has changed in Django 1.7. Please make sure you are reading the docs
 for the correct version.

 
https://docs.djangoproject.com/en/1.6/ref/contrib/contenttypes/#django.contrib.contenttypes.generic.GenericForeignKey

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

[Django] #21995: GenericForeignKey import wrong

2014-02-10 Thread Django

#21995: GenericForeignKey import wrong
-+
 Reporter:  helberg.andre@…  |  Owner:  nobody
 Type:  Uncategorized| Status:  new
Component:  Documentation|Version:  1.6
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 On the page:
 
https://docs.djangoproject.com/en/dev/ref/contrib/contenttypes/#django.contrib.contenttypes.generic.GenericForeignKey

 Under Generic relations it says to use

 {{{
 from django.contrib.contenttypes.fields import GenericForeignKey
 }}}


 There is no "fields" in contenttypes, grepping through the source revealed
 it is:


 {{{
 from django.contrib.contenttypes import generic
 }}}


 and then it should read:
 {{{
 generic.GenericForeignKey...
 }}}

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

64 matches

Mail list logo