date:20140319

Re: [Django] #22289: Field with Validator always considered changed in migrations

2014-03-19 Thread Django

#22289: Field with Validator always considered changed in migrations
+---
 Reporter:  blueyed |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.7-alpha-2
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+---

Comment (by blueyed):

 The problem is that the deconstructor (`>`)
 returns different values/objects for the validators:

 {{{
 ipdb> old_field_dec
 (u'django.db.models.CharField', [], {u'null': True, u'validators':
 [],
 u'max_length': 200, u'blank': True, u'help_text': u'IMDB ID (starts with
 "tt") or IMDB URL.', u'unique': True, u'verbose_name': 'IMDB ID'})
 ipdb> new_field_dec
 (u'django.db.models.CharField', [], {u'null': True, u'validators':
 [],
 u'max_length': 200, u'blank': True, u'help_text':
 , u'unique': True,
 u'verbose_name': 'IMDB ID'})
 ipdb> l
 334 new_model_state = self.to_state.models[app_label,
 model_name]
 335 old_field_name = renamed_fields.get((app_label,
 model_name, field_name), field_name)
 336 old_field_dec =
 old_model_state.get_field_by_name(old_field_name).deconstruct()[1:]
 337 new_field_dec =
 new_model_state.get_field_by_name(field_name).deconstruct()[1:]
 338 if old_field_dec != new_field_dec:
 4-> 339 self.add_to_migration(
 340 app_label,
 341 operations.AlterField(
 342 model_name=model_name,
 343 name=field_name,
 344
 field=new_model_state.get_field_by_name(field_name),
 }}}

 I have noticed that there is `AlterField.__eq__`, which does never get
 called though?!

 {{{
 def __eq__(self, other):
 return (
 (self.__class__ == other.__class__) and
 (self.name == other.name) and
 (self.model_name.lower() == other.model_name.lower()) and
 (self.field.deconstruct()[1:] ==
 other.field.deconstruct()[1:])
 )
 }}}

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

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

[django/django] 831ce6: Mark model renaming as irreversible for now (#2224...

2014-03-19 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 831ce69cbbcf239c0fbbf525643e12e69275c93b
  
https://github.com/django/django/commit/831ce69cbbcf239c0fbbf525643e12e69275c93b
  Author: Andrew Godwin 
  Date:   2014-03-19 (Wed, 19 Mar 2014)

  Changed paths:
M django/db/migrations/operations/models.py

  Log Message:
  ---
  Mark model renaming as irreversible for now (#22248)


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

Re: [Django] #22248: Model renaming doesn't work backwards

2014-03-19 Thread Django

#22248: Model renaming doesn't work backwards
--+
 Reporter:  andrewgodwin  |Owner:  andrewgodwin
 Type:  Bug   |   Status:  assigned
Component:  Migrations|  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by andrewgodwin):

 * severity:  Release blocker => Normal


Comment:

 I'm marking model renames as irreversible  for now in order to move this
 away from release blocker status; there's other irreversible core
 operations, and we can address this if we get time before the final.

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

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

Re: [Django] #22275: unique_together with foreign keys fails migration

2014-03-19 Thread Django

#22275: unique_together with foreign keys fails migration
-+
 Reporter:  ryanhiebert  |Owner:  bak1an
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by Andrew Godwin ):

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


Comment:

 In [changeset:"81f5408c7a16b8c79053950f05fe7a873506ca55"]:
 {{{
 #!CommitTicketReference repository=""
 revision="81f5408c7a16b8c79053950f05fe7a873506ca55"
 Fixed #22275: unique_together broken if ForeignKey split into new file.

 Thanks to bak1an for the patch.
 }}}

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

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

[django/django] 81f540: Fixed #22275: unique_together broken if ForeignKey...

2014-03-19 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 81f5408c7a16b8c79053950f05fe7a873506ca55
  
https://github.com/django/django/commit/81f5408c7a16b8c79053950f05fe7a873506ca55
  Author: Andrew Godwin 
  Date:   2014-03-19 (Wed, 19 Mar 2014)

  Changed paths:
M django/db/migrations/autodetector.py
A django:master...bak1an:ticket_22275.diff
M tests/migrations/test_autodetector.py

  Log Message:
  ---
  Fixed #22275: unique_together broken if ForeignKey split into new file.

Thanks to bak1an for the patch.


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

Re: [Django] #22275: unique_together with foreign keys fails migration

2014-03-19 Thread Django

#22275: unique_together with foreign keys fails migration
-+
 Reporter:  ryanhiebert  |Owner:  bak1an
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+

Comment (by andrewgodwin):

 It looks good enough to me; the optimisation of where to put it can be
 addressed along with the same optimisation for ForeignKeys (it currently
 errs a bit on the "splitting up" side), but in the interest of getting the
 beta out I'm committing it right now, as it fixes the bug.

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

Re: [Django] #22293: ERROR: relation "app_taggedcountryoforigin" already exists

2014-03-19 Thread Django

#22293: ERROR: relation "app_taggedcountryoforigin" already exists
+--
 Reporter:  blueyed |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by blueyed):

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


Comment:

 Sorry for the layout mess (please feel free to fix/edit it).

 Here is a proposed fix for it: https://github.com/django/django/pull/2448

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

[Django] #22293: ERROR: relation "app_taggedcountryoforigin" already exists

2014-03-19 Thread Django

#22293: ERROR: relation "app_taggedcountryoforigin" already exists
+
 Reporter:  blueyed |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  master
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  1
Easy pickings:  0   |  UI/UX:  0
+
 There is a problem in db.backends.schema.alter_field, with the call to
 `_alter_many_to_many`:

 it might try to rename a DB table to the same name.

 With django-taggit, changing arguments for the TaggableManager a migration
 is created, which triggers a RENAME of a DB table, although the name is
 not changed (e.g. when changing `blank`).

 The migration:

 operations = [
 migrations.AlterField(
 model_name='model',
 name='country_of_origin',
 field=taggit.managers.TaggableManager(through=app.models.TaggedCountryOfOrigin,
 blank=True, help_text=u'A comma-separated list of tags.',
 verbose_name=u'Country of origin'),
 ),

 The SQL:

 {{{
 % manage.py sqlmigrate app 0010
 ALTER TABLE "app_taggedcountryoforigin" RENAME TO
 "app_taggedcountryoforigin";
 ALTER TABLE "app_taggedcountryoforigin" DROP CONSTRAINT
 app__tag_id_5f04ec758472f8f8_fk_app_countryoforigintag_id;
 ALTER TABLE "app_taggedcountryoforigin" ADD CONSTRAINT
 app_taggedcountryoforigin_tag_id_5f04ec758472f8f8_fk FOREIGN KEY
 ("tag_id") REFERENCES "app_countryoforigintag" ("id") DEFERRABLE INITIALLY
 DEFERRED;
 }}}

 The SQL error: ERROR: relation "app_taggedcountryoforigin" already exists


 The code path is as follows:

 ipdb> l
 128 elif isinstance(to_field.rel.to,
 six.string_types):
 129 to_field.rel.to = from_field.rel.to
 --> 130 schema_editor.alter_field(from_model, from_field,
 to_field)
 131
 132 def database_backwards(self, app_label, schema_editor,
 from_state, to_state):
 133 self.database_forwards(app_label, schema_editor,
 from_state, to_state)
 134
 135 def describe(self):
 136 return "Alter field %s on %s" % (self.name,
 self.model_name)
 137
 138 def __eq__(self, other):

 ipdb> from_model
 
 ipdb> from_field
 
 ipdb> to_field
 
 ipdb>


 > …/django-master/django/db/backends/schema.py(767)_alter_many_to_many()
 766 # Rename the through table
 --> 767 self.alter_db_table(old_field.rel.through,
 old_field.rel.through._meta.db_table,
 new_field.rel.through._meta.db_table)
 768 # Repoint the FK to the other side


 The code that calls it (from `database_forwards`):

 if router.allow_migrate(schema_editor.connection.alias, to_model):
 from_field = from_model._meta.get_field_by_name(self.name)[0]
 to_field = to_model._meta.get_field_by_name(self.name)[0]
 # If the field is a relatedfield with an unresolved rel.to,
 just
 # set it equal to the other field side. Bandaid fix for
 AlterField
 # migrations that are part of a RenameModel change.
 if from_field.rel and from_field.rel.to:
 if isinstance(from_field.rel.to, six.string_types):
 from_field.rel.to = to_field.rel.to
 elif isinstance(to_field.rel.to, six.string_types):
 to_field.rel.to = from_field.rel.to
 schema_editor.alter_field(from_model, from_field, to_field)

 (This gets triggered by my patch to taggit (http://github.com/blueyed
 /django-taggit/compare/rel.through._meta.auto_created-for-1.7?expand=1),
 where I setup `auto_created`.

 I came up with this in an attempt to fix another taggit issue with Django
 1.7 (https://github.com/alex/django-taggit)/issues/211 - "changed
 `through` model: ValueError: Cannot alter field ... - they are not
 compatible types".)

 I will provide a fix for this, but did not manage to come with a test case
 (for the test suite).

 I would really appreciate it, if

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

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

Re: [Django] #21840: LazyObject wrapped instances can no longer be coerced to Bool due to #20924

2014-03-19 Thread Django

#21840: LazyObject wrapped instances can no longer be coerced to Bool due to 
#20924
-+-
 Reporter:  gabejackson  |Owner:  bmispelon
 Type:  Bug  |   Status:  closed
Component:  Utilities|  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  LazyObject utils | 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 Andrew Godwin ):

 In [changeset:"356f064c49f926dd771e6ee590b43c8ac5dc4efc"]:
 {{{
 #!CommitTicketReference repository=""
 revision="356f064c49f926dd771e6ee590b43c8ac5dc4efc"
 Merge pull request #2221 from bmispelon/LazyObject-refactor

 Fixed #21840 -- Moved dunder methods from SimpleLazyObject to
 LazyObject...
 }}}

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

Re: [Django] #21840: LazyObject wrapped instances can no longer be coerced to Bool due to #20924

2014-03-19 Thread Django

#21840: LazyObject wrapped instances can no longer be coerced to Bool due to 
#20924
-+-
 Reporter:  gabejackson  |Owner:  bmispelon
 Type:  Bug  |   Status:  closed
Component:  Utilities|  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  LazyObject utils | 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 Baptiste Mispelon ):

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


Comment:

 In [changeset:"61917aa08b4ab2bc35f3ffe87b7693bd8b58e205"]:
 {{{
 #!CommitTicketReference repository=""
 revision="61917aa08b4ab2bc35f3ffe87b7693bd8b58e205"
 Fixed #21840 -- Moved dunder methods from SimpleLazyObject to LazyObject.

 This commit also added tests for LazyObject and refactored
 the testsuite of SimpleLazyObject so that it can share
 test cases with LazyObject.
 }}}

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

[django/django] 61917a: Fixed #21840 -- Moved dunder methods from SimpleLa...

2014-03-19 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 61917aa08b4ab2bc35f3ffe87b7693bd8b58e205
  
https://github.com/django/django/commit/61917aa08b4ab2bc35f3ffe87b7693bd8b58e205
  Author: Baptiste Mispelon 
  Date:   2014-03-13 (Thu, 13 Mar 2014)

  Changed paths:
M django/utils/functional.py
A tests/utils_tests/test_lazyobject.py
M tests/utils_tests/test_simplelazyobject.py

  Log Message:
  ---
  Fixed #21840 -- Moved dunder methods from SimpleLazyObject to LazyObject.

This commit also added tests for LazyObject and refactored
the testsuite of SimpleLazyObject so that it can share
test cases with LazyObject.


  Commit: 5c5b266b5478aa4e8bd92f141c56f3a0997749eb
  
https://github.com/django/django/commit/5c5b266b5478aa4e8bd92f141c56f3a0997749eb
  Author: Baptiste Mispelon 
  Date:   2014-03-13 (Thu, 13 Mar 2014)

  Changed paths:
M django/contrib/staticfiles/management/commands/collectstatic.py
M django/utils/functional.py

  Log Message:
  ---
  Simplified implementation of collectstatic command.

Since d2e242d16c6dde6f4736086fb38057424bed3edb made isinstance()
calls work correctly on LazyObject, we can simplify the
implementation of is_local_storage added in
7e27885c6e7588471fd94a4def16b7081577bdfc.


  Commit: 356f064c49f926dd771e6ee590b43c8ac5dc4efc
  
https://github.com/django/django/commit/356f064c49f926dd771e6ee590b43c8ac5dc4efc
  Author: Andrew Godwin 
  Date:   2014-03-19 (Wed, 19 Mar 2014)

  Changed paths:
M django/contrib/staticfiles/management/commands/collectstatic.py
M django/utils/functional.py
A tests/utils_tests/test_lazyobject.py
M tests/utils_tests/test_simplelazyobject.py

  Log Message:
  ---
  Merge pull request #2221 from bmispelon/LazyObject-refactor

Fixed #21840 -- Moved dunder methods from SimpleLazyObject to LazyObject...


Compare: https://github.com/django/django/compare/ac9c7701a7ab...356f064c49f9

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

Re: [Django] #22289: Field with Validator always considered changed in migrations

2014-03-19 Thread Django

#22289: Field with Validator always considered changed in migrations
+---
 Reporter:  blueyed |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.7-alpha-2
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+---

Comment (by blueyed):

 @erikr: have you tested it using PostgreSQL? (I am using 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/065.912f5c8603fb36768b58f54f5eaded95%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] ac9c77: Replaced reference to ModelAdmin.get_formsets() (d...

2014-03-19 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ac9c7701a7ab869e6ec610630c6b1cfd368fe8ce
  
https://github.com/django/django/commit/ac9c7701a7ab869e6ec610630c6b1cfd368fe8ce
  Author: Daniel Hahler 
  Date:   2014-03-19 (Wed, 19 Mar 2014)

  Changed paths:
M docs/ref/contrib/admin/index.txt

  Log Message:
  ---
  Replaced reference to ModelAdmin.get_formsets() (deprecated) with 
get_formsets_with_inlines().


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

Re: [Django] #6349: HttpResponseUnauthorized is missing

2014-03-19 Thread Django

#6349: HttpResponseUnauthorized is missing
-+-
 Reporter:  moep |Owner:  winsley@…
 Type:  Uncategorized|   Status:  closed
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by aaugustin):

 The man who set this to wontfix is without doubt the most respected person
 in the Django community.

 Read https://www.djangoproject.com/weblog/2013/mar/19/goodbye-malcolm/ if
 you'd like to know why.

 I would be very embarrassed if I got caught pissing on someone's grave
 like you just did.

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

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

Re: [Django] #6349: HttpResponseUnauthorized is missing

2014-03-19 Thread Django

#6349: HttpResponseUnauthorized is missing
-+-
 Reporter:  moep |Owner:  winsley@…
 Type:  Uncategorized|   Status:  closed
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by anonymous):

 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


Comment:

 lol.

 I'd be super embarrassed if i was the asshole who decided to set this to
 'wontfix'.

 I can't believe this still doesn't exist.

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

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

Re: [Django] #22289: Field with Validator always considered changed in migrations

2014-03-19 Thread Django

#22289: Field with Validator always considered changed in migrations
+---
 Reporter:  blueyed |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.7-alpha-2
 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 blueyed):

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


Comment:

 Sorry for the confusion: I was copying the commented line from the
 Makefile.

 I am not using South anymore (removed from the virtualenv also), and use
 `manage.py makemigrations app`.

 Good to know that you cannot reproduce it though. I will see if I can come
 up with a test case in the next days.

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

Re: [Django] #21275: Cannot use migrations if model field specifies validators

2014-03-19 Thread Django

#21275: Cannot use migrations if model field specifies validators
-+-
 Reporter:  timo |Owner:  Tim
 Type:  Bug  |  Graham 
Component:  Migrations   |   Status:  closed
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:
  Needs tests:  0|  Unreviewed
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by blueyed):

 Please note that there is #22255, which is about adding a new `flags`
 kwarg.

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

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

