Re: [Django] #28747: Unclosed single quotes in django/conf/global_settings.py comments

2017-10-26 Thread Django 
#28747: Unclosed single quotes in django/conf/global_settings.py comments
-+-
 Reporter:  Oleksandr|Owner:  Duarte
 Type:   |  Fernandes
  Cleanup/optimization   |   Status:  closed
Component:  Core (Other) |  Version:  1.11
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  Comment, typo| 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:"8038b5c10e7bef8b62dbfaec796ef8f3cd52f88a" 8038b5c]:
 {{{
 #!CommitTicketReference repository=""
 revision="8038b5c10e7bef8b62dbfaec796ef8f3cd52f88a"
 [1.11.x] Fixed #28747 -- Fixed typos in django/conf/global_settings.py
 comments.

 Backport of 019c2600a6771d2cd0574062dee468ce96d7e69d 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.0404dcaaf6656966f1235b5c5bcebba6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28747: Unclosed single quotes in django/conf/global_settings.py comments

2017-10-26 Thread Django 
#28747: Unclosed single quotes in django/conf/global_settings.py comments
-+-
 Reporter:  Oleksandr|Owner:  Duarte
 Type:   |  Fernandes
  Cleanup/optimization   |   Status:  closed
Component:  Core (Other) |  Version:  1.11
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  Comment, typo| 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:"ecfa7e570f5ec29010021241861eb5b43000bb48" ecfa7e5]:
 {{{
 #!CommitTicketReference repository=""
 revision="ecfa7e570f5ec29010021241861eb5b43000bb48"
 [2.0.x] Fixed #28747 -- Fixed typos in django/conf/global_settings.py
 comments.

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

Re: [Django] #28747: Unclosed single quotes in django/conf/global_settings.py comments

2017-10-26 Thread Django 
#28747: Unclosed single quotes in django/conf/global_settings.py comments
-+-
 Reporter:  Oleksandr|Owner:  Duarte
 Type:   |  Fernandes
  Cleanup/optimization   |   Status:  closed
Component:  Core (Other) |  Version:  1.11
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  Comment, typo| 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:"019c2600a6771d2cd0574062dee468ce96d7e69d" 019c260]:
 {{{
 #!CommitTicketReference repository=""
 revision="019c2600a6771d2cd0574062dee468ce96d7e69d"
 Fixed #28747 -- Fixed typos in django/conf/global_settings.py comments.
 }}}

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

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

Re: [Django] #28747: Unclosed single quotes in django/conf/global_settings.py comments (was: Unclosed single quotes in example)

2017-10-26 Thread Django 
#28747: Unclosed single quotes in django/conf/global_settings.py comments
-+-
 Reporter:  Oleksandr|Owner:  Duarte
 Type:   |  Fernandes
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  Comment, typo| 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):

 * component:  Uncategorized => Core (Other)
 * 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/069.04c6631f9b39ffaa0e382749e7e03435%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28726: Brackets illegal in DEFAULT_FROM_EMAIL name part

2017-10-26 Thread Django 
#28726: Brackets illegal in DEFAULT_FROM_EMAIL name part
-+-
 Reporter:  Ciaran Courtney  |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Core (Mail)  |  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  email| Triage Stage:  Accepted
  DEFAULT_FROM_EMAIL |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Rebeca Sarai):

 * status:  assigned => new
 * owner:  Rebeca Sarai => (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/072.dee0558cf16e78c9edc5da9792bd5a06%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28726: Brackets illegal in DEFAULT_FROM_EMAIL name part

2017-10-26 Thread Django 
#28726: Brackets illegal in DEFAULT_FROM_EMAIL name part
-+-
 Reporter:  Ciaran Courtney  |Owner:  Rebeca
 |  Sarai
 Type:  Bug  |   Status:  assigned
Component:  Core (Mail)  |  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  email| Triage Stage:  Accepted
  DEFAULT_FROM_EMAIL |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Rebeca Sarai):

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

Re: [Django] #28747: Unclosed single quotes in example

2017-10-26 Thread Django 
#28747: Unclosed single quotes in example
-+-
 Reporter:  Oleksandr|Owner:  Duarte
 Type:   |  Fernandes
  Cleanup/optimization   |   Status:  assigned
Component:  Uncategorized|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  Comment, typo| Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Duarte Fernandes):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/9293 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/069.f460f28bb52dff560fa489e1c3dbe5a8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28747: Unclosed single quotes in example

2017-10-26 Thread Django 
#28747: Unclosed single quotes in example
-+-
 Reporter:  Oleksandr|Owner:  Duarte
 Type:   |  Fernandes
  Cleanup/optimization   |   Status:  assigned
Component:  Uncategorized|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  Comment, typo| Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Duarte Fernandes):

 Just submitted a PR to `django:stable/1.11.x`, as this ticket has `1.11`
 for its version. Please let me know if I should apply these changes to the
 master as well.

 Final work:


 {{{
 #re.compile(r'^/favicon.ico$),
 #re.compile(r'^/robots.txt$),
 #re.compile(r'^/phpmyadmin/),
 }}}

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

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

