date:20150911

Re: [Django] #24743: Django 1.8.1 migrations are actually slower than 1.8?

2015-09-11 Thread Django

#24743: Django 1.8.1 migrations are actually slower than 1.8?
--+
 Reporter:  pzrq  |Owner:  MarkusH
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Migrations|  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by MarkusH):

 Replying to [comment:27 prophile]:
 > For what it's worth, this patch greatly improved model state rendering
 for us:
 >
 > {{{
 > diff -r /tmp/saved-django/db/migrations/executor.py
 contrib/django/db/migrations/executor.py
 > 99,100d98
 > < if 'apps' not in state.__dict__:
 > < state.apps  # Render all real_apps -- performance
 critical
 > }}}
 Not really, it just delays the rendering.

 The `Rendering model state` will be faster, yes. But instead of rendering
 the models there, Django will render them when applying the migrations. At
 that phase it might even look like migrations are stuck.

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

Re: [Django] #25384: New Migrations Generated with Improperly Sorted Imports

2015-09-11 Thread Django

#25384: New Migrations Generated with Improperly Sorted Imports
--+
 Reporter:  jambonrose|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  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:  1 |UI/UX:  0
--+
Changes (by MarkusH):

 * has_patch:  0 => 1


Old description:

> New migration files are generated with the following line of code (found
> in the `django/db/migrations/writer.py` file):
>
> from django.db import models, migrations
>
> Anytime [https://pypi.python.org/pypi/isort isort] is run on a migration
> file (for example, for data migrations), it will reorder the import to:
>
> from django.db import migrations, models
>
> It would be great if we were generating properly sorted documents.

New description:

 New migration files are generated with the following line of code (found
 in the `django/db/migrations/writer.py` file):
 {{{
 from django.db import models, migrations
 }}}
 Anytime [https://pypi.python.org/pypi/isort isort] is run on a migration
 file (for example, for data migrations), it will reorder the import to:
 {{{
 from django.db import migrations, models
 }}}
 It would be great if we were generating properly sorted documents.

--

Comment:

 PR: https://github.com/django/django/pull/5274

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

Re: [Django] #25384: New Migrations Generated with Improperly Sorted Imports

2015-09-11 Thread Django

#25384: New Migrations Generated with Improperly Sorted Imports
--+
 Reporter:  jambonrose|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by MarkusH):

 * status:  closed => new
 * resolution:  duplicate =>
 * stage:  Unreviewed => Accepted


Comment:

 As briefly discussed on IRC the other day, I add a patch for 1.8 to change
 the order of those two imports. It's annoying to change the order
 manually.

 The issue is indeed fixed on 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.bc6f94e6e8645d1e9221119823579fe2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24919: Add an option not to run migrations when running tests

2015-09-11 Thread Django

Comment (by MarkusH):

Replying to [comment:11 timgraham]:
> Added some ideas for improvement to the PR.
>
> As I mentioned in IRC, it could also be useful to allow the
`DATABASES['TEST']['MIGRATE'] = False` option that Andrew's first PR
suggested to be a shortcut for setting `MIGRATION_MODULES = {'a': None,
'b': None', ...}` for all apps. This could be done later or in a separate
commit though. The main concern I have with this idea is whether or not it
makes sense in a multi-db situation.

I created #25388 to keep track of this proposal if somebody wants to work
on 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/068.b9750b318d8112ac3736f719c0e8334a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #25388: Allow disabling of all migrations during tests

2015-09-11 Thread Django

#25388: Allow disabling of all migrations during tests
-+
   Reporter:  MarkusH|  Owner:  nobody
   Type:  New feature| Status:  new
  Component:  Testing framework  |Version:  master
   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  |
-+
 As an extension to #24919 a setting `DATABASE['TEST']['MIGRATE'] = False`
 should disable all migrations on that particular database. This can be
 done by hooking into
 `django.db.migrations.loader.MigrationLoader.migrations_module()` and
 returning `None`.

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

Re: [Django] #24919: Add an option not to run migrations when running tests

2015-09-11 Thread Django

#24919: Add an option not to run migrations when running tests
-+-
 Reporter:  kairichard   |Owner:  andrewgodwin
 Type:  New feature  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  1.9  | 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 Markus Holtermann ):

 In [changeset:"f45ee1974696c8fc17ccfe12ef9e4188e29543a2" f45ee197]:
 {{{
 #!CommitTicketReference repository=""
 revision="f45ee1974696c8fc17ccfe12ef9e4188e29543a2"
 Refs #24919 -- Raised more helpful error message for disabled migrations
 }}}

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

Re: [Django] #24919: Add an option not to run migrations when running tests

2015-09-11 Thread Django

#24919: Add an option not to run migrations when running tests
-+-
 Reporter:  kairichard   |Owner:  andrewgodwin
 Type:  New feature  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  1.9  | 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 Markus Holtermann ):

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


Comment:

 In [changeset:"a3c01b0dd8060f00a5ffd2589a776b4f618af6d9" a3c01b0]:
 {{{
 #!CommitTicketReference repository=""
 revision="a3c01b0dd8060f00a5ffd2589a776b4f618af6d9"
 Fixed #24919 -- Allowed disabling of migrations on a per app basis
 }}}

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

Re: [Django] #25373: Add logging for {% include %} exceptions when template.debug = False

2015-09-11 Thread Django

#25373: Add logging for {% include %} exceptions when template.debug = False
-+
Reporter: limnick |Owner: limnick
Type: New feature | Status: assigned
Component: Template system | 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
-+

Comment (by limnick):

After some further digging it appears the django.template logger added in
the commit I originally referenced will capture exceptions bubbled through
this function, however it will also catch things like missing variables in
templates and expected fallthrough behavior. All of this is at a level of
DEBUG which seems appropriate.

In order to be able to log only unexpected exceptions, I'm proposing
adding WARNING level logging to any uncaught exceptions during import
templatetag rendering. See attached patch for changes and regression test.

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