Re: [Django] #17638: Link up topic guides with API reference

2014-03-19 Thread Django

#17638: Link up topic guides with API reference
---+-
 Reporter:  oinopion   |Owner:  anonymous
 Type:  New feature|   Status:  assigned
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+-

Comment (by mcintyre1994):

 (Created an account, same mcintyre1994 as above)

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

Re: [Django] #17638: Link up topic guides with API reference

2014-03-19 Thread Django

#17638: Link up topic guides with API reference
---+-
 Reporter:  oinopion   |Owner:  anonymous
 Type:  New feature|   Status:  assigned
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+-
Changes (by mcintyre1994):

 * status:  new => assigned
 * owner:   => anonymous


Comment:

 Implemented per my above screenshots for them pages, can be seen here.
 https://github.com/mcintyre94/django/tree/ticket_17638

 Happy to run through some other files and do the same thing if that's
 what's wanted here, but I'd appreciate some feedback first. ASsigned to
 myself, hope that's alright!

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

Re: [Django] #17971: RequestFactory requests can't be used to test views that call messages.add

2014-03-19 Thread Django

#17971: RequestFactory requests can't be used to test views that call 
messages.add
-+-
 Reporter:  hoffmaje |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  1.4
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  RequestFactory,  | Triage Stage:
  MessageFailure |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by anonymous):

 This makes the RequestFactory useless for my cases.

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

