date:20140924

Re: [Django] #23426: migrations.RunSQL's function signature implies it won't do any parameter substitution

2014-09-24 Thread Django

#23426: migrations.RunSQL's function signature implies it won't do any parameter
substitution
-+-
 Reporter:  ris  |Owner:
 Type:   |  Markush2010
  Cleanup/optimization   |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  migrations sql   | Triage Stage:  Accepted
  runsql params escape   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by loic):

 * needs_better_patch:  0 => 1
 * version:  1.7 => master
 * easy:  1 => 0


Comment:

 Reopening for the 1.8 branch.

 The implementation proposed in PR3267 won't play well with multiple
 statements (e.g. two INSERT statements separated by a semicolon).

 Possible fix, make `params` and `reverse_params` a list whose length must
 match the number of SQL statements.

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

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

[django/django] 49e693: Added my bio to team.txt

2014-09-24 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 49e693c8137d260906608f585dfb177255ab9322
  
https://github.com/django/django/commit/49e693c8137d260906608f585dfb177255ab9322
  Author: Michael Manfre 
  Date:   2014-09-24 (Wed, 24 Sep 2014)

  Changed paths:
M docs/internals/team.txt

  Log Message:
  ---
  Added my bio to team.txt


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

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

2014-09-24 Thread Django

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

Comment (by davide-ceretti):

 Patch for M2mThroughTests refactor is at
 https://github.com/django/django/pull/3273

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

Re: [Django] #15727: Add support for Content-Security-Policy (CSP) to core

2014-09-24 Thread Django

#15727: Add support for Content-Security-Policy (CSP) to core
---+
 Reporter:  db.pub.mail@…  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  HTTP handling  |  Version:  1.2
 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 nhazar):

 After 3 years and 5 major releases, adding content security policy support
 to Django would still totally rock.

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

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

Re: [Django] #23410: Backward migrations change overall state rather than reverting single migration

2014-09-24 Thread Django

#23410: Backward migrations change overall state rather than reverting single
migration
-+--
 Reporter:  Markush2010  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by Naddiseo):

 * cc: github@… (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/069.0121f34d585eb94017f5ac3761e60dc9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23551: Exception raised when using the bash autocompletion with Python 3

2014-09-24 Thread Django

#23551: Exception raised when using the bash autocompletion with Python 3
-+---
 Reporter:  marco-buttu  |Owner:  marco-buttu
 Type:  Bug  |   Status:  assigned
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+---

Comment (by marco-buttu):

 The `test_subcommand_completed.patch` contains the regression test and
 also a patch for the test itself, because in
 `tests/bash_completion/tests.py` there was an error in the value assigned
 to `$COMP_CWORD` . I created a pull request on github:
 https://github.com/django/django/pull/3272

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

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

Re: [Django] #23554: Unmodified object fails to save because of UNIQUE constraint

2014-09-24 Thread Django

#23554: Unmodified object fails to save because of UNIQUE constraint
---+--
 Reporter:  tinloaf|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Uncategorized  |  Version:  1.7
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by tinloaf):

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


Comment:

 Ugh, forget it, sometimes I'm braindead (and passing self to a super-
 call). Strange that it does not blow up though.

 Sorry for the noise.

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

Re: [Django] #23554: Unmodified object fails to save because of UNIQUE constraint

2014-09-24 Thread Django

#23554: Unmodified object fails to save because of UNIQUE constraint
---+--
 Reporter:  tinloaf|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  1.7
 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 tinloaf):

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


Comment:

 Got something: I looked at django.db.connection.queries. The first query
 is when it retrieves the mandates, the second one should be an UPDATE, but
 for some reason it's an INSERT. What's going on there?

 {{{
 >>> print(connection.queries)
 [
 {'time': '0.001', 'sql': 'QUERY = \'SELECT "finance_mandate"."id",
 "finance_mandate"."user_id", "finance_mandate"."holder",
 "finance_mandate"."street", "finance_mandate"."plz",
 "finance_mandate"."city", "finance_mandate"."country",
 "finance_mandate"."iban",
 "finance_mandate"."bic", "finance_mandate"."active",
 "finance_mandate"."revoked_on", "finance_mandate"."mandate_id" FROM
 "finance_mandate"
 LIMIT 1\' - PARAMS = ()'},

 {'time': '0.000', 'sql': "QUERY = 'BEGIN' - PARAMS = ()"}, {'time':
 '0.000', 'sql': 'QUERY = \'INSERT INTO
 "finance_mandate" ("id", "user_id", "holder", "street", "plz", "city",
 "country", "iban", "bic", "active", "revoked_on", "mandate_id")
 SELECT %s AS "id", %s AS "user_id", %s AS "holder", %s AS "street", %s AS
 "plz", %s AS "city", %s AS "country", %s AS "iban", %s AS "bic",
 %s AS "active", %s AS "revoked_on", %s AS "mandate_id"\' - PARAMS = (1, 2,
 \'...\', \'...\', ..., \'...\',
 \'Deutschland\', \'...\', \'...\', False, None, \'...\')'}]
 }}}

 (Replaced actual data with '...')

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

[Django] #23554: Unmodified object fails to save because of UNIQUE constraint

2014-09-24 Thread Django

