Re: [Django] #32191: Not RFC 6265 compliant cookies in contrib.messages.

[Django]

#32191: Not RFC 6265 compliant cookies in contrib.messages.
--+---
 Reporter:  Nico Giefing  |Owner:  Craig Smith
 Type:  Bug   |   Status:  assigned
Component:  contrib.messages  |  Version:  3.1
 Severity:  Normal|   Resolution:
 Keywords:  Cookie malformed  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+---

Comment (by Craig Smith):

 Hi All,
 I have started over. This the new
 [https://github.com/django/django/pull/13732 PR].

 Still some more work to do on it though.

 I have opted to use latin-1 to encode internal to the new functions as we
 use latin-1 elsewhere. I was surprised when using utf-8 that a character
 was unrecognised when calling
 `decompress_b64(request.cookies['messages'].value)` in the
 `messages_tests.test_mixins.test_set_messages_success` test. But using
 latin-1 works. UTF-8 would be better, IMHO because we could store messages
 in many more languages, but those changes would need to be a bit more
 widespread and possibly have a bigger impact. But as the latin-1 character
 set is contained in utf-8, all we'd need to do is change our latin-1
 encodings to utf-8 - is that something we should do here, or maybe bring
 it up on the mailing list?

 Going forward, I will add tests, in particular to confirm RFC6265
 compliant message cookies, and I will attempt integrating the new
 functions as methods of the signer base class.

 **Another question**: `signing.dumps` currently takes a `compress=False`
 keyword arg, should this be passed through to the `sign` method? Or should
 the `sign` method compress and base64 encode by default?

 Thanks for reading.

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

Re: [Django] #27021: Add explicit support for Q object annotations

[Django]

#27021: Add explicit support for Q object annotations
-+-
 Reporter:  Josh Smeaton |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Sergey Fedoseev):

 * owner:  Sergey Fedoseev => (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/066.eab659d29d109c903bfd7475a089e02b%40djangoproject.com.

Re: [Django] #32039: psycop2.extras.register_default_jsonb() crashes with TypeError in Django 3.1.1.

[Django]

#32039: psycop2.extras.register_default_jsonb() crashes with TypeError in Django
3.1.1.
-+-
 Reporter:  elliottyates |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by ziga):

 After long long debugging session – async debugging is hard – I've figured
 the main source of this issue was use of `install_all_patches` from
 `opentracing_instrumentation`.

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

Re: [Django] #15578: loaddata and processing order of fixtures

[Django]

#15578: loaddata and processing order of fixtures
--+
 Reporter:  Luc Saffre|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.2
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by muskanvaswan):

 Is this patch better framed as the following?

 Fixtures are processed in the same order as the one specified in the list.
 This means that if {{{Fixtures = ['foo', 'bar', 'baz']}}} then the order
 in which they are loaded will be 'foo' followed by 'bar' and then 'baz'.
 Where, "foo" is any fixture named 'foo' **in any application**. This
 implies that  in cases where there are several fixtures with the same
 name, the order in which applications are defined in **INSTALLED_APPS** is
 also a taken into account.
 This order may not always be predictable. If the database backend supports
 row-level constraints, these constraints will be checked at the end of the
 transaction.

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

Re: [Django] #32231: It should be possible to pass None as params for Model.objects.raw

[Django]

#32231: It should be possible to pass None as params for Model.objects.raw
-+-
 Reporter:  Alexander Lyabah |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  raw, psycopg2,   | Triage Stage:  Accepted
  execute, orm, db   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * version:  2.2 => master
 * stage:  Unreviewed => Accepted


Comment:

 To amend what I said above, `cursor` works fine, it's only `raw` that
 doesn't so the documentation divergence seems moot.

 Allowing `params=None` to be explicitly specified to opt-in this behaviour
 like the reporter suggested seems like an acceptable compromise.

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

Re: [Django] #32231: It should be possible to pass None as params for Model.objects.raw

[Django]

#32231: It should be possible to pass None as params for Model.objects.raw
-+-
 Reporter:  Alexander Lyabah |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  raw, psycopg2,   | Triage Stage:
  execute, orm, db   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Alexander Lyabah):

 I update the patch for backward compatibility

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

Re: [Django] #32231: It should be possible to pass None as params for Model.objects.raw

[Django]

