date:20140205

[Django] #21961: ForeignKey.on_delete supports database-level cascading options

2014-02-05 Thread Django

#21961: ForeignKey.on_delete supports database-level cascading options
--+-
Reporter: Xof | Owner: nobody
Type: New feature | Status: new
Component: Database layer (models, ORM) |Version: 1.7-alpha-1
Severity: Normal| Keywords:
Triage Stage: Unreviewed| Has patch: 0
Easy pickings: 0 | UI/UX: 0
--+-
Per a discussion on -developers, this ticket is to document this proposed
new feature.

The general idea is to allow developers to specify that the database
itself, rather than Django, should implement foreign key constraints where
possible. The database can be considerably more efficient, and often can
avoid locking situations, in a way that the Django backend can't.

The proposal is to add a models.CASCADE_DB, models.SET_NULL_DB,
models.PROTECT_DB constants. These specify that the appropriate
functionality is to be implemented in the database if the database
supports it; otherwise, they are implemented in the Django core as now.

Some potential design issues with proposed solutions:

1. It is not an error to specify the _DB version with a database that
doesn't support it. Instead, you get the non-_DB version.
2. The _DB version does not fire signals; this will need to be documented.
3. If a model A references a model B using CASCADE_DB, but model B
references model C using regular CASCADE, a deletion of A won't cascade
all the way to C. This needs to be documented. Another possibility is to
make this an error condition and have model validation fail, but that
seems excessive.
4. The _DB version is disallowed on generic foreign keys, because that way
madness lies.
5. The implicit foreign key created from child to parent in model
inheritance is never the _DB version. This is a shame, but there are two
issues:
a) Since it's created implicitly, there's no place to put it.
b) Even if we extended the mechanism to allow manual specification of
the key, deleting the parent wouldn't automatically delete the child.

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

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

Re: [Django] #21960: Typo in tutorial part 2

2014-02-05 Thread Django

#21960: Typo in tutorial part 2
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.6
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by bmispelon):

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


Comment:

 Hi,

 It's actually correct: the quote was started on the first line with
 `python -c "` and the one at the end finishes it.

 Having the quote this way allows us to present one command per line which
 is more readable than one long line.

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

[Django] #21960: Typo in tutorial part 2

2014-02-05 Thread Django

#21960: Typo in tutorial part 2
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 on https://docs.djangoproject.com/en/1.6/intro/tutorial02/:

 print(django.__path__)" should read print(django.__path__)

 just a typo I'd guess with that extra " ;)

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

Re: [Django] #19705: CommonMiddleware handles If-None-Match incorrectly

2014-02-05 Thread Django

#19705: CommonMiddleware handles If-None-Match incorrectly
---+
 Reporter:  aaugustin  |Owner:  hirokiky
 Type:  Bug|   Status:  assigned
Component:  HTTP handling  |  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 mrmachine):

 * cc: real.human@… (added)


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

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

Re: [Django] #21953: Memory leak in 1.6.1 in DB manager

2014-02-05 Thread Django

#21953: Memory leak in 1.6.1 in DB manager
-+-
 Reporter:  steve.hutchinz@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  invalid
 Severity:  Release blocker  | Triage Stage:
 Keywords:  memory leak DB   |  Unreviewed
  manager|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by steve.hutchinz@…):

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


Comment:

 Hey look I am really sorry to have wasted your time on this. Although my
 app is leaking on Ubuntu I thought I had narrowed it down on my test
 Windows box but didn't realise that DEBUG was True (sheepish grin). So I
 will continue looking and leave you in peace :)

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

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

Re: [Django] #21959: widthratio templatetag fails to handle NaN ratio

2014-02-05 Thread Django

#21959: widthratio templatetag fails to handle NaN ratio
-+--
 Reporter:  rmoe |Owner:
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by jwiel86):

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


Comment:

 Hi, thanks for reporting.  Do you mind giving more information on how to
 reproduce this exception so a newbie could partake?  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/062.01f08dd3c884267dbe425bb9352fb15c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 5f03b0: [1.6.x] Added missing items to 1.6.2 release notes...

2014-02-05 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 5f03b06919997aaba4244034afafdf3b84a3e7d3
  
https://github.com/django/django/commit/5f03b06919997aaba4244034afafdf3b84a3e7d3
  Author: Tim Graham 
  Date:   2014-02-05 (Wed, 05 Feb 2014)

  Changed paths:
