Re: [Django] #25370: Error display when makemigrations' field serializing fails with ValueError

[Django]

#25370: Error display when makemigrations' field serializing fails with 
ValueError
--+
 Reporter:  torstenrudolf |Owner:  awwester
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Migrations|  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by awwester):

 * owner:  nobody => awwester
 * cc: awwester@… (added)
 * status:  new => assigned


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

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

Re: [Django] #25803: npm test failure

[Django]

#25803: npm test failure
---+--
 Reporter:  nikolas|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:  worksforme
 Keywords:  javascript | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by nikolas):

 I've solved the problem: using an older version of npm, the tests work for
 me. npm 2.x works, but npm 3.x doesn't.

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

Re: [Django] #25803: npm test failure

[Django]

#25803: npm test failure
---+--
 Reporter:  nikolas|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:  worksforme
 Keywords:  javascript | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Description changed by nikolas:

Old description:

> Following the instructions to run the JavaScript tests here:
> https://docs.djangoproject.com/en/dev/internals/contributing/writing-
> code/javascript/
>
> I run `npm install`, then `npm test`. I'm using node.js v4.2.1, npm
> v3.4.1.
>
> The command fails, and here's the output:
>
> {{{
> $ npm test
>
> > Django@ pretest /home/nnyby/src/django
> > eslint django/ js_tests/admin/ js_tests/gis/
>

> django/contrib/admin/static/admin/js/SelectFilter2.js
>78:178  warning  Script URL is a form of eval  no-script-url
>84:138  warning  Script URL is a form of eval  no-script-url
>86:141  warning  Script URL is a form of eval  no-script-url
>   108:181  warning  Script URL is a form of eval  no-script-url
>
> django/contrib/admin/static/admin/js/admin/DateTimeShortcuts.js
>   108:42  warning  Script URL is a form of eval  no-script-url
>   111:44  warning  Script URL is a form of eval  no-script-url
>   149:85  warning  Script URL is a form of eval  no-script-url
>   150:90  warning  Script URL is a form of eval  no-script-url
>   151:88  warning  Script URL is a form of eval  no-script-url
>   152:86  warning  Script URL is a form of eval  no-script-url
>   153:88  warning  Script URL is a form of eval  no-script-url
>   157:67  warning  Script URL is a form of eval  no-script-url
>   216:44  warning  Script URL is a form of eval  no-script-url
>   219:42  warning  Script URL is a form of eval  no-script-url
>   258:71  warning  Script URL is a form of eval  no-script-url
>   260:71  warning  Script URL is a form of eval  no-script-url
>   272:71  warning  Script URL is a form of eval  no-script-url
>   274:67  warning  Script URL is a form of eval  no-script-url
>   276:70  warning  Script URL is a form of eval  no-script-url
>   281:67  warning  Script URL is a form of eval  no-script-url
>
> django/contrib/admin/static/admin/js/calendar.js
>   104:60  warning  Script URL is a form of eval  no-script-url
>
> ✖ 21 problems (0 errors, 21 warnings)
>

> > Django@ test /home/nnyby/src/django
> > grunt test --verbose
>
> Initializing
> Command-line options: --verbose
>
> Reading "Gruntfile.js" Gruntfile...OK
>
> Registering Gruntfile tasks.
> Initializing config...OK
>
> Registering "grunt-blanket-qunit" local Npm module tasks.
> Reading /home/nnyby/src/django/node_modules/grunt-blanket-
> qunit/package.json...OK
> Parsing /home/nnyby/src/django/node_modules/grunt-blanket-
> qunit/package.json...OK
> Loading "blanket_qunit.js" tasks...ERROR
> >> Error: Cannot find module 'grunt-contrib-qunit/node_modules/grunt-lib-
> phantomjs'
> >> at Function.Module._resolveFilename (module.js:337:15)
> >> at Function.Module._load (module.js:287:25)
> >> at Module.require (module.js:366:17)
> >> at require (module.js:385:17)
> >> at Object.module.exports (/home/nnyby/src/django/node_modules
> /grunt-blanket-qunit/tasks/blanket_qunit.js:23:21)
> >> at loadTask
> (/home/nnyby/src/django/node_modules/grunt/lib/grunt/task.js:325:10)
> >> at
> /home/nnyby/src/django/node_modules/grunt/lib/grunt/task.js:361:7
> >> at Array.forEach (native)
> >> at loadTasks
> (/home/nnyby/src/django/node_modules/grunt/lib/grunt/task.js:360:11)
> >> at Task.task.loadNpmTasks
> (/home/nnyby/src/django/node_modules/grunt/lib/grunt/task.js:408:5)
> Loading "Gruntfile.js" tasks...OK
> + default, test
>
> Running tasks: test
>
> Running "test" task
> Warning: Task "blanket_qunit" not found. Use --force to continue.
>
> Aborted due to warnings.
> npm ERR! Test failed.  See above for more details
> }}}

