Re: [Django] #19221: Check that cache keys are string

[Django]

#19221: Check that cache keys are string
-+-
 Reporter:  Mark Hughes  |Owner:  Dan
 |  Stephenson
 Type:  Bug  |   Status:  assigned
Component:  Core (Cache system)  |  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 Dan Stephenson):

 Can i propose prepending the name of the keys object type, to fix the
 issue of `42` and `"42"` pointing at same data as it does currently.

 {{{
 return '%s:%s:%s_%s' % (key_prefix, version, type(key).__name__, key)
 }}}


 The challenge for this change would be in how we handle pre-existing cache
 keys after Django is upgraded.

 - We could add some code into the **has_key** function temporarily, so
 that in scenarios where it returns None, there is an additional check
 against the legacy format, if something is found, we would update the
 cache key (delete the old one), and return it.

 or

 - Add an advisory to the release notes that the internal cache naming has
 changed, and to prevent orphaned keys taking up space, its recommended to
 flush existing caches alongside the version upgrade.

 comments welcome!

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

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

Re: [Django] #19221: Check that cache keys are string

[Django]

#19221: Check that cache keys are string
-+-
 Reporter:  Mark Hughes  |Owner:  Dan
 |  Stephenson
 Type:  Bug  |   Status:  assigned
Component:  Core (Cache system)  |  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 Dan Stephenson):

 * status:  new => assigned
 * cc: dan@… (added)
 * owner:  nobody => Dan Stephenson


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

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

Re: [Django] #27733: ClearableFileInput widget renders incorrectly

[Django]

#27733: ClearableFileInput widget renders incorrectly
-+-
 Reporter:  Luca De Feo  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.10
 Severity:  Normal   |   Resolution:
 |  worksforme
 Keywords:  forms widgets file   | Triage Stage:
  input  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Luca De Feo):

 I see. Thanks, and sorry for the noise.

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

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

Re: [Django] #27733: ClearableFileInput widget renders incorrectly

[Django]

#27733: ClearableFileInput widget renders incorrectly
-+-
 Reporter:  Luca De Feo  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.10
 Severity:  Normal   |   Resolution:
 |  worksforme
 Keywords:  forms widgets file   | Triage Stage:
  input  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz):

 * resolution:  needsinfo => worksforme


Comment:

 It has been a property for a long time (or always has), but as long as it
 used in templates only, it doesn't make a big difference. What might be
 new is its usage in Python code.

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

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

[Django] #27734: Parallel tests try to use database with too high indices

[Django]