M docs/releases/1.6.2.txt

  Log Message:
  ---
  [1.6.x] Added missing items to 1.6.2 release notes.

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

[django/django] b17c75: Added missing items to 1.6.2 release notes.

2014-02-05 Thread GitHub

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

  Changed paths:
M docs/releases/1.6.2.txt

  Log Message:
  ---
  Added missing items to 1.6.2 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/52f2d79310081_7b6e1439d3c82155%40hookshot-fe12-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21959: widthratio templatetag fails to handle NaN ratio

2014-02-05 Thread Django

#21959: widthratio templatetag fails to handle NaN ratio
-+
 Reporter:  rmoe |  Owner:
 Type:  Bug  | Status:  new
Component:  Template system  |Version:  master
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  1
Easy pickings:  0|  UI/UX:  0
-+
 When value or max_value are float('inf') or float('nan') the ratio
 calculation can raise an exception.

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

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

[django/django] 36f260: Extended the release notes for chainable Manager/Q...

2014-02-05 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 36f260341a1720d7a38e482234c84ff8e73eab85
  
https://github.com/django/django/commit/36f260341a1720d7a38e482234c84ff8e73eab85
  Author: Loic Bistuer 
  Date:   2014-02-05 (Wed, 05 Feb 2014)

  Changed paths:
M docs/releases/1.7.txt

  Log Message:
  ---
  Extended the release notes for chainable Manager/QuerySet methods.

Refs #20625.


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

Re: [Django] #20625: Custom Chainable QuerySets

2014-02-05 Thread Django

#20625: Custom Chainable QuerySets
-+-
 Reporter:  danols   |Owner:  loic84
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  QuerySet,|  Needs documentation:  0
  models.Manager, chainable  |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"36f260341a1720d7a38e482234c84ff8e73eab85"]:
 {{{
 #!CommitTicketReference repository=""
 revision="36f260341a1720d7a38e482234c84ff8e73eab85"
 Extended the release notes for chainable Manager/QuerySet methods.

 Refs #20625.
 }}}

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

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

2014-02-05 Thread Django

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

 * needs_better_patch:  0 => 1
 * needs_tests:  1 => 0


Comment:

 I've reviewed the pull request and left comments for improvement. Please
 uncheck "Patch needs improvement" when it's updated.

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

Re: [Django] #21775: No facility to specify the datafile of a django test Oracle tablespace

2014-02-05 Thread Django

#21775: No facility to specify the datafile of a django test Oracle tablespace
-+-
 Reporter:  smeatonj |Owner:  alvaro@…
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  oracle   |  Needs documentation:  1
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * easy:  1 => 0


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

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

Re: [Django] #21957: keys issues in filebased cache backend

2014-02-05 Thread Django

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

Comment:

This sounds very odd. Django's file framework is just opening and closing
files using normal Python file semantics. The worst problem I'd expect to
see would be related to cache file ownership and/or permissions. I can't
think of anything that would cause issues at the *inode* level.

I also use the file cache myself, and I've never seen anything like the
sort of problems you've described.

I'm not denying that you're having a problem, and that it's inode related
-- but we're going to need a lot more specific information if we're going
to reproduce this (I'm guessing down to the level of OS patch levels and
hardware, since inodes aren't something that Django normally has any
access to).

Closing needsinfo -- please reopen if you can provide more information.

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

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

Re: [Django] #21544: Problem with number format when not using L10N

2014-02-05 Thread Django

#21544: Problem with number format when not using L10N
---+
 Reporter:  yceruto@…  |Owner:  Yonel Ceruto
 Type:  Bug|   Status:  new
Component:  Utilities  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  number format  | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timo):

 * easy:  1 => 0


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

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

Re: [Django] #19552: makemessages ignores translations in templates with inline comment tags

2014-02-05 Thread Django

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

Comment:

As noted in the previous commit message: "Behavior of {% comment %}...{%
endcomment %}tags remains unchanged." I think that means inline
translations aren't supported for that tag.

I'm not sure if this is something that could or should be changed, or
rather if the limitation should simplify be documented if it's not
already. In either case, a new ticket is better than reopening this old
one, 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/083.a3359152781e8cfd0067e42dd28d7145%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21958: Migrations fail on adding ForeignKey field to User model

