[Django] #32606: Allow rich configuration of Selenium tests

[Django]

#32606: Allow rich configuration of Selenium tests
-+
   Reporter:  Dominik George |  Owner:  nobody
   Type:  New feature| Status:  new
  Component:  Testing framework  |Version:  dev
   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  |
-+
 Currently, the SeleniumTestCase allows passing  a list of browsers to run
 tests with.

 I propose to extend this feature from a flat list of strings to the
 following:

 A dictionary mapping browsers to a list of dictionaries can be passed. The
 key is the name of the browser (the same string that was currently passed
 in the browsers list), and the list contains dictionaries of capabilities
 that are passed to the respective browsers.

 The use case is testing with the same browser with different settings.
 e.g. different screen resolutions, different versions (possible with
 BrowserStack), etc.

 I am willing to implement this change if the idea is 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/055.7e641b2bf4542c9b9869c77b79c5e944%40djangoproject.com.

Re: [Django] #31840: Add Support for Cross-Origin Opener Policy header

[Django]

#31840: Add Support for Cross-Origin Opener Policy header
-+-
 Reporter:  meggles711   |Owner:
 |  meggles711
 Type:  New feature  |   Status:  closed
Component:  HTTP handling|  Version:  dev
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  COOP, security,  | Triage Stage:  Ready for
  headers|  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:"db5b75f10fe211af9fab9094f937436760db8488" db5b75f1]:
 {{{
 #!CommitTicketReference repository=""
 revision="db5b75f10fe211af9fab9094f937436760db8488"
 Fixed #31840 -- Added support for Cross-Origin Opener Policy header.

 Thanks Adam Johnson and Tim Graham for the reviews.

 Co-authored-by: Tim Graham 
 }}}

-- 
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/068.e5607cb9dc8095a5e80b3f5144356f63%40djangoproject.com.

Re: [Django] #32567: Issues with ":" and "|" characters in URLs when using LiveServerTestCase on Windows

[Django]

#32567: Issues with ":" and "|" characters in URLs when using 
LiveServerTestCase on
Windows
-+-
 Reporter:  Tim G|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  3.1
 Severity:  Normal   |   Resolution:
 Keywords:  windows, | Triage Stage:  Accepted
  liveservertestcase, path   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

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

Re: [Django] #28333: Filter and subquery for window expressions

[Django]

#28333: Filter and subquery for window expressions
-+-
 Reporter:  Mads Jensen  |Owner:  (none)
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  window orm filter| Triage Stage:  Accepted
  subquery GSoC  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Manav Agarwal):

 * owner:  Manav Agarwal => (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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.688fcfc909d0088bc5d533438e48d192%40djangoproject.com.

Re: [Django] #29850: Add window support for RowRange frames

[Django]

#29850: Add window support for RowRange frames
-+-
 Reporter:  Daniel Fuchs |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  GSoC | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Manav Agarwal):

 * owner:  Manav Agarwal => (none)
 * status:  assigned => new


-- 
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/065.ee13fd054739f44979d1379312448ea1%40djangoproject.com.

Re: [Django] #32595: mysql DatabaseSchemaEditor can't `quote_value` on byte strings

[Django]

#32595: mysql DatabaseSchemaEditor can't `quote_value` on byte strings
-+-
 Reporter:  Ryan Siemens |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 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:"682eba534f15e962d29026bfcac8dcaf4555aac0" 682eba53]:
 {{{
 #!CommitTicketReference repository=""
 revision="682eba534f15e962d29026bfcac8dcaf4555aac0"
 [3.2.x] Refs #32595 -- Added MySQL's SchemaEditor.quote_value() tests for
 values with Unicode chars.

 Backport of 3c75f1f3cac7985e8a134fc1c33eb6e01639a04b from main
 }}}

-- 
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.46036bf31b704f2aa86ff173c009b3c1%40djangoproject.com.

Re: [Django] #32595: mysql DatabaseSchemaEditor can't `quote_value` on byte strings

