Re: [Django] #22486: urlresolvers.reverse() security fix (1.5.6) breaks when a view is a partial

[Django]

#22486: urlresolvers.reverse() security fix (1.5.6) breaks when a view is a 
partial
-+
 Reporter:  rcoup|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (URLs)  |  Version:  1.4
 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 lfaraone):

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

Re: [Django] #18767: Admin's calendar for datetime fields doesn't show right values with russian and some other locales

[Django]

#18767: Admin's calendar for datetime fields doesn't show right values with 
russian
and some other locales
---+
 Reporter:  void   |Owner:  maxocub
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by maxocub):

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


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

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

Re: [Django] #22384: Deprecate Django string magic in URLs and the ability to reverse by dotted path

[Django]

#22384: Deprecate Django string magic in URLs and the ability to reverse by 
dotted
path
--+
 Reporter:  timo  |Owner:  timo
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (URLs)   |  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 marfire):

 +1 from me. Are there any use cases where someone needs the string version
 in `urls.py` to avoid a circular imports problem? Not that I can think of,
 but I thought I'd mention 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/062.d5b66d321169c2aaf0b519bd6f426744%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] c5306d: [1.6.x] Various documentation typo/spelling fixes

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: c5306d4af1e9430d2397e8d83b37fa3598a17e83
  
https://github.com/django/django/commit/c5306d4af1e9430d2397e8d83b37fa3598a17e83
  Author: Marti Raudsepp 
  Date:   2014-04-22 (Tue, 22 Apr 2014)

  Changed paths:
M docs/internals/committers.txt
M docs/internals/contributing/writing-documentation.txt
M docs/ref/contrib/admin/actions.txt
M docs/ref/contrib/formtools/form-wizard.txt
M docs/ref/contrib/gis/gdal.txt
M docs/ref/contrib/gis/geos.txt
M docs/ref/databases.txt
M docs/ref/utils.txt
M docs/releases/1.0-alpha-1.txt
M docs/releases/1.1.txt
M docs/releases/1.2-alpha-1.txt
M docs/releases/1.6.4.txt
M docs/topics/forms/index.txt
M docs/topics/i18n/translation.txt
M docs/topics/testing/advanced.txt

  Log Message:
  ---
  [1.6.x] Various documentation typo/spelling fixes

Errors detected by Topy (https://github.com/intgr/topy), all changes
verified by hand.

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

[django/django] ba1728: [1.7.x] Various documentation typo/spelling fixes

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: ba1728dd9b19088c0c37253a938a6d97c61d5ed6
  
https://github.com/django/django/commit/ba1728dd9b19088c0c37253a938a6d97c61d5ed6
  Author: Marti Raudsepp 
  Date:   2014-04-22 (Tue, 22 Apr 2014)

  Changed paths:
M docs/internals/committers.txt
M docs/internals/contributing/writing-code/coding-style.txt
M docs/internals/contributing/writing-documentation.txt
M docs/ref/contrib/admin/actions.txt
M docs/ref/contrib/formtools/form-wizard.txt
M docs/ref/contrib/gis/gdal.txt
M docs/ref/contrib/gis/geos.txt
M docs/ref/databases.txt
M docs/ref/migration-operations.txt
M docs/ref/utils.txt
M docs/releases/1.0-alpha-1.txt
M docs/releases/1.1.txt
M docs/releases/1.2-alpha-1.txt
M docs/releases/1.6.4.txt
M docs/spelling_wordlist
M docs/topics/forms/index.txt
M docs/topics/i18n/translation.txt
M docs/topics/testing/advanced.txt

  Log Message:
  ---
  [1.7.x] Various documentation typo/spelling fixes

Errors detected by Topy (https://github.com/intgr/topy), all changes
verified by hand.

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

Re: [Django] #22492: provide a way to prevent database queries on model objects

[Django]

#22492: provide a way to prevent database queries on model objects
-+-
 Reporter:  cjerdonek|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
  model,queryset,defer,only  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by cjerdonek):

 * cc: chris.jerdonek@… (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 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/067.b95481493970d0e301165853060bb88a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22492: provide a way to prevent database queries on model objects

[Django]

#22492: provide a way to prevent database queries on model objects
-+-
 Reporter:  cjerdonek|  Owner:  nobody
 Type:  New feature  | Status:  new
Component:  Database layer   |Version:  1.6
  (models, ORM)  |   Keywords:
 Severity:  Normal   |  model,queryset,defer,only
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 This is a feature request to provide a way to prevent database queries
 from happening in a block of code, especially on model objects (e.g. using
 a context manager, or an internal flag on model objects).

 The motivation is for use with the QuerySet method
 [https://docs.djangoproject.com/en/dev/ref/models/querysets/#only
 `only()`], for example.  (The `only()` method is used to prevent
 unnecessary fields from being loaded from a database when querying.)
 Consider the case of using `only()` to retrieve a list of many model
 objects, and then subsequently displaying them.  If one executes some
 Django code after obtaining this list (e.g. by looping through the list of
 objects), it would be bad if this later code accidentally accessed some
 other field on each object. This could trigger the unintentional execution
 of many individual database queries (e.g. on a production database), with
 potentially bad consequences.  I don't currently know an easy way to
 prevent this.

 It would be good to have such a way.  For example, Django could provide
 some sort of `noQuery()` context manager which would raise an exception if
 the database were queried inside it.  Code after the `only()` line could
 be included in such a context manager.  This could prevent accidentally
 hammering a database.

 Alternatively, the QuerySet API could expose a way to return objects with
 some sort of `no_query` flag set.  If attribute access on such a model
 object required a database query, objects with such a flag set could
 instead raise an exception.  This would also suffice to prevent accidental
 queries.

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

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

[django/django] 11d453: Various documentation typo/spelling fixes

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 11d453bcadad3c9a5ae35882792d0f1e8e8e7818
  
https://github.com/django/django/commit/11d453bcadad3c9a5ae35882792d0f1e8e8e7818
  Author: Marti Raudsepp 
  Date:   2014-04-23 (Wed, 23 Apr 2014)

  Changed paths:
M docs/internals/committers.txt
M docs/internals/contributing/writing-code/coding-style.txt
M docs/internals/contributing/writing-documentation.txt
M docs/ref/contrib/admin/actions.txt
M docs/ref/contrib/formtools/form-wizard.txt
M docs/ref/contrib/gis/gdal.txt
M docs/ref/contrib/gis/geos.txt
M docs/ref/databases.txt
M docs/ref/migration-operations.txt
M docs/ref/utils.txt
M docs/releases/1.0-alpha-1.txt
M docs/releases/1.1.txt
M docs/releases/1.2-alpha-1.txt
M docs/releases/1.6.4.txt
M docs/spelling_wordlist
M docs/topics/forms/index.txt
M docs/topics/i18n/translation.txt
M docs/topics/testing/advanced.txt

  Log Message:
  ---
  Various documentation typo/spelling fixes

Errors detected by Topy (https://github.com/intgr/topy), all changes
verified by hand.


  Commit: c3152e5bcd5bb2027fac1411f238adc70eec20e7
  
https://github.com/django/django/commit/c3152e5bcd5bb2027fac1411f238adc70eec20e7
  Author: Alex Gaynor 
  Date:   2014-04-22 (Tue, 22 Apr 2014)

  Changed paths:
M docs/internals/committers.txt
M docs/internals/contributing/writing-code/coding-style.txt
M docs/internals/contributing/writing-documentation.txt
M docs/ref/contrib/admin/actions.txt
M docs/ref/contrib/formtools/form-wizard.txt
M docs/ref/contrib/gis/gdal.txt
M docs/ref/contrib/gis/geos.txt
M docs/ref/databases.txt
M docs/ref/migration-operations.txt
M docs/ref/utils.txt
M docs/releases/1.0-alpha-1.txt
M docs/releases/1.1.txt
M docs/releases/1.2-alpha-1.txt
M docs/releases/1.6.4.txt
M docs/spelling_wordlist
M docs/topics/forms/index.txt
M docs/topics/i18n/translation.txt
M docs/topics/testing/advanced.txt

  Log Message:
  ---
  Merge pull request #2602 from intgr/typofix

Various documentation typo/spelling fixes


Compare: https://github.com/django/django/compare/985377980513...c3152e5bcd5b

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

Re: [Django] #11776: HTML class for non-field errors

[Django]

#11776: HTML class for non-field errors
-+-
 Reporter:  Daniel Pope   |Owner:
 Type:  New feature  |  NickPresta
Component:  Forms|   Status:  assigned
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  1
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by timo):

 * needs_docs:  0 => 1
 * has_patch:  0 => 1
 * version:  1.1 => master


Comment:

 Patch needs documentation as noted on the PR.

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

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

Re: [Django] #22487: Moving from initial_data to data migrations stops test data persisting

[Django]

#22487: Moving from initial_data to data migrations stops test data persisting
-+-
 Reporter:  andrewgodwin |Owner:
 Type:  Bug  |  andrewgodwin
Component:  Testing framework|   Status:  assigned
 Severity:  Release blocker  |  Version:
 Keywords:   |  1.7-beta-1
Has patch:  0|   Resolution:
  Needs tests:  0| Triage Stage:  Accepted
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by timo):

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

Re: [Django] #22486: urlresolvers.reverse() security fix (1.5.6) breaks when a view is a partial

[Django]

#22486: urlresolvers.reverse() security fix (1.5.6) breaks when a view is a 
partial
-+
 Reporter:  rcoup|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (URLs)  |  Version:  1.4
 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 timo):

 * has_patch:  0 => 1
 * version:  1.5 => 1.4
 * stage:  Unreviewed => Accepted