Re: [Django] #25373: Add logging for {% include %} exceptions when template.debug = False

2015-09-11 Thread Django

#25373: Add logging for {% include %} exceptions when template.debug = False
-+
 Reporter:  limnick  |Owner:  limnick
 Type:  New feature  |   Status:  assigned
Component:  Template system  |  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 limnick):

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

Re: [Django] #25373: Add logging for {% include %} exceptions when template.debug = False

2015-09-11 Thread Django

#25373: Add logging for {% include %} exceptions when template.debug = False
-+
 Reporter:  limnick  |Owner:  limnick
 Type:  New feature  |   Status:  assigned
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 limnick):

 * Attachment "template_import_logging.diff" 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.fe43a2dde8bb465e42b89554d9841a0a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25373: Add logging for {% include %} exceptions when template.debug = False

2015-09-11 Thread Django

#25373: Add logging for {% include %} exceptions when template.debug = False
-+
 Reporter:  limnick  |Owner:  limnick
 Type:  New feature  |   Status:  assigned
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 limnick):

 * owner:   => limnick
 * 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/065.2020d901082a845a7761885c56aa1245%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25386: Unclear documentation for default debug setting for DjangoTemplates engine

2015-09-11 Thread Django

#25386: Unclear documentation for default debug setting for DjangoTemplates 
engine
-+-
 Reporter:  lightstrike  |Owner:  dhanus
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  template, template   | Triage Stage:
  engine |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by dhanus):

 * status:  new => assigned
 * owner:  lightstrike => dhanus


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

Re: [Django] #25203: Document changes to WSGI application loading sequence in 1.7

2015-09-11 Thread Django

#25203: Document changes to WSGI application loading sequence in 1.7
-+-
 Reporter:  yscumc   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.7
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  wsgi setup   | Triage Stage:  Accepted
  application loading|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by carljm):

 Commented on the PR here:
 
https://github.com/django/django/commit/47016d4322574860f90431e1c87d19f7a1f778c6#commitcomment-13192876

 I'm not convinced this is a technique that the Django documentation should
 promote.

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

[Django] #25387: ModelAdmin actions don't get access to the ActionForm

2015-09-11 Thread Django

#25387: ModelAdmin actions don't get access to the ActionForm
---+
 Reporter:  mbox   |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  contrib.admin  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Setting an alternative ModelAdmin.action_form is supported, but
 ModelAdmin.actions don't get access to the form.

 The naive approach is to rebind the form in the action:

 {{{
 class ExampleAdmin(admin.ModelAdmin):
  action_form = ExampleForm
  actions = ['example_action']

  def example_action(self, request, queryset):
  form = ExampleForm(request.POST)
  if form.is_valid():
  # Process...
 }}}

 However, this doesn't work (`form.is_valid()` returns False) because
 there's special processing done on the `request.DATA` before the form is
 bound - see
 
https://github.com/django/django/blob/master/django/contrib/admin/options.py#L1205-L1220

 So either this code has to be duplicated in the action, or the
 `request.POST` data processed manually. Neither seem ideal.

 A proposed fix would be to make the action_form that's bound in options.py
 be available as `self.bound_action_form` so that actions could access it.
 This would be entirely backwards-compatible.

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

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

Re: [Django] #25378: Admin flat theme needs :focus styling on buttons for tab through

2015-09-11 Thread Django

#25378: Admin flat theme needs :focus styling on buttons for tab through
-+-
 Reporter:  ryangallen   |Owner:
 Type:   |  ryangallen
  Cleanup/optimization   |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  1.9  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-

Comment (by ryangallen):

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

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

Re: [Django] #25378: Admin flat theme needs :focus styling on buttons for tab through

2015-09-11 Thread Django

#25378: Admin flat theme needs :focus styling on buttons for tab through
-+-
 Reporter:  ryangallen   |Owner:
 Type:   |  ryangallen
  Cleanup/optimization   |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  1.9  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by ryangallen):

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

Re: [Django] #22932: "makemigrations" generates circular dependencies

2015-09-11 Thread Django

#22932: "makemigrations" generates circular dependencies
-+-
 Reporter:  humitos  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  circular | Triage Stage:
  dependency, migrations,|  Unreviewed
  makemigrations |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by berto):

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

Re: [Django] #22932: "makemigrations" generates circular dependencies

2015-09-11 Thread Django

Comment (by berto):

I am running into this error when squashing migrations. The swappable dep
is from Django REST Framework's `authkey` app. After reading the fix
above I'm not exactly sure how to go about fixing this within a squashed
migration.

When running the squashed migration it tells me that the `authkey` tables
do not exist. When adding `('authkey', '0001_initial')` to the
dependencies list, I get the circular dependency error.

I'm seeing this when running tests, and I'm using Django 1.7.10.

Any clues? Thank you!

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

Re: [Django] #24765: Calling flatten on a Context object fails in some cases

2015-09-11 Thread Django

#24765: Calling flatten on a Context object fails in some cases
-+
 Reporter:  poirier  |Owner:  BuddyL
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"ec704371e301c5450dd5fc012a30424a8f47b99b" ec70437]:
 {{{
 #!CommitTicketReference repository=""
 revision="ec704371e301c5450dd5fc012a30424a8f47b99b"
 Fixed #24765 -- Allowed template context updates to flatten a Context.
 }}}

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

Re: [Django] #25381: "default_app_config" causes custom commands to not be found

2015-09-11 Thread Django

#25381: "default_app_config" causes custom commands to not be found
-+-
 Reporter:  thebritican  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  1.8
  commands)  |
 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 Tim Graham ):

 In [changeset:"e7e8d30cae9457339eb49ae8584e82ff0a038e99" e7e8d30]:
 {{{
 #!CommitTicketReference repository=""
 revision="e7e8d30cae9457339eb49ae8584e82ff0a038e99"
 Refs #25381 -- Clarified that AppConfig model methods search only the
 current app.
 }}}

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

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