Re: [Django] #28747: Unclosed single quotes in example

2017-10-26 Thread Django 
#28747: Unclosed single quotes in example
-+-
 Reporter:  Oleksandr|Owner:  Duarte
 Type:   |  Fernandes
  Cleanup/optimization   |   Status:  assigned
Component:  Uncategorized|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  Comment, typo| Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Duarte Fernandes):

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

[Django] #28747: Unclosed single quotes in example

2017-10-26 Thread Django 
#28747: Unclosed single quotes in example
-+-
   Reporter:  Oleksandr  |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |
  Component: |Version:  1.11
  Uncategorized  |
   Severity:  Normal |   Keywords:  Comment, typo
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 In file: ''**django/conf/global_settings.py**''
 In lines ''251-253'' there are an example with list of compiled RegExps.
 Three of them contain unclosed quotes.
 Here is the code:

 {{{
 #IGNORABLE_404_URLS = [
 #re.compile(r'^/apple-touch-icon.*\.png$'),
 #re.compile(r'^/favicon.ico$),
 #re.compile(r'^/robots.txt$),
 #re.compile(r'^/phpmyadmin/),
 #re.compile(r'\.(cgi|php|pl)$'),
 #]
 }}}

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

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

Re: [Django] #28746: New model missing abstract model inherited Meta/Options

2017-10-26 Thread Django 
#28746: New model missing abstract model inherited Meta/Options
-+-
 Reporter:  JP Navarro   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  abstract Meta| Triage Stage:
  inheritance|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by JP Navarro):

 This issue is related to [Ticket
 #5793|https://code.djangoproject.com/ticket/5793].

 I submitted this as a bug because the behavior changed. Prior to 1.10
 custom Meta attributes were passed on, as of 1.10.7 they are filtered out.

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

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

Re: [Django] #28205: Document that ModelAdmin.prepopulated_fields only works on empty forms

2017-10-26 Thread Django 
#28205: Document that ModelAdmin.prepopulated_fields only works on empty forms
-+-
 Reporter:  Ju   |Owner:  Botond
 Type:   |  Béres
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  prepopulated_fields  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Botond Béres):

 * has_patch:  0 => 1


