[Django] #31484: Possibility to provide additional Context to Render a FlatPage

[Django]

#31484: Possibility to provide additional Context to Render a FlatPage
-+-
   Reporter:  thaxy  |  Owner:  nobody
   Type:  New| Status:  new
  feature|
  Component: |Version:
  contrib.flatpages  |   Keywords:  flatpage context
   Severity:  Normal |  template render
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 Hello,

 In one of my projects, I am using the Django flatpages app/feature. This
 worked fine so far but I have stumbled across a use case where I want to
 {% include %} another template within the template of my flatpage. The
 included template requires additional context data to work correctly.

 The current implementation of the render function of the flatpage doesn't
 allow the developer to add additional context data other than the flatpage
 itself. (see:
 
https://github.com/django/django/blob/master/django/contrib/flatpages/views.py#L69).

 One solution could be to allow additional `**kwargs` to be passed to the
 render_flatpage function eventually being used to call the template.render
 function.

 Is this worth thinking about? In my opinion, this could be an improvement
 - that's why I am writing to you. I could also try to create a PR
 according to the guidelines if you think this is an improvement.

 Some code to illustrate the problem:

 **urls.py:**
 {{{
 path('texte/', views.flatpage, {'url': '/texte/'}, name='texte')
 }}}



 **texte.html:**
 {{{
 {% extends 'base.html' %}

 {% block content %}
 
 {{ flatpage.content }}
 
 {% include 'texte/uebersicht.html' %}
 {% endblock content %}
 }}}


 **texte/uebersicht.html:**
 {{{

 
 {% for p in prosa %}  
 
 {{ p }}
 
 {% empty %}
 keine inhalte gefunden
 {% endfor %}
 
 }}}

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

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

Re: [Django] #31416: FieldError when migrating field to new model subclass.

[Django]

#31416: FieldError when migrating field to new model subclass.
---+
 Reporter:  Eduard Anghel  |Owner:  Nan Liu
 Type:  Bug|   Status:  assigned
Component:  Migrations |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by felixxm):

 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.6c714fb1287226a5d8583db4d2949574%40djangoproject.com.

Re: [Django] #31416: FieldError when migrating field to new model subclass.

[Django]

#31416: FieldError when migrating field to new model subclass.
---+
 Reporter:  Eduard Anghel  |Owner:  Nan Liu
 Type:  Bug|   Status:  new
Component:  Migrations |  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 felixxm):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/12754 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.0721bfcada04dfc1ac6c2d6d733d77fa%40djangoproject.com.

Re: [Django] #30165: Deprecate ugettext(), ugettext_lazy(), ugettext_noop(), ungettext(), and ungettext_lazy()

[Django]

#30165: Deprecate ugettext(), ugettext_lazy(), ugettext_noop(), ungettext(), and
ungettext_lazy()
-+-
 Reporter:  Jon Dufresne |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:   |  Version:  master
  Internationalization   |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"c335f168553d9a664879c99187ee9222bd479f45" c335f168]:
 {{{
 #!CommitTicketReference repository=""
 revision="c335f168553d9a664879c99187ee9222bd479f45"
 [3.0.x] Refs #30165 -- Removed obsolete doc references to deprecated
 ugettext() & co.

 The u-prefixed variants were removed from the documentation in
 6eb4996672ca5ccaba20e468d91a83d1cd019801.
 Backport of fb21625270ab169fd436c36dd51acb642a97ee50 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.356c241025fc600ebf51eb9f9b983097%40djangoproject.com.

Re: [Django] #30165: Deprecate ugettext(), ugettext_lazy(), ugettext_noop(), ungettext(), and ungettext_lazy()

[Django]

#30165: Deprecate ugettext(), ugettext_lazy(), ugettext_noop(), ungettext(), and
ungettext_lazy()
-+-
 Reporter:  Jon Dufresne |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:   |  Version:  master
  Internationalization   |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by GitHub ):

 In [changeset:"fb21625270ab169fd436c36dd51acb642a97ee50" fb216252]:
 {{{
 #!CommitTicketReference repository=""
 revision="fb21625270ab169fd436c36dd51acb642a97ee50"
 Refs #30165 -- Removed obsolete doc references to deprecated ugettext() &
 co.

 The u-prefixed variants were removed from the documentation in
 6eb4996672ca5ccaba20e468d91a83d1cd019801.
 }}}

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

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

Re: [Django] #31416: FieldError when migrating field to new model subclass.

[Django]

#31416: FieldError when migrating field to new model subclass.
---+
 Reporter:  Eduard Anghel  |Owner:  Nan Liu
 Type:  Bug|   Status:  new
Component:  Migrations |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Nan Liu):

 Replying to [comment:21 felixxm]:
 > Nan Liu, please don't close tickets that are not fixed. We first need to
 have, review and merge patch.

 felixxm, my bad. sorry about that

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

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

Re: [Django] #31477: Simplify signature of `DatabaseOperations.execute_sql_flush()`

[Django]

#31477: Simplify signature of `DatabaseOperations.execute_sql_flush()`
--+
 Reporter:  Jon Dufresne  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Uncategorized |  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 GitHub ):

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