#32231: It should be possible to pass None as params for Model.objects.raw
-+-
 Reporter:  Alexander Lyabah |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  raw, psycopg2,   | Triage Stage:
  execute, orm, db   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Alexander Lyabah):

 * Attachment "params_none.diff" added.


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

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

Re: [Django] #32231: It should be possible to pass None as params for Model.objects.raw

[Django]

#32231: It should be possible to pass None as params for Model.objects.raw
-+-
 Reporter:  Alexander Lyabah |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  raw, psycopg2,   | Triage Stage:
  execute, orm, db   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 From the ''Executing custom SQL'' directly section of the
 ''[https://docs.djangoproject.com/en/3.1/topics/db/sql/#executing-custom-
 sql-directly Performing raw SQL queries documentation]''

 > Note that if you want to include literal percent signs in the query, you
 have to double them **in the case you are passing parameters**:
 >
 > `cursor.execute("SELECT foo FROM bar WHERE baz = '30%'")`
 > `cursor.execute("SELECT foo FROM bar WHERE baz = '30%%' AND id = %s",
 [self.id])`

 So it seems that it was meant to work the way described above when not
 parameters are provided but it was never tested to do so and might have
 regressed at some point?

 We should determine for how long the implementation has diverged from the
 documentation to take an informed decision here as some users might have
 simply worked around this limitation by always doubling percentage signs
 even no parameters are provided over the years. If we were to simply
 switch back to the documented way of doing things we could silently break
 queries of the form

 {{{#!python
 cursor.execute("SELECT foo FROM bar WHERE baz = '30%%'")
 }}}

 I think we either need to go through a deprecation period where
 `params=()` keeps being passed `if '%%' in sql` or bite the bullet and
 adjust the documentation accordingly.

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

Re: [Django] #32231: It should be possible to pass None as params for Model.objects.raw

[Django]

#32231: It should be possible to pass None as params for Model.objects.raw
-+-
 Reporter:  Alexander Lyabah |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  raw, psycopg2,   | Triage Stage:
  execute, orm, db   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 Not sure I understand the rationale here

 Doing something along

 {{{#!python
 query = "SELECT * FROM raw_query_author WHERE first_name like 'J%'"
 qset = Author.objects.raw(query)
 }}}

 Is prone to SQL injection assuming `'J%'` could be coming from user input,
 you definitely want to be doing the following instead

 {{{#!python
 query = "SELECT * FROM raw_query_author WHERE first_name like %s"
 qset = Author.objects.raw(query, ('J%',))
 }}}

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

Re: [Django] #32231: It should be possible to pass None as params for Model.objects.raw

[Django]

#32231: It should be possible to pass None as params for Model.objects.raw
-+-
 Reporter:  Alexander Lyabah |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  raw, psycopg2,   | Triage Stage:
  execute, orm, db   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Alexander Lyabah):

 * Attachment "params_none.diff" added.


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

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

Re: [Django] #32231: It should be possible to pass None as params for Model.objects.raw

[Django]

#32231: It should be possible to pass None as params for Model.objects.raw
-+-
 Reporter:  Alexander Lyabah |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  raw, psycopg2,   | Triage Stage:
  execute, orm, db   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Alexander Lyabah):

 * Attachment "params_none.diff" added.


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

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

[Django] #32231: It should be possible to pass None as params for Model.objects.raw

[Django]

#32231: It should be possible to pass None as params for Model.objects.raw
-+-
   Reporter:  Alexander  |  Owner:  nobody
  Lyabah |
   Type:  Bug| Status:  new
  Component:  Database   |Version:  2.2
  layer (models, ORM)|   Keywords:  raw, psycopg2,
   Severity:  Normal |  execute, orm, db
   Triage Stage: |  Has patch:  1
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 I was playing with:

 * psycopg2==2.8.6
 * last django 2.2 (-e
 
git+...@github.com:django/django.git@e893c0ad8b0b5b0a1e5be3345c287044868effc4#egg=Django)

 Model.objects.raw has raw_query and params=None attributes, as well as
 cursor.execute has the same attributes, and `raw` will eventually calls
 `execute`, since `raw` is more low-level way of using DB.

 But, params=None of `raw` function doesn't pass as None into `execute`
 function, but empty tuple instead.

 The problem here is that, psycopg2 treats differently params=None and
 params=(), and it is impossible to pass None using `raw` function.

 The simple example can be found in test from patch

 query = "SELECT * FROM raw_query_author WHERE first_name like
 'J%'"
 qset = Author.objects.raw(query)
 results = list(qset)
 print(len(results))

 in current Django version (I was using 2.2) it raises an exception from
 psycopg2

 The attached patch allows using None in params

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

Re: [Django] #32226: QuerySet.explain(format='json') outputs repr'd JSON on PostgreSQL

[Django]

#32226: QuerySet.explain(format='json') outputs repr'd JSON on PostgreSQL
-+-
 Reporter:  Adam (Chainz)|Owner:  kosc
  Johnson|
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.0
  (models, ORM)  |
 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 Adam (Chainz) Johnson):

 It could be something to do with JSONField changes?

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

