date:20161129

Re: [Django] #27554: Queryset evaluation fails with mix of nested and flattened prefetches (AttributeError on RelatedManager)

2016-11-29 Thread Django

#27554: Queryset evaluation fails with mix of nested and flattened prefetches
(AttributeError on RelatedManager)
-+-
 Reporter:  Anthony Leontiev |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  prefetch | Triage Stage:  Accepted
  AttributeError prefetch_related|
  nested RelatedManager  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * stage:  Unreviewed => Accepted


Comment:

 I haven't tried reproducing myself but the report is complete enough that
 I trust the developer's judgment.

 Anthony, can you confirm this is also an issue when running
 `A.objects.prefetch_related('b__c__d'')`? What about
 `B.objects.prefetch_related('c__d')`?

 [https://docs.djangoproject.com/en/1.10/internals/contributing/triaging-
 tickets/#bisecting-a-regression Bisecting the exact commit that introduced
 the regression] would also be useful.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.1e44708c5eb3b70e11ff13fa7b7de791%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27552: add docs/tests for GEOSGeometry.normalize()

2016-11-29 Thread Django

#27552: add docs/tests for GEOSGeometry.normalize()
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 Type:   |  Fedoseev
  Cleanup/optimization   |   Status:  assigned
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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

Re: [Django] #27507: use SchemaEditor.execute() to run deferred_sql in migration sync_apps

2016-11-29 Thread Django

#27507: use SchemaEditor.execute() to run deferred_sql in migration sync_apps
-+-
 Reporter:  Lex Berezhny |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"8eb56f3c786b4dd7f78a60145ae2e483e24b62c1" 8eb56f3c]:
 {{{
 #!CommitTicketReference repository=""
 revision="8eb56f3c786b4dd7f78a60145ae2e483e24b62c1"
 Fixed #27507 -- Used SchemaEditor.execute() to run deferred_sql in
 migrate's sync_apps().
 }}}

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

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

Re: [Django] #27555: Remove django.utils.functional.lazy_property

2016-11-29 Thread Django

#27555: Remove django.utils.functional.lazy_property
-+-
 Reporter:  Adam Chainz  |Owner:  Adam
 Type:   |  Chainz
  Cleanup/optimization   |   Status:  closed