#27734: Parallel tests try to use database with too high indices
-+--
   Reporter:  Adam Wróbel|  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Testing framework  |Version:  1.10
   Severity:  Normal |   Keywords:  parallel
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+--
 I've had this problem since upgrading to Python 3.6 on macOS Sierra – when
 I run my tests in parallel many of them blow up trying to use database
 with index that is higher than the number of parallel test processes. On
 my MacBook the default process number is 4 and tests fail trying to
 connect to test_my_db_5. On my iMac the default process number is 8 and
 test fail connecting to test_my_db_9. The same thing happens if I set the
 number of processes explicitly, e.g. `--parallel=2`. Higher number of
 processes yields less failures. If I explicitly set the number of
 processes to a number that is greater than the number of my test files
 then the tests succeed.



 {{{
 Traceback (most recent call last):
   File "/Users/amw/.virtualenvs/envname/lib/python3.6/site-
 packages/django/test/testcases.py", line 216, in __call__
 self._post_teardown()
   File "/Users/amw/.virtualenvs/envname/lib/python3.6/site-
 packages/django/test/testcases.py", line 908, in _post_teardown
 self._fixture_teardown()
   File "/Users/amw/.virtualenvs/envname/lib/python3.6/site-
 packages/django/test/testcases.py", line 943, in _fixture_teardown
 inhibit_post_migrate=inhibit_post_migrate)
   File "/Users/amw/.virtualenvs/envname/lib/python3.6/site-
 packages/django/core/management/__init__.py", line 130, in call_command
 return command.execute(*args, **defaults)
   File "/Users/amw/.virtualenvs/envname/lib/python3.6/site-
 packages/django/core/management/base.py", line 345, in execute
 output = self.handle(*args, **options)
   File "/Users/amw/.virtualenvs/envname/lib/python3.6/site-
 packages/django/core/management/commands/flush.py", line 54, in handle
 allow_cascade=allow_cascade)
   File "/Users/amw/.virtualenvs/envname/lib/python3.6/site-
 packages/django/core/management/sql.py", line 15, in sql_flush
 tables =
 connection.introspection.django_table_names(only_existing=True,
 include_views=False)
   File "/Users/amw/.virtualenvs/envname/lib/python3.6/site-
 packages/django/db/backends/base/introspection.py", line 88, in
 django_table_names
 existing_tables = self.table_names(include_views=include_views)
   File "/Users/amw/.virtualenvs/envname/lib/python3.6/site-
 packages/django/db/backends/base/introspection.py", line 55, in
 table_names
 with self.connection.cursor() as cursor:
   File "/Users/amw/.virtualenvs/envname/lib/python3.6/site-
 packages/django/db/backends/base/base.py", line 233, in cursor
 cursor = self.make_cursor(self._cursor())
   File "/Users/amw/.virtualenvs/envname/lib/python3.6/site-
 packages/django/db/backends/base/base.py", line 204, in _cursor
 self.ensure_connection()
   File "/Users/amw/.virtualenvs/envname/lib/python3.6/site-
 packages/django/db/backends/base/base.py", line 199, in ensure_connection
 self.connect()
   File "/Users/amw/.virtualenvs/envname/lib/python3.6/site-
 packages/django/db/utils.py", line 94, in __exit__
 six.reraise(dj_exc_type, dj_exc_value, traceback)
   File "/Users/amw/.virtualenvs/envname/lib/python3.6/site-
 packages/django/utils/six.py", line 685, in reraise
 raise value.with_traceback(tb)
   File "/Users/amw/.virtualenvs/envname/lib/python3.6/site-
 packages/django/db/backends/base/base.py", line 199, in ensure_connection
 self.connect()
   File "/Users/amw/.virtualenvs/envname/lib/python3.6/site-
 packages/django/db/backends/base/base.py", line 171, in connect
 self.connection = self.get_new_connection(conn_params)
   File "/Users/amw/.virtualenvs/envname/lib/python3.6/site-
 packages/django/db/backends/postgresql/base.py", line 176, in
 get_new_connection
 connection = Database.connect(**conn_params)
   File "/Users/amw/.virtualenvs/envname/lib/python3.6/site-
 packages/psycopg2/__init__.py", line 164, in connect
 conn = _connect(dsn, connection_factory=connection_factory,
 async=async)
 django.db.utils.OperationalError: FATAL:  database "test_my_db_5" does not
 exist

 }}}


 My requirements.txt file:
 {{{
 boto3==1.4.3
 daemonize==2.4.7
 Django==1.10.5
 django-appconf==1.0.2
 django-compressor==2.1
 django-debug-toolbar==1.6
 django-dotenv==1.4.1
 django-extensions==1.7.5
 django-ipware==1.1.6
 djangorestframework==3.5.3
 filemagic==1.6
 inflection==0.3.1
 

Re: [Django] #27161: TypedChoiceField fails to validate properly when used with ArrayField

[Django]

#27161: TypedChoiceField fails to validate properly when used with ArrayField
--+
 Reporter:  Roman Karpovich   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Forms |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  TypedChoiceField  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Claude Paroz):

 It may be that the proper resolution is #27704. Roman, you might be
 interested to test the patch there.

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

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

Re: [Django] #27704: contrib.postgres.ArrayField with choices should use TypedMultipleChoiceField as its default form field class

[Django]

#27704: contrib.postgres.ArrayField with choices should use
TypedMultipleChoiceField as its default form field class
--+
 Reporter:  Carl Meyer|Owner:  (none)
 Type:  New feature   |   Status:  new
Component:  contrib.postgres  |  Version:  master
 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
--+
Changes (by Claude Paroz):

 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1


Comment:

 Here is a [https://github.com/django/django/pull/7850 preliminary patch].
 Obviously needs some more work, but it's a start...

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

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

Re: [Django] #27149: Allow using a subquery in QuerySet.filter()

[Django]

#27149: Allow using a subquery in QuerySet.filter()
-+-
 Reporter:  MikiSoft |Owner:  Matthew
 |  Schinckel
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  Queryset SubQuery| Triage Stage:  Ready for
  Exists |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"236ebe94bfe24d394d5b49f4405da445550e8aa6" 236ebe94]:
 {{{
 #!CommitTicketReference repository=""
 revision="236ebe94bfe24d394d5b49f4405da445550e8aa6"
 Fixed #27149 -- Added Subquery and Exists database expressions.

 Thanks Josh Smeaton for Oracle fixes.
 }}}

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

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

Re: [Django] #27733: ClearableFileInput widget renders incorrectly

[Django]

#27733: ClearableFileInput widget renders incorrectly
-+-
 Reporter:  Luca De Feo  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.10
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  forms widgets file   | Triage Stage:
  input  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Luca De Feo):

 You are totally right. I don't know how it had been working for so long
 before. Maybe it used to be a method before 1.10?

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

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

Re: [Django] #27718: Add QuerySet.union(), intersection(), difference()

[Django]

#27718: Add QuerySet.union(), intersection(), difference()
-+-
 Reporter:  Florian Apolloner|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (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 Tim Graham ):

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


Comment:

 In [changeset:"84c1826ded17b2d74f66717fb745fc36e37949fd" 84c1826d]:
 {{{
 #!CommitTicketReference repository=""
 revision="84c1826ded17b2d74f66717fb745fc36e37949fd"
 Fixed #27718 -- Added QuerySet.union(), intersection(), difference().

 Thanks Mariusz Felisiak for review and Oracle assistance.
 Thanks Tim Graham for review and writing docs.
 }}}

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

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

Re: [Django] #27387: Rendering "required" as HTML attribute is not documented under Field.required

[Django]

#27387: Rendering "required" as HTML attribute is not documented under
Field.required
-+-
 Reporter:  karyon   |Owner:  Zbigniew
 Type:   |  Siciarz
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"f3af0acb09219e82ad2d32b16e69ef600abddc07" f3af0acb]:
 {{{
 #!CommitTicketReference repository=""
 revision="f3af0acb09219e82ad2d32b16e69ef600abddc07"
 [1.10.x] Fixed #27387 -- Doc'd required HTML attribute in Field.required
 docs.

 Backport of 611ef422b173b450b1fc6f7f94eb262961b24e54 from master
 }}}

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

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