Re: [Django] #25762: Optimize numberformat.format

[Django]

#25762: Optimize numberformat.format
-+-
 Reporter:  Jaap Roes|Owner:  Tim
 Type:   |  McCurrach
  Cleanup/optimization   |   Status:  assigned
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Johannes Maron):

 * needs_better_patch:  0 => 1
 * needs_tests:  0 => 1


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

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

Re: [Django] #32226: QuerySet.explain(format='json') outputs repr'd JSON on PostgreSQL

[Django]

#32226: QuerySet.explain(format='json') outputs repr'd JSON on PostgreSQL
-+-
 Reporter:  Adam (Chainz)|Owner:  kosc
  Johnson|
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.0
  (models, ORM)  |
 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 Tom Forbes):

 I wonder if this changed at some point, because when I was developing this
 feature I’m almost certain that it returned a string type with valid JSON
 rather than a list of dicts 樂. I can’t see anything in the psycopg2
 release notes to support that though, so maybe I’m misremembering.

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

Re: [Django] #32226: QuerySet.explain(format='json') outputs repr'd JSON on PostgreSQL

[Django]

#32226: QuerySet.explain(format='json') outputs repr'd JSON on PostgreSQL
-+-
 Reporter:  Adam (Chainz)|Owner:  kosc
  Johnson|
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.0
  (models, ORM)  |
 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 Tom Forbes):

 * cc: Tom Forbes (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/068.a9d8004dc9effbef6269328cbf1007bd%40djangoproject.com.

Re: [Django] #32227: DebugSQLTextTestResult crashes when database error is raised in setUpTestData().

[Django]

#32227: DebugSQLTextTestResult crashes when database error is raised in
setUpTestData().
-+-
 Reporter:  Mariusz Felisiak |Owner:  Adam
 |  (Chainz) Johnson
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  3.1
 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:"b9fd09d21b722c3745501151f9cbd5b95ccc3177" b9fd09d2]:
 {{{
 #!CommitTicketReference repository=""
 revision="b9fd09d21b722c3745501151f9cbd5b95ccc3177"
 Fixed #32227 -- Prevented crash when setUpTestData() errors with --debug-
 sql.

 Thanks Mariusz Felisiak for the report.
 }}}

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

Re: [Django] #24157: Prompt to add a new field after renaming

[Django]

#24157: Prompt to add a new field after renaming
-+-
 Reporter:  Basil Upornikov  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Migrations   |  Version:  1.7
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * status:  new => closed
 * resolution:   => duplicate
 * stage:  Someday/Maybe => Unreviewed


Comment:

 Duplicate of #32206, which was closed as a duplicate of #31700.

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

Re: [Django] #32227: DebugSQLTextTestResult crashes when database error is raised in setUpTestData().

[Django]

#32227: DebugSQLTextTestResult crashes when database error is raised in
setUpTestData().
-+-
 Reporter:  Mariusz Felisiak |Owner:  Adam
 |  (Chainz) Johnson
 Type:  Bug  |   Status:  assigned
Component:  Testing framework|  Version:  3.1
 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 Mariusz Felisiak):

 * 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/065.3b800cf244b6eb8e79251ccff148ae3a%40djangoproject.com.

Re: [Django] #21021: Default geom_type attribute for GeometryWidget should be "Geometry", not "Unknown"

[Django]

#21021: Default geom_type attribute for GeometryWidget should be "Geometry", not
"Unknown"
-+-
 Reporter:  Mathieu Leplatre |Owner:  Giannis
 Type:   |  Adamopoulos
  Cleanup/optimization   |   Status:  closed