2014-02-05 Thread Django

#21958: Migrations fail on adding ForeignKey field to User model
+-
 Reporter:  code22  |  Owner:
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  1.7-alpha-1
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+-
 It seems that migrations have problems with adding columns with foreign
 key to User tables. This happens both if I use `settings.AUTH_USER_MODEL`
 and `django.contrib.auth.model.User`.

 My model looked like this:
 {{{#!python
 class TestModel(models.Model):

 text = models.CharField(max_length=10)
 }}}
 so if I add User field
 {{{#!python
 class TestModel(models.Model):

 text = models.CharField(max_length=10)
 user = models.ForeignKey(settings.AUTH_USER_MODEL, null=True)
 }}}

 then run `manage.py makemigrations` and then `manage.py migrate` I get
 this:
 {{{
 Operations to perform:
   Synchronize unmigrated apps: admin, contenttypes, auth, sessions
   Apply all migrations: migr_test
 Synchronizing apps without migrations:
   Creating tables...
   Installing custom SQL...
   Installing indexes...
 Installed 0 object(s) from 0 fixture(s)
 Running migrations:
   Applying migr_test.0002_testmodel_user...Traceback (most recent call
 last):
   File "./manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File
 "/private/tmp/test_env/src/django/django/core/management/__init__.py",
 line 427, in execute_from_command_line
 utility.execute()
   File
 "/private/tmp/test_env/src/django/django/core/management/__init__.py",
 line 419, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/private/tmp/test_env/src/django/django/core/management/base.py",
 line 288, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "/private/tmp/test_env/src/django/django/core/management/base.py",
 line 337, in execute
 output = self.handle(*args, **options)
   File
 "/private/tmp/test_env/src/django/django/core/management/commands/migrate.py",
 line 145, in handle
 executor.migrate(targets, plan, fake=options.get("fake", False))
   File
 "/private/tmp/test_env/src/django/django/db/migrations/executor.py", line
 60, in migrate
 self.apply_migration(migration, fake=fake)
   File
 "/private/tmp/test_env/src/django/django/db/migrations/executor.py", line
 94, in apply_migration
 migration.apply(project_state, schema_editor)
   File
 "/private/tmp/test_env/src/django/django/db/migrations/migration.py", line
 97, in apply
 operation.database_forwards(self.app_label, schema_editor,
 project_state, new_state)
   File
 "/private/tmp/test_env/src/django/django/db/migrations/operations/fields.py",
 line 35, in database_forwards
 field,
   File
 "/private/tmp/test_env/src/django/django/db/backends/sqlite3/schema.py",
 line 96, in add_field
 self._remake_table(model, create_fields=[field])
   File
 "/private/tmp/test_env/src/django/django/db/backends/sqlite3/schema.py",
 line 33, in _remake_table
 if field.get_default():
   File
 "/private/tmp/test_env/src/django/django/db/models/fields/related.py",
 line 1649, in get_default
 if isinstance(field_default, self.rel.to):
 TypeError: isinstance() arg 2 must be a class, type, or tuple of classes
 and types
 }}}

 Used Python3.3.3 and Python2.7.6 with the same result

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

[django/django] 55d19d: Removed import which is now unused

2014-02-05 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 55d19d370f335e3f19a65c955b5efcffbf093791
  
https://github.com/django/django/commit/55d19d370f335e3f19a65c955b5efcffbf093791
  Author: Alex Gaynor 
  Date:   2014-02-05 (Wed, 05 Feb 2014)

  Changed paths:
M tests/utils_tests/test_safestring.py

  Log Message:
  ---
  Removed import which is now unused


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

Re: [Django] #21882: Early modification bug in Django 1.6. with mark_safe + ugettext_lazy

2014-02-05 Thread Django

#21882: Early modification bug in Django 1.6. with mark_safe + ugettext_lazy
-+-
 Reporter:  nealtodd |Owner:  bmispelon
 Type:  Bug  |   Status:  closed
Component:   |  Version:  1.6
  Internationalization   |   Resolution:  fixed
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:  mark_safe|  Needs documentation:  0
  ugettext_lazy  |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by bmispelon):

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


Comment:

 As noted by the comment above, the regression was fixed by reverting the
 commit that introduced it.

 I also backported the fix to the 1.6.x branch so it will be part of the
 upcoming 1.6.2 release.

 Note that using lazy objects with `mark_safe` doesn't really work since
 `mark_safe` will force their evaluation (this is what #20296 was trying to
 fix).

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