#23554: Unmodified object fails to save because of UNIQUE constraint
---+
 Reporter:  tinloaf|  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Uncategorized  |Version:  1.7
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Hi. I have a model (see below) of which I cannot save() an object again
 after creating it once, the database backend (sqlite) states that the ID
 violates a unique constraint. See here:

 {{{
 >>> from finance.models import Mandate
 >>> m = Mandate.objects.all()[0]
 >>> m.id
 1
 >>> m.save()
 Traceback (most recent call last):
   File "", line 1, in 
   File "/mnt/daten/home/tinloaf/src/alumnet/alumnet/finance/models.py",
 line 149, in save
 super(Mandate, self).save(self, *args, **kwargs)
   File "/mnt/daten/home/tinloaf/src/alumnet/venv/lib/python3.3/site-
 packages/django/db/models/base.py", line 590, in save
 force_update=force_update, update_fields=update_fields)
   File "/mnt/daten/home/tinloaf/src/alumnet/venv/lib/python3.3/site-
 packages/django/db/models/base.py", line 618, in save_base
 updated = self._save_table(raw, cls, force_insert, force_update,
 using, update_fields)
   File "/mnt/daten/home/tinloaf/src/alumnet/venv/lib/python3.3/site-
 packages/django/db/models/base.py", line 699, in _save_table
 result = self._do_insert(cls._base_manager, using, fields, update_pk,
 raw)
   File "/mnt/daten/home/tinloaf/src/alumnet/venv/lib/python3.3/site-
 packages/django/db/models/base.py", line 732, in _do_insert
 using=using, raw=raw)
   File "/mnt/daten/home/tinloaf/src/alumnet/venv/lib/python3.3/site-
 packages/django/db/models/manager.py", line 92, in manager_method
 return getattr(self.get_queryset(), name)(*args, **kwargs)
   File "/mnt/daten/home/tinloaf/src/alumnet/venv/lib/python3.3/site-
 packages/django/db/models/query.py", line 921, in _insert
 return query.get_compiler(using=using).execute_sql(return_id)
   File "/mnt/daten/home/tinloaf/src/alumnet/venv/lib/python3.3/site-
 packages/django/db/models/sql/compiler.py", line 920, in execute_sql
 cursor.execute(sql, params)
   File "/mnt/daten/home/tinloaf/src/alumnet/venv/lib/python3.3/site-
 packages/django/db/backends/utils.py", line 81, in execute
 return super(CursorDebugWrapper, self).execute(sql, params)
   File "/mnt/daten/home/tinloaf/src/alumnet/venv/lib/python3.3/site-
 packages/django/db/backends/utils.py", line 65, in execute
 return self.cursor.execute(sql, params)
   File "/mnt/daten/home/tinloaf/src/alumnet/venv/lib/python3.3/site-
 packages/django/db/utils.py", line 94, in __exit__
 six.reraise(dj_exc_type, dj_exc_value, traceback)
   File "/mnt/daten/home/tinloaf/src/alumnet/venv/lib/python3.3/site-
 packages/django/utils/six.py", line 549, in reraise
 raise value.with_traceback(tb)
   File "/mnt/daten/home/tinloaf/src/alumnet/venv/lib/python3.3/site-
 packages/django/db/backends/utils.py", line 65, in execute
 return self.cursor.execute(sql, params)
   File "/mnt/daten/home/tinloaf/src/alumnet/venv/lib/python3.3/site-
 packages/django/db/backends/sqlite3/base.py", line 485, in execute
 return Database.Cursor.execute(self, query, params)
 django.db.utils.IntegrityError: UNIQUE constraint failed:
 finance_mandate.id

 }}}

 I looked into the database manually and verified that everything is as it
 is supposed to be, no duplicate PKs or what. Please tell me if there is
 any further debugging that I can do.

 Here is the model:

 {{{
 class Mandate(models.Model):
 user = models.ForeignKey(User)
 holder = models.TextField()
 street = models.CharField(max_length=40)
 plz = models.IntegerField()
 city = models.CharField(max_length=20)
 country = models.CharField(max_length=20)
 iban = IBANField()
 bic = SWIFTBICField()
 active = models.BooleanField()
 revoked_on = models.DateField(null=True, blank=True)
 mandate_id = models.CharField(max_length=35, unique=True)

 def save(self, *args, **kwargs):
 if (self.mandate_id is None) or (len(self.mandate_id) == 0):
 self.mandate_id = self.generate_id()
 super(Mandate, self).save(self, *args, **kwargs)
 }}}

--
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

Re: [Django] #23410: Backward migrations change overall state rather than reverting single migration

2014-09-24 Thread Django

#23410: Backward migrations change overall state rather than reverting single
migration
-+--
 Reporter:  Markush2010  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by carljm):

 #23474 was a duplicate.

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

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

Re: [Django] #23474: Schema migrations can inadvertently destroy data

2014-09-24 Thread Django

#23474: Schema migrations can inadvertently destroy data
-+-
 Reporter:  Naddiseo |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7
 Severity:  Release blocker  |   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 timgraham):

 * resolution:  fixed => duplicate


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

Re: [Django] #23474: Schema migrations can inadvertently destroy data

2014-09-24 Thread Django

#23474: Schema migrations can inadvertently destroy data
-+
 Reporter:  Naddiseo |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7
 Severity:  Release blocker  |   Resolution:  fixed
 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 Tim Graham ):

 In [changeset:"d7b32d31205834262758ca5f48e5fe3a453f7ad3"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d7b32d31205834262758ca5f48e5fe3a453f7ad3"
 [1.7.x] Revert "Fixed #23474 -- Prevented migrating backwards from
 unapplying the wrong migrations."

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

[django/django] d7b32d: [1.7.x] Revert "Fixed #23474 -- Prevented migratin...

2014-09-24 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: d7b32d31205834262758ca5f48e5fe3a453f7ad3
  
https://github.com/django/django/commit/d7b32d31205834262758ca5f48e5fe3a453f7ad3
  Author: Tim Graham 
  Date:   2014-09-24 (Wed, 24 Sep 2014)

  Changed paths:
M django/db/migrations/executor.py
M docs/releases/1.7.1.txt
M tests/migrations/test_executor.py
R tests/migrations/test_migrations_backwards_deps_1/__init__.py
R tests/migrations2/test_migrations_backwards_deps_2/0001_initial.py
R tests/migrations2/test_migrations_backwards_deps_2/__init__.py

  Log Message:
  ---
  [1.7.x] Revert "Fixed #23474 -- Prevented migrating backwards from unapplying 
the wrong migrations."

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

Re: [Django] #23474: Schema migrations can inadvertently destroy data

2014-09-24 Thread Django

#23474: Schema migrations can inadvertently destroy data
-+
 Reporter:  Naddiseo |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7
 Severity:  Release blocker  |   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"d7ab2cefb7ec94bf45d37a02c79b6703ea2880e5"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d7ab2cefb7ec94bf45d37a02c79b6703ea2880e5"
 Revert "Fixed #23474 -- Prevented migrating backwards from unapplying the
 wrong migrations."

 This reverts commit abcf28a07695a45cb5fb15b81bffc97bea5e0be3.
 }}}

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

[django/django] d7ab2c: Revert "Fixed #23474 -- Prevented migrating backwa...

2014-09-24 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: d7ab2cefb7ec94bf45d37a02c79b6703ea2880e5
  
https://github.com/django/django/commit/d7ab2cefb7ec94bf45d37a02c79b6703ea2880e5
  Author: Tim Graham 
  Date:   2014-09-24 (Wed, 24 Sep 2014)

  Changed paths:
M django/db/migrations/executor.py
M docs/releases/1.7.1.txt
M tests/migrations/test_executor.py
R tests/migrations/test_migrations_backwards_deps_1/__init__.py
R tests/migrations2/test_migrations_backwards_deps_2/0001_initial.py
R tests/migrations2/test_migrations_backwards_deps_2/__init__.py

  Log Message:
  ---
  Revert "Fixed #23474 -- Prevented migrating backwards from unapplying the 
wrong migrations."

This reverts commit abcf28a07695a45cb5fb15b81bffc97bea5e0be3.


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

Re: [Django] #23410: Backward migrations change overall state rather than reverting single migration

2014-09-24 Thread Django

Comment (by carljm):

