date:20131204

[Django] #21563: calling hasattr(model_instance, fieldname) raises DoesNotExist when False

2013-12-04 Thread Django

#21563: calling hasattr(model_instance, fieldname) raises DoesNotExist when 
False
---+
 Reporter:  monkut |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Using python 3.3 and django 1.6.

 I've got a model (created from an AbstractBaseClass) and creating an
 instance of the model from some JSON, via serializers.deserialize(), then
 checking if the resulting parsed JSON model has the fields I'm expecting.

 (thinking about it now, this seems like the wrong thing to do, since it
 may be expected that the resulting Model instance has the field, but takes
 the default value? but anyway...)

 When I check to see if the parsed instance.object has the given attribute,
 via hasattr(), it's raising DoesNotExist, instead of returning the
 expected False.

 Again, maybe it's ok that it doesn't return False... but I don't think
 hasattr() should raise an exception.



 {{{

 from django.contrib.auth.models import User

 class BaseTask(models.Model):
 assigned_to = models.ForiegnKey(User)

 class Meta:
 abstract = True

 class Task(BaseTask):
 pass
 }}}



 {{{
 Python 3.3.2 (v3.3.2:d047928ae3f6, May 16 2013, 00:06:53) [MSC v.1600 64
 bit (AMD64)] on win32
 Type "help", "copyright", "credits" or "license" for more information.
 (InteractiveConsole)
 >>> from myproject.myapp.models import Task
 >>> from django.contrib.auth.models import User
 >>> t = Task()
 >>> hasattr(t, "assigned_to")
 Traceback (most recent call last):
   File "", line 1, in 
   File "C:\Python33\lib\site-packages\django\db\models\fields\related.py",
 line 314, in __get__
 "%s has no %s." % (self.field.model.__name__, self.field.name))
 django.contrib.auth.models.DoesNotExist: Task has no assigned_to.
 >>> u = User.objects.get(pk=1)
 >>>
 >>> t.assigned_to = u
 >>> hasattr(t, "assigned_to")
 True
 >>>
 }}}

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

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

Re: [Django] #21556: Date field shows in changed_data due to different format

2013-12-04 Thread Django

#21556: Date field shows in changed_data due to different format
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Forms  |  Version:  1.5
 Severity:  Normal |   Resolution:  needsinfo
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by anonymous):

 * version:  1.6 => 1.5


Comment:

 My apologizes, I am using 1.5.

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

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

Re: [Django] #21562: Bad things happen if you name your custom user app "auth"

2013-12-04 Thread Django

#21562: Bad things happen if you name your custom user app "auth"
--+
 Reporter:  yourcelf  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by alasdair):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * type:  Bug => Cleanup/optimization
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 The warning for the [https://docs.djangoproject.com/en/dev/ref/settings
 /#installed-apps INSTALLED_APPS setting] covers this.

 {{{
 > App names must be unique

 The application names (that is, the final dotted part of the path to the
 module containing models.py) defined in INSTALLED_APPS must be unique. For
 example, you can’t include both django.contrib.auth and myproject.auth in
 INSTALLED_APPS.
 }}}

 I suggest we add a similar warning to the re-usable app tutorial. A
 reusable app shouldn't be named auth, messages, sites, or any other
 contrib name, or it's going to cause problems.

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

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

[Django] #21562: Bad things happen if you name your custom user app "auth"

2013-12-04 Thread Django

#21562: Bad things happen if you name your custom user app "auth"
---+
Reporter: yourcelf | Owner: nobody
Type: Bug| Status: new
Component: Documentation |Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
---+
It seems that odd conflicts and unexpected behavior happen if you create
an app specifying a custom user model and name that app "auth"[1]. The
general principle might also apply that bad things happen when you include
two apps with the same ultimate module name (e.g. both "" and
"django.contrib.", as well as any other dotted path to an app).

The documentation for reusable apps
https://docs.djangoproject.com/en/dev/intro/reusable-apps/ mentions
choosing app names that don't conflict with existing published apps for
sharing convenience, but I can't find any mention of the fact that module
names (even with differing dotted prefixes) should never collide for
purposes of proper code function. Particularly with custom user models,
where bare "auth" is a very natural thing to name your own implementation,
this seems worth a mention.

[1] Specific problems: importing the model in the shell (e.g. "import
auth.models.User") resulted in importing a
"django.contrib.auth.models.User"; the post-syncdb signal for creating the
first superuser followed the contract for creating a django.contrib User
but put the results in a table made for the custom User, and trying to
register the custom User resulted in an "already registered" error.

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

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

[django/django] 0daa2f: List 1.6.x releases in descending order

2013-12-04 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 0daa2f1bf1dde97cc10781b4f1e6a1a987ec2330
  
https://github.com/django/django/commit/0daa2f1bf1dde97cc10781b4f1e6a1a987ec2330
  Author: Alasdair Nicol 
  Date:   2013-12-04 (Wed, 04 Dec 2013)

  Changed paths:
M docs/releases/index.txt

  Log Message:
  ---
  List 1.6.x releases in descending order


  Commit: 1864c6b5ad70c3c403bc5621fb5856a114a98845
  
https://github.com/django/django/commit/1864c6b5ad70c3c403bc5621fb5856a114a98845
  Author: Tim Graham 
  Date:   2013-12-04 (Wed, 04 Dec 2013)

  Changed paths:
M docs/releases/index.txt

  Log Message:
  ---
  Merge pull request #2029 from alasdairnicol/releases_ordering

List ed 1.6.x releases in descending order


Compare: https://github.com/django/django/compare/3b8e46cbc7cd...1864c6b5ad70

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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/529faacc4e48b_157c1127d4c13732d%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 49fab3: [1.6.x] Listed 1.6.x releases in descending order

2013-12-04 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 49fab30496c6468b7ff323e846e4d31423c12b2b
  
https://github.com/django/django/commit/49fab30496c6468b7ff323e846e4d31423c12b2b
  Author: Alasdair Nicol 
  Date:   2013-12-04 (Wed, 04 Dec 2013)

  Changed paths:
M docs/releases/index.txt

  Log Message:
  ---
  [1.6.x] Listed 1.6.x releases in descending order

Backport of 0daa2f1bf1 from master


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

Re: [Django] #21561: broken link

2013-12-04 Thread Django

#21561: broken link
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.6
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by anonymous):

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


Comment:

 is a book fault: there is a comma in the link :D
 http://www.djangoproject.com/download/,

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

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

Re: [Django] #21561: broken link

2013-12-04 Thread Django

#21561: broken link
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by timo):

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