[Django]

#32595: mysql DatabaseSchemaEditor can't `quote_value` on byte strings
-+-
 Reporter:  Ryan Siemens |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 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:"d67d48e923eafd8ab7f8cc21985584f9606d9808" d67d48e]:
 {{{
 #!CommitTicketReference repository=""
 revision="d67d48e923eafd8ab7f8cc21985584f9606d9808"
 [3.2.x] Fixed #32595 -- Fixed SchemaEditor.quote_value() crash with bytes.

 Backport of f6018c1e63a04e0c12e2ca759e76e05ccf5e09de from main
 }}}

-- 
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.c7897b4c0e203a07eae6e0a178186b8a%40djangoproject.com.

Re: [Django] #32595: mysql DatabaseSchemaEditor can't `quote_value` on byte strings

[Django]

#32595: mysql DatabaseSchemaEditor can't `quote_value` on byte strings
-+-
 Reporter:  Ryan Siemens |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 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:"f6018c1e63a04e0c12e2ca759e76e05ccf5e09de" f6018c1e]:
 {{{
 #!CommitTicketReference repository=""
 revision="f6018c1e63a04e0c12e2ca759e76e05ccf5e09de"
 Fixed #32595 -- Fixed SchemaEditor.quote_value() crash with bytes.
 }}}

-- 
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.3de6f3c9103c08877d86223132edd217%40djangoproject.com.

Re: [Django] #32595: mysql DatabaseSchemaEditor can't `quote_value` on byte strings

[Django]

#32595: mysql DatabaseSchemaEditor can't `quote_value` on byte strings
-+-
 Reporter:  Ryan Siemens |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"3c75f1f3cac7985e8a134fc1c33eb6e01639a04b" 3c75f1f]:
 {{{
 #!CommitTicketReference repository=""
 revision="3c75f1f3cac7985e8a134fc1c33eb6e01639a04b"
 Refs #32595 -- Added MySQL's SchemaEditor.quote_value() tests for values
 with Unicode chars.
 }}}

-- 
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.a1a5e6bfa60b1e1bba9bc300c1020884%40djangoproject.com.

Re: [Django] #32595: mysql DatabaseSchemaEditor can't `quote_value` on byte strings

[Django]

#32595: mysql DatabaseSchemaEditor can't `quote_value` on byte strings
-+-
 Reporter:  Ryan Siemens |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 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 Carlton Gibson):

 * 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/066.54366b97566acb75f20a5f007cf76dd8%40djangoproject.com.

Re: [Django] #32554: Add Q.empty(), Q.TRUE, Q.FALSE, Q.any(), and Q.all()

[Django]

#32554: Add Q.empty(), Q.TRUE, Q.FALSE, Q.any(), and Q.all()
-+-
 Reporter:  jonathan-golorry |Owner:  jonathan-
 |  golorry
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  Q objects, any, all  | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

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


Comment:

 Thanks for this ticket, however I have mixed-feelings. Django API is
 already massive. IMO new hooks will make `Q` expressions more confusing
 and are not necessary per se. `Q.any()` and `Q.all()` can be replaced with
 `reduce()` (that's how we do this in Django itself, see
 
[https://github.com/django/django/blob/7c08f26bf0439c1ed593b51b51ad847f7e262bc1/django/contrib/admin/options.py#L1032
 an example]). I don't see why the new API should be preferred over an
 example with `reduce()` in
 [https://docs.djangoproject.com/en/dev/topics/db/queries/#complex-lookups-
 with-q-objects docs]. It has already been
 [https://github.com/django/django/pull/13798#issuecomment-767492096
 pointed out] that we need a good example of building `Q()` dynamically.

 About `Q.TRUE` and `Q.FALSE`, these constants are really tricky and niche.
 I don't believe that folks will not how to use them properly (I don't see
 immediate and wide use). Moreover, I'm not sure why Django should
 recommend the `pk__in=[]` lookup (and not e.g. `pk=-1`), everything
 depends on the context. It is so niche that folks should choose on their
 own.


 I strongly believe that we need a good example of building `Q()`
 dynamically with the existing API, rather than adding yet another method
 to do the same.