Andrew: I understand the contract you described, and I understand that it
preserves the invariant that the arguments you pass to "migrate" always
specify precisely one database state, regardless of whether you are
migrating forwards or backwards. But I think there is a competing value
here (reducing the risk of data loss inherent in rolling back migrations
that arguably were not requested for rollback), which to me seems a higher
priority than the name-refers-to-single-state invariant.

If I were to describe the ideal behavior precisely, it would be this:
given a request to migrate to "appname 0001", we pick whatever target spot
on the linearized migration plan between "appname 0001" and "appname 0002"
results in the fewest possible migrations from other apps requiring
migrate/rollback. The only guaranteed invariant would be that "appname
0001" refers to a state where "appname 0001" is applied and "appname 0002"
is not, and all dependency constraints are satisfied.

This choice would accept that a name like "appname 0001" is imprecise
rather than precise, but would consider that a reasonable tradeoff in
exchange for behavior that is (arguably?) more intuitive and less likely
to result in data loss.

If you'd rather discuss on the mailing list, I can bring up the question
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/069.f14bbdc541b6c399489b846583c36b09%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23474: Schema migrations can inadvertently destroy data

2014-09-24 Thread Django

#23474: Schema migrations can inadvertently destroy data
-+
 Reporter:  Naddiseo |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7
 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 carljm):

 After discussion with MarkusH and looking at the patch here more closely,
 I agree with him that this particular implementation is problematic and
 should be rolled back.

 I still favor a change in behavior as described in my comment above, but
 it needs a better implementation. That discussion can happen on the
 mailing list and/or #23410.

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

Re: [Django] #23474: Schema migrations can inadvertently destroy data

2014-09-24 Thread Django

#23474: Schema migrations can inadvertently destroy data
-+
 Reporter:  Naddiseo |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7
 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 Markush2010):

 With the patch [abcf28a076] being applied I cannot rollback to a previous
 migration if. Furthermore the detection of the "next_migration" is wrong
 and depends on a leading number in the migration name which is not
 required. Dependencies are defined explicitly and not implicit by their
 name.

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

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

Re: [Django] #23321: Remove .mo files from the Django Git repository

2014-09-24 Thread Django

#23321: Remove .mo files from the Django Git repository
--+
 Reporter:  claudep   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Internationalization  |  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 aaugustin):

 That change would make it a bit more error-prone to work on i18n'd
 projects with the development version of Django.

 I'm not saying we can't remove the .mo files, but we need to think about
 the consequences. They add some value.

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

Re: [Django] #23421: dict get for TEST_SERIALIZE in django.test.runner.setup_databases() always return True

2014-09-24 Thread Django

#23421: dict get for TEST_SERIALIZE in django.test.runner.setup_databases() 
always
return True
-+-
 Reporter:  gkoller  |Owner:  timgraham
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  1.7
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"02aa3e30e9cb8e5be5c33082c3548e2a6e1b91cb"]:
 {{{
 #!CommitTicketReference repository=""
 revision="02aa3e30e9cb8e5be5c33082c3548e2a6e1b91cb"
 [1.7.x] Fixed #23421 -- Corrected TEST SERIALIZE setting.

 Thanks gkoller for the report and Markus Holtermann for review.
 }}}

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

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

[django/django] 02aa3e: [1.7.x] Fixed #23421 -- Corrected TEST SERIALIZE s...

2014-09-24 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 02aa3e30e9cb8e5be5c33082c3548e2a6e1b91cb
  
https://github.com/django/django/commit/02aa3e30e9cb8e5be5c33082c3548e2a6e1b91cb
  Author: Tim Graham 
  Date:   2014-09-24 (Wed, 24 Sep 2014)

  Changed paths:
M django/test/runner.py
M docs/ref/settings.txt
M docs/releases/1.7.1.txt
M docs/topics/testing/advanced.txt
M tests/test_runner/tests.py

  Log Message:
  ---
  [1.7.x] Fixed #23421 -- Corrected TEST SERIALIZE setting.

Thanks gkoller for the report and Markus Holtermann for review.


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

Re: [Django] #23421: dict get for TEST_SERIALIZE in django.test.runner.setup_databases() always return True

2014-09-24 Thread Django

#23421: dict get for TEST_SERIALIZE in django.test.runner.setup_databases() 
always
return True
-+-
 Reporter:  gkoller  |Owner:  timgraham
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  1.7
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"a4f23eba2e690f1331fe35d6f29af42899e80395"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a4f23eba2e690f1331fe35d6f29af42899e80395"
 Fixed #23421 -- Corrected TEST SERIALIZE setting.

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

[django/django] a4f23e: Fixed #23421 -- Corrected TEST SERIALIZE setting.

2014-09-24 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a4f23eba2e690f1331fe35d6f29af42899e80395
  
https://github.com/django/django/commit/a4f23eba2e690f1331fe35d6f29af42899e80395
  Author: Tim Graham 
  Date:   2014-09-24 (Wed, 24 Sep 2014)

  Changed paths:
M django/test/runner.py
M docs/ref/settings.txt
M docs/releases/1.7.1.txt
M docs/topics/testing/advanced.txt
M tests/test_runner/tests.py

  Log Message:
  ---
  Fixed #23421 -- Corrected TEST SERIALIZE setting.

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

Re: [Django] #23415: OneToField reference to default 'id' instead of actual primary key

2014-09-24 Thread Django

#23415: OneToField reference to default 'id' instead of actual primary key
-+---
 Reporter:  sky-chen |Owner:  Markush2010
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7
 Severity:  Release blocker  |   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 timgraham):

 * severity:  Normal => Release blocker


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

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

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

Comment (by Tim Graham ):

 In [changeset:"5356183716daa88e5c0009b179de55370bd5c5da"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5356183716daa88e5c0009b179de55370bd5c5da"
 [1.7.x] Fixed #22959 -- Documented that class-based validators need to be
 deconstructible.

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

[django/django] 535618: [1.7.x] Fixed #22959 -- Documented that class-base...

2014-09-24 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 5356183716daa88e5c0009b179de55370bd5c5da
  
https://github.com/django/django/commit/5356183716daa88e5c0009b179de55370bd5c5da
  Author: Markus Holtermann 
  Date:   2014-09-24 (Wed, 24 Sep 2014)

  Changed paths:
M docs/ref/validators.txt

  Log Message:
  ---
  [1.7.x] Fixed #22959 -- Documented that class-based validators need to be 
deconstructible.

Backport of c692e37b63 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/54230e9be14ba_62043ff267bf12bc10926%40hookshot-fe3-cp1-prd.iad.github.net.mail.
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-09-24 Thread Django

#22959: Document that custom validator must be comparable to prevent infinite
migrations
-+-
 Reporter:  lorinkoz@…   |Owner:
 Type:   |  Markush2010
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.7-rc-1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  migrations   | 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:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"c692e37b6350171ee2e04b3e7090babf34ac140b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c692e37b6350171ee2e04b3e7090babf34ac140b"
 Fixed #22959 -- Documented that class-based validators need to be
 deconstructible.
 }}}

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