Comment:

 Looks good. We should probably backport this to all the branches where we
 applied the security fix.

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

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

Re: [Django] #20185: TypeError: unicode argument expected, got 'str' on core management validation (used gunicorn)

[Django]

#20185: TypeError: unicode argument expected, got 'str' on core management
validation (used gunicorn)
--+--
 Reporter:  avelino   |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Python 2  |  Version:  1.5
 Severity:  Normal|   Resolution:  invalid
 Keywords:  gunicorn  | Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by hobs at totalgood.com):

 Thank you very much for pointing me to the django_wsgi line that was the
 problem.

 For me run_gunicorn (gunicorn/app/django_wsgi.py) was trying to output
 error messages for one of my installed apps using the wrong StringIO. I
 reversed the try/except order for import of StringIO (to favor python2)
 and then also fixed the model inheritance in the broken app. You can do
 either to avoid this error (don't have validation errors or use the right
 StringIO to log/output the validation errors).

 This is the sort of error message that gunicorn is using StringIO to try
 to log. I was trying to ForeignKey to the abstract model
 contrib.auth.User:

 One or more models did not validate:
 agile.organization: 'user' has an m2m relation with model User, which
 has either not been installed or is abstract.

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

Re: [Django] #22486: urlresolvers.reverse() security fix (1.5.6) breaks when a view is a partial

[Django]

#22486: urlresolvers.reverse() security fix (1.5.6) breaks when a view is a 
partial
-+--
 Reporter:  rcoup|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (URLs)  |  Version:  1.5
 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 prestontimmons):

 Although partials aren't reversible by the "path.to.view" syntax, I don't
 think Django should blow up on them. Some parts of our code base use
 partials extensively.

 A simple fix might be to create `lookup_str` from the original function
 whenever a pattern callback is a partial. The behavior would end up the
 same as if update_wrapper were called.

 A possible patch is here: https://github.com/django/django/pull/2601/

 What do you think?

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

[django/django] 49f5a2: [1.6.x] Updated grammar in description of django.c...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 49f5a2949311c6c0005c4f6ab79cf96ee09d
  
https://github.com/django/django/commit/49f5a2949311c6c0005c4f6ab79cf96ee09d
  Author: Ray Ashman 
  Date:   2014-04-22 (Tue, 22 Apr 2014)

  Changed paths:
M docs/topics/auth/default.txt

  Log Message:
  ---
  [1.6.x] Updated grammar in description of django.contrib.auth.

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

[django/django] 4499c6: [1.7.x] Updated grammar in description of django.c...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 4499c676eff03d6c8a30d256c677b9958b8d0705
  
https://github.com/django/django/commit/4499c676eff03d6c8a30d256c677b9958b8d0705
  Author: Ray Ashman 
  Date:   2014-04-22 (Tue, 22 Apr 2014)

  Changed paths:
M docs/topics/auth/default.txt

  Log Message:
  ---
  [1.7.x] Updated grammar in description of django.contrib.auth.

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

[django/django] 2d450c: [1.5.x] Updated grammar in description of django.c...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 2d450cc3e5afda821dd7d527ad34378c2f131fc5
  
https://github.com/django/django/commit/2d450cc3e5afda821dd7d527ad34378c2f131fc5
  Author: Ray Ashman 
  Date:   2014-04-22 (Tue, 22 Apr 2014)

  Changed paths:
M docs/topics/auth/default.txt

  Log Message:
  ---
  [1.5.x] Updated grammar in description of django.contrib.auth.

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

[django/django] 985377: Updated grammar in description of django.contrib.a...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 985377980513dbe7d5a6d7f7c139ce5446b5c288
  
https://github.com/django/django/commit/985377980513dbe7d5a6d7f7c139ce5446b5c288
  Author: Ray Ashman 
  Date:   2014-04-22 (Tue, 22 Apr 2014)

  Changed paths:
M docs/topics/auth/default.txt

  Log Message:
  ---
  Updated grammar in description of django.contrib.auth.


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

[django/django] 58176d: Use the stdlib's compare_digest for constant time ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 58176dee88ac7c1038c7f685af023e634b143d02
  
https://github.com/django/django/commit/58176dee88ac7c1038c7f685af023e634b143d02
  Author: Alex Gaynor 
  Date:   2014-04-22 (Tue, 22 Apr 2014)

  Changed paths:
M django/utils/crypto.py

  Log Message:
  ---
  Use the stdlib's compare_digest for constant time comparisons when available


  Commit: 03401701f3671f62ef51ff791e226b0d38a978ca
  
https://github.com/django/django/commit/03401701f3671f62ef51ff791e226b0d38a978ca
  Author: Donald Stufft 
  Date:   2014-04-22 (Tue, 22 Apr 2014)

  Changed paths:
M django/utils/crypto.py

  Log Message:
  ---
  Merge pull request #2600 from alex/builtin-constant-time-compare

Use the stdlib's compare_digest for constant time comparisons when available


Compare: https://github.com/django/django/compare/9fb95dfc9fa1...03401701f367

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

Re: [Django] #15179: django.test.client.Client.login fake HttpRequest is not run through middlewares

[Django]

#15179: django.test.client.Client.login fake HttpRequest is not run through
middlewares
---+--
 Reporter:  Ciantic|Owner:  akaariai
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.7-beta-2
 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
---+--
Changes (by marfire):

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

Re: [Django] #15179: django.test.client.Client.login fake HttpRequest is not run through middlewares

[Django]

#15179: django.test.client.Client.login fake HttpRequest is not run through
middlewares
---+--
 Reporter:  Ciantic|Owner:  akaariai
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.7-beta-2
 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 marfire):

 FWIW this isn't purely theoretical - I came across this after upgrading to
 1.7b1 and getting a huge number of test failures on working code. (As I
 hinted at above, the failures were because I hadn't set up the test
 database to handle a `GET` on '/'.)

 The relevant change is
 
[https://github.com/django/django/commit/4fdd51b73240bf9c8d9472fcc45df699f0714755
 #diff-97160f50594424a40f2621d5a3c581ccL549 here]. The call to `request()`
 does a full request / response cycle. Unfortunately I don't know this area
 of the code well enough to suggest a solution. Is there a way to point the
 code at a dummy view that just returns an `HttpResponse`?

 Even with such a change there will still be some coupling with the other
 (non-authentication) middleware components. That doesn't seem like a
 problem, though, since it's hard to imagine any request-based test working
 if the middleware doesn't work. But if we care we could make this feature
 opt-in with a `use_middleware` keyword argument to `login()`. That would
 minimize coupling and ensure full backward-compatibility.

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

Re: [Django] #22491: TestCase + select_for_update()

[Django]

#22491: TestCase + select_for_update()
-+-
 Reporter:  andreas_pelme|Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.6
  (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 aaugustin):

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


Comment:

 That looks hard to implement. How would you tell an atomic block created
 by a TestCase apart from an atomic block in application code exercised by
 a TransactionTestCase?

 If you can propose an implementation that makes sense, yes, let's do it.
 Otherwise we'll have to document that code involving select_for_update
 should be tested in a TransactionTestCase.

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

[Django] #22491: TestCase + select_for_update()

[Django]

#22491: TestCase + select_for_update()
--+
 Reporter:  andreas_pelme |  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
--+
 Since 1.6.3 and the select_for_update() changes,
 TransactionManagementError is raised when run in autocommit mode.

 However, in TestCase subclasses select_for_update() with missing
 transaction.atomic() blocks are not detected, since the test case itself
 runs in an atomic block.

 This means that select_for_update() errors will be silent in most test
 suites, and then show up in production.

 I think a lot of pain could be saved if it was possible to detect these
 cases and raise an exception in the tests to point out problems. I am not
 sure how (if) that could be accomplished, but if it was possible, I think
 it would be a big win. I would be happy to work on a patch if you think
 this would be a feasible idea.

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

Re: [Django] #22489: Missing as_sql() implementation for __search lookup

[Django]

#22489: Missing as_sql() implementation for __search lookup
-+-
 Reporter:  jakub|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  mysql, search,   |  Needs documentation:  0
  full-text, __search, lookup|  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-

Comment (by jakub):

 Added a test for MySQL.

 It might be a good idea to add a DB feature flag, but the test still needs
 MySQL-specific `CREATE FULLTEXT INDEX […]` however.

 (I've accidentally messed up the original pull request and had to open a
 new one: https://github.com/django/django/pull/2598)

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

Re: [Django] #22490: get_object within a syndication Feed has no tests

[Django]

#22490: get_object within a syndication Feed has no tests
-+-
 Reporter:  danielsamuels|Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  contrib.syndication  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  1|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by danielsamuels):

 * needs_tests:  0 => 1


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

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

Re: [Django] #22490: get_object within a syndication Feed has no tests

[Django]

#22490: get_object within a syndication Feed has no tests
-+-
 Reporter:  danielsamuels|Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  contrib.syndication  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by danielsamuels):

 * needs_better_patch:   => 0
 * version:  1.6 => master
 * needs_tests:   => 0
 * needs_docs:   => 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/071.d5e90272a8767d02f62f5fcea922fce9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22490: get_object within a syndication Feed has no tests

[Django]

#22490: get_object within a syndication Feed has no tests
-+
 Reporter:  danielsamuels|  Owner:  nobody
 Type:  Uncategorized| Status:  new
Component:  contrib.syndication  |Version:  1.6
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 Within django.tests.syndication_tests.feeds there is a class named
 
[https://github.com/django/django/blob/master/tests/syndication_tests/feeds.py#L11
 ComplexFeed] which extends views.Feed and overrides the get_object()
 method, however this class is not used in any tests.  There is a reference
 to the class in the related urls.py, but again this is unused.  This means
 that there is currently no test code written for the get_object() method
 in django.contrib.syndication.views.Feed and no examples for developers to
 follow when writing their own tests.

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

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

Re: [Django] #22485: makemigrations fails with dependencies to unmigrated apps

[Django]

#22485: makemigrations fails with dependencies to unmigrated apps
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:  migrations,  | Triage Stage:  Accepted
  unmigrated, makemigrations |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by amusikal):

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

Re: [Django] #22485: makemigrations fails with dependencies to unmigrated apps

[Django]

#22485: makemigrations fails with dependencies to unmigrated apps
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:  migrations,  | Triage Stage:  Accepted
  unmigrated, makemigrations |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by loic84):

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

Re: [Django] #22451: Migrations do not work with GeoDjango

[Django]

#22451: Migrations do not work with GeoDjango
-+--
 Reporter:  scibi|Owner:  claudep
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by Claude Paroz ):

 In [changeset:"5c19c698b1d84eeaa47d56460d60478b50df6b8c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5c19c698b1d84eeaa47d56460d60478b50df6b8c"
 [1.7.x] Fixed adding new GIS column in PostGIS 1.x migration

 Refs #22451.
 Backport of fb09a489c 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/063.1ef459186f68e7d25227d2cf925b7ee3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22481: Dropping geometry columns (PostGIS < 2.0) doesn't work

[Django]

#22481: Dropping geometry columns (PostGIS < 2.0) doesn't work
-+--
 Reporter:  claudep  |Owner:  claudep
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7-beta-1
 Severity:  Release blocker  |   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 Claude Paroz ):

 In [changeset:"417e9f383f53b331576c26b29b9ab92ccb2e6df9"]:
 {{{
 #!CommitTicketReference repository=""
 revision="417e9f383f53b331576c26b29b9ab92ccb2e6df9"
 [1.7.x] Fixed removal of GIS column in PostGIS 1.x migration

 Refs #22481.
 Backport of 2f9d1576e from master, squashed with 2f9d1576e8.
 }}}

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

[django/django] 5c19c6: [1.7.x] Fixed adding new GIS column in PostGIS 1.x...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 5c19c698b1d84eeaa47d56460d60478b50df6b8c
  