Component:  Utilities|  Version:  1.10
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"71609a5b903ace05a437eb3f89859e9d35a88203" 71609a5]:
 {{{
 #!CommitTicketReference repository=""
 revision="71609a5b903ace05a437eb3f89859e9d35a88203"
 Fixed #27555 -- Removed django.utils.functional.lazy_property.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.77aebf3c20665ffa736c3bc87b8fa64c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27181: Sites framework does not normalize domains with trailing "."

2016-11-29 Thread Django

#27181: Sites framework does not normalize domains with trailing "."
---+
 Reporter:  Ran Benita |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.sites  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"05d2c5a66dd72c26e5221855e08834a66c844399" 05d2c5a]:
 {{{
 #!CommitTicketReference repository=""
 revision="05d2c5a66dd72c26e5221855e08834a66c844399"
 Fixed #27181 -- Allowed contrib.sites to match domains with trailing ".".
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.b469a252b4bdd8a3d3cb14f073c22b63%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25809: PostgreSQL 9.5 BRIN Index support in contrib.postgres

2016-11-29 Thread Django

#25809: PostgreSQL 9.5 BRIN Index support in contrib.postgres
-+-
 Reporter:  Asif Saifuddin Auvi  |Owner:  Mads
 |  Jensen
 Type:  New feature  |   Status:  assigned
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  postgres, index, | Triage Stage:  Accepted
  BRIN   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mads Jensen):

 * needs_better_patch:  1 => 0


Comment:

 Updated according to review by Tim Graham. It's tricky finding a good
 ```sql_create_index``` that suits all backends, as the current design
 requires. My solution just introduces a new one, and uses this in the
 ```as_sql```-method.

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

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

Re: [Django] #27555: Remove django.utils.functional.lazy_property

2016-11-29 Thread Django

#27555: Remove django.utils.functional.lazy_property
-+-
 Reporter:  Adam Chainz  |Owner:  Adam
 Type:   |  Chainz
  Cleanup/optimization   |   Status:  assigned
Component:  Utilities|  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Adam Chainz):

 * owner:  me@… => Adam Chainz
 * 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.8e64718e3857094ba6eca76bd571faa7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #27555: Remove django.utils.functional.lazy_property

2016-11-29 Thread Django

#27555: Remove django.utils.functional.lazy_property
+--
   Reporter:  Adam Chainz   |  Owner:  me@…
   Type:  Cleanup/optimization  | Status:  assigned
  Component:  Utilities |Version:  1.10
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+--
 `lazy_property` is not used anywhere inside core Django. The only use
 appears to be inside the ex-contrib app django-formtools, as I documented
 in an issue there: https://github.com/django/django-formtools/issues/84 .
 Also the only use seen on a few pages of Github code search is in
 committed copies of Django itself.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.f2cb218ee1f934c426b852a997d2adca%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27554: Queryset evaluation fails with mix of nested and flattened prefetches (AttributeError on RelatedManager)

2016-11-29 Thread Django

#27554: Queryset evaluation fails with mix of nested and flattened prefetches
(AttributeError on RelatedManager)
-+-
 Reporter:  Anthony Leontiev |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  prefetch | Triage Stage:
  AttributeError prefetch_related|  Unreviewed
  nested RelatedManager  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Anthony Leontiev):

 Discovered in an API integration test that relies on nested prefetching
 during an upgrade of Django 1.7 to Django 1.10.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.9d4e673caef345b7ebdae7c6f9588f19%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27554: Queryset evaluation fails with mix of nested and flattened prefetches (AttributeError on RelatedManager)

2016-11-29 Thread Django

#27554: Queryset evaluation fails with mix of nested and flattened prefetches
(AttributeError on RelatedManager)
-+-
 Reporter:  Anthony Leontiev |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  prefetch | Triage Stage:
  AttributeError prefetch_related|  Unreviewed
  nested RelatedManager  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Anthony Leontiev):

 * Attachment "prefetchbug.tar.gz" added.

 test project to reproduce the bug

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

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

[Django] #27554: Queryset evaluation fails with mix of nested and flattened prefetches (AttributeError on RelatedManager)

2016-11-29 Thread Django

#27554: Queryset evaluation fails with mix of nested and flattened prefetches
(AttributeError on RelatedManager)
-+-
   Reporter:  Anthony|  Owner:  nobody
  Leontiev   |
   Type:  Bug| Status:  new
  Component:  Database   |Version:  1.10
  layer (models, ORM)|   Keywords:  prefetch
   Severity:  Normal |  AttributeError prefetch_related
   Triage Stage: |  nested RelatedManager
  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Under certain circumstances, querysets with nested prefetches fail to
 evaluate in Django 1.10.

 With these models (populated with data):

 {{{
 #  A <-> B <-- C --> D
 #\__/


 class A(models.Model):
 pass


 class B(models.Model):
 a = models.OneToOneField('A', null=True, related_name='b')
 d = models.ManyToManyField('D', through='C', related_name='b')


 class C(models.Model):
 b = models.ForeignKey('B', related_name='c')
 d = models.ForeignKey('D', related_name='c')


 class D(models.Model):
 pass
 }}}

 ... and this query/evaluation:

 {{{
 queryset = A.objects.all().prefetch_related(
 Prefetch(
 'b',
 queryset=B.objects.all().prefetch_related(
 Prefetch('c__d')
 )
 )
 )
 content = queryset[0].b.c.all()[0].d.pk
 }}}

 Django throws this exception:

 {{{
   File "/Users/ant/code/django-bugs/prefetchbug/.venv/lib/python2.7/site-
 packages/django/db/models/query.py", line 256, in __iter__
 self._fetch_all()
   File "/Users/ant/code/django-bugs/prefetchbug/.venv/lib/python2.7/site-
 packages/django/db/models/query.py", line 1087, in _fetch_all
 self._prefetch_related_objects()
   File "/Users/ant/code/django-bugs/prefetchbug/.venv/lib/python2.7/site-
 packages/django/db/models/query.py", line 663, in
 _prefetch_related_objects
 prefetch_related_objects(self._result_cache,
 *self._prefetch_related_lookups)
   File "/Users/ant/code/django-bugs/prefetchbug/.venv/lib/python2.7/site-
 packages/django/db/models/query.py", line 1460, in
 prefetch_related_objects
 (through_attr, first_obj.__class__.__name__, lookup.prefetch_through))
 AttributeError: Cannot find 'd' on RelatedManager object, 'b__c__d' is an
 invalid parameter to prefetch_related()
 }}}

 Interestingly enough, this practically identical variant of the above
 query with a fully "nested" prefetch structure succeeds:

 {{{
 queryset = A.objects.all().prefetch_related(
 Prefetch(
 'b',
 queryset=B.objects.all().prefetch_related(
 Prefetch(
 'c',
 queryset=C.objects.all().prefetch_related(
 'd'
 )
 )
 )
 )
 )
 content = queryset[0].b.c.all()[0].d.pk
 }}}


 To reproduce, download the attachment and run:

 {{{
 pip install -r requirements.txt
 python manage.py migrate
 python manage.py runserver
 }}}

 ... and navigate to {localhost:8000/flat} and {localhost:8000/nested}.

 This only seems to impact Django 1.10; the bug does not reproduce if the
 Django version in the {requirements.txt} file is changed to 1.9 or 1.8.

 Discovered in https://github.com/AltSchool/dynamic-rest/pull/147
 Similar to https://code.djangoproject.com/ticket/26801

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

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

Re: [Django] #27358: Add a system check for FileField upload_to starting with a slash

2016-11-29 Thread Django

#27358: Add a system check for FileField upload_to starting with a slash
-+-
 Reporter:  Tim Graham   |Owner:  Henry
 Type:   |  Dang
  Cleanup/optimization   |   Status:  closed
Component:  Core (System |  Version:  1.10
  checks)|
 Severity:  Normal   |   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"7cddd8a02e60332c0d02f565c450b0eea0d88438" 7cddd8a]:
 {{{
 #!CommitTicketReference repository=""
 revision="7cddd8a02e60332c0d02f565c450b0eea0d88438"
 Fixed #27358 -- Added a system check to prevent FileField's upload_to from
 starting with a slash.

 Thanks Frank Bijlsma for the initial patch.
 }}}

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

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

Re: [Django] #27553: tutorial python manage.py runserver creates NameError: name 'include' is not defined (was: tutorial python manage.py runserver creates segmentation fault)