-- 
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/074.4366cc8d5a664a1618cf2b7afe810893%40djangoproject.com.

Re: [Django] #32605: Custom Middleware Error ====> WSGI application '.wsgi.application' could not be loaded; Error importing module.

[Django]

#32605: Custom Middleware Error > WSGI application
'.wsgi.application' could not be loaded; Error importing
module.
-+-
 Reporter:  alimp5   |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Core (System |  Version:  3.1
  checks)|
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  Middleware, WSGI-| Triage Stage:
  Error, Windows, Django3.1  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * resolution:  fixed => invalid


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

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

Re: [Django] #29127: Running tagged tests hides any with syntax errors

[Django]

#29127: Running tagged tests hides any with syntax errors
-+-
 Reporter:  Kryštof Řeháček  |Owner:  Chris
 |  Jerdonek
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  2.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  tests, tagged-   | Triage Stage:  Ready for
  tests, SyntaxError |  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:"038940cf5525c41464a1b9e9ba3801042320b0cc" 038940cf]:
 {{{
 #!CommitTicketReference repository=""
 revision="038940cf5525c41464a1b9e9ba3801042320b0cc"
 Fixed #29127 -- Prevented DiscoverRunner from hiding tagged test with
 syntax errors.

 This mades _FailedTest objects always match tags in DiscoverRunner.
 }}}

-- 
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.a6d97c589eb7b8303faccab9c2c3a408%40djangoproject.com.

Re: [Django] #32605: Custom Middleware Error ====> WSGI application '.wsgi.application' could not be loaded; Error importing module.

[Django]

#32605: Custom Middleware Error > WSGI application
'.wsgi.application' could not be loaded; Error importing
module.
-+-
 Reporter:  alimp5   |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Core (System |  Version:  3.1
  checks)|
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  Middleware, WSGI-| Triage Stage:
  Error, Windows, Django3.1  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by alimp5):

 * resolution:  invalid => 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/064.5afb979493df0b49983032107f356fc6%40djangoproject.com.

Re: [Django] #32605: Custom Middleware Error ====> WSGI application '.wsgi.application' could not be loaded; Error importing module.

[Django]

#32605: Custom Middleware Error > WSGI application
'.wsgi.application' could not be loaded; Error importing
module.
-+-
 Reporter:  alimp5   |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Core (System |  Version:  3.1
  checks)|
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  Middleware, WSGI-| Triage Stage:
  Error, Windows, Django3.1  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by alimp5):

 # FROM:
 {{{
 MIDDLEWARE = [
 'django.middleware.security.SecurityMiddleware',
 'django.contrib.sessions.middleware.SessionMiddleware',
 'django.middleware.common.CommonMiddleware',
 'django.middleware.csrf.CsrfViewMiddleware',
 'django.contrib.auth.middleware.AuthenticationMiddleware',
 'django.contrib.messages.middleware.MessageMiddleware',
 'django.middleware.clickjacking.XFrameOptionsMiddleware',

 'coffehouse.utils.middleware.CoffehouseMiddleware',<===
 ]

 }}}


  TO:
 {{{
 MIDDLEWARE = [
 'django.middleware.security.SecurityMiddleware',
 'django.contrib.sessions.middleware.SessionMiddleware',
 'django.middleware.common.CommonMiddleware',
 'django.middleware.csrf.CsrfViewMiddleware',
 'django.contrib.auth.middleware.AuthenticationMiddleware',
 'django.contrib.messages.middleware.MessageMiddleware',
 'django.middleware.clickjacking.XFrameOptionsMiddleware',

 'coffehouse.utils.middleware.CoffehouseMiddleware.CoffehouseMiddleware',
 <===
 ]

 }}}