https://github.com/django/django/commit/5c19c698b1d84eeaa47d56460d60478b50df6b8c
  Author: Claude Paroz 
  Date:   2014-04-22 (Tue, 22 Apr 2014)

  Changed paths:
M django/contrib/gis/db/backends/postgis/schema.py
A django/contrib/gis/tests/gis_migrations/test_operations.py

  Log Message:
  ---
  [1.7.x] Fixed adding new GIS column in PostGIS 1.x migration

Refs #22451.
Backport of fb09a489c from master.


  Commit: 417e9f383f53b331576c26b29b9ab92ccb2e6df9
  
https://github.com/django/django/commit/417e9f383f53b331576c26b29b9ab92ccb2e6df9
  Author: Claude Paroz 
  Date:   2014-04-22 (Tue, 22 Apr 2014)

  Changed paths:
M django/contrib/gis/db/backends/postgis/schema.py
M django/contrib/gis/tests/gis_migrations/test_operations.py

  Log Message:
  ---
  [1.7.x] Fixed removal of GIS column in PostGIS 1.x migration

Refs #22481.
Backport of 2f9d1576e from master, squashed with 2f9d1576e8.


  Commit: 1d0f1ee1993fe9fb95888158946f897a34e95a39
  
https://github.com/django/django/commit/1d0f1ee1993fe9fb95888158946f897a34e95a39
  Author: Claude Paroz 
  Date:   2014-04-22 (Tue, 22 Apr 2014)

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

  Log Message:
  ---
  [1.7.x] Fixed table cleanup in GIS migration tests

Backport of ab90c4707b from master.


Compare: https://github.com/django/django/compare/935159d9517c...1d0f1ee1993f

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

Re: [Django] #22485: makemigrations fails with dependencies to unmigrated apps

[Django]

#22485: makemigrations fails with dependencies to unmigrated apps
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:  migrations,  | Triage Stage:  Accepted
  unmigrated, makemigrations |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by andrewgodwin):

 Running makemigrations for the apps isn't enough to get them in there
 early enough - contenttypes in particular loads too early in the Django
 process that it can't be migrated (I tried to add migrations to contrib
 apps and failed due to things like that and the tests).

 I have a plan for fixing this, which just means fixing the projectstate
 creator to always include unmigrated apps when it's making migration
 states. There's no need for fake migrations, hopefully, and the
 autodetector shouldn't need any changes.

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

Re: [Django] #15179: django.test.client.Client.login fake HttpRequest is not run through middlewares

[Django]

#15179: django.test.client.Client.login fake HttpRequest is not run through
middlewares
---+--
 Reporter:  Ciantic|Owner:  akaariai
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.7-beta-2
 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
---+--
Changes (by timo):

 * version:  master => 1.7-beta-2


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

Re: [Django] #15179: django.test.client.Client.login fake HttpRequest is not run through middlewares

[Django]

#15179: django.test.client.Client.login fake HttpRequest is not run through
middlewares
---+
 Reporter:  Ciantic|Owner:  akaariai
 Type:  Bug|   Status:  new
Component:  Testing framework  |  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
---+
Changes (by timo):

 * needs_better_patch:  1 => 0
 * has_patch:  1 => 0
 * severity:  Normal => Release blocker
 * stage:  Ready for checkin => Accepted


Comment:

 Seems like it could be a legitimate concern, although I'm not sure how
 often it will be a problem in practice.

 It wasn't initially clear to me where the "real response" was generated; I
 believe that refers to the logic in the `self.request()` calls that were
 added.

 Marking as a release blocker so we make a decision before the 1.7 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/065.e2a5faa49c1fc72f0b67e90103a7bae7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22485: makemigrations fails with dependencies to unmigrated apps

[Django]

#22485: makemigrations fails with dependencies to unmigrated apps
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:  migrations,  | Triage Stage:  Accepted
  unmigrated, makemigrations |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by loic84):

 If I do `makemigrations contenttypes && migrate && makemigrations auth &&
 migrate && makemigrations business && migrate` (from
 https://github.com/TonyEight/minimal) I get the `ValueError` for
 `auth.User`.

 Am I missing the obvious or there shouldn't be any unmigrated apps in that
 case?

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

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

Re: [Django] #22485: makemigrations fails with dependencies to unmigrated apps

[Django]

#22485: makemigrations fails with dependencies to unmigrated apps
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:  migrations,  | Triage Stage:  Accepted
  unmigrated, makemigrations |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by loic84):

 @charettes I second your plan for unmigrated apps, but I'm not sure it's
 what's at play here, having migrations for `contenttypes` and `auth`
 doesn't prevent the `ValueError` for `auth.User`.

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

Re: [Django] #22485: makemigrations fails with dependencies to unmigrated apps

[Django]

#22485: makemigrations fails with dependencies to unmigrated apps
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:  migrations,  | Triage Stage:  Accepted
  unmigrated, makemigrations |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by charettes):

 The `ValueError` for `auth.User` is caused by
 2085f53f567f7619ecf3eab93fdacab7a5991a11 which ignores all unmigrated
 apps. If you revert this fix, or just pass `ignore_unmigrated=False` in
 `makemigrations` you'll hit a `ValueError` for `contenttypes.ContentType`
 instead because added fake migrations don't follow relationship to
 unmigrated apps.

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

Re: [Django] #22489: Missing as_sql() implementation for __search lookup

[Django]

#22489: Missing as_sql() implementation for __search lookup
-+-
 Reporter:  jakub|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  mysql, search,   |  Needs documentation:  0
  full-text, __search, lookup|  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-
Changes (by charettes):

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


Comment:

 Could you add a regression test for this?

 Since it's only supported on MySQL atm you'll need to decorate your tests
 with `@skipUnless(connection.vendor == 'mysql')`. Since Mark is working on
 adding support for this to the postgresl backend we might want to add a
 database feature flag and rely on `skipUnlessDbFeature` instead.

 I guess those tests should live in `tests/lookup/tests.py`.

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

Re: [Django] #22485: makemigrations fails with dependencies to unmigrated apps

[Django]

#22485: makemigrations fails with dependencies to unmigrated apps
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:  migrations,  | Triage Stage:  Accepted
  unmigrated, makemigrations |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by RLion):

 * cc: RLion (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/066.8d209c8a074d54bdda23ad4d0bcbf19e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

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

[Django]

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

 * version:  1.6 => master
 * easy:  1 => 0


Comment:

 [https://github.com/django/django/pull/2578 PR]

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

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

Re: [Django] #22319: ValueError: Related model cannot be resolved

[Django]

#22319: ValueError: Related model cannot be resolved
-+--
 Reporter:  efrinut@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by loic84):

 @charettes, interestingly, it's not the same error, but rather
 `ValueError: Lookup failed for model referenced by field
 auth.Permission.content_type: contenttypes.ContentType`.

 I find that generating migrations for `d.c.contenttypes` then `d.c.auth`
 fixes the problem up to the point of #22485.

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

Re: [Django] #22429: Wrong SQL generated when using ~Q and F

[Django]

#22429: Wrong SQL generated when using ~Q and F
-+-
 Reporter:  sipp11   |Owner:
 Type:  Bug  |  superemily
Component:  Database layer   |   Status:  assigned
  (models, ORM)  |  Version:  master
 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 timo):

 * has_patch:  0 => 1
 * severity:  Normal => Release blocker