Re: [Django] #25381: "default_app_config" causes custom commands to not be found

2015-09-11 Thread Django

#25381: "default_app_config" causes custom commands to not be found
-+-
 Reporter:  thebritican  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  1.8
  commands)  |
 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 Tim Graham ):

 In [changeset:"95c00c40ae62c4e723a3498722ab3a0921aa46e5" 95c00c4]:
 {{{
 #!CommitTicketReference repository=""
 revision="95c00c40ae62c4e723a3498722ab3a0921aa46e5"
 [1.8.x] Refs #25381 -- Clarified that AppConfig model methods search only
 the current app.

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

Re: [Django] #25386: Unclear documentation for default debug setting for DjangoTemplates engine

2015-09-11 Thread Django

#25386: Unclear documentation for default debug setting for DjangoTemplates 
engine
-+-
 Reporter:  lightstrike  |Owner:
 Type:   |  lightstrike
  Cleanup/optimization   |   Status:  new
Component:  Documentation|  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  template, template   | Triage Stage:
  engine |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 The default value for `DjangoTemplates` is
 
[https://docs.djangoproject.com/en/dev/topics/templates/#django.template.backends.django.DjangoTemplates
 documented elsewhere] from the places you linked. I think those other
 places are correct, but please clarify if you believe otherwise.

 I'll propose this patch to address your last point:
 {{{#!diff
 diff --git a/docs/ref/settings.txt b/docs/ref/settings.txt
 index f4e5c37..d2582c6 100644
 --- a/docs/ref/settings.txt
 +++ b/docs/ref/settings.txt
 @@ -2324,7 +2324,10 @@ OPTIONS
  Default: ``{}`` (Empty dict)

  Extra parameters to pass to the template backend. Available parameters
 vary
 -depending on the template backend.
 +depending on the template backend. See
 +:class:`~django.template.backends.django.DjangoTemplates` and
 +:class:`~django.template.backends.jinja2.Jinja2` for the options of the
 +built-in backends.

  .. setting:: TEMPLATE_CONTEXT_PROCESSORS

 }}}

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

Re: [Django] #25203: Document changes to WSGI application loading sequence in 1.7

2015-09-11 Thread Django

#25203: Document changes to WSGI application loading sequence in 1.7
-+-
 Reporter:  yscumc   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.7
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  wsgi setup   | Triage Stage:  Accepted
  application loading|
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:"c8773493b62083b9ca5476a6040737f5cca79944" c877349]:
 {{{
 #!CommitTicketReference repository=""
 revision="c8773493b62083b9ca5476a6040737f5cca79944"
 [1.8.x] Fixed #25203 -- Documented how to pass Apache environment
 variables to Django.

 Backport of 47016d4322574860f90431e1c87d19f7a1f778c6 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.403eeeca7fabdd45ee19230dc1d59988%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25203: Document changes to WSGI application loading sequence in 1.7

2015-09-11 Thread Django

#25203: Document changes to WSGI application loading sequence in 1.7
-+-
 Reporter:  yscumc   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.7
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  wsgi setup   | Triage Stage:  Accepted
  application loading|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"47016d4322574860f90431e1c87d19f7a1f778c6" 47016d4]:
 {{{
 #!CommitTicketReference repository=""
 revision="47016d4322574860f90431e1c87d19f7a1f778c6"
 Fixed #25203 -- Documented how to pass Apache environment variables to
 Django.
 }}}

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

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

[Django] #25386: Unclear documentation for default debug setting for DjangoTemplates engine

2015-09-11 Thread Django

#25386: Unclear documentation for default debug setting for DjangoTemplates
engine
-+-
Reporter: lightstrike | Owner: lightstrike
Type: | Status: new
Cleanup/optimization |
Component: Documentation|Version: 1.8
Severity: Normal | Keywords: template, template
| engine
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 1| UI/UX: 0
-+-
In 1.8, the TEMPLATE_DEBUG setting is deprecated in favor of setting
'debug' as part of the OPTIONS sub-setting in a backend in TEMPLATES.

In a couple parts of the documentation, it is stated that the default
'debug' setting for DjangoTemplates engine is False:

* [https://docs.djangoproject.com/en/dev/ref/templates/api/#configuring-
an-engine Template API]
* [https://docs.djangoproject.com/en/1.8/ref/settings/#template-debug
Settings:TEMPLATE_DEBUG]

In reality, the default is

[https://github.com/django/django/blob/aaacaeb0963c406c4fe6f68c6ae51f4a65878250/django/template/backends/django.py#L28
apparently set according to settings.DEBUG].

I suggest clarifying the documentation to state that the default debug
setting is equal to settings.DEBUG (which is True by default). It would be
additionally helpful to link to the possible options one can set in a
template engine on the
[https://docs.djangoproject.com/en/1.8/ref/settings/#std:setting-
TEMPLATES-OPTIONS main settings page].

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

Re: [Django] #23794: FieldDoesNotExist error in migration with deleted fields and unique_together constraint

2015-09-11 Thread Django

#23794: FieldDoesNotExist error in migration with deleted fields and
unique_together constraint
-+-
 Reporter:  heybuddy |Owner:  trg
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  migration| Triage Stage:  Accepted
  unique_together removefield|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by berto:

Old description:

> I had a model that had a ForeignKey field and a unique_together
> constraint involving that field. I deleted both the field and the
> unique_together constraint in my model and ran makemigrations. The
> migration created RemoveField operation and a AlterUniqueTogether
> operation with unique_together=set([]). When I tried to run the
> migration, a django.db.models.fields.FieldDoesNotExist exception occured.
> I edited the migration manually to put the AlterUniqueTogether operation
> before the RemoveField operation and then the migration worked.

New description:

 I had a model that had a ForeignKey field and a unique_together constraint
 involving that field. I deleted both the field and the unique_together
 constraint in my model and ran makemigrations. The migration created
 RemoveField operation and a AlterUniqueTogether operation with
 unique_together=set([]). When I tried to run the migration, a
 django.db.models.fields.FieldDoesNotExist exception occured. I edited the
 migration manually to put the AlterUniqueTogether operation before the
 RemoveField operation and then the migration worked.

 NOTE: After upgrading, you must remove the bad migration file and re-run
 `makemigrations` or manually move the `AlterUniqueTogether` operation
 manually as stated above; i.e. upgrading does not fix the existing
 migration.

--

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

Re: [Django] #25381: "default_app_config" causes custom commands to not be found

2015-09-11 Thread Django

#25381: "default_app_config" causes custom commands to not be found
-+-
 Reporter:  thebritican  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  1.8
  commands)  |
 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 thebritican):

 Replying to [comment:4 timgraham]:
 > Okay, but that doesn't look like a bug in Django. Please see
 TicketClosingReasons/UseSupportChannels for ways to get help.
 >
 > I will however propose a documentation patch which might help you
 understand why things aren't working as you expect.
 > {{{#!diff
 > diff --git a/docs/ref/applications.txt b/docs/ref/applications.txt
 > index eb3cc6f..d634e73 100644
 > --- a/docs/ref/applications.txt
 > +++ b/docs/ref/applications.txt
 > @@ -204,13 +204,14 @@ Methods
 >
 >  .. method:: AppConfig.get_models()
 >
 > -Returns an iterable of :class:`~django.db.models.Model` classes.
 > +Returns an iterable of :class:`~django.db.models.Model` classes for
 this
 > +application.
 >
 >  .. method:: AppConfig.get_model(model_name)
 >
 >  Returns the :class:`~django.db.models.Model` with the given
 > -``model_name``. Raises :exc:`LookupError` if no such model exists.
 > -``model_name`` is case-insensitive.
 > +``model_name``. Raises :exc:`LookupError` if no such model exists
 in this
 > +application. ``model_name`` is case-insensitive.
 >
 >  .. method:: AppConfig.ready()
 >
 > }}}

 Thank you, I ended up moving the AppConfig over to the other package and
 listed it in INSTALLED_APPS, resolving my issue. The documentation change
 does help clarify the issue.

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

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

Re: [Django] #25385: Allow importing django.views.generic.View from django.views.View (was: Import of Views)

2015-09-11 Thread Django

#25385: Allow importing django.views.generic.View from django.views.View
-+-
 Reporter:  jambonrose   |Owner:
 Type:   |  jambonrose
  Cleanup/optimization   |   Status:  new
Component:  Generic views|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * component:  Core (URLs) => Generic views


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

Re: [Django] #25385: Import of Views

2015-09-11 Thread Django

#25385: Import of Views
-+-
 Reporter:  jambonrose   |Owner:
 Type:   |  jambonrose
  Cleanup/optimization   |   Status:  new
Component:  Core (URLs)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Have you discussed the idea with anyone? If not, could you please raise it
 on the DevelopersMailingList to see if there are any objections?

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

Re: [Django] #25203: Document changes to WSGI application loading sequence in 1.7

2015-09-11 Thread Django

#25203: Document changes to WSGI application loading sequence in 1.7
-+-
 Reporter:  yscumc   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  wsgi setup   | Triage Stage:  Accepted
  application loading|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by paulrentschler):

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

Re: [Django] #24919: Add an option not to run migrations when running tests

2015-09-11 Thread Django

#24919: Add an option not to run migrations when running tests
-+-
 Reporter:  kairichard   |Owner:  andrewgodwin
 Type:  New feature  |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  1.9  | 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):

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