2016-11-29 Thread Django

#27553: tutorial python manage.py runserver creates NameError: name 'include' is
not defined
-+-
 Reporter:  Roel Hogervorst  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  windows10, getting   | Triage Stage:
  started, exception |  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:   => invalid


Old description:

> Hi there, I tried the tutorial / introduction to django and get stuck. I
> have installed django, verified that it is working :
> ```
> python 3.5.2:4def2a2901a5 on win32, and django 1.10.3 on mingw32 on a
> windows 10 machine.
> ```
>
> I did not install a virtual environment.
>
> `django-admin startproject mysite` worked
>
> I cd into the mysite directory (the top one, that is, the one below , `cd
> mysite` )
>
> The next step does not work though:
> python manage.py runserver gives me this output
> ```
> Performing system checks...
>
> Unhandled exception in thread started by  check_errors..wrapper at 0x03FB28A0>
> Traceback (most recent call last):
>   File "C:\Users\roel\AppData\Local\Programs\Python\Python35-32\lib\site-
> packages\django\utils\autoreload.py", line 226, in wrapper
> fn(*args, **kwargs)
>   File "C:\Users\roel\AppData\Local\Programs\Python\Python35-32\lib\site-
> packages\django\core\management\commands\runserver.py", line 121, in
> inner_run
> self.check(display_num_errors=True)
>   File "C:\Users\roel\AppData\Local\Programs\Python\Python35-32\lib\site-
> packages\django\core\management\base.py", line 374, in check
> include_deployment_checks=include_deployment_checks,
>   File "C:\Users\roel\AppData\Local\Programs\Python\Python35-32\lib\site-
> packages\django\core\management\base.py", line 361, in _run_checks
> return checks.run_checks(**kwargs)
>   File "C:\Users\roel\AppData\Local\Programs\Python\Python35-32\lib\site-
> packages\django\core\checks\registry.py", line 81, in run_checks
> new_errors = check(app_configs=app_configs)
>   File "C:\Users\roel\AppData\Local\Programs\Python\Python35-32\lib\site-
> packages\django\core\checks\urls.py", line 14, in check_url_config
> return check_resolver(resolver)
>   File "C:\Users\roel\AppData\Local\Programs\Python\Python35-32\lib\site-
> packages\django\core\checks\urls.py", line 24, in check_resolver
> for pattern in resolver.url_patterns:
>   File "C:\Users\roel\AppData\Local\Programs\Python\Python35-32\lib\site-
> packages\django\utils\functional.py", line 35, in __get__
> res = instance.__dict__[self.name] = self.func(instance)
>   File "C:\Users\roel\AppData\Local\Programs\Python\Python35-32\lib\site-
> packages\django\urls\resolvers.py", line 313, in url_patterns
> patterns = getattr(self.urlconf_module, "urlpatterns",
> self.urlconf_module)
>   File "C:\Users\roel\AppData\Local\Programs\Python\Python35-32\lib\site-
> packages\django\utils\functional.py", line 35, in __get__
> res = instance.__dict__[self.name] = self.func(instance)
>   File "C:\Users\roel\AppData\Local\Programs\Python\Python35-32\lib\site-
> packages\django\urls\resolvers.py", line 306, in urlconf_module
> return import_module(self.urlconf_name)
>   File
> "C:\Users\roel\AppData\Local\Programs\Python\Python35-32\lib\importlib\__init__.py",
> line 126, in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
>   File "", line 986, in _gcd_import
>   File "", line 969, in _find_and_load
>   File "", line 958, in
> _find_and_load_unlocked
>   File "", line 673, in _load_unlocked
>   File "", line 665, in exec_module
>   File "", line 222, in
> _call_with_frames_removed
>   File
> "D:\RmhDocs\Documents\docs\actief\Projecten\django\mysite\mysite\urls.py",
> line 20, in 
> url(r'^polls/', include('polls.urls')),
> NameError: name 'include' is not defined

New description:

 Hi there, I tried the tutorial / introduction to django and get stuck. I
 have installed django, verified that it is working :
 {{{
 python 3.5.2:4def2a2901a5 on win32, and django 1.10.3 on mingw32 on a
 windows 10 machine.
 }}}

 I did not install a virtual environment.

 `django-admin startproject mysite` worked

 I cd into the mysite directory (the top one, that is, the one below , `cd
 mysite` )

 The next step does not work though:
 python manage.py runserver gives me this output
 {{{
 Performing system checks...

 Unhandled exception in thread started by .wrapper at 0x03FB28A0>

[Django] #27553: tutorial python manage.py runserver creates segmentation fault

2016-11-29 Thread Django

#27553: tutorial python manage.py runserver creates segmentation fault
-+-
   Reporter:  Roel   |  Owner:  nobody
  Hogervorst |
   Type:  Bug| Status:  new
  Component: |Version:  1.10
  Documentation  |   Keywords:  windows10, getting
   Severity:  Normal |  started, exception
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Hi there, I tried the tutorial / introduction to django and get stuck. I
 have installed django, verified that it is working :
 ```
 python 3.5.2:4def2a2901a5 on win32, and django 1.10.3 on mingw32 on a
 windows 10 machine.
 ```

 I did not install a virtual environment.

 `django-admin startproject mysite` worked

 I cd into the mysite directory (the top one, that is, the one below , `cd
 mysite` )

 The next step does not work though:
 python manage.py runserver gives me this output
 ```
 Performing system checks...

 Unhandled exception in thread started by .wrapper at 0x03FB28A0>
 Traceback (most recent call last):
   File "C:\Users\roel\AppData\Local\Programs\Python\Python35-32\lib\site-
 packages\django\utils\autoreload.py", line 226, in wrapper
 fn(*args, **kwargs)
   File "C:\Users\roel\AppData\Local\Programs\Python\Python35-32\lib\site-
 packages\django\core\management\commands\runserver.py", line 121, in
 inner_run
 self.check(display_num_errors=True)
   File "C:\Users\roel\AppData\Local\Programs\Python\Python35-32\lib\site-
 packages\django\core\management\base.py", line 374, in check
 include_deployment_checks=include_deployment_checks,
   File "C:\Users\roel\AppData\Local\Programs\Python\Python35-32\lib\site-
 packages\django\core\management\base.py", line 361, in _run_checks
 return checks.run_checks(**kwargs)
   File "C:\Users\roel\AppData\Local\Programs\Python\Python35-32\lib\site-
 packages\django\core\checks\registry.py", line 81, in run_checks
 new_errors = check(app_configs=app_configs)
   File "C:\Users\roel\AppData\Local\Programs\Python\Python35-32\lib\site-
 packages\django\core\checks\urls.py", line 14, in check_url_config
 return check_resolver(resolver)
   File "C:\Users\roel\AppData\Local\Programs\Python\Python35-32\lib\site-
 packages\django\core\checks\urls.py", line 24, in check_resolver
 for pattern in resolver.url_patterns:
   File "C:\Users\roel\AppData\Local\Programs\Python\Python35-32\lib\site-
 packages\django\utils\functional.py", line 35, in __get__
 res = instance.__dict__[self.name] = self.func(instance)
   File "C:\Users\roel\AppData\Local\Programs\Python\Python35-32\lib\site-
 packages\django\urls\resolvers.py", line 313, in url_patterns
 patterns = getattr(self.urlconf_module, "urlpatterns",
 self.urlconf_module)
   File "C:\Users\roel\AppData\Local\Programs\Python\Python35-32\lib\site-
 packages\django\utils\functional.py", line 35, in __get__
 res = instance.__dict__[self.name] = self.func(instance)
   File "C:\Users\roel\AppData\Local\Programs\Python\Python35-32\lib\site-
 packages\django\urls\resolvers.py", line 306, in urlconf_module
 return import_module(self.urlconf_name)
   File
 