Re: [Django] #20296: django.utils.safestring.mark_safe forces evaluation of lazy objects

2014-02-05 Thread Django

#20296: django.utils.safestring.mark_safe forces evaluation of lazy objects
-+
 Reporter:  bmispelon|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Utilities|  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 bmispelon):

 * status:  closed => new
 * resolution:  fixed =>
 * stage:  Ready for checkin => Accepted


Comment:

 A better fix for the issue is here:
 https://github.com/django/django/pull/2234

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

Re: [Django] #8851: Please add a default option to list_filter in the admin interface

2014-02-05 Thread Django

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

Comment:

I would argue that this is not fixed. I believe I have the same issue as
the OP - I want to choose which of the available filter options should be
selected by default. I don't want to customize the filtering behavior by
subclassing SimpleListFilter. The desired behavior is that when I go to
admin changelist url, it is *as if I had already chosen one of the
filtering options*. I don't want to change the behavior of the filtering
options. I just want one (the defined default) to be pre-selected.

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

[django/django] 8864d2: [1.6.x] Revert "Fixed #20296 -- Allowed SafeData a...

2014-02-05 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 8864d2478946506db22d2d2d37585f55536fb358
  
https://github.com/django/django/commit/8864d2478946506db22d2d2d37585f55536fb358
  Author: Baptiste Mispelon 
  Date:   2014-02-05 (Wed, 05 Feb 2014)

  Changed paths:
M django/utils/safestring.py
M tests/utils_tests/test_safestring.py

  Log Message:
  ---
  [1.6.x] Revert "Fixed #20296 -- Allowed SafeData and EscapeData to be lazy"

This reverts commit 2ee447fb5f8974b432d3dd421af9a242215aea44.

That commit introduced a regression (#21882) and didn't really
do what it was supposed to: while it did delay the evaluation
of lazy objects passed to mark_safe(), they weren't actually
marked as such so they could end up being escaped twice.

Refs #21882.

Backport of a878bf9b093bf15d751b070d132fec52a7523a47 from master.


  Commit: a77ec255737eb87d5e876083651c9aaf950d6f46
  
https://github.com/django/django/commit/a77ec255737eb87d5e876083651c9aaf950d6f46
  Author: Baptiste Mispelon 
  Date:   2014-02-05 (Wed, 05 Feb 2014)

  Changed paths:
M docs/releases/1.6.2.txt

  Log Message:
  ---
  [1.6.x] Added previous commit to 1.6.2 release notes.

Backport of 2dd88f0687c2bc9c457816a011bf5e46f6bf84ad from master.


Compare: https://github.com/django/django/compare/fd3fa851b592...a77ec255737e

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

[django/django] 2dd88f: Added previous commit to 1.6.2 release notes.

2014-02-05 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2dd88f0687c2bc9c457816a011bf5e46f6bf84ad
  
https://github.com/django/django/commit/2dd88f0687c2bc9c457816a011bf5e46f6bf84ad
  Author: Baptiste Mispelon 
  Date:   2014-02-05 (Wed, 05 Feb 2014)

  Changed paths:
M docs/releases/1.6.2.txt

  Log Message:
  ---
  Added previous commit to 1.6.2 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/52f2a34e4d7a7_2da9801d44321f6%40hookshot-fe9-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] a878bf: Revert "Fixed #20296 -- Allowed SafeData and Escap...

2014-02-05 Thread GitHub

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

  Changed paths:
M django/utils/safestring.py
M tests/utils_tests/test_safestring.py

  Log Message:
  ---
  Revert "Fixed #20296 -- Allowed SafeData and EscapeData to be lazy"

This reverts commit 2ee447fb5f8974b432d3dd421af9a242215aea44.