Re: [Django] #25203: Document changes to WSGI application loading sequence in 1.7

2015-09-11 Thread Django

Comment (by paulrentschler):

I ran into this problem as well and created a pull request
(https://github.com/django/django/pull/5271) to address the issue.
Although I realize I didn't address the original submitter's request for
documentation about how wsgi loading is handled, I did provide changes to
the documentation at explains and provides a working solution that is also
backwards compatible for doing what the original submitter was trying to
do along with showing how to pass arbitrary variables from the Apache
configuration to Django.

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

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

[Django] #25385: Import of Views

2015-09-11 Thread Django

#25385: Import of Views
--+
 Reporter:  jambonrose|  Owner:  jambonrose
 Type:  Cleanup/optimization  | Status:  new
Component:  Core (URLs)   |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Whenever I talk about class-based views and how their concept is separate
 from generic views (typically in a class setting), the question I am asked
 is invariably: if they are different, why do we import `View` from
 `django.views.generic`?

 To help developers better avoid confusion and better separate the
 concepts, I would like to change the import of the `View` class. Ideally:

 from django.views import View

 I would furthermore like to move `View` from the generic directory into
 it's own module.

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

Re: [Django] #25381: "default_app_config" causes custom commands to not be found

2015-09-11 Thread Django

#25381: "default_app_config" causes custom commands to not be found
-+-
 Reporter:  thebritican  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  1.8
  commands)  |
 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 timgraham):

 Okay, but that doesn't look like a bug in Django. Please see
 TicketClosingReasons/UseSupportChannels for ways to get help.

 I will however propose a documentation patch which might help you
 understand why things aren't working as you expect.
 {{{#!diff
 diff --git a/docs/ref/applications.txt b/docs/ref/applications.txt
 index eb3cc6f..d634e73 100644
 --- a/docs/ref/applications.txt
 +++ b/docs/ref/applications.txt
 @@ -204,13 +204,14 @@ Methods

  .. method:: AppConfig.get_models()

 -Returns an iterable of :class:`~django.db.models.Model` classes.
 +Returns an iterable of :class:`~django.db.models.Model` classes for
 this
 +application.

  .. method:: AppConfig.get_model(model_name)

  Returns the :class:`~django.db.models.Model` with the given
 -``model_name``. Raises :exc:`LookupError` if no such model exists.
 -``model_name`` is case-insensitive.
 +``model_name``. Raises :exc:`LookupError` if no such model exists in
 this
 +application. ``model_name`` is case-insensitive.

  .. method:: AppConfig.ready()

 }}}

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