Re: [Django] #27387: Rendering "required" as HTML attribute is not documented under Field.required

[Django]

#27387: Rendering "required" as HTML attribute is not documented under
Field.required
-+-
 Reporter:  karyon   |Owner:  Zbigniew
 Type:   |  Siciarz
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"611ef422b173b450b1fc6f7f94eb262961b24e54" 611ef42]:
 {{{
 #!CommitTicketReference repository=""
 revision="611ef422b173b450b1fc6f7f94eb262961b24e54"
 Fixed #27387 -- Doc'd required HTML attribute in Field.required docs.
 }}}

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

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

Re: [Django] #16614: Support server-side cursors for queryset iteration in database backends

[Django]

#16614: Support server-side cursors for queryset iteration in database backends
-+-
 Reporter:  Dan McGee|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  memory cursors   | Triage Stage:  Accepted
  database   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"6b6be692fcd102436c7abef1d7b3fa1d37ad4bdf" 6b6be69]:
 {{{
 #!CommitTicketReference repository=""
 revision="6b6be692fcd102436c7abef1d7b3fa1d37ad4bdf"
 Refs #16614 -- Prevented database errors from being masked by cursor
 close.

 When an error occurred during the cursor.execute statement, the cursor
 is closed. This operation did not fail with client-side cursors. Now,
 with server-side cursors, the close operation might fail (example
 below). The original error should be raised, not the one raised by
 cursor.close(), this is only clean-up code.

 For example, one can attempt to create a named cursor for an invalid
 query. psycopg will raise an error about the invalid query and the
 server-side cursor will not be created on PostgreSQL. When the code
 attempts to cursor.close(), it asks psycopg to close a cursor that was
 not created. pyscopg raises a new error: psycopg2.OperationalError:
 cursor "_django_curs_140365867840512_20" does not exist.
 }}}

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

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