Re: [Django] #22292: Problems with updating a ForeignKey having a to_field attribute

2014-03-19 Thread Django

#22292: Problems with updating a ForeignKey having a to_field attribute
-+-
 Reporter:  sly010   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Uncategorized|  Version:  1.6
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  ForeignKey to_field  | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by anonymous):

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


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

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

Re: [Django] #22267: django.utils.html.smart_urlquote() is incorrectly unquoting the url

2014-03-19 Thread Django

#22267: django.utils.html.smart_urlquote() is incorrectly unquoting the url
---+
 Reporter:  meenzam@…  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Utilities  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by ienzam):

 Read the bug and ticket.
 From RFC 2396 ([http://www.ietf.org/rfc/rfc2396.txt]), valid characters
 for different parts of the url are following:
 path => {{{Alphanumeric and /;-_.!~*'():@&=+$,}}}
 query and fragment => {{{Alphanumeric and /;-_.!~*'():@&=+$,?}}} (only
 differs from path with an extra {{{?}}})

 Can we not unquote and quote again because it can introduce some corner
 cases.
 We can check if the url is already quoted or not (which was done till
 v1.4).

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

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

Re: [Django] #17638: Link up topic guides with API reference

2014-03-19 Thread Django

#17638: Link up topic guides with API reference
---+
 Reporter:  oinopion   |Owner:
 Type:  New feature|   Status:  new
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by mcintyre1994):

 I'd be interested to look at this as a first bug, but I'm a little unclear
 exactly what is wanted. I've put together a quick screenshot of
 [http://imgur.com/YP3NbIB class based views introductory material]
 ([https://docs.djangoproject.com/en/1.5/topics/class-based-views/
 current]) and [http://imgur.com/Nt3aXLI class based views API reference]
 ([https://docs.djangoproject.com/en/1.5/ref/class-based-views/ current])
 using the admonition unit for see also links at the top of each. If I did
 something like that for each page in API ref/intro material with links to
 other material at the top, would that be vaguely along the right lines?

 I'm not really sure about the second example mentioned above, inline links
 look fine to me as they are.

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

[Django] #22292: Problems with updating a ForeignKey having a to_field attribute

2014-03-19 Thread Django

#22292: Problems with updating a ForeignKey having a to_field attribute
---+-
 Reporter:  sly010 |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:  ForeignKey to_field
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+-
 class Owner(models.Model):
 uid = models.CharField(max_length = 255, unique = True)

 class Article(models.Model):
 owner = models.ForeignKey(Owner, to_field = 'uid')

 owner = ...
 article = ...

 1
 Article.objects.filter(pk = article.pk).update( owner = owner )
 # BROKEN
 # injects id into the sql instead of uid
 # best case fails with integrity error, worst case it silently continues
 (depends on the content of the tables)

 2
 Article.objects.filter(pk = article.pk).update( owner = owner.uid )
 # WORKS

 3
 Article.objects.filter(pk = article.pk).update( owner_id = owner.uid )
 # FAILS (unrecognized field name)

 4
 Article.objects.filter(pk = article.pk).update( owner_id = owner )
 # FAILS (unrecognized field name)

 5
 article.owner = owner
 article.save(update_field = ['owner'])
 # WORKS

 6
 article.owner = owner.uid
 article.save(update_field = ['owner'])
 # FAILS

 7
 article.owner_id = owner.uid
 article.save(update_field = ['owner'])
 # WORKS

 8
 article.owner_id = owner
 article.save(update_field = ['owner'])
 # FAILS

 1 and 5 should definitely be working the same way, maybe some pointer as
 to which one is the preferred way (especially going forward)?

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

[Django] #22291: transactions.atomic (with savepoints) doesn't work correctly with deadlocks in mysql

2014-03-19 Thread Django

#22291: transactions.atomic (with savepoints) doesn't work correctly with 
deadlocks
in mysql
--+
 Reporter:  err   |  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.6
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 In mysql on deadlock occurance all savepoints will be deleted. so trying
 to rollback to previous savepoint will cause error: SAVEPOINT ... does not
 exist;

 here is example:

 {{{
 1 Query create table user2(id int primary key)
 engine=innodb;
 1 Query set autocommit=0;INSERT INTO `user2` (`id`) VALUES
 (222);
 2 Query set autocommit=0;SAVEPOINT `xxx`;INSERT INTO
 `user2` (`id`) VALUES (222);
 1 Query UPDATE `user2` SET `id` = 111 WHERE NOT
 (`user2`.`id` = 222 );commit;  -- after commit there will be deadlock in
 transaction 2
 2 Query ROLLBACK TO SAVEPOINT `xxx`;
 }}}

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

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

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

2014-03-19 Thread Django

Comment (by jeroen.pulles@…):

I've checked with my existing long running processes on Django 1.5
installations, running the same mysql-python and libmysqlclient.so, with
tcpdump:

They do set the interactive flag on the MySQL connection. That explains
for me why I never experienced the Gone Away's before. Django doesn't
notice that the underlying connection went away and came back.

I haven't had enough time to find out (dig down deep enough) what makes
this flag appear on the connection in the 1.5 situation and what changed
in 1.6 that is relevant to this problem. (a) My suspicion is that it isn't
directly related to the connection persistence mechanism. (b) To me it
doesn't seem to be in any way related to the transactions mechanisms: My
transactions happen fast enough and it's fine that things break if the
transaction takes longer than wait_timeout (e.g. more than two minutes);
The same application that works fine in 1.5 also works in 1.6 with the
interactive flag set.

JeroenP

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

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

Re: [Django] #22289: Field with Validator always considered changed in migrations

2014-03-19 Thread Django

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

Comment:

I don't think this is a bug in Django. In current master, there is no
command `schemamigration --auto`, there is only `makemigrations`. When I
test a fresh project with your model, using the new built-in schema
migrations, I can not reproduce this issue - it consistently works
correctly. Therefore, this may be a bug in South (which implements
`schemamigration --auto`, but does not appear to be one in Django.

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

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

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

2014-03-19 Thread Django

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

 Great!  Thanks for your patience, everyone :)

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

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

2014-03-19 Thread Django

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

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


Comment:

 Jenkins is back to green!

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

[django/django] a01daa: [1.6.x] Fixed #22253 -- Added django-i18n to the m...

2014-03-19 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: a01daaf2319ecb2361cc3ecbe872c4fb7fc4817f
  
https://github.com/django/django/commit/a01daaf2319ecb2361cc3ecbe872c4fb7fc4817f
  Author: Anubhav Joshi 
  Date:   2014-03-19 (Wed, 19 Mar 2014)

  Changed paths:
M docs/internals/contributing/localizing.txt
M docs/internals/mailing-lists.txt

  Log Message:
  ---
  [1.6.x] Fixed #22253 -- Added django-i18n to the mailing lists docs.

Thanks bmispelon for the suggestion.

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

Re: [Django] #22253: Add django-i18n to the mailing lists documentation

2014-03-19 Thread Django

#22253: Add django-i18n to the mailing lists documentation
---+
 Reporter:  bmispelon  |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by Tim Graham ):

 In [changeset:"a01daaf2319ecb2361cc3ecbe872c4fb7fc4817f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a01daaf2319ecb2361cc3ecbe872c4fb7fc4817f"
 [1.6.x] Fixed #22253 -- Added django-i18n to the mailing lists docs.

 Thanks bmispelon for the suggestion.

 Backport of 0399523cf1ac1f6adcfe593e05824ff4f98da3d3 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.43085713df2174c53431514bb2030acb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22253: Add django-i18n to the mailing lists documentation

2014-03-19 Thread Django

#22253: Add django-i18n to the mailing lists documentation
---+
 Reporter:  bmispelon  |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"0399523cf1ac1f6adcfe593e05824ff4f98da3d3"]:
 {{{
 #!CommitTicketReference repository=""
 revision="0399523cf1ac1f6adcfe593e05824ff4f98da3d3"
 Fixed #22253 -- Added django-i18n to the mailing lists docs.

 Thanks bmispelon for the suggestion.
 }}}

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

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

[django/django] 039952: Fixed #22253 -- Added django-i18n to the mailing l...

2014-03-19 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 0399523cf1ac1f6adcfe593e05824ff4f98da3d3
  
https://github.com/django/django/commit/0399523cf1ac1f6adcfe593e05824ff4f98da3d3
  Author: Anubhav Joshi 
  Date:   2014-03-19 (Wed, 19 Mar 2014)

  Changed paths:
M docs/internals/contributing/localizing.txt
M docs/internals/mailing-lists.txt

  Log Message:
  ---
  Fixed #22253 -- Added django-i18n to the mailing lists docs.

Thanks bmispelon for the suggestion.


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

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

2014-03-19 Thread Django

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

Comment (by Tim Graham ):

 In [changeset:"c11b9346d4ebc10d8d98945a974016a5e85f25e6"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c11b9346d4ebc10d8d98945a974016a5e85f25e6"
 Fixed migration so MySQL GIS test doesn't fail; refs #22001.

 The test previously failed with the error:
 (1170, "BLOB/TEXT column 'name' used in key specification without a key
 length")
 }}}

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

[django/django] c11b93: Fixed migration so MySQL GIS test doesn't fail; re...

2014-03-19 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c11b9346d4ebc10d8d98945a974016a5e85f25e6
  
https://github.com/django/django/commit/c11b9346d4ebc10d8d98945a974016a5e85f25e6
  Author: Eric Palakovich Carr 
  Date:   2014-03-19 (Wed, 19 Mar 2014)

  Changed paths:
M django/contrib/gis/tests/gis_migrations/migrations/0001_initial.py

  Log Message:
  ---
  Fixed migration so MySQL GIS test doesn't fail; refs #22001.

The test previously failed with the error:
(1170, "BLOB/TEXT column 'name' used in key specification without a key length")


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

Re: [Django] #22235: pip can install from tarballs as well

2014-03-19 Thread Django

#22235: pip can install from tarballs as well
--+
 Reporter:  omer.drow@…   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  *.djangoproject.com   |  Version:
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by omer.drow@…):

 Please review https://github.com/django/djangoproject.com/pull/74

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

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

Re: [Django] #22289: Field with Validator always considered changed in migrations

2014-03-19 Thread Django

#22289: Field with Validator always considered changed in migrations
+---
 Reporter:  blueyed |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.7-alpha-2
 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 erikr):

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


Comment:

 I don't think it is related to #22255 - but it is related to #21275.

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

[Django] #22290: Forms DateField show_hidden_initial USE_L10N = False and custom DATE_INPUT_FORMATS

2014-03-19 Thread Django

#22290: Forms DateField show_hidden_initial USE_L10N = False and custom
DATE_INPUT_FORMATS
-+-
 Reporter:   |  Owner:  nobody
  dibrovsd@… | Status:  new
 Type:  Bug  |Version:  1.6
Component:  Forms|   Keywords:  DateField USE_L10N hidden_initial
 Severity:  Normal   |  DATE_INPUT_FORMATS
 Triage Stage:   |  Has patch:  1
  Unreviewed |  UI/UX:  0
Easy pickings:  0|
-+-
 Hi.

 if settings is:
 - USE_L10N = False
 - DATE_INPUT_FORMATS = ('%d.%m.%Y', '%Y-%m-%d')

 then format in DateInput and HiddenInput (default hidden_widget for
 DateField) is different:
 - DateInput: '01.01.2014'
 - HiddenInput: '2014-01-01'

 Field._has_changed('2014-01-01',  '2014-01-01') always return True in
 form.changed_data

 For default DATE_INPUT_FORMATS, DateInput use '%Y-%m-%d'
 (DATE_INPUT_FORMATS[0] for USE_L10N = False)
 But if DATE_INPUT_FORMATS[0] != '%Y-%m-%d'

 format HiddenInput != format DateInput

 Test case:
 {{{
 from django import forms
 from datetime import date

 class TestForm(forms.Form):
 date_field = forms.DateField(show_hidden_initial=True)

 form = TestForm(initial={'date_field': date.today()})

 print form.as_ul()
 }}}

 Fix:
 # add HiddenDateInput
 class HiddenDateInput(forms.DateInput):
 is_hidden = True
 input_type = 'hidden'

 # set HiddenDateInput for default hidden_widget in DateField
 class DateField(fields.DateField):
 hidden_widget = widgets_custom.HiddenDateInput

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

[Django] #22289: Field with Validator always considered changed in migrations

2014-03-19 Thread Django

#22289: Field with Validator always considered changed in migrations
+-
 Reporter:  blueyed |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  1.7-alpha-2
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+-
 I am having the following model, and `schemamigration --auto` considers it
 to be changed always.

 This appears to get triggered through the RegexValidator (commenting it,
 does not cause the model to be considered different every time).

 {{{
 from django.core.validators import RegexValidator
 class Model(TimeStampedModel):
 foo_id = models.CharField(
 verbose_name='FOO ID',
 max_length=200,  # allow for URL in form, cleaned in clean_foo_id
 validators =
 
[RegexValidator(r'(?i)^(?:(?:https?://)?www.foo.com/title/)?(tt\d+)(?:/.*)?$')],
 help_text=_('…'),
 blank=True,
 null=True,
 unique=True)
 }}}

 This _might_ be related to #22255, but probably only because it's about
 the same field.. ;)

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

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

Re: [Django] #19199: SyntaxError creating a project

2014-03-19 Thread Django

#19199: SyntaxError creating a project
---+--
 Reporter:  qiubox |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  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 anonymous):

 * status:  closed => new
 * version:  1.4 => master
 * resolution:  invalid =>


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

Re: [Django] #22280: "Conflicting models in application" RuntimeError for same model with different paths

2014-03-19 Thread Django

#22280: "Conflicting models in application" RuntimeError for same model with
different paths
--+--
 Reporter:  blueyed   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  app-loading   | Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by aaugustin):

 First, a question: are you using explicit relative imports (`from .xxx
 import ...`) or implicit relative imports (`from xxx import ...`)? If
 you're using the latter form, you might be accidentally using absolute
 imports.

 Let me explain a bit.

 Assume the following structure:

 {{{
 root/
 root/__init__.py
 root/foo/
 root/foo/__init__.py
 root/foo/bar.py
 root/foo/baz.py
 }}}


 Assume both `root` and `foo` are on `PYTHONPATH` (bear with me for a
 moment).
 Assume `foo/__init__.py` contains `import bar` and that line is executing.
 Assume `foo/bar.py` contains `from baz import ...`. Then an absolute
 import will be performed, since `baz.py` is found in `foo` which is on
 `PYTHONPATH`, and the `baz` module is registered as `'baz'` in
 `sys.modules`.
 On the other hand, if foo/bar.py contains `from .baz import ...`, then a
 relative import will be performed, and the `baz` module is registered as
 `'foo.baz'` in `sys.modules`.

 This bears some resemblance with the symptoms you're describing and
 doesn't involve dark magic in Django. (There used to be some dark magic in
 this area, but we removed it in 1.4.)

 

 Now, regarding your particular situation, `pip install -e .` has the
 effect of adding `.` -- the current directory at the moment you're issuing
 the command -- to `PYTHONPATH`. There's a variety of way to set
 `PYTHONPATH` and that's why I was insisting on printing `sys.path`.

 Considering your project layout, I believe only the "outer" `project`
 folder -- the one that contains manage.py -- should be on `PYTHONPATH`.

 If I read you correctly, the "inner" `project` folder -- the one next to
 manage.py -- is also on `PYTHONPATH` because you added it with `pip
 install -e`. When you're executing management commands, such as running
 the tests, with `manage.py`, Python automatically adds the folder
 containing manage.py -- the "outer" `project` folder -- to `PYTHONPATH`.

 That's one way you can end up with the two `project` folders on
 `PYTHONPATH` and suffer from the ambiguity between absolute imports and
 implicit relative imports I described above. The answer is to always use
 explicit relative imports. Implicit relative imports are a footgun.

 

 Finally, your analysis in bold is inconsistent with what I know about
 Django. Attaching a minimal sample project with reproduction instructions
 would help me, or someone else, figure out what's going on.

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

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

Re: [Django] #22125: Unnecessary creation of index for ManyToManyField

2014-03-19 Thread Django

#22125: Unnecessary creation of index for ManyToManyField
-+-
 Reporter:  tbhtan3@…|Owner:  bwreilly
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.6
Component:  Database layer   |   Resolution:  needsinfo
  (models, ORM)  | Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by Joshua Yanovski):

 Again, please look at SQL Fiddle.  It allows you to write queries against
 a database of every type mentioned here, including Oracle (and also
 Microsoft SQL Server).  And every single one of them uses the composite
 index for a query that uses only the first indexed column.

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

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

Re: [Django] #22255: RegexValidator needs support for flags passed to `re.compile` (migrations do not allow for compiled patterns)

2014-03-19 Thread Django

#22255: RegexValidator needs support for flags passed to `re.compile` 
(migrations
do not allow for compiled patterns)
-+-
 Reporter:  blueyed  |Owner:  dekomote
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Core (Other) |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by erikr):

 * needs_better_patch:  0 => 1


Comment:

 Left a comment on the patch. Minor issue in the docs.

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

Re: [Django] #21275: Cannot use migrations if model field specifies validators

2014-03-19 Thread Django

#21275: Cannot use migrations if model field specifies validators
-+-
 Reporter:  timo |Owner:  Tim
 Type:  Bug  |  Graham 
Component:  Migrations   |   Status:  closed
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:
  Needs tests:  0|  Unreviewed
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by erikr):

 Shouldn't this also be added to the release notes? If anyone has their own
 model with a custom RegexValidator where they currently pass a compiled
 regex, they'll need to pass a string now, or they will also hit this
 issue, right?

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

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

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

2014-03-19 Thread Django

#22288: F() expression not compatible with __range field look up
-+-
 Reporter:  liushaohua86@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by liushaohua86@…):

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


Comment:

 class TestModel(models.Model):
 a = models.SmallIntegerField()
 b = models.SmallIntegerField()
 TestModel.objects.filter(a_ _range=(F('b')-1, F('b')+1))

 TypeError: int() argument must be a string or a number, not
 'ExpressionNode'

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

45 matches

Mail list logo