Re: [Django] #25382: Documentation makes reference to non-existent class.

2015-09-11 Thread Django

#25382: Documentation makes reference to non-existent class.
-+-
 Reporter:  jambonrose   |Owner:
 Type:   |  waynemerry
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"f328ebdede9e10779c1fb93d45f72dade7eda23f" f328ebd]:
 {{{
 #!CommitTicketReference repository=""
 revision="f328ebdede9e10779c1fb93d45f72dade7eda23f"
 [1.8.x] Fixed #25382 -- Removed obsolete references to DateQuerySet.

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

Re: [Django] #25382: Documentation makes reference to non-existent class.

2015-09-11 Thread Django

#25382: Documentation makes reference to non-existent class.
-+-
 Reporter:  jambonrose   |Owner:
 Type:   |  waynemerry
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"e3720b990a33ae259da4b1f1f6069aa6bbc8c03d" e3720b9]:
 {{{
 #!CommitTicketReference repository=""
 revision="e3720b990a33ae259da4b1f1f6069aa6bbc8c03d"
 Fixed #25382 -- Removed obsolete references to DateQuerySet.
 }}}

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

Re: [Django] #25381: "default_app_config" causes custom commands to not be found

2015-09-11 Thread Django

Comment (by thebritican):

Replying to [comment:1 timgraham]:
> It looks like you have set

[https://docs.djangoproject.com/en/stable/ref/applications/#django.apps.AppConfig.name
AppConfig.name] incorrectly. It [https://github.com/anovelmous-dev-

squad/anovelmous/blob/7239e33172eeb411462bfefdff92aa71576f0d48/anovelmous_app/apps.py#L9
points to 'api'] but the Python path for that app appears to be
'anovelmous_app'.

When I change the name property to "anovelmous_app", I receive a
LookupError.
LookupError: App 'anovelmous_app' doesn't have a 'Token' model.

I originally tried this setup to no avail, and it looked incorrect from
the start. I need access to a database model on initialization that is
defined in the api package. It works as expected when supplying "api" to
the name property, except when looking for django commands.

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

Re: [Django] #25381: "default_app_config" causes custom commands to not be found

2015-09-11 Thread Django

#25381: "default_app_config" causes custom commands to not be found
-+-
 Reporter:  thebritican  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  1.8
  commands)  |
 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
 * resolution:   => invalid


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

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

Re: [Django] #25200: Update admin's screenshots for new admin theme

2015-09-11 Thread Django

#25200: Update admin's screenshots for new admin theme
-+-
 Reporter:  timgraham|Owner:
 |  ryangallen
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  1.9  | 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 Tim Graham ):

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


Comment:

 In [changeset:"6e8ddbaa2563ad7b95f96fe757d08870d2312977" 6e8ddbaa]:
 {{{
 #!CommitTicketReference repository=""
 revision="6e8ddbaa2563ad7b95f96fe757d08870d2312977"
 Fixed #25200 -- Updated admin screenshots in 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/067.110acdbe0eccf7ed51396a3e06fe5bb8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25384: New Migrations Generated with Improperly Sorted Imports

2015-09-11 Thread Django

#25384: New Migrations Generated with Improperly Sorted Imports
-+-
 Reporter:  jambonrose   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Migrations   |  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:  1|UI/UX:  0
-+-
Changes (by timgraham):

 * resolution:  invalid => duplicate


Comment:

 (done in #24155)

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

Re: [Django] #25384: New Migrations Generated with Improperly Sorted Imports

2015-09-11 Thread Django

#25384: New Migrations Generated with Improperly Sorted Imports
-+-
 Reporter:  jambonrose   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Migrations   |  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:  1|UI/UX:  0
-+-
Changes (by jambonrose):

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


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

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

Re: [Django] #25384: New Migrations Generated with Improperly Sorted Imports

2015-09-11 Thread Django

#25384: New Migrations Generated with Improperly Sorted Imports
-+-
 Reporter:  jambonrose   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Migrations   |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by jambonrose):

 Argh. Collin is right. I was looking at this on the wrong branch. Very
 sorry.

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

Re: [Django] #25383: Trying to access the local server in HTTPS throw a 400 error

2015-09-11 Thread Django

#25383: Trying to access the local server in HTTPS throw a 400 error
-+-
 Reporter:  mlorant  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  HTTP handling|  Version:  1.7
 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/065.de9b90cd95dcdffada283a4e07e002a6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25384: New Migrations Generated with Improperly Sorted Imports

2015-09-11 Thread Django

#25384: New Migrations Generated with Improperly Sorted Imports
-+-
 Reporter:  jambonrose   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Migrations   |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by collinanderson):

 Hi, could you try this out on master (1.9)? I think it _may_ have been
 fixed already.

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

Re: [Django] #25384: New Migrations Generated with Improperly Sorted Imports

2015-09-11 Thread Django

#25384: New Migrations Generated with Improperly Sorted Imports
-+-
 Reporter:  jambonrose   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Migrations   |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by mlorant):

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


Old description:

> New migration files are generated with the following line of code (found
> in the `django/db/migrations/writer.py` file):
>
> from django.db import models, migrations
>
> Anytime [https://pypi.python.org/pypi/isort isort] is run on a migration
> file (for example, for data migrations), it will reorder the import to:
>
> from django.db import models, migrations
>
> It would be great if we were generating properly sorted documents.

New description:

 New migration files are generated with the following line of code (found
 in the `django/db/migrations/writer.py` file):

 from django.db import models, migrations

 Anytime [https://pypi.python.org/pypi/isort isort] is run on a migration
 file (for example, for data migrations), it will reorder the import to:

 from django.db import migrations, models

 It would be great if we were generating properly sorted documents.

--

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

[Django] #25384: New Migrations Generated with Improperly Sorted Imports

2015-09-11 Thread Django

#25384: New Migrations Generated with Improperly Sorted Imports
--+
 Reporter:  jambonrose|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Migrations|Version:  1.8
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 New migration files are generated with the following line of code (found
 in the `django/db/migrations/writer.py` file):

 from django.db import models, migrations

 Anytime [https://pypi.python.org/pypi/isort isort] is run on a migration
 file (for example, for data migrations), it will reorder the import to:

 from django.db import models, migrations

 It would be great if we were generating properly sorted documents.

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

Re: [Django] #25382: Documentation makes reference to non-existent class.

2015-09-11 Thread Django

#25382: Documentation makes reference to non-existent class.
-+-
 Reporter:  jambonrose   |Owner:
 Type:   |  waynemerry
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by waynemerry):

 * owner:  nobody => waynemerry
 * 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/068.89e24ab261997bbbda047d7f4d9aa90c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25383: Trying to access the local server in HTTPS throw a 400 error

2015-09-11 Thread Django

#25383: Trying to access the local server in HTTPS throw a 400 error
-+-
 Reporter:  mlorant  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  HTTP handling|  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by mlorant):

 I mistagged the ticket first, sorry. We are using Django 1.7, I did not
 try on Django 1.8 indeed.

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

Re: [Django] #25383: Trying to access the local server in HTTPS throw a 400 error

2015-09-11 Thread Django

#25383: Trying to access the local server in HTTPS throw a 400 error
-+-
 Reporter:  mlorant  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  HTTP handling|  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by mlorant):

 * version:  1.8 => 1.7


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

Re: [Django] #25383: Trying to access the local server in HTTPS throw a 400 error

2015-09-11 Thread Django

#25383: Trying to access the local server in HTTPS throw a 400 error
-+-
 Reporter:  mlorant  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  HTTP handling|  Version:  1.8
 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 collinanderson):

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