Re: [Django] #25307: Cannot use .annotate with conditional expressions

[Django]

#25307: Cannot use .annotate with conditional expressions
-+-
 Reporter:  Jared Proffitt   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Josh Smeaton):

 * stage:  Accepted => Ready for checkin


Comment:

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

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

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

Re: [Django] #26291: loaddata cannot deserialize fixtures with forward references and natural foreign keys

[Django]

#26291: loaddata cannot deserialize fixtures with forward references and natural
foreign keys
-+-
 Reporter:  Peter Inglesby   |Owner:  Peter
 |  Inglesby
 Type:  New feature  |   Status:  assigned
Component:  Core |  Version:  master
  (Serialization)|
 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 Asif Saifuddin Auvi):

 * version:  1.9 => master


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

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

Re: [Django] #25226: ArrayField doesn't set the model attribute on the base_field instance

[Django]

#25226: ArrayField doesn't set the model attribute on the base_field instance
-+-
 Reporter:  Ion Scerbatiuc   |Owner:  Tim
 |  Graham 
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  arrayfield check-| Triage Stage:
  framework  |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 In [changeset:"2e55790838a75bf25a5536dae57880cfccfb" 2e557908]:
 {{{
 #!CommitTicketReference repository=""
 revision="2e55790838a75bf25a5536dae57880cfccfb"
 Refs #25226 -- Cloned ArrayField.base_field on deconstruction.

 This prevents the base_field from sharing attributes with the one used
 during migrations.
 }}}

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

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

Re: [Django] #24317: Deprecate field.rel, replace it with real field instances

[Django]

#24317: Deprecate field.rel, replace it with real field instances
-+-
 Reporter:  Anssi Kääriäinen |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (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 Asif Saifuddin Auvi):

 should the virtual field #16508  need to be addressed first? My analysis
 seems that should be first

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

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

Re: [Django] #27704: contrib.postgres.ArrayField with choices should use TypedMultipleChoiceField as its default form field class

[Django]

#27704: contrib.postgres.ArrayField with choices should use
TypedMultipleChoiceField as its default form field class
--+
 Reporter:  Carl Meyer|Owner:  (none)
 Type:  New feature   |   Status:  new
Component:  contrib.postgres  |  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 Claude Paroz):

 See also #27161

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

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

Re: [Django] #27387: Rendering "required" as HTML attribute is not documented under Field.required

[Django]

#27387: Rendering "required" as HTML attribute is not documented under
Field.required
-+-
 Reporter:  karyon   |Owner:  Zbigniew
 Type:   |  Siciarz
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz):

 * needs_better_patch:  1 => 0


Comment:

 New [https://github.com/django/django/pull/7848 PR].

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

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

Re: [Django] #27699: parse_duration returns None if passed a string with a negative number of seconds

[Django]

#27699: parse_duration returns None if passed a string with a negative number of
seconds
-+-
 Reporter:  Filipe L B Correia   |Owner:
 |  hardik1997
 Type:  Bug  |   Status:  closed
Component:  Utilities|  Version:  1.10
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  parse_duration,  | Triage Stage:  Accepted
  DurationField  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"f4c0eec713a6ffe7616fdc5f4744b40110d4fed1" f4c0eec7]:
 {{{
 #!CommitTicketReference repository=""
 revision="f4c0eec713a6ffe7616fdc5f4744b40110d4fed1"
 Fixed #27699 -- Added negative timedelta support to parse_duration()
 }}}

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

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

Re: [Django] #27733: ClearableFileInput widget renders incorrectly

[Django]

#27733: ClearableFileInput widget renders incorrectly
-+-
 Reporter:  Luca De Feo  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.10
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  forms widgets file   | Triage Stage:
  input  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz):

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


Comment:

 `FieldFile.url` is a property, not a method, see
 
https://github.com/django/django/blob/1.10.5/django/db/models/fields/files.py#L70

 Are you using a third-party FieldFile class?

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

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