Comment:

 From your report it sounds like the broken link is in a book not on the
 Django web site, is that correct? If so, it doesn't seem like something we
 can fix (we are not affiliated with the book).

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

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

[Django] #21561: broken link

2013-12-04 Thread Django

#21561: broken link
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 https://www.djangoproject.com/download/ leads to an error page from the
 book:   "Learning Website Development with Django"

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

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

Re: [Django] #8898: `required` validation bypassed when using `DateTimeField` with `SplitDateTimeWidget`.

2013-12-04 Thread Django

#8898: `required` validation bypassed when using `DateTimeField` with
`SplitDateTimeWidget`.
-+-
 Reporter:  mrmachine|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  DateTimeField| Triage Stage:  Accepted
  SplitDateTimeWidget|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by claudep):

 It may be that #15511 filled the above use case (setting
 `require_all_fields` to `False`, then
 `SplitDateTimeField.fields[1].required` to `False` in a
 `SplitDateTimeField` subclass).
 @mrmachine, can you confirm?

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

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

Re: [Django] #8898: `required` validation bypassed when using `DateTimeField` with `SplitDateTimeWidget`.

2013-12-04 Thread Django

#8898: `required` validation bypassed when using `DateTimeField` with
`SplitDateTimeWidget`.
-+-
 Reporter:  mrmachine|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  DateTimeField| Triage Stage:  Accepted
  SplitDateTimeWidget|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by claudep):

 Reading ticket #9721, it appears that `DateTimeField` with
 `SplitDateTimeWidget` may be used when only the time part of the field is
 optional, which would not be possible with `SplitDateTimeField`. To be
 investigated...

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

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

Re: [Django] #8898: `required` validation bypassed when using `DateTimeField` with `SplitDateTimeWidget`.

2013-12-04 Thread Django

#8898: `required` validation bypassed when using `DateTimeField` with
`SplitDateTimeWidget`.
-+-
 Reporter:  mrmachine|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  DateTimeField| Triage Stage:  Accepted
  SplitDateTimeWidget|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by claudep):

 * needs_better_patch:  1 => 0


Comment:

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

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

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

Re: [Django] #13205: Fix empty value detection in DateTimeField with SplitDateTimeWidget rendering

2013-12-04 Thread Django

#13205: Fix empty value detection in DateTimeField with SplitDateTimeWidget
rendering
-+-
 Reporter:  Bastian Kleineidam   |Owner:  nobody
   |   Status:  closed
 Type:  Bug  |  Version:  1.1
Component:  Forms|   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by claudep):

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


Comment:

 As stated in #8898, `SplitDateTimeWidget` should be used with
 `SplitDateTimeField`. The support for `SplitDateTimeWidget` in
 `DateTimeField` will be deprecated.

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

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

Re: [Django] #21558: Build CHM help file format out of box on win32

2013-12-04 Thread Django

#21558: Build CHM help file format out of box on win32
-+-
 Reporter:  mpasternak   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.6
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  html help chm| Triage Stage:  Accepted
  generation docs|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by mpasternak):

 THANKS MAN!

 I think we can close https://code.djangoproject.com/ticket/14950 too.

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

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

Re: [Django] #21560: missing 'slug' field in example code

2013-12-04 Thread Django

#21560: missing 'slug' field in example code
---+--
 Reporter:  jfindlay@… |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by jfindlay@…):

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


Comment:

 Or, maybe it will work the way it is written.  I'm confused.

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

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

[Django] #21560: missing 'slug' field in example code

2013-12-04 Thread Django

#21560: missing 'slug' field in example code
---+
 Reporter:  jfindlay@… |  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
---+
 https://docs.djangoproject.com/en/1.6/topics/forms/modelforms/#overriding-
 the-default-fields

 Consider the 2nd to last code quotation (before the lengthy 'Note') in
 this section.  Both the text and the code block refer to and imply a
 'slug' field in the fields list of the Meta class.  The last code block,
 however does not omit 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/061.809b28255f1882927d8a6e286438277b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21554: incorrect SQL generated when using multiple inheritance

2013-12-04 Thread Django

#21554: incorrect SQL generated when using multiple inheritance
-+-
 Reporter:  pegler   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  multiple-|  Unreviewed
  inheritance|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by pegler):

 I can confirm that patch works on 1.6.

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

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