[django/django] c692e3: Fixed #22959 -- Documented that class-based valida...

2014-09-24 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c692e37b6350171ee2e04b3e7090babf34ac140b
  
https://github.com/django/django/commit/c692e37b6350171ee2e04b3e7090babf34ac140b
  Author: Markus Holtermann 
  Date:   2014-09-24 (Wed, 24 Sep 2014)

  Changed paths:
M docs/ref/validators.txt

  Log Message:
  ---
  Fixed #22959 -- Documented that class-based validators need to be 
deconstructible.


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

Re: [Django] #23421: dict get for TEST_SERIALIZE in django.test.runner.setup_databases() always return True

2014-09-24 Thread Django

#23421: dict get for TEST_SERIALIZE in django.test.runner.setup_databases() 
always
return True
-+-
 Reporter:  gkoller  |Owner:  timgraham
 Type:  Bug  |   Status:  assigned
Component:  Testing framework|  Version:  1.7
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Markush2010):

 * stage:  Accepted => Ready for checkin


Comment:

 Pull request looks good to me.

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

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

[django/django] cf78a0: [1.7.x] Fixed #23473 -- Documented that @deconstru...

2014-09-24 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: cf78a0ccc39902f73a1e1540b59c3b6c89aa51f6
  
https://github.com/django/django/commit/cf78a0ccc39902f73a1e1540b59c3b6c89aa51f6
  Author: Markus Holtermann 
  Date:   2014-09-24 (Wed, 24 Sep 2014)

  Changed paths:
M docs/topics/migrations.txt

  Log Message:
  ---
  [1.7.x] Fixed #23473 -- Documented that @deconstructible classes need __eq__.

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

Re: [Django] #23473: Django prompts to create new migrations when none are needed when a class is used in a field declaration

2014-09-24 Thread Django

#23473: Django prompts to create new migrations when none are needed when a 
class
is used in a field declaration
+---
 Reporter:  dlo |Owner:  Markush2010
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.7
 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
+---

Comment (by Tim Graham ):

 In [changeset:"cf78a0ccc39902f73a1e1540b59c3b6c89aa51f6"]:
 {{{
 #!CommitTicketReference repository=""
 revision="cf78a0ccc39902f73a1e1540b59c3b6c89aa51f6"
 [1.7.x] Fixed #23473 -- Documented that @deconstructible classes need
 __eq__.

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

[django/django] 066e67: Fixed #23473 -- Documented that @deconstructible c...

2014-09-24 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 066e672d79ceb416ac87e51c8fa400221fa8604f
  
https://github.com/django/django/commit/066e672d79ceb416ac87e51c8fa400221fa8604f
  Author: Markus Holtermann 
  Date:   2014-09-24 (Wed, 24 Sep 2014)

  Changed paths:
M docs/topics/migrations.txt

  Log Message:
  ---
  Fixed #23473 -- Documented that @deconstructible classes need __eq__.


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

Re: [Django] #23473: Django prompts to create new migrations when none are needed when a class is used in a field declaration

2014-09-24 Thread Django

#23473: Django prompts to create new migrations when none are needed when a 
class
is used in a field declaration
+---
 Reporter:  dlo |Owner:  Markush2010
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.7
 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:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"066e672d79ceb416ac87e51c8fa400221fa8604f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="066e672d79ceb416ac87e51c8fa400221fa8604f"
 Fixed #23473 -- Documented that @deconstructible classes need __eq__.
 }}}

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

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

[django/django] 40e5eb: [1.7.x] Corrected --noinput docs for makemigration...

2014-09-24 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 40e5eb4114e66dfaacea162fc9f39c0618dcfad9
  
https://github.com/django/django/commit/40e5eb4114e66dfaacea162fc9f39c0618dcfad9
  Author: Tim Graham 
  Date:   2014-09-24 (Wed, 24 Sep 2014)

  Changed paths:
M docs/ref/django-admin.txt

  Log Message:
  ---
  [1.7.x] Corrected --noinput docs for makemigrations; refs #23407.

Backport of 450a616004 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/5422ffb48b189_3b033ff1c846f2b81049ab%40hookshot-fe4-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23407: makemigrations doesn't use --noinput

2014-09-24 Thread Django

#23407: makemigrations doesn't use --noinput
--+
 Reporter:  bmispelon |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  1.7
 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 Tim Graham ):

 In [changeset:"40e5eb4114e66dfaacea162fc9f39c0618dcfad9"]:
 {{{
 #!CommitTicketReference repository=""
 revision="40e5eb4114e66dfaacea162fc9f39c0618dcfad9"
 [1.7.x] Corrected --noinput docs for makemigrations; refs #23407.

 Backport of 450a616004 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/067.ef5500b5cdf7b445764515f58cc08dc5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23407: makemigrations doesn't use --noinput

2014-09-24 Thread Django

#23407: makemigrations doesn't use --noinput
--+
 Reporter:  bmispelon |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  1.7
 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 timgraham):

 * severity:  Release blocker => Normal


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

Re: [Django] #23407: makemigrations doesn't use --noinput

2014-09-24 Thread Django

#23407: makemigrations doesn't use --noinput
--+
 Reporter:  bmispelon |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  1.7
 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 Tim Graham ):

 In [changeset:"450a61600407d7320b85b75b441ce67b199da68b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="450a61600407d7320b85b75b441ce67b199da68b"
 Corrected --noinput docs for makemigrations; refs #23407.
 }}}

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

[django/django] 450a61: Corrected --noinput docs for makemigrations; refs ...

2014-09-24 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 450a61600407d7320b85b75b441ce67b199da68b
  
https://github.com/django/django/commit/450a61600407d7320b85b75b441ce67b199da68b
  Author: Tim Graham 
  Date:   2014-09-24 (Wed, 24 Sep 2014)

  Changed paths:
M docs/ref/django-admin.txt

  Log Message:
  ---
  Corrected --noinput docs for makemigrations; refs #23407.


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

Re: [Django] #23553: Incorrect LOCALE_PATHS settings doesn't raise any exception

2014-09-24 Thread Django

#23553: Incorrect LOCALE_PATHS settings doesn't raise any exception
-+-
 Reporter:  elvard   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:   |  Version:  1.7
  Internationalization   |   Resolution:  duplicate
 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 elvard):

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


Comment:

 Sorry, it's duplicate of #22780... Bug is already fixed in 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.9537e27141d0e6469a31b4df4ca0021a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23553: Incorrect LOCALE_PATHS settings doesn't raise any exception

2014-09-24 Thread Django