Comment:

 Interesting. There should be a friendly message from #23398. The friendly
 message works for me. You're using django 1.8?


 {{{
 You're accessing the development server over HTTPS, but it only supports
 HTTP.
 [11/Sep/2015 10:06:13] code 400, message Bad request syntax
 
('\x16\x03\x01\x00·\x01\x00\x00³\x03\x03³Ü\x8eñì\x87È\x11,hÛ=P\x80¦ËÚ\x9f\x81\'Or%?\x1afp\x883µ°Ý\x00\x00"À+À/\x00\x9eÌ\x14Ì\x13Ì\x15À')
 }}}

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

[Django] #25383: Trying to access the local server in HTTPS throw a 400 error

2015-09-11 Thread Django

#25383: Trying to access the local server in HTTPS throw a 400 error
--+
 Reporter:  mlorant   |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  HTTP handling |Version:  1.8
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Using the `manage.py runserver` command, when I try to access to
 https://127.0.0.1:8000 (note the https protocol), the server throws an
 error:


 {{{
 [11/Sep/2015 16:48:05] code 400, message Bad request syntax
 
('\x16\x03\x01\x00\xba\x01\x00\x00\xb6\x03\x03k[\xae\x88;\x81\xefJ\xa5\xa5\xa9j[F,uK\xcfb\xf4\x90\xbf\xd9k\x14\x86(w\x00_V0\x00\x00\x1e\xc0+\xc0/\xc0')
 
 Exception happened during processing of request from ('127.0.0.1', 35451)
 Traceback (most recent call last):
   File "/usr/lib/python2.7/SocketServer.py", line 593, in
 process_request_thread
 self.finish_request(request, client_address)
   File "/usr/lib/python2.7/SocketServer.py", line 334, in finish_request
 self.RequestHandlerClass(request, client_address, self)
   File "my_virtual_env/local/lib/python2.7/site-
 packages/django/core/servers/basehttp.py", line 129, in __init__
 super(WSGIRequestHandler, self).__init__(*args, **kwargs)
   File "/usr/lib/python2.7/SocketServer.py", line 649, in __init__
 self.handle()
   File "/usr/lib/python2.7/wsgiref/simple_server.py", line 117, in handle
 if not self.parse_request(): # An error code has been sent, just exit
   File "/usr/lib/python2.7/BaseHTTPServer.py", line 286, in parse_request
 self.send_error(400, "Bad request syntax (%r)" % requestline)
   File "/usr/lib/python2.7/BaseHTTPServer.py", line 368, in send_error
 self.send_response(code, message)
   File "/usr/lib/python2.7/BaseHTTPServer.py", line 385, in send_response
 self.log_request(code)
   File "/usr/lib/python2.7/BaseHTTPServer.py", line 422, in log_request
 self.requestline, str(code), str(size))
   File "my_virtual_env/local/lib/python2.7/site-
 packages/django/core/servers/basehttp.py", line 136, in log_message
 msg = "[%s] %s\n" % (self.log_date_time_string(), format % args)
 UnicodeDecodeError: 'ascii' codec can't decode byte 0xba in position 5:
 ordinal not in range(128)
 
 }}}

 I don't know if there are limitations about having a local server
 supporting the HTTPS protocol, but Django should at least throw a nicer
 exception. This error happened to a colleague who modified in his browser
 a production URL (which only works in https) to a local one, and the error
 was quite cryptic at first sight.

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

Re: [Django] #25382: Documentation makes reference to non-existent class.

2015-09-11 Thread Django

#25382: Documentation makes reference to non-existent class.
--+
 Reporter:  jambonrose|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by charettes):

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


