date:20140811

[Django] #23273: MigrationRecorder does not obey db_router allow_migrate rules

2014-08-11 Thread Django

#23273: MigrationRecorder does not obey db_router allow_migrate rules
+--
 Reporter:  froomzy |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  1.7-rc-2
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+--
 Hi,

 We have a multi-db setup. We have one connection that is for the django
 project, and several connections that talk to other dbs for information
 (ie models with managed = False). Django should only create tables in the
 first connection, never in any of the other connections. We have a simple
 router that does the following:

 {{{
 class Router(object):

 def allow_migrate(self, db, model):
 if db == 'default':
 return True
 return False
 }}}

 '''Current Behaviour'''

 * We run our functional tests and the migrate command is called against
 each connection when the test databases are created (see
 django/test/runner.py, setup_databases, line 300-ish, which calls
 django/db/backends/creation.py, create_test_db, line 377-ish)
 * When this migrate runs, it tries to apply our migrations, which tries to
 record that a migration has been applied (see
 django/db/migrations/executor.py, apply_migration, which has several calls
 to self.recorder.record_applied).
 * The first thing that record_applied does is a call to
 self.ensure_schema() (see django/db/migrations/recorder.py,
 record_applied, lien 66-ish).
 * ensure_schema checks to see if the Migration model is in the tables in
 the connection. If it does not find the table then it tries to create the
 table.

 I believe that this is incorrect behaviour when a db_router has been
 provided. If using the router above, my expectation would be that the
 table is not created on any connection other than the 'default'
 connection. Looking at the other methods on the MigrationRecorder, I would
 expect that there will be similar issues with applied_migrations and
 record_unapplied.

-- 
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/050.4f360c1bdcad3bb34cbe82e164ebfe18%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23130: BooleanField should not override 'blank' if choices are specified

2014-08-11 Thread Django

#23130: BooleanField should not override 'blank' if choices are specified
-+-
 Reporter:  jonash   |Owner:  tushar
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (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 timgraham):

 What are the backwards compatibility ramifications of the proposal?

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

[django/django] 954e7b: Added words to spelling wordlist.

2014-08-11 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 954e7b8aad3f3925e63a0a156b7df7466895e073
  
https://github.com/django/django/commit/954e7b8aad3f3925e63a0a156b7df7466895e073
  Author: Tim Graham 
  Date:   2014-08-11 (Mon, 11 Aug 2014)

  Changed paths:
M docs/spelling_wordlist

  Log Message:
  ---
  Added words to spelling wordlist.


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

Re: [Django] #23271: Makemessages can corrupt existing .po files on Windows

2014-08-11 Thread Django

#23271: Makemessages can corrupt existing .po files on Windows
-+-
 Reporter:  danielmenzel |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  1.7-rc-2
  Internationalization   |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:  makemessages utf8|  Needs documentation:  0
  unicode|  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by claudep):

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


Comment:

 I'm guilty for the regression, but I'm afraid I will not be able to debug
 this issue as I don't have access to Windows machines.

 If noone else can fix it, I can revert the patch in the 1.7 branch to
 remove the release blocking for 1.7.

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

Re: [Django] #23263: Document sqlmigrate in migrations topic guide (was: add migrate --dry-run and --verbose to show database changes in SQL)

2014-08-11 Thread Django

#23263: Document sqlmigrate in migrations topic guide
--+
 Reporter:  wizpig64  |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:  1 |UI/UX:  0
--+
Changes (by bmispelon):

 * type:  New feature => Cleanup/optimization
 * component:  Migrations => Documentation
 * easy:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 Adding a link and/or a brief explanation of what `sqlmigrate` does on the
 topics page makes sense.

 I'm accepting this ticket on this basis.

 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/066.b7b28ac3b7ce1cfcb3a5d95a2a980fc8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23261: Deprecate old style list support for defaultfilters.unordered_list

2014-08-11 Thread Django

#23261: Deprecate old style list support for defaultfilters.unordered_list
--+
 Reporter:  jaap3 |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Template system   |  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 Tim Graham ):

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


Comment:

 In [changeset:"e92b057e06b41eb05930637119e83ed3acd3d324"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e92b057e06b41eb05930637119e83ed3acd3d324"
 Fixed #23261 -- Deprecated old style list support for unordered_list
 filter.
 }}}

-- 
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.3eaaa2eabe2ee0e72295844f8f11ef86%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23263: add migrate --dry-run and --verbose to show database changes in SQL

2014-08-11 Thread Django

#23263: add migrate --dry-run and --verbose to show database changes in SQL
-+--
 Reporter:  wizpig64 |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Migrations   |  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
-+--

Comment (by wizpig64):

 @timgraham

 It seems you're right. The migrations documentation page doesn't mention
 the sqlmigrate: https://docs.djangoproject.com/en/1.7/topics/migrations/ -
 Could it be updated then?

-- 
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.5cf6af4165129fe61266c67aa9c1a1cc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23265: Django don't start on French Windows with Python 2.7 (but only in February, August and December!)

2014-08-11 Thread Django