Comment:

 Here's a [https://github.com/django/django/pull/2588 PR]. Since it's a
 regression 1.6, it qualifies for a backport there so a mention in the
 1.6.4 release notes would be good.

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

Re: [Django] #21821: ORM lookup refactor broke Oracle tests

[Django]

#21821: ORM lookup refactor broke Oracle tests
-+-
 Reporter:  timo |Owner:  akaariai
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by jakub):

 Replying to [comment:13 akaariai]:
 > This one should be now fixed.
 >
 > Interestingly tests seem to pass even without
 1c360dbbf56b76e1df7c945458ae2987306fcfcd. I haven't ran full test suite on
 Oracle, but other databases pass without that, and timezones tests pass on
 Oracle also without that commit.
 >
 > I noticed that the `__search` lookup isn't tested at all. It is only
 supported on MySQL. It likely doesn't work currently, but that is food for
 another ticket.
 >
 > Edit note: One reason for the high amount of regressions is that I
 intentionally did not try to move existing make_atom() logic to class
 based lookups. The make_atom logic was somewhat weird in some places. The
 end result should be much cleaner now.


 The `__search` lookup indeed doesn't work. I've opened a ticked & pull
 request: #22489

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

Re: [Django] #22485: makemigrations fails with dependencies to unmigrated apps

[Django]

#22485: makemigrations fails with dependencies to unmigrated apps
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:  migrations,  | Triage Stage:  Accepted
  unmigrated, makemigrations |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by charettes):

 Since we just rolled out 1.7b2 which non more ignore dangling related
 model references I guess we're going to get a lot of issues pointing here.

 The planned approach here is to:

 1. Always load installed but unmigrate apps into the loader project state
 using fake migrations.
 2. Teach the `MigrationAutodetector` how to deal with those faked
 migration in order to avoid re-introducing #21968.

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

Re: [Django] #22478: Wrong module name used in build_test

[Django]

#22478: Wrong module name used in build_test
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:
 Severity:  Normal   |  1.7-beta-1
 Keywords:  tests, test suite|   Resolution:  fixed
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  1
 |UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"935159d9517ca951cbd5665c521d3c91102948d8"]:
 {{{
 #!CommitTicketReference repository=""
 revision="935159d9517ca951cbd5665c521d3c91102948d8"
 [1.7.x] Fixed #22478 -- Regression in test label discovery.

 As part of the app-loading updates the old test runner was changed to not
 require a models module. This introduced a regression in behavior so
 applabel.TestCase failed for tests defined in a directory.

 The fix is thanks to yakky and rtnpro.
 }}}

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

[django/django] 935159: [1.7.x] Fixed #22478 -- Regression in test label d...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 935159d9517ca951cbd5665c521d3c91102948d8
  
https://github.com/django/django/commit/935159d9517ca951cbd5665c521d3c91102948d8
  Author: Preston Timmons 
  Date:   2014-04-22 (Tue, 22 Apr 2014)

  Changed paths:
M django/test/simple.py
M tests/test_runner/tests.py
M tests/test_runner/valid_app/tests/__init__.py

  Log Message:
  ---
  [1.7.x] Fixed #22478 -- Regression in test label discovery.

As part of the app-loading updates the old test runner was changed to not
require a models module. This introduced a regression in behavior so
applabel.TestCase failed for tests defined in a directory.

The fix is thanks to yakky and rtnpro.


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

Re: [Django] #22319: ValueError: Related model cannot be resolved

[Django]

#22319: ValueError: Related model cannot be resolved
-+--
 Reporter:  efrinut@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by charettes):

 @RLion the `auth.User` dependency problem is tracked in #22485.

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

[Django] #22489: Missing as_sql() implementation for __search lookup

[Django]

#22489: Missing as_sql() implementation for __search lookup
-+-
 Reporter:  jakub|  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Database layer   |Version:
  (models, ORM)  |   Keywords:  mysql, search, full-
 Severity:  Normal   |  text, __search, lookup
 Triage Stage:  Unreviewed   |  Has patch:  1
Easy pickings:  0|  UI/UX:  0
-+-
 The (MySQL-only) __search full-text lookup isn't properly implemented
 using the new ORM lookup system. It's use results to a runtime exception:


 {{{
 >>> MyModel.objects.filter(field__search='hello world')
 [...]
  return node.as_sql(self, self.connection)
   File "/site-packages/django/db/models/sql/where.py", line 106, in as_sql
 sql, params = qn.compile(child)
   File "/site-packages/django/db/models/sql/compiler.py", line 80, in
 compile
 return node.as_sql(self, self.connection)
   File "/site-packages/django/db/models/sql/where.py", line 106, in as_sql
 sql, params = qn.compile(child)
   File "/site-packages/django/db/models/sql/compiler.py", line 80, in
 compile
 return node.as_sql(self, self.connection)
   File "/site-packages/django/db/models/lookups.py", line 150, in as_sql
 rhs_sql = self.get_rhs_op(connection, rhs_sql)
   File "/site-packages/django/db/models/lookups.py", line 154, in
 get_rhs_op
 return connection.operators[self.lookup_name] % rhs
 KeyError: 'search'
 }}}


 I've opened a pull request here:

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

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

Re: [Django] #22319: ValueError: Related model cannot be resolved

[Django]

#22319: ValueError: Related model cannot be resolved
-+--
 Reporter:  efrinut@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 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 RLion):

 * cc: RLion (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/075.b9f4cfbad55b2ec5ccc2ecb60cc4d428%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22319: ValueError: Related model cannot be resolved

[Django]

#22319: ValueError: Related model cannot be resolved
-+--
 Reporter:  efrinut@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by RLion):

 It seems like there's another dependancy problem, occuring with auth.User.

 https://github.com/TonyEight/minimal

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

Re: [Django] #22485: makemigrations fails with dependencies to unmigrated apps

[Django]

#22485: makemigrations fails with dependencies to unmigrated apps
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:  migrations,  | Triage Stage:  Accepted
  unmigrated, makemigrations |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by charettes):

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

Re: [Django] #22488: "ValueError: Lookup failed" on migrate after 1.7b2 upgrade

[Django]

#22488: "ValueError: Lookup failed" on migrate after 1.7b2 upgrade
-+--
 Reporter:  kmtracey |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7-beta-2
 Severity:  Release blocker  |   Resolution:  duplicate
 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 charettes):

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


Comment:

 Hi Karen,

 This is a duplicate of #22485 which is related to #21968 and #22397.

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

Re: [Django] #22486: urlresolvers.reverse() security fix (1.5.6) breaks when a view is a partial

[Django]

#22486: urlresolvers.reverse() security fix (1.5.6) breaks when a view is a 
partial
-+--
 Reporter:  rcoup|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (URLs)  |  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by timo):

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


Comment:

 Are you suggesting a change in Django itself or would a documentation
 update that notes this restriction be sufficient?

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

[Django] #22488: "ValueError: Lookup failed" on migrate after 1.7b2 upgrade