New description:

 Following the instructions to run the JavaScript tests here:
 https://docs.djangoproject.com/en/dev/internals/contributing/writing-
 code/javascript/#running-tests

 I run `npm install`, then `npm test`. I'm using node.js v4.2.1, npm
 v3.4.1.

 The command fails, and here's the output:

 {{{
 $ npm test

 > Django@ pretest /home/nnyby/src/django
 > eslint django/ js_tests/admin/ js_tests/gis/


 django/contrib/admin/static/admin/js/SelectFilter2.js
78:178  warning  Script URL is a form of eval  no-script-url
84:138  warning  Script URL is a form of eval  no-script-url
86:141  warning  Script URL is a form of eval  no-script-url
   108:181  warning

Re: [Django] #25412: Migrate command does not create index with operator class for CharField

[Django]

#25412: Migrate command does not create index with operator class for CharField
+
 Reporter:  synasius|Owner:  synasius
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+
Changes (by timgraham):

 * needs_better_patch:  0 => 1
 * stage:  Ready for checkin => 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/066.64d3ca65eb4109a5dd61d72303fbac9f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24694: Add support for OPTIONS['context_processors'] to Jinja2 template backend

[Django]

#24694: Add support for OPTIONS['context_processors'] to Jinja2 template backend
-+
 Reporter:  carljm   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by carljm):

 Since I never got around to making a PR for this for Django 1.9, I've
 uploaded the implementation I've been using that subclasses the built-in
 backend. This may be immediately useful to someone working in Django 1.8
 or 1.9, and should also provide a reasonable basis for anyone motivated to
 turn it into a proper patch. It needs to be integrated into the main
 Jinja2 backend instead of being a subclass, and needs tests and docs
 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/064.2b1f1e1401658f331ab20bb71e2893c7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24694: Add support for OPTIONS['context_processors'] to Jinja2 template backend

[Django]

#24694: Add support for OPTIONS['context_processors'] to Jinja2 template backend
-+
 Reporter:  carljm   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by carljm):

 * Attachment "24694.py" added.

 implementation as a subclass of existing backend

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

Re: [Django] #25663: `LinearRing` and `LineString` don't check number of points during instantiation

[Django]

#25663: `LinearRing` and `LineString` don't check number of points during
instantiation
-+-
 Reporter:  sir-sigurd   |Owner:  sir-
 Type:   |  sigurd
  Cleanup/optimization   |   Status:  closed
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


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

Re: [Django] #25803: npm test failure

[Django]

#25803: npm test failure
---+--
 Reporter:  nikolas|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:  worksforme
 Keywords:  javascript | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by timgraham):

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


Comment:

 Okay, please reopen if the problem turns out to be Django's fault. Thanks!

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

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

Re: [Django] #25663: `LinearRing` and `LineString` don't check number of points during instantiation

[Django]

#25663: `LinearRing` and `LineString` don't check number of points during
instantiation
-+-
 Reporter:  sir-sigurd   |Owner:  sir-
 Type:   |  sigurd
  Cleanup/optimization   |   Status:  new
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"229fc793a027f1fd3e6e9d553ed09c15b521776c" 229fc793]:
 {{{
 #!CommitTicketReference repository=""
 revision="229fc793a027f1fd3e6e9d553ed09c15b521776c"
 Refs #25663 -- Fixed checking of the number of points for LineString if
 initialized from numpy.array.
 }}}

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

Re: [Django] #25739: deprecate geos.factory.fromstr

[Django]