#23265: Django don't start on French Windows with Python 2.7 (but only in 
February,
August and December!)
-+-
 Reporter:  SpaceFox |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Core (Management |  Version:  1.6
  commands)  |   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 claudep):

 SpaceFox, could you test if this patch solves your issue?

 {{{
 diff --git a/django/core/management/commands/runserver.py
 b/django/core/management/commands/runserver.py
 index 503cff2..dfff57d 100644
 --- a/django/core/management/commands/runserver.py
 +++ b/django/core/management/commands/runserver.py
 @@ -11,6 +11,7 @@ import socket
  from django.core.management.base import BaseCommand, CommandError
  from django.core.servers.basehttp import run,
 get_internal_wsgi_application
  from django.utils import autoreload
 +from django.utils.encoding import get_system_encoding
  from django.utils import six

  naiveip_re = re.compile(r"""^(?:
 @@ -101,7 +102,7 @@ class Command(BaseCommand):
  self.validate(display_num_errors=True)
  now = datetime.now().strftime('%B %d, %Y - %X')
  if six.PY2:
 -now = now.decode('utf-8')
 +now = now.decode(get_system_encoding())

  self.stdout.write((
  "%(started_at)s\n"
 }}}

-- 
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.63ff103c2c78887d703fef874db1078e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23265: Django don't start on French Windows with Python 2.7 (but only in February, August and December!)

2014-08-11 Thread Django

#23265: Django don't start on French Windows with Python 2.7 (but only in 
February,
August and December!)
-+-
 Reporter:  SpaceFox |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Core (Management |  Version:  1.6
  commands)  |   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 claudep):

 I'd suggest to use the `django.utils.encoding.get_system_encoding`
 function instead of the hardcoded 'utf-8'.

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

[Django] #23272: Extra join on filtered + exclude + annotate query

2014-08-11 Thread Django

#23272: Extra join on filtered + exclude + annotate query
--+
 Reporter:  doctormo  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.5
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 The the following code:

 {{{
 e = reduce(OR, (Q(**{'health_uses__purchase__sku__icontains':v}) for v in
 ['COMP','NUTR','DEEP']))
 qs = Customer.objects.filter(pk=8265,
 health_uses__transact__name__in=('Use', 'Adjustment'))
 .exclude(b).annotate(p_value=Sum('health_uses__quantity')).values_list('id',
 'p_value')
 qs.query.group_by = []
 }}}

 qs results in: [(8265, 961)]
 With the query:

 {{{
 SELECT "customers_customer"."id", SUM("healthclub_usage"."quantity") AS
 "p_value" FROM "customers_customer"
 LEFT OUTER JOIN "healthclub_usage" ON ("customers_customer"."id" =
 "healthclub_usage"."customer_id")
 LEFT OUTER JOIN "healthclub_transactiontype" ON
 ("healthclub_usage"."transact_id" = "healthclub_transactiontype"."id")
 LEFT OUTER JOIN "healthclub_usage" T4 ON ("customers_customer"."id" =
 T4."customer_id")
 LEFT OUTER JOIN "healthclub_purchase" ON (T4."purchase_id" =
 "healthclub_purchase"."id")
   WHERE ("customers_customer"."id" = 8265  AND
 "healthclub_transactiontype"."name" IN (Use, Adjustment)
 AND NOT ((UPPER("healthclub_purchase"."sku"::text) LIKE UPPER(%COMP%)
 OR UPPER("healthclub_purchase"."sku"::text)
   LIKE UPPER(%NUTR%)  OR UPPER("healthclub_purchase"."sku"::text) LIKE
 UPPER(%DEEP%) )))
   GROUP BY "customers_customer"."id";
 }}}

 The problem is that T4 JOIN up there. It's a duplicate join because we've
 already joined on healthclub_usage. Tweaking the SQL so it's now:

 {{{
 SELECT "customers_customer"."id", SUM("healthclub_usage"."quantity") AS
 "p_value" FROM "customers_customer"
 LEFT OUTER JOIN "healthclub_usage" ON ("customers_customer"."id" =
 "healthclub_usage"."customer_id")
 LEFT OUTER JOIN "healthclub_transactiontype" ON
 ("healthclub_usage"."transact_id" = "healthclub_transactiontype"."id")
 LEFT OUTER JOIN "healthclub_purchase" ON
 ("healthclub_usage"."purchase_id" = "healthclub_purchase"."id")
   WHERE ("customers_customer"."id" = 8265  AND
 "healthclub_transactiontype"."name" IN ('Use', 'Adjustment')
 AND NOT ((UPPER("healthclub_purchase"."sku"::text) LIKE
 UPPER('%COMP%')  OR UPPER("healthclub_purchase"."sku"::text)
   LIKE UPPER('%NUTR%')  OR UPPER("healthclub_purchase"."sku"::text)
 LIKE UPPER('%DEEP%') )))
   GROUP BY "customers_customer"."id";
 }}}

 Simply removing the T4 join and linking the purchase_id to
 healthclub_usage directly, we get:

 {{{
   id  | p_value
 --+-
  8265 |  30
 (1 row)
 }}}

 Which is the value we expect. I'm unsure if django orm is incapable of
 performing the needed query, or if it's got a subtle bug in there when we
 use excludes. Please help.

-- 
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.6177b19b27b98ef4c4c3c1966642c44e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23271: Makemessages can corrupt existing .po files on Windows

2014-08-11 Thread Django

#23271: Makemessages can corrupt existing .po files on Windows
-+-
 Reporter:  danielmenzel |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:   |Version:  1.7-rc-2
  Internationalization   |   Keywords:  makemessages utf8
 Severity:  Normal   |  unicode
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 == Description ==

 Seen on German Windows7 SP1 with 64bit Python 3.4.1 and gettext 0.18.1.

 When you have '''an existing .po file''' with translations, e.g.
 {{{
 msgid ""
 msgstr ""
 "Project-Id-Version: \n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2014-03-03 10:44+0100\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: \n"
 "Language-Team: \n"
 "Language: de\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 "Plural-Forms: nplurals=2; plural=(n != 1);\n"

 msgid "Size"
 msgstr "Größe"
 }}}
 and then run
 {{{
 manage.py makemessages --no_location --no_wrap -l de
 }}}
 to update the .po file, you get '''a corrupted .po file''':
 {{{
 msgid ""
 msgstr ""
 "Project-Id-Version: \n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2014-03-03 10:44+0100\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: \n"
 "Language-Team: \n"
 "Language: de\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 "Plural-Forms: nplurals=2; plural=(n != 1);\n"

 msgid "Size"
 msgstr "GrÃƒÂ¶ÃƒÅ¸e"
 }}}

 == Investigation ==

 Setting environment variables like LANG, LANGUAGE, LC_ALL, LC_MESSAGES,
 etc. has no effect on the outcome. Also calling chcp 65001 on the Windows
 console does not fix the problem.

 However, it seems like the described behavior was introduced as a side-
 effect with this commit
 
[https://github.com/django/django/commit/dbb48d2bb99a5f660cf2d85f137b8d87fc12d99f]:
 All file accesses in ''makemessages.py'' were changed to explicitly use
 utf-8, but the stdout of the gettext binaries (like ''msgmerge'' etc.) are
 still interpreted with the Windows encoding cp1252, as ''popen_wrapper''
 sets ''universal_newline=True'' which in turn uses the encoding returned
 by ''locale.getpreferredencoding()''.

 As a test I patched ''popen_wrapper'' to interpret output of external
 processes with utf-8 encoding instead of
 ''locale.getpreferredencoding()'':
 {{{
 def popen_wrapper_utf8(args,
 os_err_exc_type=django.core.management.base.CommandError):
 """Monkey-patch for django.core.management.utils.popen_wrapper"""
 try:
 p = Popen(args, shell=False, stdout=PIPE, stderr=PIPE,
   close_fds=os.name != 'nt', universal_newlines=True)
 except OSError as e:
 six.reraise(os_err_exc_type, os_err_exc_type('Error executing %s:
 %s' %
  (args[0],
 e.strerror)), sys.exc_info()[2])
 output, errors = p.communicate()

 # Additional utf-8 decoding
 output =
 output.encode(locale.getpreferredencoding(False)).decode('utf-8')
 #

 return (
 output,
 force_text(errors, DEFAULT_LOCALE_ENCODING, strings_only=True),
 p.returncode
 )
 }}}
 This has the desired effect and prevents the corruption of the .po files.

 I also tried changing the value returned by
 ''locale.getpreferredencoding()'' to "utf-8", but that seems impossible on
 Windows, as Python uses the win32 API ''GetACP()'', which according to
 MSDN [http://msdn.microsoft.com/en-
 us/library/windows/desktop/dd318070(v=vs.85).aspx] only returns ANSI
 codepages and thus will never return "utf-8".

-- 
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/055.5eb5628d971d1a8526a7e796fd9c1368%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #8618: Many-to-many intermediary tables can't have multiple foreign keys to source/target models

2014-08-11 Thread Django

#8618: Many-to-many intermediary tables can't have multiple foreign keys to
source/target models
-+-
 Reporter:  coda |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  m2m intermediary |  Needs documentation:  0
  validation |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by bmispelon):

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


Comment:

 Indeed, it seems that this ticket was a duplicate of #14549 which was
 fixed in c627da0ccc12861163f28177aa7538b420a9d310.

 Thanks for the heads 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/062.b533d475fa8fc0e250398fd71f5c2fec%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #8618: Many-to-many intermediary tables can't have multiple foreign keys to source/target models

2014-08-11 Thread Django

#8618: Many-to-many intermediary tables can't have multiple foreign keys to
source/target models
-+-
 Reporter:  coda |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  m2m intermediary |  Needs documentation:  0
  validation |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by asendecka):

 This ticket seems to be already resolved in Django 1.7:
 
https://docs.djangoproject.com/en/dev/ref/models/fields/#django.db.models.ManyToManyField.through_fields

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

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

Re: [Django] #23270: select_related on fields pointing to subclasses does not work when using defer

2014-08-11 Thread Django

#23270: select_related on fields pointing to subclasses does not work when using
defer
-+-
 Reporter:  islavov  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.7-rc-2
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  select_related   |  Needs documentation:  1
  defer  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-

Comment (by jarshwah):

 Verified that there is an extra query. Tried the patch from #23001
 thinking it may be related, but same problem there.

-- 
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.8059e46c10508eb43caaa364028a639d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23270: select_related on fields pointing to subclasses does not work when using defer

2014-08-11 Thread Django

#23270: select_related on fields pointing to subclasses does not work when using
defer
-+-
 Reporter:  islavov  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.7-rc-2
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  select_related   |  Needs documentation:  1
  defer  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-
Changes (by jarshwah):

 * needs_docs:   => 1
 * stage:  Unreviewed => Accepted
 * needs_tests:   => 1
 * needs_better_patch:   => 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/065.67679fe557ce452b073336850b454e05%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #2443: Add IntervalField to database models

2014-08-11 Thread Django

#2443: Add IntervalField to database models
-+-
 Reporter:  ben.tucker@… |Owner:  mjtamlyn
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  IntervalField|  Needs documentation:  0
  interval duration DurationField|  Patch needs improvement:  1
  feature|UI/UX:  1
Has patch:  1|
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by akaariai):

 * needs_better_patch:  0 => 1


Comment:

 I think we need support for `qs.filter(event_startdate__gte=datetime.now()
 - F('event_duration))`. I think this works on PostgreSQL, but at least on
 Oracle it produces wrong results. The event_duration is in microseconds,
 but in oracle the date arithmetic interprets integers as days. Actually, I
 am not sure if this query works at all.

 In any case usages of F('duration_field') need tests. Raising errors from
 F() usage is acceptable, but producing wrong results is clearly not OK.

 Another issue that keeps nagging me is the use of SubfieldBase to support
 value conversion (SubfieldBase basically calls to_python() anytime the
 field is set on the object). Other fields in Django core do not use this,
 instead they let the backend convert the values. I am not sure if usage of
 SubfieldBase leads to any problems, but I keep getting the feeling we
 should be consistent in not using SubfieldBase. One case where usage of
 backend specific converters differ from usage of to_python  + SubfieldBase
 is that SubfieldBase does value conversions on assignment. So:
 {{{
>>> obj.duration_field = '12:34:56'
>>> obj.duration_field
OUT: '12:34:56' if not using SubfieldBase
OUT: timedelta(12h, 34m, 56s)
 }}}
 Currently no local field in Django core do value conversions on
 assignment. In addition there is clear overhead in model `__init__` when
 using SubfieldBase, I'd guess the overhead is somewhere around 20% per
 field that uses SubfieldBase, though I haven't benchmarked 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/078.2f0918c6523159f6957881b2907cd739%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22959: Document that custom validator must be comparable to prevent infinite migrations

2014-08-11 Thread Django

#22959: Document that custom validator must be comparable to prevent infinite
migrations
--+
 Reporter:  lorinkoz@…|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.7-rc-1
 Severity:  Normal|   Resolution:
 Keywords:  migrations| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by lorinkoz):

 Here's the original validator I used to get to know the problem (of
 course, by the time I discovered it there was no __cmp__)


 {{{
 class LimitWordsValidator:

 def __init__(self, limit, upper=True):
 self.limit = limit
 self.upper = upper

 def __cmp__(x, y):
 return cmp(x.limit, y.limit) or cmp(x.upper, y.upper)

 def __call__(self, value):
 words = len(strip_tags(value).split())
 args = {
 'limit': self.limit,
 'current': words,
 }
 if self.upper and words > self.limit:
 raise ValidationError(_('You cannot exceed %(limit)s words,
 you have %(current)s.') % args)
 if not self.upper and words < self.limit:
 raise ValidationError(_('You need at least %(limit)s words,
 you have %(current)s.') % args)

 def deconstruct(self):
 return (
 'common.validators.LimitWordsValidator',
 [self.limit],
 {'upper': self.upper},
 )
 }}}

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

Re: [Django] #21604: Embed raw queries as subqueries when used with an __in filter

2014-08-11 Thread Django

* needs_better_patch: 0 => 1

Comment:

Sorry for not responding to this ticket sooner.

I think the patch is a bit too invasive for this ticket. We only need
support for `somefield__in=rawqs`. It would be hopefully possible to just
alter the way how the SQL is generated when used in an `in` lookup. In
particular there shouldn't be any need

I wonder if it would be better to just add support for
`qs.filter(somefield__in=RawQuery(sql_str, params))` (and also do the same
for other lookup types if at all possible). This would be a lot easier to
support (actually, this will be likely extremely easy to do after #14030).
Of course, this doesn't allow one to use an existing raw query.

If this could be implemented with just wrapping the query in subquery when
used from `__in` lookup, then I think supporting `somefield__in=rawqs`
directly is OK. If not, then lets focus on adding support for
`somefield__in=RawQuery(sql_str, params)`. In other words, the current
patch seems too complicated for the added feature.

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

[Django] #23270: select_related on fields pointing to subclasses does not work when using defer

2014-08-11 Thread Django

#23270: select_related on fields pointing to subclasses does not work when using
defer
--+
 Reporter:  islavov   |  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.7-rc-2
 Severity:  Normal|   Keywords:  select_related
 Triage Stage:  Unreviewed|  defer
Easy pickings:  0 |  Has patch:  0
  |  UI/UX:  0
--+
 I have the following models
 {{{
 #!python
 from django.db import models

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

 class SubClassA(Base):
 name = models.CharField(max_length=32)

 }}}
 In shell
 {{{
 #!python
 In [3]: from defertest.models import SubClassA, Base

 # Select related + defer
 In [4]: c=Base.objects.select_related("subclassa").defer("text")[0]
 (0.001) SELECT "defertest_base"."id", "defertest_subclassa"."base_ptr_id",
 "defertest_subclassa"."name" FROM "defertest_base" LEFT OUTER JOIN
 "defertest_subclassa" ON ("defertest_base"."id" =
 "defertest_subclassa"."base_ptr_id") LIMIT 1; args=()

 # We get an extra query when accessing the subclass
 In [5]: c.subclassa
 (0.000) SELECT "defertest_base"."id", "defertest_base"."text",
 "defertest_subclassa"."base_ptr_id", "defertest_subclassa"."name" FROM
 "defertest_subclassa" INNER JOIN "defertest_base" ON
 ("defertest_subclassa"."base_ptr_id" = "defertest_base"."id") WHERE
 "defertest_subclassa"."base_ptr_id" = 1 ; args=(1,)
 Out[5]: 

 # If no deferred fields
 In [6]: c=Base.objects.select_related("subclassa")[0]
 (0.000) SELECT "defertest_base"."id", "defertest_base"."text",
 "defertest_subclassa"."base_ptr_id", "defertest_subclassa"."name" FROM
 "defertest_base" LEFT OUTER JOIN "defertest_subclassa" ON
 ("defertest_base"."id" = "defertest_subclassa"."base_ptr_id") LIMIT 1;
 args=()

 # select related works fine ( no extra query )
 In [7]: c.subclassa
 Out[7]: 
 }}}

-- 
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/050.fc2e87d9020703d142526a0025284c44%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21160: in_bulk() fails on SQLite when passing more than 999 ids

2014-08-11 Thread Django

* needs_better_patch: 0 => 1

Comment:

Updated patch can be found from
https://github.com/django/django/pull/3046.

The usage of bulk_batch_size() is incorrect in the patch. The method is
documented to receive a list of objects, but for the use case in this
ticket it receives an iterable of field values. We can either change the
method definition so that it can receive either an iterable of field
values, or a list of objects. Or we can just add a new feature
"max_query_params" and use that instead.

I slightly prefer the approach of adding max_query_params in to database
features. Then we can make supports_1000_query_params to be a property
which is calculated based on max_query_params, and also make the base
bulk_batch_size() to use the max_query_params feature.

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

Re: [Django] #23263: add migrate --dry-run and --verbose to show database changes in SQL

2014-08-11 Thread Django

#23263: add migrate --dry-run and --verbose to show database changes in SQL
-+--
 Reporter:  wizpig64 |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Migrations   |  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 knyghty):

 * version:  1.7-rc-2 => 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/066.ea164f9deb361c54703c1929489bddb6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #6785: QuerySet.get() should only attempt to fetch a limited number of rows

2014-08-11 Thread Django

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

Comment:

Yes, optimizing the successful case is important. The .get() method can be
used in try-except workflows, but I don't know of any realistic use case
where the try-except is interested in multiple objects returned case.

The question is how much overhead the LIMIT 21 clause adds for get() on
databases that support it. If it doesn't add overhead, then keeping the
current behavior on databases that support LIMIT seems OK to me. If it
adds overhead, then lets just get rid of the LIMIT clause and close this
ticket as wontfix. As said before we can get rid of the clone overhead
easily, so that isn't a factor in deciding what to do here.

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

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

Re: [Django] #23269: Deprecate django.utils.remove_tags() and removetags template filter

2014-08-11 Thread Django

#23269: Deprecate django.utils.remove_tags() and removetags template filter
-+-
 Reporter:  timgraham|Owner:  timgraham
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Template system  |   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 timgraham):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/3045 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/067.48bff9c05ee370bcf47814877714ca75%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23016: Review FAQs

2014-08-11 Thread Django

Comment (by olasitarska):

I did three improvements suggested here by Aymeric.
https://github.com/django/django/pull/3044

I didn't touch question about depending on external libraries, because I
don't have the full knowledge about this.

I also think that [[https://docs.djangoproject.com/en/1.6/faq/install
/#will-django-run-under-shared-hosting-like-textdrive-or-dreamhost|answer
about hosting]] that links to a very outdated wiki page should be either
removed or linked to much better mantained
[[http://djangofriendly.com/hosts/|Django Friendly]].

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

[Django] #23269: Deprecate django.utils.remove_tags() and removetags template filter

2014-08-11 Thread Django

#23269: Deprecate django.utils.remove_tags() and removetags template filter
-+-
   Reporter:  timgraham  |  Owner:  timgraham
   Type: | Status:  new
  Cleanup/optimization   |Version:  master
  Component:  Template   |   Keywords:
  system |  Has patch:  0
   Severity:  Normal |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 From the [https://www.djangoproject.com/weblog/2014/aug/11/remove-tags-
 advisory/ removetags security advisory]: "We plan to deprecate these
 functions in a future version of Django rather keep around functions whose
 names are likely to lead to their use in security-sensitive contexts where
 they are not actually safe."

 This also includes the undocumented and unused
 `django.utils.html.strip_entities()`.

-- 
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.5bc51721053c7cb3ffaf071ec09c6821%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 88cb7a: [1.4.x] Added a warning that remove_tags() output ...

2014-08-11 Thread GitHub

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: 88cb7aa6aa2272b02aa3914111083c4cd3094f1b
  
https://github.com/django/django/commit/88cb7aa6aa2272b02aa3914111083c4cd3094f1b
  Author: Tim Graham 
  Date:   2014-08-11 (Mon, 11 Aug 2014)

  Changed paths:
M docs/ref/templates/builtins.txt

  Log Message:
  ---
  [1.4.x] Added a warning that remove_tags() output shouldn't be considered 
safe.

Backport of 7efce77de2 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/53e8a4fe54acf_30fe885d385969%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] d07394: [1.6.x] Added a warning that remove_tags() output ...

2014-08-11 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: d07394a51e1194b5bf8edeb1c6127e6c8df197a4
  
https://github.com/django/django/commit/d07394a51e1194b5bf8edeb1c6127e6c8df197a4
  Author: Tim Graham 
  Date:   2014-08-11 (Mon, 11 Aug 2014)

  Changed paths:
M docs/ref/templates/builtins.txt
M docs/ref/utils.txt

  Log Message:
  ---
  [1.6.x] Added a warning that remove_tags() output shouldn't be considered 
safe.

Backport of 7efce77de2 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/53e8a4fbeb4b1_f7ceefd40721cf%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 00ec30: [1.5.x] Added a warning that remove_tags() output ...

2014-08-11 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 00ec30d3c43ff2be0bb4d0ff14310d67475503c8
  
https://github.com/django/django/commit/00ec30d3c43ff2be0bb4d0ff14310d67475503c8
  Author: Tim Graham 
  Date:   2014-08-11 (Mon, 11 Aug 2014)

  Changed paths:
M docs/ref/templates/builtins.txt
M docs/ref/utils.txt

  Log Message:
  ---
  [1.5.x] Added a warning that remove_tags() output shouldn't be considered 
safe.

Backport of 7efce77de2 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/53e8a4ff8336c_13a2ff9d4470359%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 9a5127: [1.7.x] Added a warning that remove_tags() output ...

2014-08-11 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 9a51270dba8a1f0ca282411a9da62a81a10cb6bb
  
https://github.com/django/django/commit/9a51270dba8a1f0ca282411a9da62a81a10cb6bb
  Author: Tim Graham 
  Date:   2014-08-11 (Mon, 11 Aug 2014)

  Changed paths:
M docs/ref/templates/builtins.txt
M docs/ref/utils.txt

  Log Message:
  ---
  [1.7.x] Added a warning that remove_tags() output shouldn't be considered 
safe.

Backport of 7efce77de2 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/53e8a4fd4266c_f596afd388369b%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 7efce7: Added a warning that remove_tags() output shouldn'...

2014-08-11 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 7efce77de254ee2ffabaf00b826ece19c04eb2d9
  
https://github.com/django/django/commit/7efce77de254ee2ffabaf00b826ece19c04eb2d9
  Author: Tim Graham 
  Date:   2014-08-11 (Mon, 11 Aug 2014)

  Changed paths:
M docs/ref/templates/builtins.txt
M docs/ref/utils.txt

  Log Message:
  ---
  Added a warning that remove_tags() output shouldn't be considered safe.


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

[django/django] c2d3f1: Fixed typo in 1.8 release notes.

2014-08-11 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c2d3f18874e119a8639aa075dea587203b53
  
https://github.com/django/django/commit/c2d3f18874e119a8639aa075dea587203b53
  Author: Markus Bertheau 
  Date:   2014-08-11 (Mon, 11 Aug 2014)

  Changed paths:
M docs/releases/1.8.txt

  Log Message:
  ---
  Fixed typo in 1.8 release notes.


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

[django/django] e92b05: Fixed #23261 -- Deprecated old style list support ...

2014-08-11 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e92b057e06b41eb05930637119e83ed3acd3d324
  
https://github.com/django/django/commit/e92b057e06b41eb05930637119e83ed3acd3d324
  Author: Jaap Roes 
  Date:   2014-08-11 (Mon, 11 Aug 2014)

  Changed paths:
M django/template/defaultfilters.py
M docs/internals/deprecation.txt
M docs/ref/templates/builtins.txt
M docs/releases/1.8.txt
M tests/defaultfilters/tests.py
M tests/template_tests/tests.py

  Log Message:
  ---
  Fixed #23261 -- Deprecated old style list support for unordered_list filter.


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

Re: [Django] #23016: Review FAQs

2014-08-11 Thread Django

#23016: Review FAQs
-+-
 Reporter:  aaugustin|Owner:
 Type:   |  olasitarska
  Cleanup/optimization   |   Status:  assigned
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 olasitarska):

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


-- 
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.5b7fd17c57eb76c707a830738b63b97a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23267: Typo in Translation documentation

2014-08-11 Thread Django

#23267: Typo in Translation documentation
---+---
 Reporter:  Tomin1 |Owner:  olasitarska
 Type:  Bug|   Status:  closed
Component:  Documentation  |  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:  1  |UI/UX:  0
---+---

Comment (by Baptiste Mispelon ):

 In [changeset:"927d7b8b712680ca9fb9ec2a16dccae0f3c8e794"]:
 {{{
 #!CommitTicketReference repository=""
 revision="927d7b8b712680ca9fb9ec2a16dccae0f3c8e794"
 [1.7.x] Fixed #23267 -- Fixed typo in Translation documentation

 Thanks to Tomin1 for the report.

 Backport of 2e7be92b4df29ac851d570e57da5dcf756c5ac52 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/064.3f096e5c4ea4f456b23debf29b6ee704%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 5d6e40: [1.5.x] Fixed #23267 -- Fixed typo in Translation ...

2014-08-11 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 5d6e4031dff26c3df32712e5037037a7c71a81ea
  
https://github.com/django/django/commit/5d6e4031dff26c3df32712e5037037a7c71a81ea
  Author: Ola Sitarska 
  Date:   2014-08-11 (Mon, 11 Aug 2014)

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

  Log Message:
  ---
  [1.5.x] Fixed #23267 -- Fixed typo in Translation documentation

Thanks to Tomin1 for the report.

Backport of 2e7be92b4df29ac851d570e57da5dcf756c5ac52 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/53e8970a9c2ef_1029f9fd443128a%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 927d7b: [1.7.x] Fixed #23267 -- Fixed typo in Translation ...

2014-08-11 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 927d7b8b712680ca9fb9ec2a16dccae0f3c8e794
  
https://github.com/django/django/commit/927d7b8b712680ca9fb9ec2a16dccae0f3c8e794
  Author: Ola Sitarska 
  Date:   2014-08-11 (Mon, 11 Aug 2014)

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

  Log Message:
  ---
  [1.7.x] Fixed #23267 -- Fixed typo in Translation documentation

Thanks to Tomin1 for the report.

Backport of 2e7be92b4df29ac851d570e57da5dcf756c5ac52 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/53e8970a44647_22d7b47d3c87282%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23267: Typo in Translation documentation

2014-08-11 Thread Django

#23267: Typo in Translation documentation
---+---
 Reporter:  Tomin1 |Owner:  olasitarska
 Type:  Bug|   Status:  closed
Component:  Documentation  |  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:  1  |UI/UX:  0
---+---

Comment (by Baptiste Mispelon ):

 In [changeset:"ffb9cbfd84378d59a25abe9fb711ece4de7e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ffb9cbfd84378d59a25abe9fb711ece4de7e"
 [1.6.x] Fixed #23267 -- Fixed typo in Translation documentation

 Thanks to Tomin1 for the report.

 Backport of 2e7be92b4df29ac851d570e57da5dcf756c5ac52 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/064.f3b742e1f70ea7c92acc564ba360063e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] ffb9cb: [1.6.x] Fixed #23267 -- Fixed typo in Translation ...

2014-08-11 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: ffb9cbfd84378d59a25abe9fb711ece4de7e
  
https://github.com/django/django/commit/ffb9cbfd84378d59a25abe9fb711ece4de7e
  Author: Ola Sitarska 
  Date:   2014-08-11 (Mon, 11 Aug 2014)

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

  Log Message:
  ---
  [1.6.x] Fixed #23267 -- Fixed typo in Translation documentation

Thanks to Tomin1 for the report.

Backport of 2e7be92b4df29ac851d570e57da5dcf756c5ac52 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/53e897081fb8b_56f9b3d406332e%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23267: Typo in Translation documentation

2014-08-11 Thread Django

#23267: Typo in Translation documentation
---+---
 Reporter:  Tomin1 |Owner:  olasitarska
 Type:  Bug|   Status:  closed
Component:  Documentation  |  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:  1  |UI/UX:  0
---+---

Comment (by Baptiste Mispelon ):

 In [changeset:"5d6e4031dff26c3df32712e5037037a7c71a81ea"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5d6e4031dff26c3df32712e5037037a7c71a81ea"
 [1.5.x] Fixed #23267 -- Fixed typo in Translation documentation

 Thanks to Tomin1 for the report.

 Backport of 2e7be92b4df29ac851d570e57da5dcf756c5ac52 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/064.6d869a7092a8f5a5aaa9e2360b7a4b62%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23267: Typo in Translation documentation

2014-08-11 Thread Django

#23267: Typo in Translation documentation
---+---
 Reporter:  Tomin1 |Owner:  olasitarska
 Type:  Bug|   Status:  closed
Component:  Documentation  |  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:  1  |UI/UX:  0
---+---
Changes (by Baptiste Mispelon ):

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


Comment:

 In [changeset:"2e7be92b4df29ac851d570e57da5dcf756c5ac52"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2e7be92b4df29ac851d570e57da5dcf756c5ac52"
 Fixed #23267 -- Fixed typo in Translation documentation

 Thanks to Tomin1 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/064.5dfac1c0994a090b24118b4437bc6477%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 2e7be9: Fixed #23267 -- Fixed typo in Translation document...

2014-08-11 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2e7be92b4df29ac851d570e57da5dcf756c5ac52
  
https://github.com/django/django/commit/2e7be92b4df29ac851d570e57da5dcf756c5ac52
  Author: Ola Sitarska 
  Date:   2014-08-11 (Mon, 11 Aug 2014)

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

  Log Message:
  ---
  Fixed #23267 -- Fixed typo in Translation documentation

Thanks to Tomin1 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/53e895b1f3224_6e0963d40396fa%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23267: Typo in Translation documentation

2014-08-11 Thread Django

#23267: Typo in Translation documentation
---+---
 Reporter:  Tomin1 |Owner:  olasitarska
 Type:  Bug|   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:  0
Easy pickings:  1  |UI/UX:  0
---+---
Changes (by olasitarska):

 * has_patch:  0 => 1


Comment:

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

-- 
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.38f4dd39e760b47598f564f4dbdeab5f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23267: Typo in Translation documentation

2014-08-11 Thread Django

#23267: Typo in Translation documentation
---+---
 Reporter:  Tomin1 |Owner:  olasitarska
 Type:  Bug|   Status:  assigned
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:  1  |UI/UX:  0
---+---
Changes (by olasitarska):

 * owner:  nobody => olasitarska
 * 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/064.a1e17011ac31c330a154be08901d5d35%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #16426: sqlite: Cannot delete more than 999 things if there is a relation pointing to them

2014-08-11 Thread Django

#16426: sqlite: Cannot delete more than 999 things if there is a relation 
pointing
to them
-+-
 Reporter:  kmtracey |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   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 Anssi Kääriäinen ):

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


Comment:

 In [changeset:"dfadbdac6a63dce3304dff1977b5b0a15dc2d7b5"]:
 {{{
 #!CommitTicketReference repository=""
 revision="dfadbdac6a63dce3304dff1977b5b0a15dc2d7b5"
 Fixed #16426 -- deletion of 1000+ objects with relations on SQLite

 SQLite doesn't work with more than 1000 parameters in a single query.
 The deletion code could generate queries that try to get related
 objects for more than 1000 objects thus breaking the limit. Django now
 splits the related object fetching into batches with at most 1000
 parameters.

 The tests and patch include some work done by Trac alias NiGhTTraX in
 ticket #21205.
 }}}

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

[django/django] dfadbd: Fixed #16426 -- deletion of 1000+ objects with rel...

2014-08-11 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: dfadbdac6a63dce3304dff1977b5b0a15dc2d7b5
  
https://github.com/django/django/commit/dfadbdac6a63dce3304dff1977b5b0a15dc2d7b5
  Author: Anssi Kääriäinen 
  Date:   2014-08-11 (Mon, 11 Aug 2014)

  Changed paths:
M django/db/models/deletion.py
M tests/delete/tests.py

  Log Message:
  ---
  Fixed #16426 -- deletion of 1000+ objects with relations on SQLite

SQLite doesn't work with more than 1000 parameters in a single query.
The deletion code could generate queries that try to get related
objects for more than 1000 objects thus breaking the limit. Django now
splits the related object fetching into batches with at most 1000
parameters.

The tests and patch include some work done by Trac alias NiGhTTraX in
ticket #21205.


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

Re: [Django] #17785: PostgreSQL Introspection: get_relations() broken after drop column

2014-08-11 Thread Django

#17785: PostgreSQL Introspection: get_relations() broken after drop column
-+-
 Reporter:  guettli  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  psycopg2 |  Needs documentation:  0
  introspection  |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by akaariai):

 * needs_better_patch:  0 => 1


Comment:

 The attached tests will not work on MySQL. The tests use fixed quoting
 (not every database uses " for quoting). In addition, I don't think the
 table creation belongs into the test, if at all possible it would be
 better to use normal models and then alter those dynamically. This would
 give better portability.

 Instead of doing selects to the local and remote table in get_relations(),
 we could likely use information_schema.columns to skip the missing field
 indexes. The query is something like:
 {{{
 WITH augmented_information_schema_columns AS (
 SELECT table_name, ordinal_position,
row_number() OVER (PARTITION BY table_name ORDER BY
 ordinal_position)
   FROM information_schema.columns
 )
 SELECT aisc1.row_number - 1 as local_field_index, aisc2.row_number - 1 as
 remote_field_index, c2.relname
   FROM pg_constraint con
   JOIN pg_class c1 ON c1.oid = con.conrelid
   JOIN pg_class c2 ON c2.oid = con.confrelid
   JOIN augmented_information_schema_columns aisc1 ON con.conkey[1] =
 aisc1.ordinal_position
AND aisc1.table_name = c1.relname
   JOIN augmented_information_schema_columns aisc2 ON con.confkey[1] =
 aisc2.ordinal_position
AND aisc2.table_name = c2.relname
   WHERE c1.relname = 'bar'
AND con.contype = 'f';
 }}}
 (only very quickly tested).

 Maybe a better approach would be to dump usage of column numbers
 altogether, instead use just column names in get_relations().

-- 
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.5828ff4814a81b5e2a79a355410f6bc8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23251: Use a temporary folder to store uploaded files during tests

2014-08-11 Thread Django

#23251: Use a temporary folder to store uploaded files during tests
-+-
 Reporter:  shai |Owner:
 Type:  Bug  |  pavel_shpilev
Component:  Testing framework|   Status:  assigned
 Severity:  Normal   |  Version:  master
 Keywords:  file storage upload  |   Resolution:
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  1|  Needs documentation:  1
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by pavel_shpilev):

 * owner:  nobody => pavel_shpilev
 * 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/062.b4acaaba549049a9a281affd31da465c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23261: Deprecate old style list support for defaultfilters.unordered_list

2014-08-11 Thread Django

#23261: Deprecate old style list support for defaultfilters.unordered_list
--+
 Reporter:  jaap3 |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Template system   |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by jaap3):

 * has_patch:  0 => 1


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

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

Re: [Django] #23261: Deprecate old style list support for defaultfilters.unordered_list

2014-08-11 Thread Django

#23261: Deprecate old style list support for defaultfilters.unordered_list
--+
 Reporter:  jaap3 |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Template system   |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by jaap3):

 Created a pull request https://github.com/django/django/pull/3041

-- 
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.589c839ff15aac6330f8e651ba1ab6e0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23267: Typo in Translation documentation

2014-08-11 Thread Django

#23267: Typo in Translation documentation
---+
 Reporter:  Tomin1 |Owner:  nobody
 Type:  Bug|   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:  1  |UI/UX:  0
---+
Changes (by bmispelon):

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


Comment:

 Good catch, that is indeed a typo.

 If you'd like to try your hand at fixing it, the file to edit is
 
https://github.com/django/django/blob/master/docs/topics/i18n/translation.txt#L1043.

 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/064.5851fc3bfccf7a39a9610f95afe1a952%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23268: Fixtures: Natural Key support for Generic Foreign Keys

2014-08-11 Thread Django

#23268: Fixtures: Natural Key support for Generic Foreign Keys
-+-
Reporter: eskhool | Owner: nobody
Type: Bug | Status: new
Component: Core |Version: 1.6
(Serialization)| Keywords: natural generic
Severity: Normal | fixtures
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0| UI/UX: 0
-+-
Currently, the natural key support is incomplete when it comes to generic
foreign keys (I say bug, you may think feature). One cannot remove PKs
from any object that has a generic foreign key reference limiting the
whole idea of having natural keys to direct foreign keys only. Since
generic foreign keys can inherently have an entry with any model, PKs have
to be dumped for all models necessitating the maintenance of updated PKs

There is a great answer by someone who has done the leg work for figuring
out what is required.
http://stackoverflow.com/questions/11159377/is-it-possible-to-use-a
-natural-key-for-a-genericforeignkey-in-django

Creating a ticket to document it here and see what the interest is for the
same.

--
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/050.4ca9c9ee2002fadfa9980f294cb23470%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22288: F() expression not compatible with __range field look up

2014-08-11 Thread Django

#22288: F() expression not compatible with __range field look up
-+-
 Reporter:  liushaohua86@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 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 akaariai):

 * needs_better_patch:  0 => 1


Comment:

 I checked the patch. It seems we need changes to too many places just to
 support `something__range=(F('foo'), F('bar'))`. The main issue is that we
 have many rounds of value preparation.

 The main issue here is that we just don't handle the case here value is an
 iterable correctly for value preparation. While the above mentioned commit
 touches the area around range lookups, we should likely fix all the
 lookups to lists of F() objects properly. Even if the only other example
 in core is `somefield__in=[F()]`.

 It might be better to wait for #14030 before applying this one.

 In addition the tests of the above patch aren't correct, the code checks
 generated SQL, but that SQL differs between backends (quote character is
 not always `"`, and some backends IIRC use upper case table names).

 Sorry for delay in commenting 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/080.ca9f34556aee074ab5ef64e8c5f33fc8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23267: Typo in Translation documentation

2014-08-11 Thread Django

#23267: Typo in Translation documentation
---+
 Reporter:  Tomin1 |  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
---+
 On page https://docs.djangoproject.com/en/dev/topics/i18n/translation/
 under "Note on performance" it says:
 "In the following example, the cache is invalidated whenever your restart
 your application server."
 I think it should say:
 "In the following example, the cache is invalidated whenever you restart
 your application server."
 English is not my first language, but I think it's wrong.

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

Re: [Django] #23266: Query relation lookup check issues extra queries.

2014-08-11 Thread Django

#23266: Query relation lookup check issues extra queries.
-+-
 Reporter:  apollo13 |Owner:  coder9042
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Anssi Kääriäinen ):

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


Comment:

 In [changeset:"cdfdcf4b70bebfc68871df885387790c6afbc23c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="cdfdcf4b70bebfc68871df885387790c6afbc23c"
 Fixed #23266 -- Prevented queries caused by type checking lookup values

 Small modifications done by committer.
 }}}

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

[django/django] cdfdcf: Fixed #23266 -- Prevented queries caused by type c...

2014-08-11 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: cdfdcf4b70bebfc68871df885387790c6afbc23c
  
https://github.com/django/django/commit/cdfdcf4b70bebfc68871df885387790c6afbc23c
  Author: Anubhav Joshi 
  Date:   2014-08-11 (Mon, 11 Aug 2014)

  Changed paths:
M django/db/models/sql/query.py
M tests/queries/tests.py

  Log Message:
  ---
  Fixed #23266 -- Prevented queries caused by type checking lookup values

Small modifications done by committer.


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

Re: [Django] #23259: Query extra() select_params are inserted in the incorrect order in the overall query parameters with values_list

2014-08-11 Thread Django

#23259: Query extra() select_params are inserted in the incorrect order in the
overall query parameters with values_list
-+-
 Reporter:  rajivm   |Owner:  akaariai
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.7-rc-2
  (models, ORM)  |   Resolution:  fixed
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Anssi Kääriäinen ):

 In [changeset:"4ce5ced230481fc93288aeea922398bc36102d1e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="4ce5ced230481fc93288aeea922398bc36102d1e"
 [1.7.x] Fixed #23259 -- Corrected insertion order of extra() select_params

 A regression caused queries to produce incorrect results for cases where
 extra(select) is excluded by values() but included by extra(order_by)

 The regression was caused by 2f35c6f10fcbae541691207fb0c0560a13b754fc.

 Backport of f0b358880a 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/064.2a55d6f3e96d75c18e75f3f79d9684fe%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 4ce5ce: [1.7.x] Fixed #23259 -- Corrected insertion order ...

2014-08-11 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 4ce5ced230481fc93288aeea922398bc36102d1e
  
https://github.com/django/django/commit/4ce5ced230481fc93288aeea922398bc36102d1e
  Author: Rajiv Makhijani 
  Date:   2014-08-11 (Mon, 11 Aug 2014)

  Changed paths:
M django/db/models/sql/compiler.py
M tests/queries/tests.py

  Log Message:
  ---
  [1.7.x] Fixed #23259 -- Corrected insertion order of extra() select_params

A regression caused queries to produce incorrect results for cases where
extra(select) is excluded by values() but included by extra(order_by)

The regression was caused by 2f35c6f10fcbae541691207fb0c0560a13b754fc.

Backport of f0b358880a 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/53e86278c4139_785e733d4055563%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] f0b358: Fixed #23259 -- Corrected insertion order of extra...

2014-08-11 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: f0b358880a6825d667c037757caac470bc526a1f
  
https://github.com/django/django/commit/f0b358880a6825d667c037757caac470bc526a1f
  Author: Rajiv Makhijani 
  Date:   2014-08-11 (Mon, 11 Aug 2014)

  Changed paths:
M django/db/models/sql/compiler.py
M tests/queries/tests.py

  Log Message:
  ---
  Fixed #23259 -- Corrected insertion order of extra() select_params

A regression caused queries to produce incorrect results for cases where
extra(select) is excluded by values() but included by extra(order_by)

The regression was caused by 2f35c6f10fcbae541691207fb0c0560a13b754fc.


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

Re: [Django] #23259: Query extra() select_params are inserted in the incorrect order in the overall query parameters with values_list

2014-08-11 Thread Django

#23259: Query extra() select_params are inserted in the incorrect order in the
overall query parameters with values_list
-+-
 Reporter:  rajivm   |Owner:  akaariai
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.7-rc-2
  (models, ORM)  |   Resolution:  fixed
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Anssi Kääriäinen ):

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


Comment:

 In [changeset:"f0b358880a6825d667c037757caac470bc526a1f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f0b358880a6825d667c037757caac470bc526a1f"
 Fixed #23259 -- Corrected insertion order of extra() select_params

 A regression caused queries to produce incorrect results for cases where
 extra(select) is excluded by values() but included by extra(order_by)

 The regression was caused by 2f35c6f10fcbae541691207fb0c0560a13b754fc.
 }}}

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

Re: [Django] #23259: Query extra() select_params are inserted in the incorrect order in the overall query parameters with values_list

2014-08-11 Thread Django

#23259: Query extra() select_params are inserted in the incorrect order in the
overall query parameters with values_list
-+-
 Reporter:  rajivm   |Owner:  akaariai
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.7-rc-2
  (models, ORM)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by akaariai):

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


Comment:

 I'll finish this one.

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

60 matches

Mail list logo