"C:\Users\roel\AppData\Local\Programs\Python\Python35-32\lib\importlib\__init__.py",
 line 126, in import_module
 return _bootstrap._gcd_import(name[level:], package, level)
   File "", line 986, in _gcd_import
   File "", line 969, in _find_and_load
   File "", line 958, in
 _find_and_load_unlocked
   File "", line 673, in _load_unlocked
   File "", line 665, in exec_module
   File "", line 222, in
 _call_with_frames_removed
   File
 "D:\RmhDocs\Documents\docs\actief\Projecten\django\mysite\mysite\urls.py",
 line 20, in 
 url(r'^polls/', include('polls.urls')),
 NameError: name 'include' is not defined

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

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

Re: [Django] #27498: Filtering annotated field in SQLite returns wrong results

2016-11-29 Thread Django

#27498: Filtering annotated field in SQLite returns wrong results
-+-
 Reporter:  Tim Düllmann |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  sqlite,  | Triage Stage:  Accepted
  annotations, filter|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Anton Samarchyan):

 * version:  1.10 => master


Old description:

> When filtering an annotated field with SQLite backend the result from
> Django QuerySet differs from what the raw SQL-query returns. This does
> not affect other databases, only SQLite.
>
> The following is the problematic queryset:
> {{{
> qs =
> Product.objects.annotate(qty_available_sum=Sum('stock__qty_available')) \
> .annotate(qty_needed=F('qty_target') -
> F('qty_available_sum')) \
> .filter(qty_needed__gt=0)
> }}}
>
> This translates to the following Query, which returns the correct
> results, when run natively:
>
> {{{
> SELECT "testapp_product"."id", "testapp_product"."name",
> "testapp_product"."qty_target", CAST(SUM("testapp_stock"."qty_available")
> AS NUMERIC) AS "qty_available_sum", ("testapp_product"."qty_target" -
> CAST(SUM("testapp_stock"."qty_available") AS NUMERIC)) AS "qty_needed"
> FROM "testapp_product"
> LEFT OUTER JOIN "testapp_stock" ON ("testapp_product"."id" =
> "testapp_stock"."product_id")
> GROUP BY "testapp_product"."id", "testapp_product"."name",
> "testapp_product"."qty_target"
> HAVING ("testapp_product"."qty_target" -
> CAST(SUM("testapp_stock"."qty_available") AS NUMERIC)) > 0
> }}}
>
> Using the QuerySet, it does not respect the filter condition. For details
> see the test below.
>
> Here is a simple App with a test that shows the difference. The complete
> files with imports are attached.
>
> {{{
> ##
> # models.py:
> ##
>
> class Product(models.Model):
> name = models.CharField(max_length=80)
> qty_target = models.DecimalField(max_digits=6, decimal_places=2)
>
> class Stock(models.Model):
> product = models.ForeignKey(Product, related_name="stock")
> qty_available = models.DecimalField(max_digits=6, decimal_places=2)
>
> ##
> # tests.py:
> ##
>
> class ErrorTestCase(TestCase):
>
> def setUp(self):
> p1 = Product.objects.create(name="Product1", qty_target=10)
> p2 = Product.objects.create(name="Product2", qty_target=10)
> p3 = Product.objects.create(name="Product3", qty_target=10)
>
> s1 = Stock.objects.create(product=p1, qty_available=5)
> s2 = Stock.objects.create(product=p1, qty_available=5)
> s3 = Stock.objects.create(product=p1, qty_available=3)  # 3 over
> target
>
> s4 = Stock.objects.create(product=p2, qty_available=5)
> s5 = Stock.objects.create(product=p2, qty_available=4)  # 1 under
> target
>
> s6 = Stock.objects.create(product=p3, qty_available=0)  # 10
> under target
>
> def testError(self):
> # This is the exciting stuff:
> qs =
> Product.objects.annotate(qty_available_sum=Sum('stock__qty_available'))\
> .annotate(qty_needed=F('qty_target') -
> F('qty_available_sum'))\
> .filter(qty_needed__gt=0)
>
> # Retrieve by raw query:
> query = str(qs.query)
> print("# Query from QuerySet:")
> print(query)
> rows = []
> with connection.cursor() as cursor:
> cursor.execute(query)
> rows = cursor.fetchall()
> print("# Results from above Query:")
> for r in rows:
> print(r)
> self.assertEqual(len(rows), 2, "Two products need stock by SQL
> query.")
>
> # retrieve by Django QuerySet:
> print("# Results from QuerySet:")
> for q in qs:
> print(q, q.qty_needed)
> self.assertEqual(qs.count(), 2, "Two products need stock by
> Django QuerySet.")
> }}}
>
> And here is the output of the test. You can see the full query as it is
> retrieved from the queryset and then run natively to retrieve the correct
> amount of two rows. After that the same queryset is used to retreive the
> data, but it retreived no row at all.
>
> {{{
> ##
> # Output with SQLite:
> ##
> Creating test database for alias 'default'...
>
> # Query from QuerySet:
> SELECT "testapp_product"."id", "testapp_product"."name",
> "testapp_product"."qty_target", CAST(SUM("testapp_stock"."qty_available")
> AS NUMERIC)

Re: [Django] #27542: Client.force_login() shouldn't use authentication backends without a get_user() method

2016-11-29 Thread Django

#27542: Client.force_login() shouldn't use authentication backends without a
get_user() method
--+
 Reporter:  Tom   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Testing framework |  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 Anton Samarchyan):

 * cc: desecho@… (added)
 * has_patch:  0 => 1
 * version:  1.10 => master


Comment:

 Added [https://github.com/django/django/pull/7634 PR].

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

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

Re: [Django] #24646: File names jinja2.py cannot import jinja2

2016-11-29 Thread Django

#24646: File names jinja2.py cannot import jinja2
-+-
 Reporter:  Daniel Greenfeld |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  jinja2   | 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 Aymeric Augustin):

 The point is almost moot as the next version of Django will drop support
 for Python 2, and this problem can't happen on Python 3.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.be4e8c7e195b303ed898a52687a1f668%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27533: inspectdb crashes on unsupported unique_together constraints in PostgreSQL

2016-11-29 Thread Django

#27533: inspectdb crashes on unsupported unique_together constraints in 
PostgreSQL
-+-
 Reporter:  Wei Ma   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Wei Ma):

 I have closed my PR https://github.com/django/django/pull/7618 due to not
 able to create test cases. If anyone want to help,  please fork my repo
 and add needed tests.

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

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

Re: [Django] #27552: add docs/tests for GEOSGeometry.normalize()

2016-11-29 Thread Django

#27552: add docs/tests for GEOSGeometry.normalize()
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 Type:   |  Fedoseev
  Cleanup/optimization   |   Status:  assigned
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Sergey Fedoseev):

 * has_patch:  0 => 1


Comment:

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

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

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

Re: [Django] #27402: When using i18n_patterns and prefix_default_language=False, 404 page redirects incorrectly

2016-11-29 Thread Django

#27402: When using i18n_patterns and prefix_default_language=False, 404 page
redirects incorrectly
--+
 Reporter:  Hovi  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Internationalization  |  Version:  1.10
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"81b5971b1ce08466791b3c6f795b66c666d7" 81b5971b]:
 {{{
 #!CommitTicketReference repository=""
 revision="81b5971b1ce08466791b3c6f795b66c666d7"
 [1.10.x] Fixed #27402 -- Fixed incorrect LocaleMiddleware redirects with
 prefix_default_language=False.

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

Re: [Django] #24646: File names jinja2.py cannot import jinja2

2016-11-29 Thread Django

#24646: File names jinja2.py cannot import jinja2
-+-
 Reporter:  Daniel Greenfeld |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  jinja2   | 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:  new => closed
 * resolution:   => fixed


Comment:

 I can't reproduce a problem unless I remove the `from __future__ import
 absolute_import` that the commit for this ticket added. Could you please
 provide a sample project that reproduces the problem? Ideally, you would
 use [wiki:TicketClosingReasons/UseSupportChannels our support channnels]
 rather than this ticket tracker. Thanks.

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

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

Re: [Django] #27402: When using i18n_patterns and prefix_default_language=False, 404 page redirects incorrectly

2016-11-29 Thread Django

#27402: When using i18n_patterns and prefix_default_language=False, 404 page
redirects incorrectly
--+
 Reporter:  Hovi  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Internationalization  |  Version:  1.10
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"b8a815e9dfea89034ede7ff786551f89af84a31b" b8a815e9]:
 {{{
 #!CommitTicketReference repository=""
 revision="b8a815e9dfea89034ede7ff786551f89af84a31b"
 Fixed #27402 -- Fixed incorrect LocaleMiddleware redirects with
 prefix_default_language=False.
 }}}

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

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

Re: [Django] #24646: File names jinja2.py cannot import jinja2

2016-11-29 Thread Django

#24646: File names jinja2.py cannot import jinja2
-+-
 Reporter:  Daniel Greenfeld |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  jinja2   | 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 taigit):

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

Re: [Django] #24646: File names jinja2.py cannot import jinja2

2016-11-29 Thread Django

#24646: File names jinja2.py cannot import jinja2
-+-
 Reporter:  Daniel Greenfeld |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  jinja2   | 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 taigit):

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


Comment:

 The previous fix still has the same problem and causes a django error.
 see: http://stackoverflow.com/questions/40873096/error-when-using-jinja2
 -as-django-template-engine-cannot-import-name-environme/40873097#40873097

 A fix that will get rid of the problem:
 change:  myproject/jinja2.py
 to  myproject/jinja2_bridge.py

 in the documentation.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.91d0ba3a25b1dd4a0dcbe17b0b371f49%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #27552: add docs/tests for GEOSGeometry.normalize()

2016-11-29 Thread Django

#27552: add docs/tests for GEOSGeometry.normalize()
+
   Reporter:  Sergey Fedoseev   |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  GIS   |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  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/053.f7f1f6a26a66115738ac8b68d4f3e7d8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27552: add docs/tests for GEOSGeometry.normalize()

2016-11-29 Thread Django

#27552: add docs/tests for GEOSGeometry.normalize()
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 Type:   |  Fedoseev
  Cleanup/optimization   |   Status:  assigned
Component:  GIS  |  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 Sergey Fedoseev):

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

Re: [Django] #27543: AttributeError: '_Frame' object has no attribute 'f_back' / Django and celery error logging gone wrong

2016-11-29 Thread Django

#27543: AttributeError: '_Frame' object has no attribute 'f_back' / Django and
celery error logging gone wrong
-+-
 Reporter:  Simon Chenard|Owner:  (none)
 Type:  Bug  |   Status:  closed
Component:  Error reporting  |  Version:  1.10
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  celery logging   | Triage Stage:
  traceback  |  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:   => needsinfo


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.e71e38535fb36d23368c54eaf13cb057%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27549: django.utils.functional.lazy cannot be used with regular expressions module (re)

2016-11-29 Thread Django

#27549: django.utils.functional.lazy cannot be used with regular expressions 
module
(re)
---+--
 Reporter:  Daniel Hahler  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Utilities  |  Version:  master
 Severity:  Normal |   Resolution:  needsinfo
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Tim Graham):

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


Comment:

 Please reopen if anyone has an idea about an implementation or can provide
 a patch.

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

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

Re: [Django] #27551: Search box on the Django 'Documentation' page is not behaving as expected

2016-11-29 Thread Django

#27551: Search box on the Django 'Documentation' page is not behaving as 
expected
---+--
 Reporter:  Sacha  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.10
 Severity:  Normal |   Resolution:  invalid
 Keywords:  Seach  | 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:   => invalid


Comment:

 This is tracked in https://github.com/django/djangoproject.com/issues/713.

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

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

Re: [Django] #27544: F() Expressions updating dates in .update() field fails on SQLite

2016-11-29 Thread Django

#27544: F() Expressions updating dates in .update() field fails on SQLite
-+-
 Reporter:  Gary Graham  |Owner:  Andrew
 |  Nester
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  F()  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"75de55f1f381880348ad5215e15604a83f8971a5" 75de55f1]:
 {{{
 #!CommitTicketReference repository=""
 revision="75de55f1f381880348ad5215e15604a83f8971a5"
 [1.10.x] Fixed #27544 -- Fixed QuerySet.update(dt=F('dt') + timedelta)
 crash on SQLite.

 Backport of ade52ef71f04e57e217585358cb289098260e3ec from master
 }}}

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

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

Re: [Django] #27544: F() Expressions updating dates in .update() field fails on SQLite

2016-11-29 Thread Django

#27544: F() Expressions updating dates in .update() field fails on SQLite
-+-
 Reporter:  Gary Graham  |Owner:  Andrew
 |  Nester
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  F()  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"ade52ef71f04e57e217585358cb289098260e3ec" ade52ef7]:
 {{{
 #!CommitTicketReference repository=""
 revision="ade52ef71f04e57e217585358cb289098260e3ec"
 Fixed #27544 -- Fixed QuerySet.update(dt=F('dt') + timedelta) crash on
 SQLite.
 }}}

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

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

[Django] #27551: Search box on the Django 'Documentation' page is not behaving as expected

2016-11-29 Thread Django

1. Go to https://docs.djangoproject.com/en/1.10/
2. In the search box (top right of the screen) enter for example 'php' and
hit enter-key on keyboard

Result:
375 results for ''php'' in version 1.10

You can replace "php" with virtually anything, it always seems to returns:
375 results for [something] in version 1.10 and pages 1 of 38

I wanted to search for MathJax and it returned 375 results for MathJax in
version 1.10 with mostly empty canvas with pages 1 of 38 but no search
results.

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

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

Re: [Django] #27550: add version of GEOSGeometry.normalize() that returns new geometry

2016-11-29 Thread Django

#27550: add version of GEOSGeometry.normalize() that returns new geometry
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 |  Fedoseev
 Type:  New feature  |   Status:  assigned
Component:  GIS  |  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
-+-

Comment (by Claude Paroz):

 I'm not sure. Could you audit other methods and tell us if the use case
 could be applied to other methods? Then we might better recommend using
 the `clone()` method before normalizing the geometry.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.fc5890208c76b9adba02d845a8a48d9c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27549: django.utils.functional.lazy cannot be used with regular expressions module (re)

2016-11-29 Thread Django

#27549: django.utils.functional.lazy cannot be used with regular expressions 
module
(re)
---+--
 Reporter:  Daniel Hahler  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Utilities  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by Claude Paroz):

 In general, `lazy` stuff in Django is safe for Django's own code, but not
 for any Python code. It's explained for example in
 https://docs.djangoproject.com/en/stable/topics/i18n/translation/#working-
 with-lazy-translation-objects

 If you think a fix is possible for this, why not, but I think you are not
 the first to try and I'm not sure it's possible.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.70c5ce72a029603cf9490a3e224a6789%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27544: F() Expressions updating dates in .update() field fails on SQLite

2016-11-29 Thread Django

#27544: F() Expressions updating dates in .update() field fails on SQLite
-+-
 Reporter:  Gary Graham  |Owner:  Andrew
 |  Nester
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  F()  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz):

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

Re: [Django] #27550: add version of GEOSGeometry.normalize() that returns new geometry

2016-11-29 Thread Django

#27550: add version of GEOSGeometry.normalize() that returns new geometry
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 |  Fedoseev
 Type:  New feature  |   Status:  assigned
Component:  GIS  |  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
-+-
Description changed by Sergey Fedoseev:

Old description:

> GEOSGeometry.normalize() normalizes geometry in-place. In some cases it
> would be more convenient to have a cloned normalized geometry for the
> code conciseness.
> We could add `clone` kwarg to this method similarly to
> [https://docs.djangoproject.com/en/1.10/ref/contrib/gis/geos/#django.contrib.gis.geos.GEOSGeometry.clone
> GEOSGeometry.clone()] or we could add the `normalized` property.

New description:

 GEOSGeometry.normalize() normalizes geometry in-place. In some cases it
 would be more convenient to have a cloned normalized geometry for the code
 conciseness.
 We could add `clone` kwarg to this method similarly to
 
[https://docs.djangoproject.com/en/1.10/ref/contrib/gis/geos/#django.contrib.gis.geos.GEOSGeometry.transform
 GEOSGeometry.transform()] or we could add the `normalized` property.

--

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.0e083609d563250b0c3adfe82a2e5a0e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27550: add version of GEOSGeometry.normalize() that returns new geometry

2016-11-29 Thread Django

#27550: add version of GEOSGeometry.normalize() that returns new geometry
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 |  Fedoseev
 Type:  New feature  |   Status:  assigned
Component:  GIS  |  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 Sergey Fedoseev):

 * status:  new => assigned
 * owner:  nobody => Sergey Fedoseev


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.f8847305b2e4bb695994ccf6e5978eb6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #27550: add version of GEOSGeometry.normalize() that returns new geometry

2016-11-29 Thread Django

#27550: add version of GEOSGeometry.normalize() that returns new geometry
---+
   Reporter:  Sergey Fedoseev  |  Owner:  nobody
   Type:  New feature  | Status:  new
  Component:  GIS  |Version:  master
   Severity:  Normal   |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+
 GEOSGeometry.normalize() normalizes geometry in-place. In some cases it
 would be more convenient to have a cloned normalized geometry for the code
 conciseness.
 We could add `clone` kwarg to this method similarly to
 
[https://docs.djangoproject.com/en/1.10/ref/contrib/gis/geos/#django.contrib.gis.geos.GEOSGeometry.clone
 GEOSGeometry.clone()] or we could add the `normalized` property.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.3c15d72550f95885e7e0b7230e8ab596%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26632: System check for list_display_links ignores value of ModelAdmin.get_list_display()

2016-11-29 Thread Django

#26632: System check for list_display_links ignores value of
ModelAdmin.get_list_display()
---+
 Reporter:  Zach Borboa|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Anton Samarchyan):

 * needs_tests:  1 => 0


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

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

Re: [Django] #26632: System check for list_display_links ignores value of ModelAdmin.get_list_display()

2016-11-29 Thread Django

#26632: System check for list_display_links ignores value of
ModelAdmin.get_list_display()
---+
 Reporter:  Zach Borboa|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Anton Samarchyan):

 Replying to [comment:3 Simon Charette]:
 > What about adding a hint to the error that you should override
 `get_list_display_link()` to return dynamic results if
 `get_list_display()` was overrode?
 Currently, I silence all errors if get_list_display() is overridden.  Do
 you want to bring the errors back or create a new error or else?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.c9b0f8ca6ca0950694b4f069f646e84d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #27549: django.utils.functional.lazy cannot be used with regular expressions module (re)

2016-11-29 Thread Django

#27549: django.utils.functional.lazy cannot be used with regular expressions 
module
(re)
-+
   Reporter:  Daniel Hahler  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Utilities  |Version:  master
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 {{{
 from django.utils.functional import lazy
 import re

 f = lazy(lambda: 's', str)()
 re.match('s', f)
 }}}

 results in `TypeError: expected string or bytes-like object`.

 This gets generated in
 
https://github.com/python/cpython/blob/e02afa7a78f1515dd7386912812685fb4d519a44/Modules/_sre.c#L338-L342,
 where the `PyObject_GetBuffer` call appears to fail.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.abb9cd4b2090c51cd288ec6a46d4076d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23504: Oracle GIS test failures

2016-11-29 Thread Django

#23504: Oracle GIS test failures
+--
 Reporter:  Tim Graham  |Owner:  Tim Graham
 Type:  Bug |   Status:  closed
Component:  GIS |  Version:  master
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by Tim Graham ):

 In [changeset:"fb3716b15679bc27926aebfd7c6ca9a8b3e986c3" fb3716b]:
 {{{
 #!CommitTicketReference repository=""
 revision="fb3716b15679bc27926aebfd7c6ca9a8b3e986c3"
 Enabled GeoQuerySetTest.test_unionagg on Oracle; refs #23504.

 It's not clear when it started to work.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.f442b39030304aa112daf080f6b4dbb4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25569: Add a friendly error report when using select_related() on a reverse relation

2016-11-29 Thread Django

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

Comment:

Hi Vincent,

Thanks for your efforts, and sorry for your time, but I agree with Tim:
This ticket would have been nice to add early in the 1.8 lifecycle, but
it's become much less valuable now. Most of the people who wanted to
upgrade from pre-1.8 have already done so. Your latest suggestion is
indeed simple, but IMO doesn't really add much value, and without the
"help upgrade to 1.8" motive, indeed sets a bad precedent for adding
unnecessary details to an error message.

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

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

Re: [Django] #27548: Documentation missing section about adding your app to INSTALLED_APPS in settings

2016-11-29 Thread Django

#27548: Documentation missing section about adding your app to INSTALLED_APPS in
settings
+--
 Reporter:  nvrrdt  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Documentation   |  Version:  1.10
 Severity:  Normal  |   Resolution:
 Keywords:  INSTALLED_APPS  | 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):

 Which page contains the "First steps" section that you mentioned? For what
 it's worth, the template loading process is briefly described
 [https://docs.djangoproject.com/en/1.10/intro/tutorial03/#write-views-
 that-actually-do-something in the tutorial]. Did you complete 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/064.f45e3ec99d9a262fa1a4d12b441f725e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27544: F() Expressions updating dates in .update() field fails on SQLite

2016-11-29 Thread Django

#27544: F() Expressions updating dates in .update() field fails on SQLite
-+-
 Reporter:  Gary Graham  |Owner:  Andrew
 |  Nester
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  F()  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Andrew Nester):

 * owner:  nobody => Andrew Nester
 * status:  new => assigned


Comment:

 I added pull request for this issue
 [https://github.com/django/django/pull/7630 PR]

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

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

Re: [Django] #27546: Replace hardcoded class names in repr-methods

2016-11-29 Thread Django

#27546: Replace hardcoded class names in __repr__-methods
-+-
 Reporter:  Mads Jensen  |Owner:  Adiyat
 Type:   |  Mubarak
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  1.10
 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
-+-

Comment (by Mads Jensen):

 Ticket will be closed when a maintainer merges the changes and marks it as
 solved.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.259694957507bd9ed2d9089347f28750%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #27548: Documentation missing section about adding your app to INSTALLED_APPS in settings

2016-11-29 Thread Django

#27548: Documentation missing section about adding your app to INSTALLED_APPS in
settings
-+
   Reporter:  nvrrdt |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Documentation  |Version:  1.10
   Severity:  Normal |   Keywords:  INSTALLED_APPS
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 I'm a first time django user and after reading the documentation I started
 my first experiment. There I encountered a TemplateDoesNotExist error and
 I had to resort to Stack Overflow to find a solution, which was to add the
 name of my app to INSTALLED_APPS in settings.
 Shouldn't this be mentioned in the documentation ('first steps' section)?

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

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

Re: [Django] #27547: Unicode in Textarea breaks rendering

2016-11-29 Thread Django

#27547: Unicode in Textarea breaks rendering
+--
 Reporter:  Nitesh Lohchab  |Owner:  nobody
 Type:  Uncategorized   |   Status:  closed
Component:  Uncategorized   |  Version:  1.10
 Severity:  Normal  |   Resolution:  worksforme
 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 Claude Paroz):

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


Comment:

 It is highly unlikely that the bug is in Django. The string you mention is
 already unicode due to the `from __future__ import unicode_literals`
 import at the top of `django/forms/widgets.py`.
 Please use TicketClosingReasons/UseSupportChannels first to determine the
 problem, and reopen the ticket if you can demonstrate that Django is at
 fault.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.847af26ca8d66e3bc063334a5a9b1796%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

48 matches

Mail list logo