That commit introduced a regression (#21882) and didn't really
do what it was supposed to: while it did delay the evaluation
of lazy objects passed to mark_safe(), they weren't actually
marked as such so they could end up being escaped twice.

Refs #21882.


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

Re: [Django] #21882: Early modification bug in Django 1.6. with mark_safe + ugettext_lazy

2014-02-05 Thread Django

#21882: Early modification bug in Django 1.6. with mark_safe + ugettext_lazy
-+-
 Reporter:  nealtodd |Owner:  bmispelon
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  1.6
  Internationalization   |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:  mark_safe|  Needs documentation:  0
  ugettext_lazy  |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by Baptiste Mispelon ):

 In [changeset:"a878bf9b093bf15d751b070d132fec52a7523a47"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a878bf9b093bf15d751b070d132fec52a7523a47"
 Revert "Fixed #20296 -- Allowed SafeData and EscapeData to be lazy"

 This reverts commit 2ee447fb5f8974b432d3dd421af9a242215aea44.

 That commit introduced a regression (#21882) and didn't really
 do what it was supposed to: while it did delay the evaluation
 of lazy objects passed to mark_safe(), they weren't actually
 marked as such so they could end up being escaped twice.

 Refs #21882.
 }}}

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

Re: [Django] #20296: django.utils.safestring.mark_safe forces evaluation of lazy objects

2014-02-05 Thread Django

Comment (by Baptiste Mispelon ):

In [changeset:"a878bf9b093bf15d751b070d132fec52a7523a47"]:
{{{
#!CommitTicketReference repository=""
revision="a878bf9b093bf15d751b070d132fec52a7523a47"
Revert "Fixed #20296 -- Allowed SafeData and EscapeData to be lazy"

This reverts commit 2ee447fb5f8974b432d3dd421af9a242215aea44.

That commit introduced a regression (#21882) and didn't really
do what it was supposed to: while it did delay the evaluation
of lazy objects passed to mark_safe(), they weren't actually
marked as such so they could end up being escaped twice.

Refs #21882.
}}}

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

[django/django] a0fc7f: Fixed ImportError when running contrib.gis tests w...

2014-02-05 Thread GitHub

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

  Changed paths:
M django/contrib/gis/tests/maps/tests.py

  Log Message:
  ---
  Fixed ImportError when running contrib.gis tests without libgeos installed.


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

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

2014-02-05 Thread Django

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

Comment (by Florian Apolloner ):

 In [changeset:"297c009cf22b14b0124b790303404ee06a28"]:
 {{{
 #!CommitTicketReference repository=""
 revision="297c009cf22b14b0124b790303404ee06a28"
 Simplified signal code.

 Refs #21952
 }}}

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

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

2014-02-05 Thread Django

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

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


Comment:

 In [changeset:"c29d6f767691cceb9964c0d212e01281ac6721d3"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c29d6f767691cceb9964c0d212e01281ac6721d3"
 Fixed #21952 -- signals deadlock due to locking + weakref interaction
 }}}

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

[django/django] c29d6f: Fixed #21952 -- signals deadlock due to locking + ...

2014-02-05 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c29d6f767691cceb9964c0d212e01281ac6721d3
  
https://github.com/django/django/commit/c29d6f767691cceb9964c0d212e01281ac6721d3
  Author: Anssi Kääriäinen 
  Date:   2014-02-05 (Wed, 05 Feb 2014)

  Changed paths:
M django/dispatch/dispatcher.py
M tests/dispatch/tests/test_dispatcher.py

  Log Message:
  ---
  Fixed #21952 -- signals deadlock due to locking + weakref interaction


  Commit: 297c009cf22b14b0124b790303404ee06a28
  
https://github.com/django/django/commit/297c009cf22b14b0124b790303404ee06a28
  Author: Florian Apolloner 
  Date:   2014-02-05 (Wed, 05 Feb 2014)

  Changed paths:
M django/dispatch/dispatcher.py

  Log Message:
  ---
  Simplified signal code.

Refs #21952


Compare: https://github.com/django/django/compare/aea9faa146f5...297c009cf22b

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

[django/django] f265c1: Fixed gendered examples in the docs.

2014-02-05 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: f265c1ef13e6eaa75c8e1cfdaade527a1505bb5e
  
https://github.com/django/django/commit/f265c1ef13e6eaa75c8e1cfdaade527a1505bb5e
  Author: Loic Bistuer 
  Date:   2014-02-05 (Wed, 05 Feb 2014)

  Changed paths:
M docs/topics/db/managers.txt

  Log Message:
  ---
  Fixed gendered examples in the docs.


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

Re: [Django] #19947: weakref'd signal receivers may cause deadlock when gc'd

2014-02-05 Thread Django

#19947: weakref'd signal receivers may cause deadlock when gc'd
--+-
 Reporter:  john@…|Owner:
 Type:  Bug   |   Status:  closed