[Django]

#22488: "ValueError: Lookup failed" on migrate after 1.7b2 upgrade
---+
   Reporter:  kmtracey |  Owner:  nobody
   Type:  Bug  | Status:  new
  Component:  Migrations   |Version:  1.7-beta-2
   Severity:  Release blocker  |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+
 I'm getting an error running migrate on a project after upgrading from
 1.7b1 to 1.7b2. Running tests produces same error (somewhat different
 traceback). Besides the error something weird I notice is that auth is
 listed in both the "unmigrated" and "migrated" apps...I have no idea why.
 The project does use a custom user model. auth is listed as both migrated
 and not for 1.7b1 and 1.7b2, but the error only occurs on 1.7b2.

 I am not sure what would be helpful to debug this. This is what I see:

 {{{
 (uncfm) kmtracey@caktus006 11:48:48: ~/projects/uncfm
 --> ./manage.py shell
 Python 3.3.5 (default, Mar 12 2014, 02:09:17)
 [GCC 4.6.3] on linux
 Type "help", "copyright", "credits" or "license" for more information.
 (InteractiveConsole)
 >>> import django
 >>> django.get_version()
 '1.7b1'
 >>> quit()

 (uncfm) kmtracey@caktus006 11:48:59: ~/projects/uncfm
 --> ./manage.py migrate --list
 core
  [X] 0001_initial
 m3app
  [X] 0001_initial
  [X] 0002_observer_active
  [X] 0003_auto_20140415_1317
 scribbler
  (no migrations)

 (uncfm) kmtracey@caktus006 11:49:02: ~/projects/uncfm
 --> ./manage.py migrate
 Operations to perform:
   Synchronize unmigrated apps: compressor, sitemaps, contenttypes,
 scribbler, sessions, auth, admin
   Apply all migrations: auth, core, m3app
 Synchronizing apps without migrations:
   Creating tables...
   Installing custom SQL...
   Installing indexes...
 Running migrations:
   No migrations needed.

 (uncfm) kmtracey@caktus006 11:49:08: ~/projects/uncfm
 --> pip install requirements/sdists/Django-1.7b2.tar.gz
 Unpacking ./requirements/sdists/Django-1.7b2.tar.gz
   Running setup.py (path:/tmp/pip-v_a8yl-build/setup.py) egg_info for
 package from
 file:///home/kmtracey/projects/uncfm/requirements/sdists/Django-1.7b2.tar.gz

 warning: no previously-included files matching '__pycache__' found
 under directory '*'
 warning: no previously-included files matching '*.py[co]' found under
 directory '*'
 Installing collected packages: Django
   Found existing installation: Django 1.7b1
 Uninstalling Django:
   Successfully uninstalled Django
   Running setup.py install for Django

 warning: no previously-included files matching '__pycache__' found
 under directory '*'
 warning: no previously-included files matching '*.py[co]' found under
 directory '*'
 changing mode of build/scripts-3.3/django-admin.py from 664 to 775
 changing mode of /home/kmtracey/.virtualenvs/uncfm/bin/django-admin.py
 to 775
 Installing django-admin script to
 /home/kmtracey/.virtualenvs/uncfm/bin
 Successfully installed Django
 Cleaning up...

 (uncfm) kmtracey@caktus006 11:49:36: ~/projects/uncfm
 --> ./manage.py migrate --list
 core
  [X] 0001_initial
 m3app
  [X] 0001_initial
  [X] 0002_observer_active
  [X] 0003_auto_20140415_1317
 scribbler
  (no migrations)

 (uncfm) kmtracey@caktus006 11:49:45: ~/projects/uncfm
 --> ./manage.py migrate
 Operations to perform:
   Synchronize unmigrated apps: sitemaps, contenttypes, scribbler, auth,
 compressor, sessions, admin
   Apply all migrations: auth, m3app, core
 Synchronizing apps without migrations:
   Creating tables...
   Installing custom SQL...
   Installing indexes...
 Running migrations:
   No migrations needed.
 Traceback (most recent call last):
   File "./manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "/home/kmtracey/.virtualenvs/uncfm/lib/python3.3/site-
 packages/django/core/management/__init__.py", line 427, in
 execute_from_command_line
 utility.execute()
   File "/home/kmtracey/.virtualenvs/uncfm/lib/python3.3/site-
 packages/django/core/management/__init__.py", line 419, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/kmtracey/.virtualenvs/uncfm/lib/python3.3/site-
 packages/django/core/management/base.py", line 288, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "/home/kmtracey/.virtualenvs/uncfm/lib/python3.3/site-
 packages/django/core/management/base.py", line 337, in execute
 output = self.handle(*args, **options)
   File "/home/kmtracey/.virtualenvs/uncfm/lib/python3.3/site-
 packages/django/core/management/commands/migrate.py", line 140, in handle
 changes = 

[django/django] 1edb16: [1.4.x] Post release version bump.

[GitHub]

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: 1edb163592a21975d69aaca3215678f192421b71
  
https://github.com/django/django/commit/1edb163592a21975d69aaca3215678f192421b71
  Author: Tim Graham 
  Date:   2014-04-22 (Tue, 22 Apr 2014)

  Changed paths:
M django/__init__.py

  Log Message:
  ---
  [1.4.x] Post release version bump.


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

[django/django] 036b2d: [1.5.x] Post release version bump.

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 036b2d4f30ce77414b1c14d5c9f0f07a546ec904
  
https://github.com/django/django/commit/036b2d4f30ce77414b1c14d5c9f0f07a546ec904
  Author: Tim Graham 
  Date:   2014-04-22 (Tue, 22 Apr 2014)

  Changed paths:
M django/__init__.py

  Log Message:
  ---
  [1.5.x] Post release version bump.


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

[django/django] a93768: [1.6.x] Post release version bump.

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: a937687633e86f547c95ba8d21228ff220b5385c
  
https://github.com/django/django/commit/a937687633e86f547c95ba8d21228ff220b5385c
  Author: Tim Graham 
  Date:   2014-04-22 (Tue, 22 Apr 2014)

  Changed paths:
M django/__init__.py

  Log Message:
  ---
  [1.6.x] Post release version bump.


  Commit: 362ce5e936842bc3b3ea0aec15074e3752fe0ce5
  
https://github.com/django/django/commit/362ce5e936842bc3b3ea0aec15074e3752fe0ce5
  Author: Tim Graham 
  Date:   2014-04-22 (Tue, 22 Apr 2014)

  Changed paths:
A docs/releases/1.6.4.txt
M docs/releases/index.txt

  Log Message:
  ---
  [1.6.x] Added 1.6.4 release note stub.

Backport of 9fb95dfc9f from master


Compare: https://github.com/django/django/compare/6ec346ba7b25...362ce5e93684

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

[django/django] 55da4e: [1.7.x] Added 1.6.4 release note stub.

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 55da4e818d835205f42280ca06ef2a9a6d75fe08
  
https://github.com/django/django/commit/55da4e818d835205f42280ca06ef2a9a6d75fe08
  Author: Tim Graham 
  Date:   2014-04-22 (Tue, 22 Apr 2014)

  Changed paths:
A docs/releases/1.6.4.txt
M docs/releases/index.txt

  Log Message:
  ---
  [1.7.x] Added 1.6.4 release note stub.

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

[django/django] 9fb95d: Added 1.6.4 release note stub.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 9fb95dfc9fa1f9df73e384624c345199dd281dd5
  
https://github.com/django/django/commit/9fb95dfc9fa1f9df73e384624c345199dd281dd5
  Author: Tim Graham 
  Date:   2014-04-22 (Tue, 22 Apr 2014)

  Changed paths:
A docs/releases/1.6.4.txt
M docs/releases/index.txt

  Log Message:
  ---
  Added 1.6.4 release note stub.


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

Re: [Django] #22487: Moving from initial_data to data migrations stops test data persisting

[Django]

#22487: Moving from initial_data to data migrations stops test data persisting
-+-
 Reporter:  andrewgodwin |Owner:
 Type:  Bug  |  andrewgodwin
Component:  Testing framework|   Status:  assigned
 Severity:  Release blocker  |  Version:
 Keywords:   |  1.7-beta-1
Has patch:  0|   Resolution:
  Needs tests:  0| Triage Stage:
Easy pickings:  0|  Unreviewed
 |  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by andrewgodwin):

 * status:  new => assigned
 * type:  Uncategorized => 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/070.d2dd72fd70f8f199073a6efdf8b19efd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22487: Moving from initial_data to data migrations stops test data persisting

[Django]

#22487: Moving from initial_data to data migrations stops test data persisting
-+-
 Reporter:  andrewgodwin |Owner:
 Type:  Uncategorized|  andrewgodwin
Component:  Testing framework|   Status:  new
 Severity:  Release blocker  |  Version:
 Keywords:   |  1.7-beta-1
Has patch:  0|   Resolution:
  Needs tests:  0| Triage Stage:
Easy pickings:  0|  Unreviewed
 |  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by andrewgodwin):

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


Comment:

 This is being discussed at https://groups.google.com/forum/#!topic/django-
 developers/wR6hTy9Nu2k

 My initial proposal, and what I'll look at first, is dumping the data in
 the database into a temporary (possibly in-memory) fixture at the start of
 the test run, and then having flush restore from that.

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

[Django] #22487: Moving from initial_data to data migrations stops test data persisting

[Django]

#22487: Moving from initial_data to data migrations stops test data persisting
---+--
 Reporter:  andrewgodwin   |  Owner:  andrewgodwin
 Type:  Uncategorized  | Status:  new
Component:  Testing framework  |Version:  1.7-beta-1
 Severity:  Release blocker|   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+--
 Before migrations came along, tests would happily flush the database
 before each test so they could restore the data that was previously in
 there - initial data could be easily loaded from the initial_data fixture.

 Now we're encouraging data migrations to load initial data in - which are
 superior in almost every way - there's no easy way to replay that data
 back at the moment and so tests just don't see this data. Something needs
 to be done to allow initial data to persist across tests.

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

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

Re: [Django] #18767: Admin's calendar for datetime fields doesn't show right values with russian and some other locales

[Django]

#18767: Admin's calendar for datetime fields doesn't show right values with 
russian
and some other locales
---+
 Reporter:  void   |Owner:  maxocub
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by maxocub):

 This [https://github.com/django/django/pull/2560 PR] needs to be reviewed
 please.

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

Re: [Django] #22046: unhelpful queryset handling for model formsets with data

[Django]

#22046: unhelpful queryset handling for model formsets with data
+
 Reporter:  Jim Bailey  |Owner:  hershbergien
 Type:  Bug |   Status:  assigned
Component:  Forms   |  Version:  1.6
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+

Comment (by Jim Bailey):

 Hello, thank you very much for taking a look.

 I do not agree with the expectation stated in
 test_model_formset_with_paginated_form_data(). What I would expect is:

 Before the form is saved:
 {{{
 pk | name
 ---+-
  1 | a
  2 | c
  3 | e
  4 | g
  5 | b
 }}}

 The form data specifies that the record with id/pk 3 should be updated to
 have name 'c' and the record with id/pk 4 should be updated to have name
 'g', so after the form is saved:
 {{{
 pk | name
 ---+-
  1 | a
  2 | c
  3 | c
  4 | g
  5 | b
 }}}

 So there should now be two authors named 'c'.

 I don't think this new test really touches on any of the issues raised by
 this ticket as the specified queryset does contain all the records present
 in the form. The order is irrelevant. This is why this test fails both
 with and without my patch, and if it is corrected (there actually should
 be two 'c' authors) then it passes both with and without my patch.

 I feel that test_model_formset_with_mismatched_queryset() adequately tests
 problem 2 - that the correct record is updated (instead of a new one being
 created) despite the specified queryset not covering the form's record.

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

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

Re: [Django] #22482: Sites documentation suggest using initial data fixtures which are deprecated in 1.7

[Django]

#22482: Sites documentation suggest using initial data fixtures which are
deprecated in 1.7
---+--
 Reporter:  scibi  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.7-beta-1
 Severity:  Normal |   Resolution:
 Keywords:  sites, 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 scibi):

 IMHO it should be possible to initialize `sites` automatically while
 deploying the project. So it would be great to have a way of doing this
 described 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/063.c9144790db7123b1d3b4e714ead4b7ea%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22466: 'ManyToOneRel' object has no attribute 'rel'