Comment:

 In [changeset:"5673d4b10240b1b00bdf060fb7ac6bef858f38a3" 5673d4b]:
 {{{
 #!CommitTicketReference repository=""
 revision="5673d4b10240b1b00bdf060fb7ac6bef858f38a3"
 Fixed #31477 -- Removed "using" argument from
 DatabaseOperations.execute_sql_flush().
 }}}

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

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

Re: [Django] #24559: MigrationLoader.load_disk ImportError handling differs under py3/pypy vs py2

[Django]

#24559: MigrationLoader.load_disk ImportError handling differs under py3/pypy vs
py2
-+-
 Reporter:  Keryn Knight |Owner:  Jon
 |  Dufresne
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"661e39c8d5bb05d8ebe8492912bf9f63453b279f" 661e39c8]:
 {{{
 #!CommitTicketReference repository=""
 revision="661e39c8d5bb05d8ebe8492912bf9f63453b279f"
 Fixed #24559 -- Made MigrationLoader.load_disk() catch more specific
 ModuleNotFoundError.

 Avoids inspecting the exception message, which is not considered a
 stable API and can change across Python versions.

 ModuleNotFoundError was introduced in Python 3.6. It is a subclass of
 ImportError that is raised when the imported module does not exist. It
 is not raised for other errors that can occur during an import. This
 exception instance has the property "name" which holds the name of
 module that failed to import.
 }}}

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

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

Re: [Django] #24559: MigrationLoader.load_disk ImportError handling differs under py3/pypy vs py2

[Django]

#24559: MigrationLoader.load_disk ImportError handling differs under py3/pypy vs
py2
-+-
 Reporter:  Keryn Knight |Owner:  Jon
 |  Dufresne
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * owner:  nobody => Jon Dufresne
 * status:  new => assigned
 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #31416: FieldError when migrating field to new model subclass.

[Django]

#31416: FieldError when migrating field to new model subclass.
---+
 Reporter:  Eduard Anghel  |Owner:  Nan Liu
 Type:  Bug|   Status:  new
Component:  Migrations |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by felixxm):

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


Comment:

 Nan Liu, please don't close tickets that are not fixed. We first need to
 have, review and merge 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.ff63c3651e2792d019acdd1817d7175b%40djangoproject.com.

Re: [Django] #31483: Remove admin change_form.js dependency on jQuery.

[Django]

#31483: Remove admin change_form.js dependency on jQuery.
-+-
 Reporter:  Jon Dufresne |Owner:  Jon
 Type:   |  Dufresne
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * owner:  nobody => Jon Dufresne
 * status:  new => assigned
 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #29069: Static file serving does not call request_finished signal

[Django]

#29069: Static file serving does not call request_finished signal
-+-
 Reporter:  André Cruz   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  HTTP handling|  Version:  3.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  streamingresponse| Triage Stage:  Accepted
  request_finished   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"141ab6bc6d93d3a91259896f6ea3b7485172df88" 141ab6bc]:
 {{{
 #!CommitTicketReference repository=""
 revision="141ab6bc6d93d3a91259896f6ea3b7485172df88"
 Refs #29069 -- Added test for calling request_finished signal by static
 file responses.

 Fixed in 41a3b3d18647b258331104520e76f977406c590d.
 }}}

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

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

Re: [Django] #31481: Admin crash when using functions in model meta ordering of o2o primary key. (was: Using model functions in model meta ordering fails in admin)

[Django]

#31481: Admin crash when using functions in model meta ordering of o2o primary 
key.
+--
 Reporter:  Gergely Kalmár  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  contrib.admin   |  Version:  master
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by felixxm):

 * status:  new => closed
 * version:  3.0 => master
 * resolution:   => fixed


Comment:

 Thanks for this ticket. It was fixed in
 013147fae2b9168b06c495aa78c10725cab294cd (I'm not marking this as a
 duplicate because it's a different scenario).

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

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

Re: [Django] #31480: Accessing admin panel doesn't work. (was: Accessing admin panel.)

[Django]

#31480: Accessing admin panel doesn't work.
+--
 Reporter:  Abhishek Kumar  |Owner:  nobody
 Type:  Uncategorized   |   Status:  closed
Component:  contrib.admin   |  Version:  3.0
 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
+--

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

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

Re: [Django] #31480: Accessing admin panel. (was: accessing admin panel)

[Django]

#31480: Accessing admin panel.
+--
 Reporter:  Abhishek Kumar  |Owner:  nobody
 Type:  Uncategorized   |   Status:  closed
Component:  contrib.admin   |  Version:  3.0
 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 felixxm):

 * owner:  (none) => nobody
 * resolution:   => worksforme
 * status:  new => closed
 * component:  Error reporting => contrib.admin


Comment:

 Admin works for me. I strongly believe that there is some issue in your
 projects, e.g. you're using unsupported database or 3rd party packages
 that don't support Django 3.0. Nevertheless, it's hard to say without a
 sample project. I would start from
 [https://code.djangoproject.com/wiki/TicketClosingReasons/UseSupportChannels
 support channels].

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

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