Component:  Core (Other)  |  Version:  1.5
 Severity:  Normal|   Resolution:  duplicate
 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 akaariai):

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


Comment:

 I am marking this as duplicate of #21952, that ticket contains a patch for
 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/077.c9a5f634c9c8637a0de76833a6ef8c85%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16774: Backtracking URL resolver

2014-02-05 Thread Django

#16774: Backtracking URL resolver
---+
 Reporter:  nbstrite   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Kronuz):

 When using a generator, as it did before, patch for #16774 wasn't
 resolving nested patterns like the following because the generator for the
 first pattern`r'^nestred/'` had already been extracted from the generator
 by the second try (so HTTP 404 was returned instead of HttpResponse "OK"):

 {{{#!python

 def response_view():
 return HttpResponse("OK")

 def does_not_resolve_view():
 raise DoesNotResolve

 urlpatterns += patterns('',
 (r'^nested/', include(patterns('',
 (r'^overlapping_view/$', does_not_resolve_view),
 (r'^overlapping_view/$', response_view),
 ))),
 )
 }}}

 I'm attaching a patch with tests.

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

Re: [Django] #21956: Inconsistent behaviour of Q objects

2014-02-05 Thread Django

#21956: Inconsistent behaviour of Q objects
-+-
 Reporter:  debanshuk|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by shai):

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


Comment:

 Per the documented [https://docs.djangoproject.com/en/1.6/internals
 /release-process/#supported-versions release process]:

   Committers may choose to backport bugfixes at their own discretion,
 provided they do not introduce backwards incompatibilities.

 This is a bugfix, not a security fix; a committer has considered
 backporting it, and decided against. The route to getting it backported
 nonetheless can go through two directions:

  * Go to [http://groups.google.com/group/django-developers the developers
 list] and argue your case there, and/or
  * Provide a patch against 1.5 yourself -- but be warned, without
 agreement on the list, there's a high chance of it getting rejected.

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

Re: [Django] #13024: Signal sent on application startup

2014-02-05 Thread Django

#13024: Signal sent on application startup
-+-
 Reporter:  wojteks  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Other) |  Version:
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Fixed on
Has patch:  0|  a branch
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by guettli):

 Just for the docs: With Django 1.7 there is a callback, which can be
 implemented: ready():

 
https://docs.djangoproject.com/en/dev/ref/applications/#django.apps.AppConfig.ready

 It gets called if the application is loaded. But it is called for non web
 usage, too (e.g. cron jobs).

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

[django/django] aea9fa: Fix pep8 violation in migration template.

2014-02-05 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: aea9faa146f5ce8bfaf038dfa2f4377e0543c569
  
https://github.com/django/django/commit/aea9faa146f5ce8bfaf038dfa2f4377e0543c569
  Author: Marc Tamlyn 
  Date:   2014-02-05 (Wed, 05 Feb 2014)

  Changed paths:
M django/db/migrations/writer.py

  Log Message:
  ---
  Fix pep8 violation in migration template.


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

[Django] #21957: keys issues in filebased cache backend

2014-02-05 Thread Django

#21957: keys issues in filebased cache backend
---+-
 Reporter:  san@…  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:  filebased cache
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+-
 on my fedora 19 system with django version 1.6.1 final I have an error
 while try to set and get keys from
 different sessionś : I add custom command to the django manage which set
 key in django.core.cache, this work is done by apache user. After that
 when apache server is runing and operate from apache user I can´t read
 that key. I found that file based backend give right file name and abs
 path to the pickle file but that file for some reason have different inode
 number when I read it in the apache operate mode and from django shell
 from apache user.

 thx

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

Re: [Django] #21954: 1.7a1 - Migration syntax error

2014-02-05 Thread Django

* cc: loic@… (added)

Comment:

@caulagi, migrations have limitations that normal models do not have:
everything must be serializable, or more specifically, "reconstructable"
(the system relies on "code generation" rather than "serialization" like
`pickle`).

For instance, `lambda` are valid and pretty common in models, especially
for `default` values, but these can't be supported by migrations; being
valid for model validation doesn't automatically make something usable by
migrations.