Re: [Django] #21554: incorrect SQL generated when using multiple inheritance

2013-12-04 Thread Django

#21554: incorrect SQL generated when using multiple inheritance
-+-
 Reporter:  pegler   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  multiple-|  Unreviewed
  inheritance|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by mitchell):

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


Comment:

 I've also stumbled onto this one today.

 I've made [https://gist.github.com/mitchellrj/7792290 a gist] of a
 rudimentary module with a quick and dirty monkey patch for Django 1.6.

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

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

Re: [Django] #21559: Generic relations regression in Django 1.6

2013-12-04 Thread Django

#21559: Generic relations regression in Django 1.6
-+-
 Reporter:  khoobks@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by akaariai):

 * needs_docs:   => 0
 * needs_better_patch:   => 0
 * severity:  Normal => Release blocker
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 I can confirm that the queries work differently. However, the 1.5 version
 didn't work correctly at all. Using generic_relations test models:
 {{{
 a = Animal.objects.create(common_name='foo', latin_name='bar')
 Vegetable.objects.create(name='foo', pk=a.pk)
 TaggedItem.objects.create(content_object=a)
 print TaggedItem.objects.filter(vegetable__name__icontains='foo')
 print
 TaggedItem.objects.filter(vegetable__name__icontains='foo').query
 }}}
 The output is:
 {{{
 []
 SELECT ...
   FROM "generic_relations_taggeditem"
  INNER JOIN "generic_relations_taggeditem" T2 ON
 ("generic_relations_taggeditem"."id" = T2."id")
  INNER JOIN "generic_relations_vegetable" ON (T2."object_id" =
 "generic_relations_vegetable"."id")
  INNER JOIN "django_content_type" ON
("generic_relations_taggeditem"."content_type_id" =
 "django_content_type"."id")
  WHERE "generic_relations_vegetable"."name" LIKE %foo% ESCAPE '\'
  ORDER BY "generic_relations_taggeditem"."tag" ASC,
 "django_content_type"."name" ASC
 }}}
 Note the lack of any constraint on the content type. For this reason a
 vegetable is found even if there is no relationship to any vegetable at
 all.

 The query construct used wasn't documented (at least I can't find a
 reference) and is completely untested. I am confident that having the
 query produce any results at all is just an accident caused by
 implementation details.

 I think I'll just have to document that such queries do not work any more,
 and that they never actually produced any correct results. The other
 option is to make this construct work properly in 1.6, but I believe that
 will be a lot of work and could require changes that break popular 3rd
 party software (django-taggit comes to mind here). It would likely be
 possible to make the query construct work like in 1.5, too, but loud
 failure seems a lot better than a silently returning wrong data.

 Marking as release blocker, docs need updating at least.

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

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

Re: [Django] #21483: [RFE] Add WSGI environ to request_started signal emission

2013-12-04 Thread Django

#21483: [RFE] Add WSGI environ to request_started signal emission
--+-
 Reporter:  jag@… |Owner:  anonymous
 Type:  New feature   |   Status:  assigned
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-

Comment (by Joshua "jag" Ginsberg ):

 For many (most?) cases, I'd agree with you - middleware has that
 explicitness, where as signals are automated magic. However the signal is
 the absolute earliest place to modify the handling of a request - for
 cases where middleware may even be too late, doing work with a signal
 handler could be the best option.

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

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

[django/django] 3b8e46: Migration VCS conflict detection and --merge for m...

2013-12-04 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 3b8e46cbc7cdb03bb40b3b07a5f659a2d402
  
https://github.com/django/django/commit/3b8e46cbc7cdb03bb40b3b07a5f659a2d402
  Author: Andrew Godwin 
  Date:   2013-12-04 (Wed, 04 Dec 2013)

  Changed paths:
M django/core/management/commands/makemigrations.py
M django/core/management/commands/migrate.py
M django/db/migrations/autodetector.py
M django/db/migrations/loader.py
A django/db/migrations/questioner.py
M tests/migrations/test_autodetector.py
M tests/migrations/test_commands.py
A tests/migrations/test_migrations_conflict/0001_initial.py
A tests/migrations/test_migrations_conflict/0002_conflicting_second.py
A tests/migrations/test_migrations_conflict/0002_second.py
A tests/migrations/test_migrations_conflict/__init__.py

  Log Message:
  ---
  Migration VCS conflict detection and --merge for makemigrations


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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/529f526fd7fe4_47716f9d486645b%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21558: Build CHM help file format out of box on win32

2013-12-04 Thread Django

#21558: Build CHM help file format out of box on win32
-+-
 Reporter:  mpasternak   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.6
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  html help chm| Triage Stage:  Accepted
  generation docs|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"2d4f399ad40c63bbfd7917a9f2006f4ebb495099"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2d4f399ad40c63bbfd7917a9f2006f4ebb495099"
 [1.4.x] Fixed #21558 -- Support building CHM files.

 Thanks Michał Pasternak.

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

[django/django] 2d4f39: [1.4.x] Fixed #21558 -- Support building CHM files...

2013-12-04 Thread GitHub

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: 2d4f399ad40c63bbfd7917a9f2006f4ebb495099
  
https://github.com/django/django/commit/2d4f399ad40c63bbfd7917a9f2006f4ebb495099
  Author: Aymeric Augustin 
  Date:   2013-12-04 (Wed, 04 Dec 2013)

  Changed paths:
M docs/_theme/djangodocs/layout.html

  Log Message:
  ---
  [1.4.x] Fixed #21558 -- Support building CHM files.