#23553: Incorrect LOCALE_PATHS settings doesn't raise any exception
--+
 Reporter:  elvard|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Internationalization  |Version:  1.7
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 I had following line in settings:


 {{{
 LOCALE_PATHS = os.path.join(PROJECT_ROOT, 'locale')
 }}}

 which is invalid. LOCALE_PATHS must be list or tuple of paths, not string.

 Runserver command doesn't raise any warning or error. System check doesn't
 find any issue. Still, runserver auto-reloading is broken with this
 settings and it's quiet difficult to spot this bug.

 Compared with other similar settings:
 - TEMPLATE_DIRS raises ImproperlyConfigured directly
 - STATICFILES_DIRS raises ImproperlyConfigured with command collectstatic,
 runserver works fine (even with reloading).

--
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.47df5b06a466462c5e481bf07e4e724b%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-09-24 Thread Django

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

 * has_patch:  0 => 1


Comment:

 I added a pull request with documentation updates:
 https://github.com/django/django/pull/3271

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

Re: [Django] #23473: Django prompts to create new migrations when none are needed when a class is used in a field declaration

2014-09-24 Thread Django

#23473: Django prompts to create new migrations when none are needed when a 
class
is used in a field declaration
+---
 Reporter:  dlo |Owner:  Markush2010
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  1.7
 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 Markush2010):

 * has_patch:  0 => 1


Comment:

 I added a pull request with documentation updates:
 https://github.com/django/django/pull/3271

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

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

[django/django] 216830: Added SuspiciousOperation to list of caught except...

2014-09-24 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 21683011d5b46806d12106a3079b704ed41cd261
  
https://github.com/django/django/commit/21683011d5b46806d12106a3079b704ed41cd261
  Author: Thomas Grainger 
  Date:   2014-09-24 (Wed, 24 Sep 2014)

  Changed paths:
M docs/topics/testing/tools.txt

  Log Message:
  ---
  Added SuspiciousOperation to list of caught exceptions in testing 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/5422f9aeeafaa_40a53f94da2e12c082469%40hookshot-fe4-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 9beca9: [1.6.x] Added SuspiciousOperation to list of caugh...

2014-09-24 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 9beca95eb0f2b5c19b6f7824fd75326527132566
  
https://github.com/django/django/commit/9beca95eb0f2b5c19b6f7824fd75326527132566
  Author: Thomas Grainger 
  Date:   2014-09-24 (Wed, 24 Sep 2014)

  Changed paths:
M docs/topics/testing/tools.txt

  Log Message:
  ---
  [1.6.x] Added SuspiciousOperation to list of caught exceptions in testing 
docs.

Backport of 21683011d5 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/5422f9c9ea6dc_612e3f9c67ae92bc40455%40hookshot-fe3-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] bebdb0: [1.7.x] Added SuspiciousOperation to list of caugh...

2014-09-24 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: bebdb026ceb659d5e86955f5ab07fd971040a878
  
https://github.com/django/django/commit/bebdb026ceb659d5e86955f5ab07fd971040a878
  Author: Thomas Grainger 
  Date:   2014-09-24 (Wed, 24 Sep 2014)

  Changed paths:
M docs/topics/testing/tools.txt

  Log Message:
  ---
  [1.7.x] Added SuspiciousOperation to list of caught exceptions in testing 
docs.

Backport of 21683011d5 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/5422f9c91dddb_3c5d3f87ea2a52b86893b%40hookshot-fe4-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23473: Django prompts to create new migrations when none are needed when a class is used in a field declaration

2014-09-24 Thread Django

#23473: Django prompts to create new migrations when none are needed when a 
class
is used in a field declaration
+---
 Reporter:  dlo |Owner:  Markush2010
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  1.7
 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 Markush2010):

 Replying to [comment:6 dlo]:
 > Is there any way we could also make the `./manage.py makemigrations`
 command fail unless `__eq__` is implemented? Otherwise, users might not
 know where to look to fix the problem.
 This is rather complicated as `object` itself has a `__eq__` method. and
 would require some crazy comparisons. For what I've tested, this seems to
 work.

 Two solutions that somehow work, but that I'm not really a friend of. The
 if clause is really error-prone.

 1. Fails even on `manage.py shell`:

 {{{#!python
 diff --git a/django/utils/deconstruct.py b/django/utils/deconstruct.py
 index a51a169..b0443ee 100644
 --- a/django/utils/deconstruct.py
 +++ b/django/utils/deconstruct.py
 @@ -49,6 +49,13 @@ def deconstructible(*args, **kwargs):
  klass.__new__ = staticmethod(__new__)
  klass.deconstruct = deconstruct

 +if not hasattr(klass, '__eq__') or klass.__eq__ == object.__eq__:
 +raise ValueError(
 +"Cannot deconstruct class %s since no __eq__ method
 exists or "
 +"__eq__ is inherited from 'object'. This method is
 required "
 +"to prevent infinit migration creation"
 +% klass.__name__)
 +
  return klass

  if not args:
 }}}

 2. Fails only when `__eq__` is called:

 {{{#!python
 diff --git a/django/utils/deconstruct.py b/django/utils/deconstruct.py
 index a51a169..7c3abac 100644
 --- a/django/utils/deconstruct.py
 +++ b/django/utils/deconstruct.py
 @@ -49,6 +49,16 @@ def deconstructible(*args, **kwargs):
  klass.__new__ = staticmethod(__new__)
  klass.deconstruct = deconstruct

 +if not hasattr(klass, '__eq__') or klass.__eq__ == object.__eq__:
 +def __eq__(obj, other):
 +raise ValueError(
 +"Cannot deconstruct class %s since no __eq__ method "
 +"exists or __eq__ is inherited from 'object'. This
 method "
 +"is required to prevent infinit migration creation"
 +% obj.__class__.__name__)
 +
 +klass.__eq__ = __eq__
 +
  return klass

  if not args:
 }}}

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

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

Re: [Django] #23552: Bad request (Error 400) on almost all inline adding calls

2014-09-24 Thread Django

#23552: Bad request (Error 400) on almost all inline adding calls
-+-
 Reporter:  nux17|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.7
 Severity:  Release blocker  |   Resolution:  duplicate
 Keywords:  inline, error,   | Triage Stage:
  http, response, 400|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

 * status:  new => closed
 * needs_better_patch:   => 0
 * component:  HTTP handling => contrib.admin
 * needs_tests:   => 0
 * needs_docs:   => 0
 * resolution:   => duplicate


Comment:

 I'm pretty confident this a duplicate of #23431.

 Can you confirm your issues are solved on the `stable/1.7.x` branch? (`pip
 uninstall django && pip install
 git+git://github.com/django/django.git@stable/1.7.x`.

 The fix should be part of the `1.7.1` release.

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

Re: [Django] #23473: Django prompts to create new migrations when none are needed when a class is used in a field declaration

2014-09-24 Thread Django

#23473: Django prompts to create new migrations when none are needed when a 
class
is used in a field declaration
+---
 Reporter:  dlo |Owner:  Markush2010
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  1.7
 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 dlo):

 Is there any way we could also make the `./manage.py makemigrations`
 command fail unless `__eq__` is implemented? Otherwise, users might not
 know where to look to fix the problem.

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

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