Comment:

 `DateQuerySet` was an implementation detail removed by
 cbb5cdd155668ba771cad6b975676d3b20fed37b.

 The documentation should be updated to specify `dates()` now return a
 simple `QuerySet()`.

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

[Django] #25382: Documentation makes reference to non-existent class.

2015-09-11 Thread Django

#25382: Documentation makes reference to non-existent class.
--+
 Reporter:  jambonrose|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.8
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 The documentation mentions a `DateQuerySet` in the QuerySet API reference,
 but no such class appears to exist.

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

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

Re: [Django] #25377: Regression in expressions refactor causes database queries to run COUNT('') instead of COUNT()

2015-09-11 Thread Django

#25377: Regression in expressions refactor causes database queries to run
COUNT('*') instead of COUNT(*)
-+-
 Reporter:  adamchainz   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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

Re: [Django] #25381: "default_app_config" causes custom commands to not be found

2015-09-11 Thread Django

#25381: "default_app_config" causes custom commands to not be found
-+-
 Reporter:  thebritican  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  1.8
  commands)  |
 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):

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


Comment:

 It looks like you have set
 
[https://docs.djangoproject.com/en/stable/ref/applications/#django.apps.AppConfig.name
 AppConfig.name] incorrectly. It [https://github.com/anovelmous-dev-
 
squad/anovelmous/blob/7239e33172eeb411462bfefdff92aa71576f0d48/anovelmous_app/apps.py#L9
 points to 'api'] but the Python path for that app appears to be
 'anovelmous_app'.

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

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

Re: [Django] #25376: Replace "sudo pip install" recommendation with virtualenv

2015-09-11 Thread Django

#25376: Replace "sudo pip install" recommendation with virtualenv
-+-
 Reporter:  timgraham|Owner:  tyagi-
 Type:   |  iiitv
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by tyagi-iiitv):

 * needs_docs:  0 => 1
 * easy:  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/067.7925b06c84d1e5036f746b15303f70be%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25376: Replace "sudo pip install" recommendation with virtualenv

2015-09-11 Thread Django

#25376: Replace "sudo pip install" recommendation with virtualenv
-+-
 Reporter:  timgraham|Owner:  tyagi-
 Type:   |  iiitv
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by tyagi-iiitv):

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

Re: [Django] #25374: Admin system check prevents dynamic ModelAdmin attributes

2015-09-11 Thread Django

#25374: Admin system check prevents dynamic ModelAdmin attributes
-+-
 Reporter:  mbox |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  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 Tim Graham ):

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


Comment:

 In [changeset:"1d8eb0cae57731b481a88dca272b2cb0d645bd8e" 1d8eb0ca]:
 {{{
 #!CommitTicketReference repository=""
 revision="1d8eb0cae57731b481a88dca272b2cb0d645bd8e"
 Fixed #25374 -- Made ModelAdmin checks work on instances instead of
 classes.

 This allows dynamically-generated attributes to be specified in
 checked ModelAdmin attributes without triggering errors.
 }}}

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

Re: [Django] #24765: Calling flatten on a Context object fails in some cases

2015-09-11 Thread Django

#24765: Calling flatten on a Context object fails in some cases
-+
 Reporter:  poirier  |Owner:  BuddyL
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  1.8
 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
 * has_patch:  0 => 1


Comment:

 I left some comments for improvement on the
 [https://github.com/django/django/pull/5264 pull request]. poirier, could
 you check if it solves your problem? I'm not sure if we should add a
 higher level test for the case presented in the ticket or 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/065.659f85f545893a3db6b2efc825f2018b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25200: Update admin's screenshots for new admin theme

2015-09-11 Thread Django

#25200: Update admin's screenshots for new admin theme
-+-
 Reporter:  timgraham|Owner:
 |  ryangallen
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  1.9  | 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):

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

Re: [Django] #25374: Admin system check prevents dynamic ModelAdmin attributes

2015-09-11 Thread Django

#25374: Admin system check prevents dynamic ModelAdmin attributes
-+-
 Reporter:  mbox |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  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 timgraham):

 * stage:  Unreviewed => 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/062.335c273f42d946843c9bf96a3b593b95%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25351: Add example for database test settings

2015-09-11 Thread Django

#25351: Add example for database test settings
-+-
 Reporter:  m4r0v3r  |Owner:  cacoze
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.8
 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:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"d32edd8c99da8a5035542b7bcc83891edda73116" d32edd8]:
 {{{
 #!CommitTicketReference repository=""
 revision="d32edd8c99da8a5035542b7bcc83891edda73116"
 [1.8.x] Fixed #25351 -- Added example for database test settings to docs.

 Backport of cf99bae53af2ed8f73622bc8a8ed0331c272fda3 from master
 }}}

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

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

Re: [Django] #25351: Add example for database test settings

2015-09-11 Thread Django

#25351: Add example for database test settings
-+-
 Reporter:  m4r0v3r  |Owner:  cacoze
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.8
 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:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"cf99bae53af2ed8f73622bc8a8ed0331c272fda3" cf99bae]:
 {{{
 #!CommitTicketReference repository=""
 revision="cf99bae53af2ed8f73622bc8a8ed0331c272fda3"
 Fixed #25351 -- Added example for database test settings to docs.
 }}}

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

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

Re: [Django] #25380: Add Postgres.app to the suggested options for PostGIS on OS X

2015-09-11 Thread Django

#25380: Add Postgres.app to the suggested options for PostGIS on OS X
-+-
 Reporter:  fcurella |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  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):

 * has_patch:  0 => 1
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => 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.bb81ab52b0aa20aa8a75589a78ec048c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25380: Add Postgres.app to the suggested options for PostGIS on OS X

2015-09-11 Thread Django

#25380: Add Postgres.app to the suggested options for PostGIS on OS X
---+--
 Reporter:  fcurella   |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  master
 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 Tim Graham ):

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