#25739: deprecate geos.factory.fromstr
-+-
 Reporter:  sir-sigurd   |Owner:  sir-
 Type:   |  sigurd
  Cleanup/optimization   |   Status:  closed
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 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 Tim Graham ):

 In [changeset:"013309eaf55ca88e4c412d2a83a95c60691dfe50" 013309ea]:
 {{{
 #!CommitTicketReference repository=""
 revision="013309eaf55ca88e4c412d2a83a95c60691dfe50"
 [1.9.x] Refs #25739 -- Lessened the prominence of geos.fromstr() in the
 docs.

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

Re: [Django] #25739: deprecate geos.factory.fromstr

[Django]

#25739: deprecate geos.factory.fromstr
-+-
 Reporter:  sir-sigurd   |Owner:  sir-
 Type:   |  sigurd
  Cleanup/optimization   |   Status:  closed
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 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 Tim Graham ):

 In [changeset:"954d63155f92d92c5fa33c30be2869a2592830ef" 954d631]:
 {{{
 #!CommitTicketReference repository=""
 revision="954d63155f92d92c5fa33c30be2869a2592830ef"
 [1.8.x] Refs #25739 -- Lessened the prominence of geos.fromstr() in the
 docs.

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

[Django] #25804: Jinja2 template backend context additions are undocumented

[Django]

#25804: Jinja2 template backend context additions are undocumented
+
   Reporter:  carljm|  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Documentation |Version:  1.8
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 The Jinja2 template backend adds a few things to the template context by
 default: the request, and the CSRF token and CSRF input tag generator. As
 far as I can find (and perhaps I missed it), these additions are not
 documented anywhere, and they should be.

 Issue originally noted by Patrick Spencer in
 https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg
 /django-users/kd8m9miWCK4/v-G9yfaYCAAJ

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

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

Re: [Django] #25739: deprecate geos.factory.fromstr

[Django]

#25739: deprecate geos.factory.fromstr
-+-
 Reporter:  sir-sigurd   |Owner:  sir-
 Type:   |  sigurd
  Cleanup/optimization   |   Status:  closed
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 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 Tim Graham ):

 In [changeset:"97e1d2433085e01696dc2fac8bfbb9c421c82b67" 97e1d243]:
 {{{
 #!CommitTicketReference repository=""
 revision="97e1d2433085e01696dc2fac8bfbb9c421c82b67"
 Refs #25739 -- Lessened the prominence of geos.fromstr() 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/068.85828e18b5a2a52e2243513948e3af15%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25803: npm test failure

[Django]

#25803: npm test failure
---+--
 Reporter:  nikolas|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  javascript | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by nikolas):

 I'm able to execute `phantomjs`, so that's not the issue. I looked around
 but none of the proposed solutions I've found have worked for me so far. I
 will try to figure this out, but the error seems reproducible so I thought
 this was an issue with Django's grunt setup.

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

Re: [Django] #25803: npm test failure

[Django]

#25803: npm test failure
---+--
 Reporter:  nikolas|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  javascript | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by timgraham):

 Can you try googling the error in your log ouput, "Error: Cannot find
 module 'grunt-contrib-qunit/node_modules/grunt-lib-phantomjs". e.g.
 https://github.com/gruntjs/grunt-contrib-
 qunit/issues/26#issuecomment-22134722 might help.

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

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

Re: [Django] #25803: npm test failure

[Django]

#25803: npm test failure
---+--
 Reporter:  nikolas|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  javascript | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by nikolas):

 I got the same errors using Node 0.10.25 on Ubuntu 14.04:

 http://dpaste.com/22738JV

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

Re: [Django] #24475: Add a new testconnections management command

[Django]

#24475: Add a new testconnections management command
-+-
 Reporter:  gannetson|Owner:
 |  alexmorozov
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 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 timgraham):

 I think testing only connections is fine as it's a fundamentally different
 type of check from the static code checks but this is subject to the
 implementation, what checks we actually add, and what others think is
 best.

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

Re: [Django] #25803: npm test failure

[Django]

#25803: npm test failure
---+--
 Reporter:  nikolas|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  javascript | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by timgraham):

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


Comment:

 I guess it might be related to the node version -- we are using the
 version packaged for Ubuntu 14.04 -- 0.10.25. Could you investigate?

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

Re: [Django] #25789: Inefficient Queries Generated due to not using WHERE EXISTS

[Django]

#25789: Inefficient Queries Generated due to not using WHERE EXISTS
-+-
 Reporter:  cancan101|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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

Re: [Django] #2316: GenericRelation and get_or_create do not work together

[Django]

#2316: GenericRelation and get_or_create do not work together
--+
 Reporter:  Rudolph   |Owner:  adrian
 Type:  Bug   |   Status:  new
Component:  contrib.contenttypes  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  GenericRelation   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by auvipy):

 * version:  1.2 => master


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

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

Re: [Django] #25789: Inefficient Queries Generated due to not using WHERE EXISTS

[Django]

#25789: Inefficient Queries Generated due to not using WHERE EXISTS
-+-
 Reporter:  cancan101|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 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 akaariai):

 Yes, this is possible, and something Django's ORM should do.

 Unfortunately this is hard to implement correctly. The big problem is
 aggregation, when doing .filter().annotate(), where both operations target
 the same relation, the aggregation must use results of the join generated
 by the filter. But if the filter doesn't generate a join, then we have a
 problem.

 It would be Djangoic if the exists query would be generated automatically.
 For the above mentioned reason this is hard. Maybe it would be easier if
 we had something like .filter(models.Exists(somerel__col=val)), where the
 Exists() class would inform Django that an exists subquery should be
 generated.

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

Re: [Django] #24475: Add a new testconnections management command

[Django]

#24475: Add a new testconnections management command
-+-
 Reporter:  gannetson|Owner:
 |  alexmorozov
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by alexmorozov):

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


Comment:

 @timgraham, thank you. Will have a closer look on this. Should the `check
 --connections` test '''only''' connections as its name implies, or maybe
 we should rename the option? My English is pretty poor, but wouldn't
 something like `--with-connections` be more clear?

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

[Django] #25803: npm test failure

[Django]