[Django] #23552: Bad request (Error 400) on almost all inline adding calls

2014-09-24 Thread Django

I'm forwarding my Django setup to 1.7 and having a check for
incompatibilites/bugs from my setup previously on 1.6.

Working on a test setup, I found out most of the adding inline (green
crosses) models now retrieve a "Bad Request (400)" error. The URL seems to
have changed from 1.6, but this seems to work with some inline calls
(found one working and actually displaying the adding form).

Nothing on logs from Django, and Debug is set to True.

Cutting the URL from the slash '/' after 'add' just before the GET
arguments (to_field=xxx=1) brings the page up.

This is blocking my deployment, and after being investigating about this
bug for half a day now I can't manage to find fix/info about it.

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

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

Re: [Django] #23473: Django prompts to create new migrations when none are needed when a class is used in a field declaration

2014-09-24 Thread Django

#23473: Django prompts to create new migrations when none are needed when a 
class
is used in a field declaration
+---
 Reporter:  dlo |Owner:  Markush2010
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  1.7
 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 Markush2010):

 * owner:  nobody => Markush2010
 * cc: info+coding@… (added)
 * 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/061.b8b2c19d361b7e1819d3ead539438c72%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-09-24 Thread Django

#22959: Document that custom validator must be comparable to prevent infinite
migrations
-+-
 Reporter:  lorinkoz@…   |Owner:
 Type:   |  Markush2010
  Cleanup/optimization   |   Status:  assigned
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
-+-
Changes (by Markush2010):

 * status:  new => assigned
 * cc: info+coding@… (added)
 * owner:  nobody => Markush2010


--
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.5c5ce482180937ab2d892b84ffccb9bd%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-09-24 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 Markush2010):

 This is similar to #23473

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

Re: [Django] #23473: Django prompts to create new migrations when none are needed when a class is used in a field declaration

2014-09-24 Thread Django

#23473: Django prompts to create new migrations when none are needed when a 
class
is used in a field declaration
+
 Reporter:  dlo |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.7
 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 Markush2010):

 * stage:  Unreviewed => Accepted


Comment:

 I can confirm this behavior. I suggest to document the requirement for a
 `__eq__` method.

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

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

Re: [Django] #23547: BooleanField that is required and have value False always will raise ValidationError

2014-09-24 Thread Django

#23547: BooleanField that is required and have value False always will raise
ValidationError
---+--
 Reporter:  Lagovas|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Forms  |  Version:  1.6
 Severity:  Normal |   Resolution:  worksforme
 Keywords:  Form BooleanField  | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Lagovas):

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


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

Re: [Django] #23547: BooleanField that is required and have value False always will raise ValidationError

2014-09-24 Thread Django

#23547: BooleanField that is required and have value False always will raise
ValidationError
---+--
 Reporter:  Lagovas|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Forms  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords:  Form BooleanField  | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by Lagovas):

 Sorry. Revised documentation and saw note about this (after error first of
 all went to code to see from what and why raises and code behavior was
 nonobvious. But in my opinion, it's not good that field can't be required
 and return all valid values. Ticket can be closed i guess.

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

Re: [Django] #901: Reload method for models

2014-09-24 Thread Django

#901: Reload method for models
-+-
 Reporter:  andreas@…|Owner:  akaariai
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by dbrgn):

 * cc: mail@… (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/080.954350815d18ec3684e08ce35ba260b7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23547: BooleanField that is required and have value False always will raise ValidationError

2014-09-24 Thread Django

Comment (by timgraham):

Your proposed change is backwards incompatible. You can't just call the
existing behavior a bug and remove tests that don't conform to how you
expect things to work.

[https://docs.djangoproject.com/en/dev/ref/forms/fields/#booleanfield As
documented]: "Since all `Field` subclasses have `required=True` by
default, the validation condition here is important. If you want to
include a boolean in your form that can be either `True` or `False` (e.g.
a checked or unchecked checkbox), you must remember to pass in
`required=False` when creating the `BooleanField`."

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

Re: [Django] #23426: migrations.RunSQL's function signature implies it won't do any parameter substitution

2014-09-24 Thread Django

#23426: migrations.RunSQL's function signature implies it won't do any parameter
substitution
-+-
 Reporter:  ris  |Owner:
 Type:   |  Markush2010
  Cleanup/optimization   |   Status:  closed
Component:  Migrations   |  Version:  1.7
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  migrations sql   | Triage Stage:  Accepted
  runsql params escape   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by Tim Graham ):

 In [changeset:"ae14c75014379d1cf405509b65eb986c0cb3b0f3"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ae14c75014379d1cf405509b65eb986c0cb3b0f3"
 [1.7.x] Fixed #23426 -- Don't require double percent sign in RunSQL
 without parameters

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

[django/django] ae14c7: [1.7.x] Fixed #23426 -- Don't require double perce...

2014-09-24 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: ae14c75014379d1cf405509b65eb986c0cb3b0f3
  
https://github.com/django/django/commit/ae14c75014379d1cf405509b65eb986c0cb3b0f3
  Author: Markus Holtermann 
  Date:   2014-09-24 (Wed, 24 Sep 2014)

  Changed paths:
M django/db/migrations/operations/special.py
M docs/ref/migration-operations.txt
M docs/releases/1.7.1.txt
M tests/migrations/test_operations.py

  Log Message:
  ---
  [1.7.x] Fixed #23426 -- Don't require double percent sign in RunSQL without 
parameters

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

Re: [Django] #23426: migrations.RunSQL's function signature implies it won't do any parameter substitution

2014-09-24 Thread Django

#23426: migrations.RunSQL's function signature implies it won't do any parameter
substitution
-+-
 Reporter:  ris  |Owner:
 Type:   |  Markush2010
  Cleanup/optimization   |   Status:  closed
Component:  Migrations   |  Version:  1.7
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  migrations sql   | Triage Stage:  Accepted
  runsql params escape   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"b9a670b22799a44fe7d3467d1d21949f9f717593"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b9a670b22799a44fe7d3467d1d21949f9f717593"
 Fixed #23426 -- Don't require double percent sign in RunSQL without
 parameters
 }}}

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

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

[django/django] b9a670: Fixed #23426 -- Don't require double percent sign ...

2014-09-24 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b9a670b22799a44fe7d3467d1d21949f9f717593
  
https://github.com/django/django/commit/b9a670b22799a44fe7d3467d1d21949f9f717593
  Author: Markus Holtermann 
  Date:   2014-09-24 (Wed, 24 Sep 2014)

  Changed paths:
M django/db/migrations/operations/special.py
M docs/ref/migration-operations.txt
M docs/releases/1.7.1.txt
M tests/migrations/test_operations.py

  Log Message:
  ---
  Fixed #23426 -- Don't require double percent sign in RunSQL without parameters


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

Re: [Django] #23547: BooleanField that is required and have value False always will raise ValidationError

2014-09-24 Thread Django

#23547: BooleanField that is required and have value False always will raise
ValidationError
---+--
 Reporter:  Lagovas|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Forms  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords:  Form BooleanField  | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by Lagovas):

 Added new patch. For correct way, in "to_python" will saving raw_value and
 then in "validate" check that it value not in empty_values if field is
 required. And removed 2 tests, that expect ValidationError with correct
 false value.

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

Re: [Django] #23321: Remove .mo files from the Django Git repository

2014-09-24 Thread Django

#23321: Remove .mo files from the Django Git repository
--+
 Reporter:  claudep   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Internationalization  |  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 slav0nic):

 * cc: slav0nic@… (added)


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

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

[django/django] cc74d8: [1.7.x] Fixed #23539 -- Added get_extra(), get_max...

2014-09-24 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: cc74d8e02e8b659b914859d60002aaa47600f0ff
  
https://github.com/django/django/commit/cc74d8e02e8b659b914859d60002aaa47600f0ff
  Author: Justin Caratzas 
  Date:   2014-09-24 (Wed, 24 Sep 2014)

  Changed paths:
M django/contrib/contenttypes/admin.py
M docs/releases/1.7.1.txt
M tests/generic_inline_admin/tests.py

  Log Message:
  ---
  [1.7.x] Fixed #23539 -- Added get_extra(), get_max_num(), and get_min_num() 
hooks to GenericInlineModelAdmin.

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

Re: [Django] #23539: GenericInlineModelAdmin doesn't utilize get_extra (and get_max_num/get_min_num)

2014-09-24 Thread Django

#23539: GenericInlineModelAdmin doesn't utilize get_extra (and
get_max_num/get_min_num)
--+
 Reporter:  bigjust   |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  contrib.contenttypes  |  Version:  1.7
 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
--+

Comment (by Tim Graham ):

 In [changeset:"cc74d8e02e8b659b914859d60002aaa47600f0ff"]:
 {{{
 #!CommitTicketReference repository=""
 revision="cc74d8e02e8b659b914859d60002aaa47600f0ff"
 [1.7.x] Fixed #23539 -- Added get_extra(), get_max_num(), and
 get_min_num() hooks to GenericInlineModelAdmin.

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

[django/django] cf43a1: Fixed #23539 -- Added get_extra(), get_max_num(), ...

2014-09-24 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: cf43a1ee909ab5dbca5b6a40247cd093a3e2ac8d
  
https://github.com/django/django/commit/cf43a1ee909ab5dbca5b6a40247cd093a3e2ac8d
  Author: Justin Caratzas 
  Date:   2014-09-24 (Wed, 24 Sep 2014)

  Changed paths:
M django/contrib/contenttypes/admin.py
M docs/releases/1.7.1.txt
M tests/generic_inline_admin/tests.py

  Log Message:
  ---
  Fixed #23539 -- Added get_extra(), get_max_num(), and get_min_num() hooks to 
GenericInlineModelAdmin.


  Commit: 0aca91cf7f0ec6547659a9404f139a0c9ba280a1
  
https://github.com/django/django/commit/0aca91cf7f0ec6547659a9404f139a0c9ba280a1
  Author: Tim Graham 
  Date:   2014-09-24 (Wed, 24 Sep 2014)

  Changed paths:
M django/db/backends/postgresql_psycopg2/introspection.py
M tests/one_to_one/models.py

  Log Message:
  ---
  Fixed flake8 warnings.


Compare: https://github.com/django/django/compare/2f3a4cd57316...0aca91cf7f0e

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

Re: [Django] #23539: GenericInlineModelAdmin doesn't utilize get_extra (and get_max_num/get_min_num)

2014-09-24 Thread Django

#23539: GenericInlineModelAdmin doesn't utilize get_extra (and
get_max_num/get_min_num)
--+
 Reporter:  bigjust   |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  contrib.contenttypes  |  Version:  1.7
 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:"cf43a1ee909ab5dbca5b6a40247cd093a3e2ac8d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="cf43a1ee909ab5dbca5b6a40247cd093a3e2ac8d"
 Fixed #23539 -- Added get_extra(), get_max_num(), and get_min_num() hooks
 to GenericInlineModelAdmin.
 }}}

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

[django/django] 2f3a4c: Removed numbering from the models.py header of som...

2014-09-24 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2f3a4cd573166e6b7bac9ed89d448ca34ab93edf
  
https://github.com/django/django/commit/2f3a4cd573166e6b7bac9ed89d448ca34ab93edf
  Author: Loic Bistuer 
  Date:   2014-09-24 (Wed, 24 Sep 2014)

  Changed paths:
M tests/basic/models.py
M tests/choices/models.py
M tests/custom_columns/models.py
M tests/custom_managers/models.py
M tests/custom_methods/models.py
M tests/custom_pk/models.py
M tests/empty/models.py
M tests/field_defaults/models.py
M tests/file_storage/models.py
M tests/fixtures/models.py
M tests/generic_relations/models.py
M tests/get_object_or_404/models.py
M tests/lookup/models.py
M tests/m2m_and_m2o/models.py
M tests/m2m_intermediary/models.py
M tests/m2m_multiple/models.py
M tests/m2m_recursive/models.py
M tests/m2o_recursive/models.py
M tests/many_to_many/models.py
M tests/many_to_one/models.py
M tests/many_to_one_null/models.py
M tests/mutually_referential/models.py
M tests/one_to_one/models.py
M tests/or_lookups/models.py
M tests/ordering/models.py
M tests/properties/models.py
M tests/reserved_names/models.py
M tests/reverse_lookup/models.py
M tests/save_delete_hooks/models.py
M tests/select_related/models.py
M tests/serializers/models.py
M tests/str/models.py
M tests/test_client/tests.py
M tests/transactions/models.py
M tests/user_commands/models.py

  Log Message:
  ---
  Removed numbering from the models.py header of some test packages.

This is a reliqua from the early days of the modeltests/regressiontests era.


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

Re: [Django] #23547: BooleanField that is required and have value False always will raise ValidationError

2014-09-24 Thread Django