Comment:

 Opened a [https://github.com/django/django/pull/9290 small PR] which adds
 in the `prepopulated_fields` docs that it only works on empty forms.

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

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

Re: [Django] #28746: New model missing abstract model inherited Meta/Options

2017-10-26 Thread Django 
#28746: New model missing abstract model inherited Meta/Options
-+-
 Reporter:  JP Navarro   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  abstract Meta| Triage Stage:
  inheritance|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by JP Navarro):

 Just noticed the relevant migration is missing the db_name:

 {{{
 options={
 'abstract': 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/067.f01a124818423c4469c9f17f05b1ec20%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28205: Document that ModelAdmin.prepopulated_fields only works on empty forms

2017-10-26 Thread Django 
#28205: Document that ModelAdmin.prepopulated_fields only works on empty forms
-+-
 Reporter:  Ju   |Owner:  Botond
 Type:   |  Béres
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  prepopulated_fields  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Botond Béres):

 * owner:  James Seden Smith => Botond Béres


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

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

Re: [Django] #21080: collectstatic post-processing fails for references inside comments

2017-10-26 Thread Django 
#21080: collectstatic post-processing fails for references inside comments
-+
 Reporter:  shreyas@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.staticfiles  |  Version:  1.11
 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 Udo Schochtert):

 * version:  1.5 => 1.11


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

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

Re: [Django] #28726: Brackets illegal in DEFAULT_FROM_EMAIL name part

2017-10-26 Thread Django 
#28726: Brackets illegal in DEFAULT_FROM_EMAIL name part
-+-
 Reporter:  Ciaran Courtney  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Mail)  |  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  email| Triage Stage:  Accepted
  DEFAULT_FROM_EMAIL |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Jonatas CD):

 Should also the default value be changed to a tuple?
 Seems somewhat more coherent to me.
 What do you think?

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

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

[Django] #28746: New model missing abstract model inherited Meta/Options

2017-10-26 Thread Django 
#28746: New model missing abstract model inherited Meta/Options
-+-
   Reporter:  JP |  Owner:  nobody
  Navarro|
   Type:  Bug| Status:  new
  Component:  Database   |Version:  1.10
  layer (models, ORM)|   Keywords:  abstract Meta
   Severity:  Normal |  inheritance
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Given:

 {{{
 class AbstractGlue2Model(models.Model):
 ID = models.CharField(primary_key=True, max_length=200)
 
 class Meta:
 abstract = True
 db_name = 'glue2'
 ...
 class Contact(AbstractGlue2Model):
 Detail = models.CharField(max_length=128)
 Type = models.CharField(max_length=16)
 }}}


 A migrate that should create the new Contacts DB objects sees inherited
 fields (such as ID), but is missing Meta db_name value:


 {{{
 (Pdb) pp hints['model']
 
 (Pdb) pp hints['model']._meta.db_name
 *** AttributeError: AttributeError("'Options' object has no attribute
 'db_name'",)
 (Pdb) pp hints['model']._meta.abstract
 False
 (Pdb) pp hints['model'].ID
 
 }}}

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

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

Re: [Django] #28745: Add first page and last page links to paginator documentation

2017-10-26 Thread Django 
#28745: Add first page and last page links to paginator documentation
---+--
 Reporter:  Sam Morrow |Owner:  Sam Morrow
 Type:  New feature|   Status:  assigned
Component:  Documentation  |  Version:  1.11
 Severity:  Normal |   Resolution:
 Keywords:  pagination | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Sam Morrow):

 * status:  new => assigned
 * owner:  nobody => Sam Morrow


Old description:

> It would be good for the pagination example template to include first
> page and last page links. This seems to be more in line with the current
> convention / best practices for pagination behavior across the web.

New description:

 It would be good for the pagination example template to include first page
 and last page links. This seems to be more in line with the current
 convention / best practices for pagination behavior across the web.

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

--

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

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

[Django] #28745: Add first page and last page links to paginator documentation

2017-10-26 Thread Django 
#28745: Add first page and last page links to paginator documentation
-+
   Reporter:  Sam Morrow |  Owner:  nobody
   Type:  New feature| Status:  new
  Component:  Documentation  |Version:  1.11
   Severity:  Normal |   Keywords:  pagination
   Triage Stage:  Unreviewed |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 It would be good for the pagination example template to include first page
 and last page links. This seems to be more in line with the current
 convention / best practices for pagination behavior across the web.

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

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

[Django] #28744: enctype on if FileField

2017-10-26 Thread Django 
#28744: enctype on  if FileField
--+
   Reporter:  Thomas Güttler  |  Owner:  nobody
   Type:  Uncategorized   | Status:  new
  Component:  Uncategorized   |Version:  1.11
   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   |