#25803: npm test failure
---+
 Reporter:  nikolas|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  master
 Severity:  Normal |   Keywords:  javascript
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Following the instructions to run the JavaScript tests here:
 https://docs.djangoproject.com/en/dev/internals/contributing/writing-
 code/javascript/

 I run `npm install`, then `npm test`. I'm using node.js v4.2.1, npm
 v3.4.1.

 The command fails, and here's the output:

 {{{
 $ npm test

 > Django@ pretest /home/nnyby/src/django
 > eslint django/ js_tests/admin/ js_tests/gis/


 django/contrib/admin/static/admin/js/SelectFilter2.js
78:178  warning  Script URL is a form of eval  no-script-url
84:138  warning  Script URL is a form of eval  no-script-url
86:141  warning  Script URL is a form of eval  no-script-url
   108:181  warning  Script URL is a form of eval  no-script-url

 django/contrib/admin/static/admin/js/admin/DateTimeShortcuts.js
   108:42  warning  Script URL is a form of eval  no-script-url
   111:44  warning  Script URL is a form of eval  no-script-url
   149:85  warning  Script URL is a form of eval  no-script-url
   150:90  warning  Script URL is a form of eval  no-script-url
   151:88  warning  Script URL is a form of eval  no-script-url
   152:86  warning  Script URL is a form of eval  no-script-url
   153:88  warning  Script URL is a form of eval  no-script-url
   157:67  warning  Script URL is a form of eval  no-script-url
   216:44  warning  Script URL is a form of eval  no-script-url
   219:42  warning  Script URL is a form of eval  no-script-url
   258:71  warning  Script URL is a form of eval  no-script-url
   260:71  warning  Script URL is a form of eval  no-script-url
   272:71  warning  Script URL is a form of eval  no-script-url
   274:67  warning  Script URL is a form of eval  no-script-url
   276:70  warning  Script URL is a form of eval  no-script-url
   281:67  warning  Script URL is a form of eval  no-script-url

 django/contrib/admin/static/admin/js/calendar.js
   104:60  warning  Script URL is a form of eval  no-script-url

 ✖ 21 problems (0 errors, 21 warnings)


 > Django@ test /home/nnyby/src/django
 > grunt test --verbose

 Initializing
 Command-line options: --verbose

 Reading "Gruntfile.js" Gruntfile...OK

 Registering Gruntfile tasks.
 Initializing config...OK

 Registering "grunt-blanket-qunit" local Npm module tasks.
 Reading /home/nnyby/src/django/node_modules/grunt-blanket-
 qunit/package.json...OK
 Parsing /home/nnyby/src/django/node_modules/grunt-blanket-
 qunit/package.json...OK
 Loading "blanket_qunit.js" tasks...ERROR
 >> Error: Cannot find module 'grunt-contrib-qunit/node_modules/grunt-lib-
 phantomjs'
 >> at Function.Module._resolveFilename (module.js:337:15)
 >> at Function.Module._load (module.js:287:25)
 >> at Module.require (module.js:366:17)
 >> at require (module.js:385:17)
 >> at Object.module.exports (/home/nnyby/src/django/node_modules
 /grunt-blanket-qunit/tasks/blanket_qunit.js:23:21)
 >> at loadTask
 (/home/nnyby/src/django/node_modules/grunt/lib/grunt/task.js:325:10)
 >> at
 /home/nnyby/src/django/node_modules/grunt/lib/grunt/task.js:361:7
 >> at Array.forEach (native)
 >> at loadTasks
 (/home/nnyby/src/django/node_modules/grunt/lib/grunt/task.js:360:11)
 >> at Task.task.loadNpmTasks
 (/home/nnyby/src/django/node_modules/grunt/lib/grunt/task.js:408:5)
 Loading "Gruntfile.js" tasks...OK
 + default, test

 Running tasks: test

 Running "test" task
 Warning: Task "blanket_qunit" not found. Use --force to continue.

 Aborted due to warnings.
 npm ERR! Test failed.  See above for more details
 }}}

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

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

Re: [Django] #25800: IIS ISAPI request throws AppRegistryNotReady: Apps aren't loaded yet.

[Django]

#25800: IIS ISAPI request throws AppRegistryNotReady: Apps aren't loaded yet.
---+--
 Reporter:  atarkowska |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  HTTP handling  |  Version:  1.8
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by shaib):

 Replying to [comment:4 atarkowska]:
 > and I am using from django.utils.translation import ugettext_lazy as _

 The traceback you quote claims otherwise.

 Also, it has been mentioned to you that Trac is not a support channel. The
 place to ask "is this a bug" questions, when you are not sure what is
 wrong, is the django-users mailing list or the #django IRC channel. This
 ticket has been closed, and you should expect no more answers here.

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

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

Re: [Django] #24475: Add a new testconnections management command

[Django]

#24475: Add a new testconnections management command
-+-
 Reporter:  gannetson|Owner:
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |
 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 timgraham):

 Currently the system check framework is limited to static code analysis.
 Adding a new option like `check --conections` could work. I think these
 checks shouldn't run if that option isn't specified though.

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

Re: [Django] #25789: Inefficient Queries Generated due to not using WHERE EXISTS

[Django]

#25789: Inefficient Queries Generated due to not using WHERE EXISTS
-+-
 Reporter:  cancan101|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 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 timgraham):

 * cc: akaariai (added)
 * needs_better_patch:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Anssi, is this feasible? The closest existing ticket I could find is
 #16603 but not sure if it should be considered 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/067.281f5e382622aa10f5b1157eb91d2fcf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25786: set_*_order raises ValueError when ForeignKey referenced Model also has OneToOneField

[Django]

#25786: set_*_order raises ValueError when ForeignKey referenced Model also has
OneToOneField
-+-
 Reporter:  aktiur   |Owner:  timgraham
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
  order_with_respect_to ForeignKey   |
  OneToOneField  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"8edf8db52f626e6bf384a729063f91caa6592f92" 8edf8db]:
 {{{
 #!CommitTicketReference repository=""
 revision="8edf8db52f626e6bf384a729063f91caa6592f92"
 [1.9.x] Refs #25786 -- Added tests/release notes for set_FOO_order() crash
 with order_with_respect_to referencing OneToOneField pk.

 Forwardport of 6d9f061b07ce7aa1a9da6799b3104971ee73998b from stable/1.8.x
 The issue was fixed by 7bec480fe2ace94c8e7f0c88485442bfa74436b4.
 }}}

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

Re: [Django] #25791: Implement autoreload behaviour for cached template loader

[Django]

#25791: Implement autoreload behaviour for cached template loader
-+-
 Reporter:  jaap3|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  autoreload   | Triage Stage:
  templates cached loader|  Someday/Maybe
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 [https://groups.google.com/d/topic/django-
 developers/JMwJWTgtFfc/discussion django-developers discussion]

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

Re: [Django] #25788: Enabling the cached template loader should be easier

[Django]