#23547: BooleanField that is required and have value False always will raise
ValidationError
---+--
 Reporter:  Lagovas|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Forms  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords:  Form BooleanField  | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by timgraham):

 The tests do not pass with your proposed change:
 {{{
 ==
 FAIL: test_booleanfield
 (forms_tests.tests.test_error_messages.FormsErrorMessagesTestCase)
 --
 Traceback (most recent call last):
   File
 "/home/tim/code/django/tests/forms_tests/tests/test_error_messages.py",
 line 169, in test_booleanfield
 self.assertFormErrors(['REQUIRED'], f.clean, '')
   File
 "/home/tim/code/django/tests/forms_tests/tests/test_error_messages.py",
 line 23, in assertFormErrors
 self.fail("Testing the 'clean' method on %s failed to raise a
 ValidationError.")
 AssertionError: Testing the 'clean' method on %s failed to raise a
 ValidationError.

 ==
 FAIL: test_booleanfield_1 (forms_tests.tests.test_fields.FieldsTests)
 --
 Traceback (most recent call last):
   File "/home/tim/code/django/tests/forms_tests/tests/test_fields.py",
 line 891, in test_booleanfield_1
 self.assertRaisesMessage(ValidationError, "'This field is required.'",
 f.clean, '')
   File "/home/tim/code/django/django/test/testcases.py", line 579, in
 assertRaisesMessage
 re.escape(expected_message), callable_obj, *args, **kwargs)
   File "/home/tim/code/django/django/utils/six.py", line 690, in
 assertRaisesRegex
 return getattr(self, _assertRaisesRegex)(*args, **kwargs)
 AssertionError: ValidationError not raised
 }}}

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

Re: [Django] #23551: Exception raised when using the bash autocompletion with Python 3

2014-09-24 Thread Django

#23551: Exception raised when using the bash autocompletion with Python 3
-+---
 Reporter:  marco-buttu  |Owner:  marco-buttu
 Type:  Bug  |   Status:  assigned
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+---
Changes (by timgraham):

 * has_patch:  0 => 1
 * needs_tests:  0 => 1
 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #23551: Exception raised when using the bash autocompletion with Python 3

2014-09-24 Thread Django

#23551: Exception raised when using the bash autocompletion with Python 3
-+---
 Reporter:  marco-buttu  |Owner:  marco-buttu
 Type:  Bug  |   Status:  assigned
Component:  Utilities|  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 marco-buttu):

 * status:  new => assigned
 * cc: marco.buttu@… (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * owner:  nobody => marco-buttu
 * needs_docs:   => 0


Old description:

> My environment is Python 3.4 and Linux Mint 17. When using the django
> autocompletion, a TAB-completion after a command gives me an exception.
> For instance, typing a TAB after *django-admin startproject*:
>
> {{{
> $ django-admin startproject Traceback (most recent call last):
>   ...
>   File ".../django/core/management/__init__.py", line 262, in
> autocomplete
> options = sorted((k, v) for k, v in options if k.startswith(curr))
>   TypeError: unorderable types: bool() < NoneType()
> }}}
>

> That happens because at line 225 the *options* list is initilized as:
>

> {{{
> options = [('--help', None)]
> }}}
>

> and at line 263:
>

> {{{
> options = sorted((k, v) for k, v in options if k.startswith(curr))
> }}}
>

> But since *options* contains *--help* twice, in Python 3 we get an error
> comparing a *bool* with *None*:
>

> {{{
> >>> sorted([('foo', True), ('--help', False), ('--help', None)])
> Traceback (most recent call last):
> ...
> TypeError: unorderable types: NoneType() < bool()
> }}}
>

> That obviously does not happen in Python 2. The doctring of
> *autocomplete()* says:
>

> {{{
> >>> from django.core.management import ManagementUtility
> >>> for line in
> ManagementUtility.autocomplete.__doc__.splitlines()[10:15]:
> ... print(line)
> ...
>
> Subcommand options are saved as pairs. A pair consists of
> the long option string (e.g. '--exclude') and a boolean
> value indicating if the option requires arguments. When
> printing to
> stdout, an equal sign is appended to options which require
> arguments.
> }}}
>

> So, how come *options* is initialized with the pair *('--help', None)*
> instead of *('--help', False)*?

New description:

 My environment is Python 3.4 and Linux Mint 17. When using the django
 autocompletion, a TAB-completion after a command gives me an exception.
 For instance, typing a TAB after `django-admin startproject`:

 {{{
 $ django-admin startproject Traceback (most recent call last):
   ...
   File ".../django/core/management/__init__.py", line 262, in autocomplete
 options = sorted((k, v) for k, v in options if k.startswith(curr))
   TypeError: unorderable types: bool() < NoneType()
 }}}


 That happens because at line 225 the `options` list is initilized as:


 {{{
 options = [('--help', None)]
 }}}


 and at line 263:


 {{{
 options = sorted((k, v) for k, v in options if k.startswith(curr))
 }}}


 But since `options` contains `--help` twice, in Python 3 we get an error
 comparing a `bool` with `None`:


 {{{
 >>> sorted([('foo', True), ('--help', False), ('--help', None)])
 Traceback (most recent call last):
 ...
 TypeError: unorderable types: NoneType() < bool()
 }}}


 That obviously does not happen in Python 2. The doctring of
 `autocomplete()` says:


 {{{
 >>> from django.core.management import ManagementUtility
 >>> for line in
 ManagementUtility.autocomplete.__doc__.splitlines()[10:15]:
 ... print(line)
 ...

 Subcommand options are saved as pairs. A pair consists of
 the long option string (e.g. '--exclude') and a boolean
 value indicating if the option requires arguments. When
 printing to
 stdout, an equal sign is appended to options which require
 arguments.
 }}}


 So, how come `options` is initialized with the pair `('--help', None)`
 instead of `('--help', False)`?

--

--
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

Re: [Django] #23548: Transform.relabeled_clone calls own constructor with wrong number of arguments

2014-09-24 Thread Django

#23548: Transform.relabeled_clone calls own constructor with wrong number of
arguments
-+-
 Reporter:  ris  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.7
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  lookup transform |  Needs documentation:  0
  orm subquery   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by dfunckt):

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


Comment:

 I'm marking the ticket as accepted based on the discussion with @akaariai
 in #django-dev.

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

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

Re: [Django] #23547: BooleanField that is required and have value False always will raise ValidationError

2014-09-24 Thread Django

#23547: BooleanField that is required and have value False always will raise
ValidationError
---+--
 Reporter:  Lagovas|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Forms  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords:  Form BooleanField  | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Lagovas):

 * cc: Lagovas (added)
 * status:  closed => new
 * has_patch:  0 => 1
 * resolution:  duplicate =>


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

Re: [Django] #23542: Add ability to disable migrations

2014-09-24 Thread Django

#23542: Add ability to disable migrations
---+--
 Reporter:  yuriiz |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.7
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by yuriiz):

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


Comment:

 The problem turned out to be in another third-party application having
 'migrate' management command 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/064.15728ed5bce17d921577c0dcd55f19c2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

74 matches

Mail list logo