[Django]

#22466: 'ManyToOneRel' object has no attribute 'rel'
---+--
 Reporter:  takis  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Uncategorized  |  Version:  1.7-beta-1
 Severity:  Normal |   Resolution:  needsinfo
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by takis):

 Hi,

 The codebase is large, so I will try to extract the smallest possible
 amount of code which still triggers the error. I cannot do it right away
 though, but I'll try to have a go after work this evening or tomorrow
 evening.

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

Re: [Django] #22051: Running `makemigrations` twice in a row fails

[Django]

#22051: Running `makemigrations` twice in a row fails
-+
 Reporter:  bmispelon|Owner:  andrewgodwin
 Type:  Bug  |   Status:  new
Component:  Migrations   |  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 l.a.evil.genius@…):

 If you are subclassing from `User` maybe this will help:
 In your model's migration file find string: `bases=('auth.user',),` and
 replace it with `bases=(User,),`. And don't forget to import: `from
 django.contrib.auth.models import User`

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

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

[Django]

#21231: Limiting the number of variables and files that a POST request can 
contain
---+
 Reporter:  epandurski@…   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by anonymous):

 Any news regarding this?

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

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

Re: [Django] #22426: Django >= 1.6.0 can't handle old style messages cookie

[Django]

#22426: Django >= 1.6.0 can't handle old style messages cookie
-+-
 Reporter:  iivvoo   |Owner:  ofirov
 Type:  Bug  |   Status:  closed
Component:  contrib.messages |  Version:  1.6
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  messages, cookie,| Triage Stage:  Accepted
  1.4|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Florian Apolloner ):

 In [changeset:"6ec346ba7b251a9bcebcd467dde72463197ad210"]:
 {{{
 #!CommitTicketReference repository=""
 revision="6ec346ba7b251a9bcebcd467dde72463197ad210"
 [1.6.x] Fixed #22426 -- Added support old-style d.c.messages format.

 Forward ported code from 1.5 that adds backwards compatibility with legacy
 message length.
 See commit 9e7183073f64e541587e8dcfd8bb3ddeb47f8162 for details.

 Thanks to Ofir Ovadia for the initial patch.

 Backport of f286721f7fdc2202f77a5f4d650d9d0779b86811 from master
 }}}

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

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

[django/django] 6ec346: [1.6.x] Fixed #22426 -- Added support old-style d....

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 6ec346ba7b251a9bcebcd467dde72463197ad210
  
https://github.com/django/django/commit/6ec346ba7b251a9bcebcd467dde72463197ad210
  Author: Florian Apolloner 
  Date:   2014-04-22 (Tue, 22 Apr 2014)

  Changed paths:
M django/contrib/messages/storage/cookie.py
M django/contrib/messages/tests/test_cookie.py

  Log Message:
  ---
  [1.6.x] Fixed #22426 -- Added support old-style d.c.messages format.

Forward ported code from 1.5 that adds backwards compatibility with legacy 
message length.
See commit 9e7183073f64e541587e8dcfd8bb3ddeb47f8162 for details.

Thanks to Ofir Ovadia for the initial patch.

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

Re: [Django] #22470: Migrations fail with order_with_respect_to and ForeignKey to self

[Django]

#22470: Migrations fail with order_with_respect_to and ForeignKey to self
-+-
 Reporter:  Jonas|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:
 Severity:  Normal   |  1.7-beta-1
 Keywords:  migrations   |   Resolution:
  order_with_respect_to  | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Jonas):

 * cc: Jonas (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 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/063.a0c9f497aaa269a5fad099511ddc2e5c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22426: Django >= 1.6.0 can't handle old style messages cookie

[Django]

#22426: Django >= 1.6.0 can't handle old style messages cookie
-+-
 Reporter:  iivvoo   |Owner:  ofirov
 Type:  Bug  |   Status:  closed
Component:  contrib.messages |  Version:  1.6
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  messages, cookie,| Triage Stage:  Accepted
  1.4|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Florian Apolloner ):

 In [changeset:"97b5833e212d3e6520dfa43525aa75f625a760a0"]:
 {{{
 #!CommitTicketReference repository=""
 revision="97b5833e212d3e6520dfa43525aa75f625a760a0"
 [1.7.x] Fixed #22426 -- Added support old-style d.c.messages format.

 Forward ported code from 1.5 that adds backwards compatibility with legacy
 message length.
 See commit 9e7183073f64e541587e8dcfd8bb3ddeb47f8162 for details.

 Thanks to Ofir Ovadia for the initial patch.

 Backport of f286721f7fdc2202f77a5f4d650d9d0779b86811 from master.
 }}}

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

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

[django/django] 97b583: [1.7.x] Fixed #22426 -- Added support old-style d....

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 97b5833e212d3e6520dfa43525aa75f625a760a0
  
https://github.com/django/django/commit/97b5833e212d3e6520dfa43525aa75f625a760a0
  Author: Florian Apolloner 
  Date:   2014-04-22 (Tue, 22 Apr 2014)

  Changed paths:
M django/contrib/messages/storage/cookie.py
M django/contrib/messages/tests/test_cookie.py

  Log Message:
  ---
  [1.7.x] Fixed #22426 -- Added support old-style d.c.messages format.

Forward ported code from 1.5 that adds backwards compatibility with legacy 
message length.
See commit 9e7183073f64e541587e8dcfd8bb3ddeb47f8162 for details.

Thanks to Ofir Ovadia for the initial patch.

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

Re: [Django] #22426: Django >= 1.6.0 can't handle old style messages cookie

[Django]

#22426: Django >= 1.6.0 can't handle old style messages cookie
-+-
 Reporter:  iivvoo   |Owner:  ofirov
 Type:  Bug  |   Status:  closed
Component:  contrib.messages |  Version:  1.6
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  messages, cookie,| Triage Stage:  Accepted
  1.4|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Florian Apolloner ):

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


Comment:

 In [changeset:"f286721f7fdc2202f77a5f4d650d9d0779b86811"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f286721f7fdc2202f77a5f4d650d9d0779b86811"
 Fixed #22426 -- Added support old-style d.c.messages format.

 Forward ported code from 1.5 that adds backwards compatibility with legacy
 message length.
 See commit 9e7183073f64e541587e8dcfd8bb3ddeb47f8162 for details.

 Thanks to Ofir Ovadia for the initial patch.
 }}}

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

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

[django/django] f28672: Fixed #22426 -- Added support old-style d.c.messag...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: f286721f7fdc2202f77a5f4d650d9d0779b86811
  
https://github.com/django/django/commit/f286721f7fdc2202f77a5f4d650d9d0779b86811
  Author: Florian Apolloner 
  Date:   2014-04-22 (Tue, 22 Apr 2014)

  Changed paths:
M django/contrib/messages/storage/cookie.py
M django/contrib/messages/tests/test_cookie.py

  Log Message:
  ---
  Fixed #22426 -- Added support old-style d.c.messages format.

Forward ported code from 1.5 that adds backwards compatibility with legacy 
message length.
See commit 9e7183073f64e541587e8dcfd8bb3ddeb47f8162 for details.

Thanks to Ofir Ovadia for the initial patch.


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

Re: [Django] #22479: Support byte range requests in django.views.static.serve

[Django]

#22479: Support byte range requests in django.views.static.serve
---+
 Reporter:  slurms |Owner:  slurms
 Type:  New feature|   Status:  assigned
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by slurms):

 Good points, it would be great if we could get closer to dev/prod parity.
 But sometimes I don't have a need for something rock-solid and production
 tested, and instead I just want things to "easily" work. I don't think
 gunicorn or the 'static' python library (used by dj_static) support
 partial content, and I've only had the need for it to be supported
 recently due to serving video content on a small internal application.
 This internal application is still reverse proxied via nginx, and serving
 content via gunicorn and `django.views.static.serve`. Werkzeug does
 support partial content, but not for multipart/byterange requests (not
 sure if this is a big deal).

 The use-case for supporting it in `django.views.static.serve` is that this
 application of ours runs in a container via docker. Without the support I
 am faced with two decisions: I could map out the static and media dirs to
 the host, and share the filesystem from the host to our nginx server and
 serve it like that, or run an instance of nginx (or another http server)
 directly within the container. Both of the options are time-consuming,
 require oodles of extra configuration, and are probably not ideal. We just
 need something simple that works for serving video content that supports
 seeking within the video. The application won't be serving millions of
 requests. If it was, I certainly wouldn't be using this support, I would
 opt for a different solution. But it doesn't mean we shouldn't support it
 at all :).

 It would be good to move away from the devserver, but also, it would be
 useful to support partial content in `django.views.static.serve` so that
 things just work in the meantime. Maybe not ideal, but pragmatic?

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

Re: [Django] #5437: Make GDAL optional for GIS test runner

[Django]

#5437: Make GDAL optional for GIS test runner
-+
 Reporter:  rcoup|Owner:  vlal
 Type:  Bug  |   Status:  assigned
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  testing  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by vlal):

 * cc: vlal (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/063.f1c19517fddf43f8b2e09ff97b13f012%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.