-- 
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.2cb6ebea66276e4f18c75fc595ed3608%40djangoproject.com.

Re: [Django] #32605: Custom Middleware Error ====> WSGI application '.wsgi.application' could not be loaded; Error importing module.

[Django]

#32605: Custom Middleware Error > WSGI application
'.wsgi.application' could not be loaded; Error importing
module.
-+-
 Reporter:  alimp5   |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Core (System |  Version:  3.1
  checks)|
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  Middleware, WSGI-| Triage Stage:
  Error, Windows, Django3.1  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

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


Comment:

 Please don't use Trac as a support channel. Closing per
 TicketClosingReasons/UseSupportChannels.

-- 
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.f7bb3586ebd04c2aefe567c82cd7594f%40djangoproject.com.

Re: [Django] #32605: Custom Middleware Error ====> WSGI application '.wsgi.application' could not be loaded; Error importing module.

[Django]

#32605: Custom Middleware Error > WSGI application
'.wsgi.application' could not be loaded; Error importing
module.
-+-
 Reporter:  alimp5   |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Core (System |  Version:  3.1
  checks)|
 Severity:  Normal   |   Resolution:
 Keywords:  Middleware, WSGI-| Triage Stage:
  Error, Windows, Django3.1  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by alimp5):

 * Attachment "errors for debugging.txt" 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.df6753cc5a1a653f5c7f310f942b4b5b%40djangoproject.com.

[Django] #32605: Custom Middleware Error ====> WSGI application '.wsgi.application' could not be loaded; Error importing module.

[Django]

#32605: Custom Middleware Error > WSGI application
'.wsgi.application' could not be loaded; Error importing
module.
-+-
   Reporter:  alimp5 |  Owner:  nobody
   Type: | Status:  new
  Uncategorized  |
  Component:  Core   |Version:  3.1
  (System checks)|   Keywords:  Middleware, WSGI-
   Severity:  Normal |  Error, Windows, Django3.1
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Greetings

 Django: 3.1.7
 OS: Windows 10 - 64 bit
 Python: 3.8.6 - 64 bit

 Project Name: coffehouse
 App Names: about, stores, coffe_app

 I was creating a custom middleware for my django project. And after adding
 the path of middleware file to settings.py file (in MIDDLEWARE variable),
 I got error below:

 {{{
 raise ImproperlyConfigured(
 django.core.exceptions.ImproperlyConfigured: WSGI application
 'coffehouse.wsgi.application' could not be loaded; Error importing module.
 }}}


  settings.py:

 {{{
 INSTALLED_APPS = [
 'coffe_app.apps.CoffeAppConfig',
 'stores',
 'about',

 'django.contrib.admin',
 'django.contrib.auth',
 'django.contrib.contenttypes',
 'django.contrib.sessions',
 'django.contrib.messages',
 'django.contrib.staticfiles',
 ]

 MIDDLEWARE = [
 'django.middleware.security.SecurityMiddleware',
 'django.contrib.sessions.middleware.SessionMiddleware',
 'django.middleware.common.CommonMiddleware',
 'django.middleware.csrf.CsrfViewMiddleware',
 'django.contrib.auth.middleware.AuthenticationMiddleware',
 'django.contrib.messages.middleware.MessageMiddleware',
 'django.middleware.clickjacking.XFrameOptionsMiddleware',

 'coffehouse.utils.middleware.CoffehouseMiddleware',<===
 ]

 }}}

  coffehouse\coffehouse\utils\middleware\CoffehouseMiddleware.py:

 {{{
 class CoffehouseMiddleware (object):
 def __init__(self, get_response):
 self.get_response = get_response

 def __call__(self, request):
 response = self.get_response (request)
 return response

 def process_view (self, request, view_func, view_args, view_kwargs):
 pass

 def process_exception (self, request, exception):
 pass

 def process_template_response (self, request, response):
 pass
 }}}


  wsgi.py:

 {{{
 import os
 from django.core.wsgi import get_wsgi_application
 os.environ.setdefault('DJANGO_SETTINGS_MODULE', 'coffehouse.settings')
 application = get_wsgi_application()
 }}}

-- 
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/049.5b9a8603c05d5df3de662e50838f2b7b%40djangoproject.com.

Re: [Django] #32604: File uploads larger than FILE_UPLOAD_MAX_MEMORY_SIZE get wrong unix group based on setgid

[Django]

#32604: File uploads larger than FILE_UPLOAD_MAX_MEMORY_SIZE get wrong unix 
group
based on setgid
--+
 Reporter:  Gavin Wahl|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  File uploads/storage  |  Version:  3.1
 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 Carlton Gibson):

 * type:  Uncategorized => Cleanup/optimization
 * component:  Uncategorized => File uploads/storage
 * stage:  Unreviewed => Accepted