Now for the specific case of `datetime`, the system already goes out of
its way to add support for it, but trips because of timezone support. We
currently rely on the `repr` of `datetime` objects, but when a `tzinfo` is
present, the `repr` isn't valid Python. The challenge is now, how to make
`datetime` objects with `tzinfo` "reconstructable".

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

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

2014-02-05 Thread Django

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

Comment (by akaariai):

 hmmh, yeah, it could be possible that we leak dead weakref receivers. We
 could just add a and not self._dead_receivers check in 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/064.b4b4f32ed25242ad806fa058b1d632ce%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21954: 1.7a1 - Migration syntax error

2014-02-05 Thread Django

#21954: 1.7a1 - Migration syntax error
-+---
 Reporter:  caulagi  |Owner:
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-alpha-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+---

Comment (by caulagi):

 Our usecase is that when creating a Blog entry, most of the time, the
 default value is what we want.  But sometimes, we want to set
 {{{created}}} to a date in the past.  So in these cases, the user will
 override the default timezone.now that is shown in admin for Blog entry.

 Like @russellm mentioned, the stumbling thing is that it is a valid value.
 Otherwise, the model validation should fail, rather than the migration
 throwing an error, IMO.

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

Re: [Django] #21231: Limiting the number of variables and files that a POST request can contain

2014-02-05 Thread Django

#21231: Limiting the number of variables and files that a POST request can 
contain
---+
 Reporter:  epandurski@…   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  HTTP handling  |  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 epandurski@…):

 @apollo13: I may try to do this, but I am quite busy lately. Most
 probably, I will not have enough spare time to work on this soon. I expect
 the work to take 0.5-2 days, but I remember that the HTTP-parsing code is
 quite hairy, so it might get longer to do it right.

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

[Django] #21956: Inconsistent behaviour of Q objects

2014-02-05 Thread Django

#21956: Inconsistent behaviour of Q objects
--+
 Reporter:  debanshuk |  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
--+
 Suppose we have a contact model with following definition:

 {{{
 class Contact(models.Model):
 name = models.CharField()
 company_uid = models.IntegerField(null=True, blank=True)
 }}}

 Consider following two queries:

 `Contact.objects.filter(~(Q(name='ABC') | Q(company_uid=5)))`
 `Contact.objects.filter(~Q(name='ABC') & ~Q(company_uid=5))`

 These queries are exactly the same, right? Just used DeMorgan's law i.e
 "not (A or B)" is the same as "(not A) and (not B)". But the generated SQL
 of these queries says something else:

 `SELECT "profiles_contact"."id", "profiles_contact"."name",
 "profiles_contact"."company_uid" FROM "profiles_contact" WHERE NOT
 (("profiles_contact"."name" = ABC  OR "profiles_contact"."company_uid" = 5
 ))`

 `SELECT "profiles_contact"."id", "profiles_contact"."name",
 "profiles_contact"."company_uid" FROM "profiles_contact" WHERE (NOT
 ("profiles_contact"."name" = ABC ) AND NOT
 (("profiles_contact"."company_uid" = 5  AND
 "profiles_contact"."company_uid" IS NOT NULL)))`


 (The desired query is the one with `IS NOT NULL` condition)


 This issue only exists till version 1.5, it has been fixed in Django-1.6.
 There is already a closed bug
 (https://code.djangoproject.com/ticket/21192) which was similar to this
 one. The bug was closed stating that the issue has been fixed in
 Django-1.6 and changes required to back-patch the fixes to 1.5 are just
 too big. But I believe this issue is more severe than the issue stated the
 that bug, as it is a more general case and should be back-patched to 1.5
 and older version 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/052.d0b9f75d6e02e00f87033dc8de2407ee%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19716: Support microsecond precision in MySQL ORM DateTimeField

2014-02-05 Thread Django

#19716: Support microsecond precision in MySQL ORM DateTimeField
-+-
 Reporter:  erik@…   |Owner:  nobody
 Type:  New feature  |   Status:  new
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 russ.blaisdell@…):

 Here is the update to mysqldb/times.py
 54c54,59
 < return datetime(*[ int(x) for x in d.split('-')+t.split(':') ])
 ---
 > if '.' in t:
 > t, ms = t.split('.',1)
 > ms = ms.ljust(6, '0')
 > else:
 > ms = 0
 > return datetime(*[ int(x) for x in
 d.split('-')+t.split(':')+[ms] ])
 63,65c68,75
 < h, m, s = int(h), int(m), float(s)
 < td = timedelta(hours=abs(h), minutes=m, seconds=int(s),
  if '.' in s:
 > s, ms = s.split('.')
 > ms = ms.ljust(6, '0')
 > else:
 > ms = 0
 > h, m, s, ms = int(h), int(m), int(s), int(ms)
 > td = timedelta(hours=abs(h), minutes=m, seconds=s,
 >microseconds=ms)
 77,79c87,94
 < h, m, s = int(h), int(m), float(s)
 < return time(hour=h, minute=m, second=int(s),
 < microsecond=int(math.modf(s)[0] * 100))
 ---
 > if '.' in s:
 > s, ms = s.split('.')
 > ms = ms.ljust(6, '0')
 > else:
 > ms = 0
 > h, m, s, ms = int(h), int(m), int(s), int(ms)
 > return time(hour=h, minute=m, second=s,
 > microsecond=ms)

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

Re: [Django] #19716: Support microsecond precision in MySQL ORM DateTimeField

2014-02-05 Thread Django

#19716: Support microsecond precision in MySQL ORM DateTimeField
-+-
 Reporter:  erik@…   |Owner:  nobody
 Type:  New feature  |   Status:  new
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 anonymous):

 I have been running with this for awhile. For 1.6.1 this is the diff for
 db/backends/mysql/base.py
 162c162
 < supports_microsecond_precision = True
 ---
 > supports_microsecond_precision = False
 352c352
 < return six.text_type(value)
 ---
 > return six.text_type(value.replace(microsecond=0))
 363c363
 < return six.text_type(value)
 ---
 > return six.text_type(value.replace(microsecond=0))
 368c368
 < return [first, second]
 ---
 > return [first.replace(microsecond=0),
 second.replace(microsecond=0)]


 I must add that I also updated mysqldb 1.2.4 to handle microseconds at the
 same time.  Both have been working without issue ever since.

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