Thanks Michał Pasternak.

Backport of cd9e85ec from master.


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

[django/django] 6691ab: [1.6.x] Fixed #21558 -- Support building CHM files...

2013-12-04 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 6691abcdf0db219bfa584d52eb21e891d88f2aeb
  
https://github.com/django/django/commit/6691abcdf0db219bfa584d52eb21e891d88f2aeb
  Author: Aymeric Augustin 
  Date:   2013-12-04 (Wed, 04 Dec 2013)

  Changed paths:
M docs/_theme/djangodocs/layout.html

  Log Message:
  ---
  [1.6.x] Fixed #21558 -- Support building CHM files.

Thanks Michał Pasternak.

Backport of cd9e85ec from master.


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

Re: [Django] #21558: Build CHM help file format out of box on win32

2013-12-04 Thread Django

#21558: Build CHM help file format out of box on win32
-+-
 Reporter:  mpasternak   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.6
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  html help chm| Triage Stage:  Accepted
  generation docs|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"6691abcdf0db219bfa584d52eb21e891d88f2aeb"]:
 {{{
 #!CommitTicketReference repository=""
 revision="6691abcdf0db219bfa584d52eb21e891d88f2aeb"
 [1.6.x] Fixed #21558 -- Support building CHM files.

 Thanks Michał Pasternak.

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

[django/django] deeed4: [1.5.x] Fixed #21558 -- Support building CHM files...

2013-12-04 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: deeed42253edf583974662657c70014d1634b46b
  
https://github.com/django/django/commit/deeed42253edf583974662657c70014d1634b46b
  Author: Aymeric Augustin 
  Date:   2013-12-04 (Wed, 04 Dec 2013)

  Changed paths:
M docs/_theme/djangodocs/layout.html

  Log Message:
  ---
  [1.5.x] Fixed #21558 -- Support building CHM files.

Thanks Michał Pasternak.

Backport of cd9e85ec from master.


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

Re: [Django] #21558: Build CHM help file format out of box on win32

2013-12-04 Thread Django

#21558: Build CHM help file format out of box on win32
-+-
 Reporter:  mpasternak   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.6
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  html help chm| Triage Stage:  Accepted
  generation docs|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"deeed42253edf583974662657c70014d1634b46b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="deeed42253edf583974662657c70014d1634b46b"
 [1.5.x] Fixed #21558 -- Support building CHM files.

 Thanks Michał Pasternak.

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

Re: [Django] #21558: Build CHM help file format out of box on win32

2013-12-04 Thread Django

#21558: Build CHM help file format out of box on win32
-+-
 Reporter:  mpasternak   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.6
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  html help chm| Triage Stage:  Accepted
  generation docs|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by Aymeric Augustin ):

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


Comment:

 In [changeset:"cd9e85ece94214718257d972e9e5ab4bac3f0e65"]:
 {{{
 #!CommitTicketReference repository=""
 revision="cd9e85ece94214718257d972e9e5ab4bac3f0e65"
 Fixed #21558 -- Support building CHM files.

 Thanks Michał Pasternak.
 }}}

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

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

[django/django] cd9e85: Fixed #21558 -- Support building CHM files.

2013-12-04 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: cd9e85ece94214718257d972e9e5ab4bac3f0e65
  
https://github.com/django/django/commit/cd9e85ece94214718257d972e9e5ab4bac3f0e65
  Author: Aymeric Augustin 
  Date:   2013-12-04 (Wed, 04 Dec 2013)

  Changed paths:
M docs/_theme/djangodocs/layout.html

  Log Message:
  ---
  Fixed #21558 -- Support building CHM files.

Thanks Michał Pasternak.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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/529f4f513ccc1_62cb6fd50118697%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21558: Build CHM help file format out of box on win32

2013-12-04 Thread Django

Comment (by mpasternak):

I agree about changes to make.bat . They may be lost during the next run
of sphinx tools, the file is autogenerated, so there is no point in
patching it really. I created an issue for Sphinx
https://bitbucket.org/birkenfeld/sphinx/issue/1318/compile-chm-files-out-
of-box-on-windows and the fix https://bitbucket.org/birkenfeld/sphinx
/pull-request/195/compile-chm-files-out-of-box/diff#chg-
sphinx/quickstart.py and it is not really so trival thing to fix properly
because of strange Microsoft Windows shell problems here
http://www.blinnov.com/en/2010/06/04/microsoft-was-unexpected-at-this-
time/ .

If you think we should add the part that detects the builder and omits
jquery, I'd be more than happy.

Thank You!

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

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

Re: [Django] #21523: Models DateField to_python method no longer supports mock dates.

2013-12-04 Thread Django

#21523: Models DateField to_python method no longer supports mock dates.
-+-
 Reporter:  hugo@…   |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by hugorodgerbrown):

 I've submitted a PR for this (https://github.com/django/django/pull/2026)
 - but I've gone off message slightly in using `hasattr(value,
 'isoformat')` instead of `tzinfo` or `strftime` as suggested above.

 This way, we maintain the `isinstance(value, datetime.datetime)` and
 `isinstance(value, datetime.date)` checks as-is, but if the object fails
 both of those, and has an `isoformat`atribute it gets converted into a
 string and then parsed using `parse_date` as currently happens. Using
 `isoformat` instead of `str` or `smart_str` seems tighter, as if an object
 has such an attribute it's a reasonable assumption to assume that it
 thinks it's a date (as opposed to `str`).

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

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

Re: [Django] #21558: Build CHM help file format out of box on win32

2013-12-04 Thread Django

#21558: Build CHM help file format out of box on win32
-+-
 Reporter:  mpasternak   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:  html help chm| Triage Stage:  Accepted
  generation docs|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by aaugustin):

 The change to the documentation template is a good idea.

 I'm less sure about the change to make.bat, how is it specific to Django?
 If it isn't, it should be made in Sphinx itself, since `make.bat` is
 generated by Sphinx.

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

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

[Django] #21559: Generic relations regression in Django 1.6

2013-12-04 Thread Django

#21559: Generic relations regression in Django 1.6
--+
 Reporter:  khoobks@… |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.6
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Please see the code below for a demonstration of the regression.

 == The Model ==
 {{{
 from django.db import models
 from django.contrib.contenttypes.models import ContentType
 from django.contrib.contenttypes import generic

 class TaggedItem(models.Model):
 tag = models.SlugField()
 content_type = models.ForeignKey(ContentType)
 object_id = models.PositiveIntegerField()
 content_object = generic.GenericForeignKey('content_type',
 'object_id')

 # On Python 3: def __str__(self):
 def __unicode__(self):
 return self.tag

 class Bookmark(models.Model):
 url = models.URLField()
 tags = generic.GenericRelation(TaggedItem)
 }}}

 == The Setup ==
 {{{
 from test_app.models import *

 b = Bookmark(url='https://www.djangoproject.com/')
 b.save()
 t1 = TaggedItem(content_object=b, tag='django')
 t1.save()
 t2 = TaggedItem(content_object=b, tag='python')
 t2.save()
 }}}

 == Django 1.5 ==
 {{{
 Python 2.7.3 (default, Apr 10 2012, 23:31:26) [MSC v.1500 32 bit (Intel)]
 on win32
 Type "help", "copyright", "credits" or "license" for more information.
 (InteractiveConsole)
 >>> import django
 >>> from test_app.models import *
 >>> django.VERSION
 (1, 5, 5, 'final', 0)
 >>> TaggedItem.objects.filter(bookmark__url__icontains='django')
 [, ]
 >>>
 }}}

 == Django 1.6 ==
 {{{
 Python 2.7.3 (default, Apr 10 2012, 23:31:26) [MSC v.1500 32 bit (Intel)]
 on win32
 Type "help", "copyright", "credits" or "license" for more information.
 (InteractiveConsole)
 >>>
 >>> import django
 >>> from test_app.models import *
 >>> django.VERSION
 (1, 6, 0, 'final', 0)
 >>> TaggedItem.objects.filter(bookmark__url__icontains='django')
 Traceback (most recent call last):
   File "", line 1, in 
   File "C:\workspace\django_generic_relationship\django16\lib\site-
 packages\django\db\models\manager.py", line 163, in f
 ilter
 return self.get_queryset().filter(*args, **kwargs)
   File "C:\workspace\django_generic_relationship\django16\lib\site-
 packages\django\db\models\query.py", line 590, in fil
 ter
 return self._filter_or_exclude(False, *args, **kwargs)
   File "C:\workspace\django_generic_relationship\django16\lib\site-
 packages\django\db\models\query.py", line 608, in _fi
 lter_or_exclude
 clone.query.add_q(Q(*args, **kwargs))
   File "C:\workspace\django_generic_relationship\django16\lib\site-
 packages\django\db\models\sql\query.py", line 1198, i
 n add_q
 clause = self._add_q(where_part, used_aliases)
   File "C:\workspace\django_generic_relationship\django16\lib\site-
 packages\django\db\models\sql\query.py", line 1232, i
 n _add_q
 current_negated=current_negated)
   File "C:\workspace\django_generic_relationship\django16\lib\site-
 packages\django\db\models\sql\query.py", line 1100, i
 n build_filter
 allow_explicit_fk=True)
   File "C:\workspace\django_generic_relationship\django16\lib\site-
 packages\django\db\models\sql\query.py", line 1351, i
 n setup_joins
 names, opts, allow_many, allow_explicit_fk)
   File "C:\workspace\django_generic_relationship\django16\lib\site-
 packages\django\db\models\sql\query.py", line 1274, i
 n names_to_path
 "Choices are: %s" % (name, ", ".join(available)))
 FieldError: Cannot resolve keyword 'bookmark' into field. Choices are:
 content_type, id, object_id, tag
 >>>
 }}}

 I would have expected that the same code should work the same way between
 Django 1.5 and 1.6.

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

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

[django/django] ab587f: Add --dry-run option to makemigrations

2013-12-04 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ab587fa51a3be3ffc6f011189c0abab32dec6155
  
https://github.com/django/django/commit/ab587fa51a3be3ffc6f011189c0abab32dec6155
  Author: Andrew Godwin 
  Date:   2013-12-04 (Wed, 04 Dec 2013)

  Changed paths:
M django/core/management/commands/makemigrations.py

  Log Message:
  ---
  Add --dry-run option to makemigrations


  Commit: df800b160990884246d73786e85b082d9b703b57
  
https://github.com/django/django/commit/df800b160990884246d73786e85b082d9b703b57
  Author: Andrew Godwin 
  Date:   2013-12-04 (Wed, 04 Dec 2013)

  Changed paths:
M django/db/models/fields/__init__.py

  Log Message:
  ---
  Add clone() method to Field to get clean copies of it.


  Commit: ce05b8a69ee0e9f7f7e0154b2b9bf1dcb15edbcb
  
https://github.com/django/django/commit/ce05b8a69ee0e9f7f7e0154b2b9bf1dcb15edbcb
  Author: Andrew Godwin 
  Date:   2013-12-04 (Wed, 04 Dec 2013)

  Changed paths:
M django/db/migrations/autodetector.py
M django/db/migrations/operations/fields.py
M tests/migrations/test_operations.py

  Log Message:
  ---
  Don't make a second migration if there was a force-null-default addcol.


Compare: https://github.com/django/django/compare/1d20e6df9553...ce05b8a69ee0

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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/529f34a7e86df_3bf11efd4c592ca%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21556: Date field shows in changed_data due to different format

2013-12-04 Thread Django

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

Comment:

Are you really using Django 1.6? Some recent improvements have been made
in this realm. Change detection is now done on the field level and the
input value is transformed to a python date value before the comparison,
so generally what you describe should not happen.

Could you please give us a more comprehensive code example so as we can
better see what's happening in your case?

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

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

[django/django] 1d20e6: Migrate prompts if you need makemigrations, runser...

2013-12-04 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 1d20e6df9553346c79edd92e6e8934e9c5c4aa2c
  
https://github.com/django/django/commit/1d20e6df9553346c79edd92e6e8934e9c5c4aa2c
  Author: Andrew Godwin 
  Date:   2013-12-04 (Wed, 04 Dec 2013)

  Changed paths:
M django/core/management/commands/migrate.py
M django/core/management/commands/runserver.py

  Log Message:
  ---
  Migrate prompts if you need makemigrations, runserver prompts for migrate


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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/529f2f5b58c27_154798dd481066a1%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] c8cf49: [1.6.x] Added link to localized formatting doc fro...

2013-12-04 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: c8cf49e5c48eca4936c3729d1a4f963a4666c282
  
https://github.com/django/django/commit/c8cf49e5c48eca4936c3729d1a4f963a4666c282
  Author: Ramiro Morales 
  Date:   2013-12-04 (Wed, 04 Dec 2013)

  Changed paths:
M docs/index.txt
M docs/topics/i18n/formatting.txt

  Log Message:
  ---
  [1.6.x] Added link to localized formatting doc from main index.

abb04f1f3f from master.


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

[django/django] abb04f: Added link to localized formatting doc from main i...

2013-12-04 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: abb04f1f3f19f460643177e780004ff199423757
  
https://github.com/django/django/commit/abb04f1f3f19f460643177e780004ff199423757
  Author: Ramiro Morales 
  Date:   2013-12-04 (Wed, 04 Dec 2013)

  Changed paths:
M docs/index.txt
M docs/topics/i18n/formatting.txt

  Log Message:
  ---
  Added link to localized formatting doc from main index.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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/529f2d9b8a042_430958fd5410030%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21558: Build CHM help file format out of box on win32

2013-12-04 Thread Django

#21558: Build CHM help file format out of box on win32
-+-
 Reporter:  mpasternak   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:  html help chm| Triage Stage:  Accepted
  generation docs|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by mpasternak):

 Hi,

 my original patch was too complicated. As @apollo13 pointed out on IRC, I
 can use builder variable in jinja context, so:

 
https://github.com/mpasternak/django/commit/c06cd4f95b7051da86c29320f069d06187d54792

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

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

Re: [Django] #21557: search function is broken

2013-12-04 Thread Django

#21557: search function is broken
---+--
 Reporter:  tjtimer@…  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by anonymous):

 No, i do the same things. I think i'll try another browser.

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

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

Re: [Django] #14950: Javascript errors when building CHM file from django docs using Sphinx

2013-12-04 Thread Django

#14950: Javascript errors when building CHM file from django docs using Sphinx
-+-
 Reporter:  Aryeh Leib Taurog|Owner:  nobody
  |   Status:  closed
 Type:  Bug  |  Version:  1.2
Component:  Documentation|   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  chm javascript   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by ramiro):

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


Comment:

 I'm going to close this as duplicate of #21558 that, even if newer, has a
 patch and renewed energies.

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

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

Re: [Django] #14950: Javascript errors when building CHM file from django docs using Sphinx

2013-12-04 Thread Django

#14950: Javascript errors when building CHM file from django docs using Sphinx
-+-
 Reporter:  Aryeh Leib Taurog|Owner:  nobody
  |   Status:  new
 Type:  Bug  |  Version:  1.2
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  chm javascript   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by mpasternak):

 Hi,

 I know, 3 years are a long time.

 Anyways, here's a patch, that makes CHM compilation readily available out
 of box
 
https://github.com/mpasternak/django/commit/1336d8f8599f8d0571893c0bbd03f52f66eb36ef
 ,
 and here's an issue I created for it
 https://code.djangoproject.com/ticket/21558

 With kind regards,
 Michal

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

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

Re: [Django] #21558: Build CHM help file format out of box on win32

2013-12-04 Thread Django

#21558: Build CHM help file format out of box on win32
-+-
 Reporter:  mpasternak   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:  html help chm| Triage Stage:  Accepted
  generation docs|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by ramiro):

 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #21558: Build CHM help file format out of box on win32

2013-12-04 Thread Django

#21558: Build CHM help file format out of box on win32
-+-
 Reporter:  mpasternak   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:  html help chm| Triage Stage:
  generation docs|  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by mpasternak):

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


Comment:

 And, here's the simple fix from yours truly:
 
https://github.com/mpasternak/django/commit/1336d8f8599f8d0571893c0bbd03f52f66eb36ef
 . It is for stable/1.6.x, as I need CHM documentation for this particular
 version, but it should be the same patch for the master branch.

 What do you say?

 PS: thank you, thank you, thank you for a GREATEST WEB FRAMEWORK of ALL
 TIME. ALL 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/068.8cef3fc9a3abf1f13a8084c2beb7c5ff%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21558: Build CHM help file format out of box on win32

2013-12-04 Thread Django

CHM file format is Microsoft Help file Compiled HTML Help format and for
me and perhaps some other people, it is very convinient to use it[1]. In
the past, various individuals([2], [3]) built their own, unofficial CHM
files by hand. Also, there are other projects, not less prominent, than
ours beloved Django ([4], [5], [6]), who happily provide CHM help on their
official pages.

So, why aren't we doing that? Let's fix this now.

For the CHM help file building... why do it by hand, when we are already
using Makefiles to build documentation?

Modify the Makefile... done!

Another problem: the files compiled by Sphinx can not be feed to Microsoft
Help Compiler, because of included JQuery
(https://code.djangoproject.com/ticket/14950), which caused errors on
every page opened. This is relativley easy to fix, by using sphinx-build
command line switch -A, which feeds variables directly to template
rendering context.

So, in the commit linked to this issue, I am fixing both 14950 _and_ I am
including call to Microsoft Help Compiler, to build the required CHM file,
so perhaps in the future our project would be able to provide CHM help
files for those win32-based djangonauts out there. And, the make.bat
contains a link to Microsoft Help Compiler download, if anybody does need
that.

The errorlevel checking part is a bit strange for anybody using a regular
shell like bash or zsh, it is explained here [7].

So, what do you say, guys? I will include the patch in the comment as soon
as I add this issue to tracker, so I can use its number in the commit...

Links:
1. Comments below this article http://blog.pythonaro.com/2009/08/django-11
-help-file-chm-version.html for example
2. http://www.aryehleib.com/CHM.html
3. http://blog.pythonaro.com/2009/08/django-11-help-file-chm-version.html
4. http://php.net/download-docs.php
5. http://rubyinstaller.org/downloads/
6. http://python.org/download/releases/2.7.6/
7. http://www.incodesystems.com/PRODUCTS/ERRORLE1.HTM

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

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

Re: [Django] #21411: CommandError: One or more models did not validate but backtrace not saying anything useful

2013-12-04 Thread Django

#21411: CommandError: One or more models did not validate but backtrace not 
saying
anything useful
---+--
 Reporter:  artscoop   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.6
 Severity:  Normal |   Resolution:  worksforme
 Keywords:  validate   | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by ramiro):

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


Comment:

 Replying to [comment:6 aaugustin]:
 > We've seen similar issues and reached the conclusion that the proper way
 to link to the user model is:
 >
 > {{{
 > user = models.ForeignKey(settings.AUTH_USER_MODEL)
 > }}}
 >
 > We should document this.

 It is documented already:
 
https://docs.djangoproject.com/en/1.5/topics/auth/customizing/#django.contrib.auth.get_user_model

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

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

Re: [Django] #21406: blocktrans trimmed mixes up po-file source line numbers

2013-12-04 Thread Django

#21406: blocktrans trimmed mixes up po-file source line numbers
--+
 Reporter:  bouke |Owner:  bouke
 Type:  Bug   |   Status:  closed
Component:  Internationalization  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by ramiro):

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


Comment:

 In 91c38ce4b236e6eeb5f6f636250df7316fa766bd:

 Fixed 21406 -- Made blocktrans 'trimmed' option preserve line numbers.

 Thanks Bouke Haarsma for report, fix and initial 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/063.b25a77780052de1667c23bf7e320b136%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21524: Annotation and .extra with group function breaks at database level

2013-12-04 Thread Django

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

Comment:

I don't think we can support this. It is impossible to detect which parts
of the SQL in extra select needs to be in group by. Trying to parse the
SQL doesn't work. Consider for example:
account_balance - SUM(transaction_amount)

Here account_balance must be in group by, but transaction_amount not.

The .extra() as it is currently implemented in Django just doesn't work
for your use case. I hope we will have something better later on, but for
now I'll have to just wontfix this issue.

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

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

[django/django] 91c38c: Fixed 21406 -- Made blocktrans 'trimmed' option pr...

2013-12-04 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 91c38ce4b236e6eeb5f6f636250df7316fa766bd
  
https://github.com/django/django/commit/91c38ce4b236e6eeb5f6f636250df7316fa766bd
  Author: Bouke Haarsma 
  Date:   2013-12-04 (Wed, 04 Dec 2013)

  Changed paths:
M django/utils/translation/trans_real.py
M tests/i18n/commands/templates/test.html
M tests/i18n/test_extraction.py

  Log Message:
  ---
  Fixed 21406 -- Made blocktrans 'trimmed' option preserve line numbers.

Thanks Bouke Haarsma for report, fix and initial patch.


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

Re: [Django] #21300: Allow DateTimeField to return a naive datetime

2013-12-04 Thread Django

#21300: Allow DateTimeField to return a naive datetime
-+-
 Reporter:  brycegroff   |Owner:  aaugustin
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  forms DateTimeField  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 I looked at the ORM layer and there's a dozen places where it's going to
 be very hard to inject the `USE_TZ` setting. See 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/068.6fc0797899f15ae54bb4a722bd6215d8%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21300: Allow DateTimeField to return a naive datetime

2013-12-04 Thread Django

#21300: Allow DateTimeField to return a naive datetime
-+-
 Reporter:  brycegroff   |Owner:  aaugustin
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  forms DateTimeField  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 The main problem in practice is... the global `USE_TZ` setting :( How
 surprising.

 For instance, when using PostgreSQL, `DateTimeField`s return aware
 datetimes because database cursors are configured to add time zone
 information to all datetimes:

 {{{
 def create_cursor(self):
 cursor = self.connection.cursor()
 cursor.tzinfo_factory = utc_tzinfo_factory if settings.USE_TZ else
 None
 return cursor
 }}}

 

 Of course, there's a good reasons for making `USE_TZ` global: the
 template, form and model layers must agree on the mode (naive or aware) in
 which Django is running.

 But it could be useful to provide a way to work with naive datetimes in
 the database and form layers. The template layer already provides a
 sufficient API.

 That would require:
 - a way to override `TIME_ZONE` and `USE_TZ` on a per-database basis.
 Currently it's already possible, although undocumented, to override
 `TIME_ZONE`.
 - a way to override `USE_TZ` in model and form`DateField` and
 `DateTimeField` on a per-field basis.

 This would be documented as an advanced use case and it would be up to
 each project that takes advantage of this to ensure that the right models
 are used on the right databases. In practice, the main use case is to
 access third-party databases that store date times in an way that's
 incompatible with the main project settings.

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

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

Re: [Django] #17990: Distinct + Random + Postgres = Bug

2013-12-04 Thread Django

#17990: Distinct + Random + Postgres = Bug
-+-
 Reporter:  pizzapanther |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by gcbirzan):

 Actually, an even easier fix would be to exclude the RANDOM from the
 distinct. That's in a patch. In a trivial case, that can be worked around
 like this:

 Model.objects.extra(select={'rand':
 'RANDOM()'}).distinct('pk').order_by('rand')

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

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

Re: [Django] #21557: search function is broken

2013-12-04 Thread Django

#21557: search function is broken
---+--
 Reporter:  tjtimer@…  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by bmispelon):

 I can't reproduce that.

 Here's what I do:

 * Navigate to https://docs.djangoproject.com/
 * Get redirected to https://docs.djangoproject.com/en/1.6/ automatically
 * Type something in the search bar on the right
 * Change the version in the dropdown to 1.5
 * Press the "Search" button

 When I do this, I arrive to the correct URL mentionned above.
 Do yo do anything differently from this?

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

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

[django/django] 4d738f: Fixed #21546 -- Strengthened kqueue detection.

2013-12-04 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 4d738fcc3bad4e13c3667646a86f9a17603b7d23
  
https://github.com/django/django/commit/4d738fcc3bad4e13c3667646a86f9a17603b7d23
  Author: Aymeric Augustin 
  Date:   2013-12-04 (Wed, 04 Dec 2013)

  Changed paths:
M django/utils/autoreload.py

  Log Message:
  ---
  Fixed #21546 -- Strengthened kqueue detection.

Thanks Loic Bistuer.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving 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/529ef1fecd936_207f6dd5893372%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21546: ValueError when tracing runserver.

2013-12-04 Thread Django

#21546: ValueError when tracing runserver.
-+-
 Reporter:  loic84   |Owner:  aaugustin
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Core (Management |   Resolution:  fixed
  commands)  | Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Aymeric Augustin ):

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


Comment:

 In [changeset:"4d738fcc3bad4e13c3667646a86f9a17603b7d23"]:
 {{{
 #!CommitTicketReference repository=""
 revision="4d738fcc3bad4e13c3667646a86f9a17603b7d23"
 Fixed #21546 -- Strengthened kqueue detection.

 Thanks Loic Bistuer.
 }}}

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

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

Re: [Django] #21557: search function is broken

2013-12-04 Thread Django

#21557: search function is broken
---+--
 Reporter:  tjtimer@…  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by tjtimer@…):

 I typed "DateField" into the search field, choosed version 1.5 and pressed
 search.

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

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

Re: [Django] #21557: search function is broken

2013-12-04 Thread Django

#21557: search function is broken
---+--
 Reporter:  tjtimer@…  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by bmispelon):

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


Comment:

 Hi,

 That's the wrong URL for the search page, it should be
 https://docs.djangoproject.com/search/?q=django&release=7 (that's for 1.5
 but you can change which version to search in the dropdown).

 How did you end up on that link you gave?

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

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

[Django] #21557: search function is broken

2013-12-04 Thread Django

#21557: search function is broken
---+
 Reporter:  tjtimer@…  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Hey!
 You`re doing a awesome job!
 You're search function always directs to
 "https://docs.djangoproject.com/search/1.6/";, "PAGE NOT FOUND"...
 Even if i'm looking for something in version 1.5.

 Greets Tim

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

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

Re: [Django] #21238: `ImageFieldFile.url` raises an AttributeError exception after retrieving it from cache

2013-12-04 Thread Django

#21238: `ImageFieldFile.url` raises an AttributeError exception after 
retrieving it
from cache
-+
 Reporter:  dulaccc  |Owner:  vajrasky
 Type:  Bug  |   Status:  assigned
Component:  Core (Cache system)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  imagefield, cache| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by lucmult@…):

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

59 matches

Mail list logo