Component:  GIS  |  Version:
 |  1.6-beta-1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  minor| 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:"7603036bd0629d5f9e58f8da2418170070357f62" 7603036b]:
 {{{
 #!CommitTicketReference repository=""
 revision="7603036bd0629d5f9e58f8da2418170070357f62"
 Fixed #21021 -- Changed BaseGeometryWidget's default geometry type to
 'Geometry'.
 }}}

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

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

Re: [Django] #31978: Include hidden username field on password reset to help password managers

[Django]

#31978: Include hidden username field on password reset to help password 
managers
-+-
 Reporter:  Collin Anderson  |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  1 => 0


Comment:

 [https://github.com/django/django/pull/13730 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/072.5115a395cf4fe2918785cb8f0b4983f3%40djangoproject.com.

Re: [Django] #31978: Include hidden username field on password reset to help password managers

[Django]

#31978: Include hidden username field on password reset to help password 
managers
-+-
 Reporter:  Collin Anderson  |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * owner:  Collin Anderson => Mariusz Felisiak
 * 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/072.28f6a2a3066a591b7cf5c759e54b69b0%40djangoproject.com.

Re: [Django] #32230: Add support for pathlib.Path to the django.contrib.gis.gdal.DataSource.

[Django]

#32230: Add support for pathlib.Path to the django.contrib.gis.gdal.DataSource.
-+-
 Reporter:  Mariusz Felisiak |Owner:  Hasan
 |  Ramezani
 Type:  New feature  |   Status:  closed
Component:  GIS  |  Version:  3.1
 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 GitHub ):

 In [changeset:"2ab8b5f4f8f645be153236af210e6d8edad69668" 2ab8b5f]:
 {{{
 #!CommitTicketReference repository=""
 revision="2ab8b5f4f8f645be153236af210e6d8edad69668"
 [3.1.x] Refs #32230 -- Fixed LayerMapping example in GeoDjango tutorial.

 LayerMapping.data_source doesn't support pathlib.Path().

 Regression in 26554cf5d1e96db10d0d5f4b69683a22fb82fdf8.

 Follow up to e46ca51c249677c52e04db28fc0c60ae1948b3b2.
 }}}

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

Re: [Django] #21021: Default geom_type attribute for GeometryWidget should be "Geometry", not "Unknown"

[Django]

#21021: Default geom_type attribute for GeometryWidget should be "Geometry", not
"Unknown"
-+-
 Reporter:  Mathieu Leplatre |Owner:  Giannis
 Type:   |  Adamopoulos
  Cleanup/optimization   |   Status:  assigned
Component:  GIS  |  Version:
 |  1.6-beta-1
 Severity:  Normal   |   Resolution:
 Keywords:  minor| 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):

 * needs_tests:  1 => 0
 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #32230: Add support for pathlib.Path to the django.contrib.gis.gdal.DataSource.

[Django]

#32230: Add support for pathlib.Path to the django.contrib.gis.gdal.DataSource.
-+-
 Reporter:  Mariusz Felisiak |Owner:  Hasan
 |  Ramezani
 Type:  New feature  |   Status:  closed
Component:  GIS  |  Version:  3.1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"b37be072a27f3d4aaf22342a17afd0c24518ff8b" b37be072]:
 {{{
 #!CommitTicketReference repository=""
 revision="b37be072a27f3d4aaf22342a17afd0c24518ff8b"
 Fixed #32230 -- Made DataSource support pathlib.Path.
 }}}

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

Re: [Django] #32230: Add support for pathlib.Path to the django.contrib.gis.gdal.DataSource.

[Django]

#32230: Add support for pathlib.Path to the django.contrib.gis.gdal.DataSource.
-+-
 Reporter:  Mariusz Felisiak |Owner:  Hasan
 |  Ramezani
 Type:  New feature  |   Status:  closed
Component:  GIS  |  Version:  3.1
 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 Mariusz Felisiak ):

 In [changeset:"931c6e982c078073dfa9b5dc1ef0059f8c787719" 931c6e98]:
 {{{
 #!CommitTicketReference repository=""
 revision="931c6e982c078073dfa9b5dc1ef0059f8c787719"
 Refs #32230 -- Made LayerMapping support pathlib.Path.
 }}}

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