Re: [Django] #19726: Ordering on booleans works different with SQLite and Postgres

2014-02-05 Thread Django

Comment (by anonymous):

I'd just like to follow up with another scenario which might not have been
considered - developers building reusable apps, or entire projects
designed to be setup and deployed by others (e.g. Sentry).

This is vastly different to "one specific type of use case -- the
developer who switches databases between development and production", as
this assumes that the developer is working on one app/project and are also
the ones who deploy the project.

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

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

2014-02-05 Thread Django

#21795: preserve_filter doesn't work on production server
---+--
 Reporter:  honyczek   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  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:  1
---+--

Comment (by honyczek):

 No, on edit form I have URL:
 
{{{http://server/confiback/admin/frontend/device/89/?_changelist_filters=e%3D1}}}
 and after saving it returns to list with URL:
 {{{http://server/confiback/admin/frontend/device/?e=1}}}. But filter is
 not applied.

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

[Django] #21955: Formset save_as_new=True causes "This QueryDict instance is immutable" error

2014-02-05 Thread Django

#21955: Formset save_as_new=True causes "This QueryDict instance is immutable"
error
+
 Reporter:  robin   |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Forms   |Version:  1.6
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 Basically if you post a properly setup inline formset with
 '''save_as_new=True''' argument:
 {{{
 FormSet = inlineformset_factory(Model, SubModel)
 formset = FormSet(request.POST, save_as_new=True)
 }}}
 You will get
 {{{
 AttributeError at /
 This QueryDict instance is immutable
 }}}

 '''Some demo code below:'''

 views.py
 {{{#!python
 from django.forms.models import inlineformset_factory
 from django.middleware.csrf import get_token
 from django.http import HttpResponse
 from django.template.base import Template, Context

 from app.models import App, SubApp

 def home(request):
 FormSet = inlineformset_factory(App, SubApp)
 if request.method == 'POST':
 formset = FormSet(request.POST, save_as_new=True)
 else:
 formset = FormSet()

 csrf = get_token(request)

 t = '''
 
 {{ formset }}
 
 
 
 '''
 c = {
 'formset': formset,
 'csrf': csrf,
 }
 s = Template(t).render(Context(c))
 return HttpResponse(s)
 }}}

 models.py
 {{{#!python
 from django.db import models

 class App(models.Model):
 pass

 class SubApp(models.Model):
 app = models.ForeignKey(App)
 }}}

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

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

47 matches

Mail list logo