Re: [Django] #31416: FieldError when migrating field to new model subclass.

[Django]

#31416: FieldError when migrating field to new model subclass.
---+
 Reporter:  Eduard Anghel  |Owner:  Nan Liu
 Type:  Bug|   Status:  closed
Component:  Migrations |  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 Nan Liu):

 I am wondering when people are gonna look at the pull request? since if it
 is accepted, then I would possibly gain some extra credits for my class!
 much appreciated!!

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

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

Re: [Django] #31416: FieldError when migrating field to new model subclass.

[Django]

#31416: FieldError when migrating field to new model subclass.
---+
 Reporter:  Eduard Anghel  |Owner:  Nan Liu
 Type:  Bug|   Status:  closed
Component:  Migrations |  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
---+
Changes (by Nan Liu):

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


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

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

Re: [Django] #31483: Remove admin change_form.js dependency on jQuery.

[Django]

#31483: Remove admin change_form.js dependency on jQuery.
-+-
 Reporter:  Jon Dufresne |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.admin|  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 Jon Dufresne):

 * has_patch:  0 => 1


Comment:

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

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

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

[Django] #31483: Remove admin change_form.js dependency on jQuery.

[Django]

#31483: Remove admin change_form.js dependency on jQuery.
+
   Reporter:  Jon Dufresne  |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  contrib.admin |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 |
+
 
https://github.com/django/django/blob/3.0/django/contrib/admin/static/admin/js/change_form.js

 The file currently uses jQuery for two purposes:

 1. To add an onclick handler to elements with the `add-another` class.
 This event handler has been unused since
 07988744b347302925bc6cc66511e34224db55ab (Django 1.8) when the class was
 removed. Rather than porting and maintaining this code block, it can be
 removed.

 2. To find the first visible, enabled input and then focus it. This code
 is simple enough to port.

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

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

[Django] #31482: The templatetags folder doesn't need to be a package.

[Django]

#31482: The templatetags folder doesn't need to be a package.
-+-
   Reporter:  Nat S  |  Owner:  nobody
  Dunn   |
   Type: | Status:  new
  Cleanup/optimization   |
  Component: |Version:  3.0
  Documentation  |
   Severity:  Normal |   Keywords:  templatetags
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 In [https://docs.djangoproject.com/en/3.0/howto/custom-template-tags| the
 documentation], it says "The app should contain a templatetags directory,
 at the same level as models.py, views.py, etc. If this doesn’t already
 exist, create it - **don’t forget the _ _ init _ _.py file to ensure the
 directory is treated as a Python package**."

 The directory doesn't need to be a package.

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

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

[Django] #31481: Using model functions in model meta ordering fails in admin

[Django]

#31481: Using model functions in model meta ordering fails in admin
-+
   Reporter:  GergelyKalmar  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  contrib.admin  |Version:  3.0
   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  |
-+
 Let's assume we have two models as follows:

 {{{
 from django.db import models


 class ExampleObject(models.Model):
 some_field = models.CharField(max_length=50)

 class Meta:
 ordering = [models.functions.Lower('some_field')]


 class ExampleExtension(models.Model):
 example_object = models.OneToOneField(
 ExampleObject, primary_key=True, on_delete=models.PROTECT
 )
 }}}

 If I register the latter model in admin:
 {{{
 from django.contrib import admin

 from myapp import models

 admin.site.register(models.ExampleExtension)
 }}}

 I get the following error:
 {{{
 FieldError at /admin/myapp/exampleextension/
 Cannot resolve keyword 'some_field' into field. Choices are:
 example_object, example_object_id
 }}}

 If I remove the `Lower` model function it works as expected. Also, the
 ordering generally seems to work fine in all other places, except in the
 admin interface. Am I doing something silly?

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

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

[Django] #31480: accessing admin panel

[Django]

#31480: accessing admin panel
---+
   Reporter:  abhiaryz |  Owner:  (none)
   Type:  Uncategorized| Status:  new
  Component:  Error reporting  |Version:  3.0
   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|
---+
 Hey,
 Recently I started using django3, in this new version whenever I am try to
 access my admin panel, it stops automatically. But reset of the urls are
 working fine. Like if I go to 127.0.0.1:8000/api/ this url it will work
 fine but if I go to  127.0.0.1:8000/admin/ and type my username and
 password it automatically stops the server. I have tried many different
 project. But same problems occurs .

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

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

Re: [Django] #24559: MigrationLoader.load_disk ImportError handling differs under py3/pypy vs py2

[Django]

#24559: MigrationLoader.load_disk ImportError handling differs under py3/pypy vs
py2
--+
 Reporter:  Keryn Knight  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Migrations|  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 Jon Dufresne):

 * has_patch:  0 => 1


Comment:

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

 Python 2 is no longer suported, but this bug report shows why inspecting
 an exception's message isn't a stable API. The above PR changes the code
 to use the exception type and its "name" 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.0ed2acc5638aa7fbeaaa53c4ecf09990%40djangoproject.com.