#25788: Enabling the cached template loader should be easier
-+-
 Reporter:  jaap3|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Someday/Maybe
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Unreviewed => Someday/Maybe


Comment:

 [https://groups.google.com/d/topic/django-
 developers/JMwJWTgtFfc/discussion django-developers discussion]

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

Re: [Django] #25802: The 'logout' button is ineffective on code.djangoproject.com.

[Django]

#25802: The 'logout' button is ineffective on code.djangoproject.com.
---+--
 Reporter:  jribbens   |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:
 Severity:  Normal |   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 timgraham):

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


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

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

Re: [Django] #25802: The 'logout' button is ineffective on code.djangoproject.com.

[Django]

#25802: The 'logout' button is ineffective on code.djangoproject.com.
---+--
 Reporter:  jribbens   |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:
 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 jribbens):

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


Comment:

 I've moved this to
 https://github.com/django/code.djangoproject.com/issues/61

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

Re: [Django] #25786: set_*_order raises ValueError when ForeignKey referenced Model also has OneToOneField

[Django]

#25786: set_*_order raises ValueError when ForeignKey referenced Model also has
OneToOneField
-+-
 Reporter:  aktiur   |Owner:  timgraham
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
  order_with_respect_to ForeignKey   |
  OneToOneField  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"e07def14b82b065f010a251cfbc8b3881f3c4d85" e07def14]:
 {{{
 #!CommitTicketReference repository=""
 revision="e07def14b82b065f010a251cfbc8b3881f3c4d85"
 Refs #25786 -- Added tests/release notes for set_FOO_order() crash with
 order_with_respect_to referencing OneToOneField pk.

 Forwardport of 6d9f061b07ce7aa1a9da6799b3104971ee73998b from stable/1.8.x
 The issue was fixed by 7bec480fe2ace94c8e7f0c88485442bfa74436b4.
 }}}

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

Re: [Django] #25412: Migrate command does not create index with operator class for CharField

[Django]

#25412: Migrate command does not create index with operator class for CharField
+-
 Reporter:  synasius|Owner:  synasius
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Ready for checkin
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+-
Changes (by charettes):

 * needs_better_patch:  1 => 0
 * stage:  Accepted => Ready for checkin


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

Re: [Django] #25801: No way to change password on code.djangoproject.com

[Django]

#25801: No way to change password on code.djangoproject.com
---+--
 Reporter:  jribbens   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Uncategorized  |  Version:
 Severity:  Normal |   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 timgraham):

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


Comment:

 Moved to https://github.com/django/code.djangoproject.com/issues/60

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

Re: [Django] #25786: set_*_order raises ValueError when ForeignKey referenced Model also has OneToOneField

[Django]

#25786: set_*_order raises ValueError when ForeignKey referenced Model also has
OneToOneField
-+-
 Reporter:  aktiur   |Owner:  timgraham
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
  order_with_respect_to ForeignKey   |
  OneToOneField  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"6d9f061b07ce7aa1a9da6799b3104971ee73998b" 6d9f061b]:
 {{{
 #!CommitTicketReference repository=""
 revision="6d9f061b07ce7aa1a9da6799b3104971ee73998b"
 [1.8.x] Fixed #25786 -- Fixed set_FOO_order() crash with
 order_with_respect_to referencing OneToOneField pk.

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

Re: [Django] #25800: IIS ISAPI request throws AppRegistryNotReady: Apps aren't loaded yet.

[Django]

#25800: IIS ISAPI request throws AppRegistryNotReady: Apps aren't loaded yet.
---+--
 Reporter:  atarkowska |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  HTTP handling  |  Version:  1.8
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by atarkowska):

 and I am using from django.utils.translation import ugettext_lazy as _

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

[Django] #25802: The 'logout' button is ineffective on code.djangoproject.com.

[Django]

#25802: The 'logout' button is ineffective on code.djangoproject.com.
---+
 Reporter:  jribbens   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Clicking 'logout' is ineffective - if you click 'DjangoProject Login'
 afterwards then you are logged straight back in again without being asked
 for any username or password.

 I am using Chrome 46.0.2490.86m (64-bit) on Windows.

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

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

[Django] #25801: No way to change password on code.djangoproject.com

[Django]

#25801: No way to change password on code.djangoproject.com
---+
 Reporter:  jribbens   |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Uncategorized  |Version:
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 There is no obvious way to change your DjangoProject login password on
 code.djangoproject.com.

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

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

Re: [Django] #25800: IIS ISAPI request throws AppRegistryNotReady: Apps aren't loaded yet.

[Django]

#25800: IIS ISAPI request throws AppRegistryNotReady: Apps aren't loaded yet.
---+--
 Reporter:  atarkowska |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  HTTP handling  |  Version:  1.8
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by atarkowska):

 I went one step forward and now got


 {{{
 Traceback (most recent call last):
 File "c:\OMERO.server\lib\python\omeroweb\webclient\views.py", line 197,
 in login form = LoginForm(data=request.POST.copy())
 File "c:\OMERO.server\lib\python\omeroweb\webadmin\forms.py", line 52, in
 __init__ super(LoginForm, self).__init__(*args, **kwargs)
 File "c:\OMERO.server\lib\python\omeroweb\custom_forms.py", line 35, in
 __init__ super(NonASCIIForm, self).__init__(*args, **kwargs)
 File "C:\Python27\lib\site-packages\django\forms\forms.py", line 129, in
 __init__ self.label_suffix = label_suffix if label_suffix is not None else
 _(':')
 File "C:\Python27\lib\site-packages\django\utils\translation\__init__.py",
 line 84, in ugettext return _trans.ugettext(message)
 File "C:\Python27\lib\site-
 packages\django\utils\translation\trans_real.py", line 327, in ugettext
 return do_translate(message, 'ugettext')
 File "C:\Python27\lib\site-
 packages\django\utils\translation\trans_real.py", line 304, in
 do_translate _default = _default or translation(settings.LANGUAGE_CODE)
 File "C:\Python27\lib\site-
 packages\django\utils\translation\trans_real.py", line 206, in translation
 _translations[language] = DjangoTranslation(language)
 File "C:\Python27\lib\site-
 packages\django\utils\translation\trans_real.py", line 116, in __init__
 self._add_installed_apps_translations()
 File "C:\Python27\lib\site-
 packages\django\utils\translation\trans_real.py", line 164, in
 _add_installed_apps_translations "The translation infrastructure cannot be
 initialized before the " \nAppRegistryNotReady: The translation
 infrastructure cannot be initialized before the apps registry is ready.
 Check that you don't make non-lazy gettext calls at import time.
 }}}

 It looks very simmilar to
 https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg
 /django-users/jk_BrQY_S5c/1cWN6KF9qNIJ although I use wsgi_isapi rather
 then fastcgi. Calling setup like https://github.com/aleksandra-
 
tarkowska/openmicroscopy/blob/iss_deploy_improvement/components/tools/OmeroPy/src/omero_web_iis.py
 cause IIS error

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

Re: [Django] #25800: IIS ISAPI request throws AppRegistryNotReady: Apps aren't loaded yet.

[Django]

#25800: IIS ISAPI request throws AppRegistryNotReady: Apps aren't loaded yet.
---+--
 Reporter:  atarkowska |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  HTTP handling  |  Version:  1.8
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by aaugustin):

 To expand on what Tim just said -- your deployment probably bypasses the
 official APIs for running Django on a WSGI server. As a consequence, in
 Django ≥ 1.7, `django.setup()` isn't called and you're seeing this
 exception.

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

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