--+
 I think it would be feasible to add the attribute `enctype` to html input
 elements for FileFields.

 Related docs: https://developer.mozilla.org/de/docs/Web/HTML/Element/Input
 #attr-formenctype

 My use case: to be able to stop this useless dancing in admin:


 {{{
 grep -rsi 'has_file_field' .

 ./contrib/admin/options.py:'has_file_field': True,  # FIXME -
 this should check if form or formsets have a FileField,


 ./contrib/admin/templates/admin/change_form.html:{%
 csrf_token %}{% block form_top %}{% endblock %}


 }}}

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

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

Re: [Django] #28743: Clarify the term "deployment server" in the documentation (was: What is a "deployment server"?)

2017-10-26 Thread Django 
#28743: Clarify the term "deployment server" in the documentation
--+
 Reporter:  Thomas Güttler|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.11
 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 Tim Graham):

 * stage:  Unreviewed => Accepted
 * type:  Uncategorized => Cleanup/optimization


Comment:

 It's the server to which you deploy your code. I wonder if a web search
 for [https://serverfault.com/questions/176525/what-is-deploying-a-server
 what is a deployment server] would have answered your question. I'm not
 sure if it merits further explanation in Django's documentation as I guess
 it assumes some basic knowledge in web development but you can either
 propose a patch or close this issue if this answer seems sufficient.

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

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

Re: [Django] #27025: Python 3.6 compatibility

2017-10-26 Thread Django 
#27025: Python 3.6 compatibility
--+
 Reporter:  Tim Graham|Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  Core (Other)  |  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):

 No, Django 1.8 doesn't have official support for Python 3.6 and only
 receives data loss and security fixes its end-of-life in April 2018.

 Perhaps you can use `warnings.filterwarnings()` to hide the warnings.

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

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

Re: [Django] #27025: Python 3.6 compatibility

2017-10-26 Thread Django 
#27025: Python 3.6 compatibility
--+
 Reporter:  Tim Graham|Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  Core (Other)  |  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 Jeroen Pulles):

 Would it be possible to backport dd99e69fa8f89263d0396f23e0db9aa8fa667b01
 (metaclass magic) to Django 1.8?

 I'm seeing quite a few warnings for this, hiding the more useful
 warnings...

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

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

Re: [Django] #6148: Add generic support for database schemas

2017-10-26 Thread Django 
#6148: Add generic support for database schemas
-+-
 Reporter:  Ian Kelly|Owner:  Anssi
 |  Kääriäinen
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle postgresql| Triage Stage:  Accepted
  mysql schemas  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlos Palol):

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

Re: [Django] #28743: What is a "deployment server"?

2017-10-26 Thread Django 
#28743: What is a "deployment server"?
+--
 Reporter:  Thomas Güttler  |Owner:  nobody
 Type:  Uncategorized   |   Status:  new
Component:  Documentation   |  Version:  1.11
 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 Thomas Güttler):

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

[Django] #28743: What is a "deployment server"?

2017-10-26 Thread Django 
#28743: What is a "deployment server"?
--+
   Reporter:  Thomas Güttler  |  Owner:  nobody
   Type:  Uncategorized   | Status:  new
  Component:  Uncategorized   |Version:  1.11
   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 the docs:

 > If you need to run system checks on your **deployment server**, trigger
 them explicitly using check.

 Source: https://docs.djangoproject.com/en/1.11/topics/checks/

 What is a "deployment server"?


 I tried tried to find the answer in the "Deployment checklist"
 (https://docs.djangoproject.com/en/1.11/howto/deployment/checklist/)
 But no luck. There the I find

 "application server" and "web server" and "development server".

 ... I am confused :-)

 A glossary or definition of the basics words would make it clear.

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

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

Re: [Django] #28735: Typo in django/views/templates/default_urlconf.html

2017-10-26 Thread Django 
#28735: Typo in django/views/templates/default_urlconf.html
-+-
 Reporter:  Scot Hacker  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Other) |  Version:  2.0
 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 Scot Hacker):

 D'oh! Sure enough, that was a leftover. Fixed that and yes, I now get a
 standard 404. Cheers.

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

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