Comment:

 In [changeset:"0c7c18cc9e80101c882749c99437ad700fde0ca0" 0c7c18cc]:
 {{{
 #!CommitTicketReference repository=""
 revision="0c7c18cc9e80101c882749c99437ad700fde0ca0"
 Fixed #25380 -- Added Postgres.app to the PostGIS options on OS X.
 }}}

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

Re: [Django] #25380: Add Postgres.app to the suggested options for PostGIS on OS X

2015-09-11 Thread Django

#25380: Add Postgres.app to the suggested options for PostGIS on OS X
---+--
 Reporter:  fcurella   |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  master
 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
---+--

Comment (by Tim Graham ):

 In [changeset:"501b32b2551c12428b7637733701541bb7222cfa" 501b32b2]:
 {{{
 #!CommitTicketReference repository=""
 revision="501b32b2551c12428b7637733701541bb7222cfa"
 [1.8.x] Fixed #25380 -- Added Postgres.app to the PostGIS options on OS X.

 Backport of 0c7c18cc9e80101c882749c99437ad700fde0ca0 from master
 }}}

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

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

Re: [Django] #25339: Aggregation and annotation by time period and intervals (by month, week, day, hour, etc)

2015-09-11 Thread Django

Comment (by malefice):

I do not think that excerpt does the same functionality mine does. It
seems that it only filters for the year 2015, extracts the month number,
and then performs a 'GROUP BY' based on the month number. It does not
generate an actual timeseries that can easily be parsed by javascript and
charting libraries.

My excerpt outputs actual time periods based on a range of dates with
specific intervals/frequency. If for example, the `start_date` is
2015-01-01, `end_date` is 2015-07-07, and `frequency` is month, it will
aggregate the results that match the date range and group them by month
dates like so: 2015-01-01, 2015-02-01, 2015-03-01, ... 2015-07-01.

If the `frequency` is hour, then it will output each and every hour like
so: 2015-01-01 00:00:00, 2015-01-01 01:00:00, 2015-01-01 02:00:00, ...
2015-05-01 00:00:00, 2015-05-01 01:00:00 , ... , 2015-07-07 22:00:00, and
2015-07-07 23:00:00. You will have a column containing the actual
timeseries.

One can only do that efficiently in PostgreSQL by using the `DATE_TRUNC`
function, and I looked in the source code, but it does not seem to be used
in anywhere that might resemble something like my excerpt. I think it is
possible to write a custom Transform for that, but it would be nice to
have it ready out of the box. At least in my case, projects always involve
aggregating and presenting data with a timeseries.

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

Re: [Django] #25363: Model fields pre_save not called if force_insert=True

2015-09-11 Thread Django

#25363: Model fields pre_save not called if force_insert=True
-+-
 Reporter:  davidfischer-ch  |Owner:
 |  davidfischer-ch
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  pre_save,save| Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by davidfischer-ch):

 Interesting:
 https://docs.python.org/3.4/library/collections.html#collections.ChainMap.
 That can be our copy-on-write "kind of" data structure!

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

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

Re: [Django] #25363: Model fields pre_save not called if force_insert=True

2015-09-11 Thread Django

Comment (by davidfischer-ch):

Hi akaariai,

Your mix-in is interesting but it has some issues, hopefully easy to fix.

1. This is actually broken by the `pre_save` logic for a simple reason :
The `pre_save` methods are called inside the save, a.k.a inside the
`super().save(...)` so your mix-in and my mix-in [https://github.com
/davidfischer-
ch/pytoolbox/blob/master/pytoolbox/django/models/mixins.py#L115
AutoUpdateFieldsMixin] will not detect those. Its a reason why I
implemented [https://github.com/davidfischer-
ch/pytoolbox/blob/master/pytoolbox/django/models/mixins.py#L153
CallFieldsPreSaveMixin].
I also implemented another mix-in (sometimes I feel like a DJ, doing many
mixes),[https://github.com/davidfischer-
ch/pytoolbox/blob/master/pytoolbox/django/models/mixins.py#L89
AutoRemovePKFromUpdateFieldsMixin] that will check if the primary key is
set to a new value, then the intention of the developer is probably to
duplicate the model by saving it with a new primary key. So the mix-in let
Django save with its own default options for save.

2. `__dict__.copy()` is not sufficient, if one of the fields, is, for
example, a `JSONField` then the content is a mutable type (`dict`). This
container may contains nested mutable types, and you have to `deepcopy` to
ensure your copy will reflect the unchanged data from the database and
will not be modified.

3. your overload of `save()` isn't generic enough to support all possible
arguments.

Interesting you saved the data in `_state`.
That's cleaner than my mix-in.

I am thinking loudly, but is it more performant that any field set by the
code should be updated regardless the value, something that will not
happen often, or is it better to check for diff. Checking for diff will
also double the memory usage for the data (is it any copy-on-write mix-in
out here?).

We also need to think about concurrent updates when designing a save-the-
changes mix-in. For that reason I implemented another mix-in
[https://github.com/davidfischer-
ch/pytoolbox/blob/master/pytoolbox/django/models/mixins.py#L243
UpdatePreconditionsMixin]. I don't know what is the best option, but maybe
its more explicit and intuitive that if the program sets the fields, that
they will be saved regardless the value.

Yes, many questions and thoughts.
I am eager to heard about you guys.

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

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

Re: [Django] #25329: _nodb_connection is open for an entire test suite run

2015-09-11 Thread Django

#25329: _nodb_connection is open for an entire test suite run
-+-
 Reporter:  mewtaylor|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  nodb, testing, test  | Triage Stage:  Ready for
  runner |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"b2f6e421a332ce45cf0f1f2f6bd5962765a013f1" b2f6e42]:
 {{{
 #!CommitTicketReference repository=""
 revision="b2f6e421a332ce45cf0f1f2f6bd5962765a013f1"
 Fixed #25329 -- Prevented _nodb_connection from being left open
 }}}

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

70 matches

Mail list logo