Re: [Django] #25663: `LinearRing` and `LineString` don't check number of points during instantiation

[Django]

#25663: `LinearRing` and `LineString` don't check number of points during
instantiation
-+-
 Reporter:  sir-sigurd   |Owner:  sir-
 Type:   |  sigurd
  Cleanup/optimization   |   Status:  new
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

 * stage:  Accepted => Ready for checkin


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

Re: [Django] #18392: Use utf8mb4 encoding with MySQL 5.5

[Django]

#18392: Use utf8mb4 encoding with MySQL 5.5
-+-
 Reporter:  EmilStenstrom|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  utf8mb4 mysql| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 Thanks Collin, in that case your proposal makes more sense to me. It could
 be nice to get a consensus from more MySQL users though.

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

Re: [Django] #25795: formfield_for_foreignkey() and limit_choices_to() dont work as expected

[Django]

#25795: formfield_for_foreignkey() and limit_choices_to() dont work as expected
---+--
 Reporter:  olivierpons|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Uncategorized  |  Version:  1.8
 Severity:  Normal |   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 timgraham):

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


Comment:

 Duplicate of #23595

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

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

Re: [Django] #18392: Use utf8mb4 encoding with MySQL 5.5

[Django]

#18392: Use utf8mb4 encoding with MySQL 5.5
-+-
 Reporter:  EmilStenstrom|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  utf8mb4 mysql| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by collinanderson):

 I'm not thinking of limiting the _name_ of the index. The issue is "the
 maximum number of characters that can be indexed".

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

Re: [Django] #25800: IIS ISAPI request throws AppRegistryNotReady: Apps aren't loaded yet.

[Django]

#25800: IIS ISAPI request throws AppRegistryNotReady: Apps aren't loaded yet.
---+--
 Reporter:  atarkowska |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  HTTP handling  |  Version:  1.8
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by timgraham):

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


Comment:

 Please see the
 [https://docs.djangoproject.com/en/stable/ref/applications/#troubleshooting
 Troubleshooting guide] which describes reasons why you would hit
 `AppRegistryNotReady`. As with #25607, please use our support channels at
 TicketClosingReasons/UseSupportChannels as the report doesn't demonstrate
 that Django is at fault. Thanks!

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

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

[Django] #25800: IIS ISAPI request throws AppRegistryNotReady: Apps aren't loaded yet.

[Django]