Comment:

 OK, yes, this is related to #27334 (also #28540) - if we can make a
 similar adjustment for the group it should be acceptable.

-- 
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.bed213b428de53479546bc31ea9e%40djangoproject.com.

Re: [Django] #32603: Add transaction handling to Changelist list_editable processing. (was: Changelist view in admin is missing transaction)

[Django]

#32603: Add transaction handling to Changelist list_editable processing.
+
 Reporter:  Vlastimil Zíma  |Owner:  nobody
 Type:  New feature |   Status:  new
Component:  contrib.admin   |  Version:  dev
 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 Carlton Gibson):

 * type:  Bug => New feature
 * stage:  Unreviewed => Accepted


Comment:

 So, this has never been wrapped in a transaction.
 See https://github.com/django/django/commit/7bc0878922 where it was added.

 Happy to accept as a New Feature to investigate adding that. (I can't
 immediately see any obvious blockers.)

-- 
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/063.6718d96cc617af22eeb3ad6bf224f2cb%40djangoproject.com.

Re: [Django] #32260: handler500 as a Class-based view raises SystemCheckError

[Django]

#32260: handler500 as a Class-based view raises SystemCheckError
-+-
 Reporter:  Daniyal Abbasi   |Owner:  Daniyal
 Type:   |  Abbasi
  Cleanup/optimization   |   Status:  closed
Component:  Core (System |  Version:  dev
  checks)|
 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:"7c08f26bf0439c1ed593b51b51ad847f7e262bc1" 7c08f26b]:
 {{{
 #!CommitTicketReference repository=""
 revision="7c08f26bf0439c1ed593b51b51ad847f7e262bc1"
 Fixed #32260 -- Made View.as_view() do not use update_wrapper().

 View.as_view() should not use update_wrapper() for copying attributes
 it's unintended and have side-effects such as adding `self` to the
 signature.

 This also fixes system check for arguments of custom error handler
 views with class-based views.

 Co-authored-by: Nick Pope 
 }}}

-- 
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.16ea851a46ee1ecdcd3f9bb000419074%40djangoproject.com.

Re: [Django] #32260: handler500 as a Class-based view raises SystemCheckError

[Django]

#32260: handler500 as a Class-based view raises SystemCheckError
-+-
 Reporter:  Daniyal Abbasi   |Owner:  Daniyal
 Type:   |  Abbasi
  Cleanup/optimization   |   Status:  assigned
Component:  Core (System |  Version:  dev
  checks)|
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"0c0b87725bbcffca3bc3a7a2c649995695a5ae3b" 0c0b8772]:
 {{{
 #!CommitTicketReference repository=""
 revision="0c0b87725bbcffca3bc3a7a2c649995695a5ae3b"
 Refs #32260 -- Made admindocs and technical 404 debug page use
 view_func.view_class.

 Internals of admindocs and technical 404 debug page should use the
 view_class attribute and do not rely on __name__.
 }}}

-- 
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.030c0a14874d33acba2a1700c9174b5b%40djangoproject.com.