#25800: IIS ISAPI request throws AppRegistryNotReady: Apps aren't loaded yet.
---+
 Reporter:  atarkowska |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  HTTP handling  |Version:  1.8
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 After deep investigation of why IIS throws ''A server error occurred.
 Please contact the administrator.`'' looks like

 {{{

 url(r'^render_template/', views.render_template, name="render_template"),


 def render_template(request):
 try:
 logger.error("test template iis")
 context = {'foo': 'template'}
 t = template_loader.get_template('webclient/test.html')
 c = RequestContext(request, context)
 return HttpResponse(t.render(c))
 except:
 logger.error(traceback.format_exc())
 return HttpResponse(traceback.format_exc())
 }}}

 throws

 {{{
 Traceback (most recent call last): File
 "C:\OMERO.server\lib\python\omeroweb\webclient\views.py", line 36, in
 render_template t = template_loader.get_template('webclient/test.html')
 File "C:\Python27\lib\site-packages\django\template\loader.py", line 35,
 in get_template return engine.get_template(template_name, dirs) File
 "C:\Python27\lib\site-packages\django\template\backends\django.py", line
 30, in get_template return
 Template(self.engine.get_template(template_name, dirs)) File
 "C:\Python27\lib\site-packages\django\template\engine.py", line 167, in
 get_template template, origin = self.find_template(template_name, dirs)
 File "C:\Python27\lib\site-packages\django\template\engine.py", line 141,
 in find_template source, display_name = loader(name, dirs) File
 "C:\Python27\lib\site-packages\django\template\loaders\base.py", line 13,
 in __call__ return self.load_template(template_name, template_dirs) File
 "C:\Python27\lib\site-packages\django\template\loaders\base.py", line 17,
 in load_template template_name, template_dirs) File "C:\Python27\lib\site-
 packages\django\template\loaders\app_directories.py", line 36, in
 load_template_source for filepath in
 self.get_template_sources(template_name, template_dirs): File
 "C:\Python27\lib\site-
 packages\django\template\loaders\app_directories.py", line 26, in
 get_template_sources template_dirs = get_app_template_dirs('templates')
 File "C:\Python27\lib\site-packages\django\utils\lru_cache.py", line 125,
 in wrapper result = user_function(*args, **kwds) File "C:\Python27\lib
 \site-packages\django\template\utils.py", line 122, in
 get_app_template_dirs for app_config in apps.get_app_configs(): File
 "C:\Python27\lib\site-packages\django\apps\registry.py", line 137, in
 get_app_configs self.check_apps_ready() File "C:\Python27\lib\site-
 packages\django\apps\registry.py", line 124, in check_apps_ready raise
 AppRegistryNotReady("Apps aren't loaded yet.") AppRegistryNotReady: Apps
 aren't loaded yet.
 }}}

 Note above error appear only with IIS response rendering template, plain
 HttpResponse("string") or JsonResponse, HttpResponseRedirect works as
 expected.

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

Re: [Django] #24931: 404 error for "Views by namespace admin" at Admin Docs

[Django]

#24931: 404 error for "Views by namespace admin" at Admin Docs
---+--
 Reporter:  girishkumarkh  |Owner:  benmcnelly
 Type:  Bug|   Status:  assigned
Component:  contrib.admindocs  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  Admin, AdminDocs   | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by lordscales91):

 I think I've spotted where the issue comes from. When you use namespaced
 urls on your ROOT_URL_CONF you will have RegexURLResolver instances in
 your patterns, but the _callback_strs are not properly added, maybe it's
 better to show you a snippet from the actual code on
 django.core.urlresolvers at version 1.8.4 (I added the comment at the end)


 {{{
 if isinstance(pattern, RegexURLResolver):
 if pattern.namespace:
 namespaces[pattern.namespace] = (p_pattern, pattern)
 if pattern.app_name:
 apps.setdefault(pattern.app_name,
 []).append(pattern.namespace)
 else:
 parent_pat = pattern.regex.pattern
 for name in pattern.reverse_dict:
 for matches, pat, defaults in
 pattern.reverse_dict.getlist(name):
 new_matches = normalize(parent_pat + pat)
 lookups.appendlist(
 name,
 (
 new_matches,
 p_pattern + pat,
 dict(defaults,
 **pattern.default_kwargs),
 )
 )
 for namespace, (prefix, sub_pattern) in
 pattern.namespace_dict.items():
 namespaces[namespace] = (p_pattern + prefix,
 sub_pattern)
 for app_name, namespace_list in
 pattern.app_dict.items():
 apps.setdefault(app_name,
 []).extend(namespace_list)
 self._callback_strs.update(pattern._callback_strs) #
 This should be done even if a namespace is specified I 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/071.6eee11436baa47b77c4d23b25234ebaf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #18392: Use utf8mb4 encoding with MySQL 5.5

[Django]

#18392: Use utf8mb4 encoding with MySQL 5.5
-+-
 Reporter:  EmilStenstrom|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  utf8mb4 mysql| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 In case it's not clear, here's the problematic scenario I see:

 * Indexes are created with max index name length=191 and truncated
 accordingly.
 * Developer increases max index name length setting to 200 (no changes to
 index names in the database).
 * Now migrations can't operate on existing indexes because the 200
 character index names it generates aren't what's in the database.

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

Re: [Django] #7975: Admin inlines incorrectly report "this field is required" if inline model has field with default value

[Django]

#7975: Admin inlines incorrectly report "this field is required" if inline model
has field with default value
---+
 Reporter:  russellm   |Owner:  brosner
 Type:  Uncategorized  |   Status:  closed
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords:  1.0-blocker| Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timgraham):

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


Comment:

 This ticket has been closed for 7 years. Please open a new report with
 more details to reproduce (a sample project is nice if possible). I
 couldn't reproduce a problem with what you provided in your comment.
 Thanks!

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

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

Re: [Django] #25799: list_filter filtering by groups doesn't appear until at least two groups exist (was: Filtering by groups does not appear until at least two groups exist)

[Django]

#25799: list_filter filtering by groups doesn't appear until at least two groups
exist
-+-
 Reporter:  mitar|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 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 timgraham):

 * status:  new => closed
 * needs_better_patch:   => 0
 * resolution:   => fixed
 * needs_tests:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Cleanup/optimization


Comment:

 This is fixed in Django 1.9 by 8f30556329b64005d63b66859a74752a0b261315.

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

Re: [Django] #25797: error when using GeoManager.distance on fields with SRID 32140 with no GDAL

[Django]

#25797: error when using GeoManager.distance on fields with SRID 32140 with no 
GDAL
+--
 Reporter:  sir-sigurd  |Owner:  sir-sigurd
 Type:  Bug |   Status:  assigned
Component:  GIS |  Version:  1.8
 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 timgraham):

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

Re: [Django] #25617: Disallow usernames that differ only in case in UserCreationForm

[Django]

#25617: Disallow usernames that differ only in case in UserCreationForm
--+
 Reporter:  timgraham |Owner:  nmundar
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  contrib.auth  |  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 nmundar):

 * needs_better_patch:  1 => 0


Comment:

 It's fixed now, stupid mistake. Previous form data that I've used didn't
 trigger password length validation.

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

Re: [Django] #25796: annotate() exception if there are same fields name OR in Q

[Django]

#25796: annotate() exception if there are same fields name OR in Q
-+-
 Reporter:  Falldog  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  annotate | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by jarshwah):

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


Comment:

 The problem here is that you're combining two filters together that can't
 logically be grouped together. You've got half of a "HAVING" clause and
 half of a "WHERE" clause and you're trying to OR them together. This can't
 work.

 This would work (Maybe you should split these two filter clause):

 query.filter(commodity_count=0, Q(name__isnull=False) |
 Q(subshipment_set__name__isnull=False))
 # or maybe..
 query.filter(commodity_count=0).filter(Q(name__isnull=False) |
 Q(subshipment_set__name__isnull=False))

 But I'm not really sure what you're trying to **do** with your query. Do
 you perhaps want to do the name is null checking *before* the Count?
 Adding the filtering after the annotation always filters after the result
 of annotating. These are different:

 {{{
 Shipment.objects
 .annotate(commodity_count=Count('commodity_set'))
 .filter(name__isnull=False)

 # different!
 Shipment.objects
 .filter(name__isnull=False)
 .annotate(commodity_count=Count('commodity_set'))
 }}}

 The first will do the count, and then will remove any with null. The
 second will remove any with null and *then* do a count, which is important
 when you're trying to filter on the result of the count.

 This is *probably* the query you want:

 {{{

 Shipment.objects
 .filter(Q(name__isnull=False) | Q(subshipment__name__isnull=False)) #
 WHERE CLAUSE
 .annotate(commodity_count=Count('commodity_set'))  # count excludes
 null names
 .filter(commodity_count=0)  # inserts HAVING CLAUSE

 }}}

 Closing this as invalid because you can't combine aggregate filters with
 regular filters, but please reopen if I've misinterpreted your query.

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

Re: [Django] #25791: Implement autoreload behaviour for cached template loader

[Django]

#25791: Implement autoreload behaviour for cached template loader
-+-
 Reporter:  jaap3|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  autoreload   | Triage Stage:
  templates cached loader|  Someday/Maybe
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jaap3):

 I think the issue you mention about template precedence is solvable, how
 does Jinja2 handle these cases? Jinja2's engine enables auto_reload if
 DEBUG is true (and a cache is set) so I'm assuming it will be turned on in
 development in many cases.

 Since template (origin) invalidation is the responsibility of the loader
 (in both our implementations) it should (probably?) be possible to
 implement an is_stale/uptodate function that checks if the template is
 superseded.

 Regarding loader configuration in the Engine options. The Jina2 engine
 passes all it's arguments into an Environment
 (http://jinja.pocoo.org/docs/dev/api/#jinja2.Environment) that is used by
 Jinja2's internals to configure all sorts of things. Django doesn't have
 the concept of an environment, but the engine is used in a similar way (in
 fact this commit
 
https://github.com/django/django/commit/29a977ab143f549c8849e9f08ca5800830eaaabb
 #diff-2ec90d8b6d7f44124689729e42876209 specifically mentions that template
 loaders can look up configuration on the engine.

 But, this isn't so much about configuring loaders as it is about making
 template caching a more prominent feature of the Django template engine.
 That template caching is currently possible by way of a quasi template
 loader is an implementation detail.

 I'll try to write up something for the developers mailinglist today to get
 some more input.

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

[Django] #25799: Filtering by groups does not appear until at least two groups exist

[Django]

#25799: Filtering by groups does not appear until at least two groups exist
---+
 Reporter:  mitar  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  contrib.admin  |Version:  1.8
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I noticed that filtering by groups in users list does not appear until at
 least two groups exist in the system. This is problematic because I cannot
 then filter users which are in my one group vs. which are not.

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

Re: [Django] #7975: Admin inlines incorrectly report "this field is required" if inline model has field with default value

[Django]

#7975: Admin inlines incorrectly report "this field is required" if inline model
has field with default value
---+
 Reporter:  russellm   |Owner:  brosner
 Type:  Uncategorized  |   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  1.0-blocker| Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Zopieux):

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


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

Re: [Django] #20468: loaddata - during import exclude some applications

[Django]

#20468: loaddata - during import exclude some applications
-+-
 Reporter:  fizista  |Owner:
 |  alexmorozov
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by alexmorozov):

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


Comment:

 Seems useful. Recently I've faced a similar problem. Will give it a try.

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