Re: [Django] #25002: Postgresql migration fails when changing a CharField to a TimeField

[Django]

#25002: Postgresql migration fails when changing a CharField to a TimeField
-+-
 Reporter:  dirkcuys |Owner:  charettes
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  migrations   | 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 charettes):

 * status:  new => closed
 * resolution:   => fixed
 * stage:  Accepted => Ready for checkin


Comment:

 Merged the patch marked as RFC by Shai on Github.

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

Re: [Django] #25002: Postgresql migration fails when changing a CharField to a TimeField

[Django]

#25002: Postgresql migration fails when changing a CharField to a TimeField
-+-
 Reporter:  dirkcuys |Owner:  charettes
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  migrations   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette ):

 In [changeset:"bdb382b2a49de4a2426c3dde944776c1bdd08eb7" bdb382b]:
 {{{
 #!CommitTicketReference repository=""
 revision="bdb382b2a49de4a2426c3dde944776c1bdd08eb7"
 Refs #25002 -- Supported textual to temporal column alteration on Oracle.

 Thanks to Tim Graham for the report and Shai Berger for the review.
 }}}

--
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.57f86425d99a8538a749291ba7c34fb9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24840: Add Warp and Transform functionality for GDALRasters

[Django]

#24840: Add Warp and Transform functionality for GDALRasters
-+
 Reporter:  yellowcap|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  GIS  |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  raster gdal gis  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by charettes):

 * status:  closed => new
 * needs_docs:  1 => 0
 * has_patch:  1 => 0
 * resolution:  fixed =>
 * needs_better_patch:  1 => 0


Comment:

 Error on Oracle for the new
 `gis_tests.gdal_tests.test_raster.GDALRasterTests.test_raster_transform`
 [http://djangoci.com/job/pull-requests-
 
oracle/36/database=oracle11,python=python3.4/testReport/junit/gis_tests.gdal_tests.test_raster/GDALRasterTests/test_raster_transform/
 test]:

 {{{
 Traceback (most recent call last):
   File "/mnt/jenkinsdata/workspace/pull-requests-
 
oracle/database/oracle11/python/python3.4/tests/gis_tests/gdal_tests/test_raster.py",
 line 266, in test_raster_transform
 ndv, ndv, 20, ndv, ndv, ndv, ndv,
 AssertionError: Lists differ: [99, [118 chars]23, 99, 99, 99, 15, 21, 22,
 99, 99, 99, 99, 20, 99, 99, 99, 64] != [99, [118 chars]23, 99, 99, 99, 15,
 21, 22, 99, 99, 99, 99, 20, 99, 99, 99, 99]

 First differing element 48:
 64
 99

   [99,
99,
99,
99,
4,
99,
99,
99,
99,
2,
3,
9,
99,
99,
99,
1,
2,
8,
13,
19,
99,
0,
6,
6,
12,
18,
18,
24,
99,
10,
11,
16,
22,
23,
99,
99,
99,
15,
21,
22,
99,
99,
99,
99,
20,
99,
99,
99,
 -  64]
 +  99]
 }}}

--
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.4b29742dd160958d50c421698a1edae2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24865: Add a feature to programmatically remove stale content types

[Django]

#24865: Add a feature to programmatically remove stale content types
-+-
 Reporter:  Protosac |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:   |  Version:  master
  contrib.contenttypes   |
 Severity:  Normal   |   Resolution:
 Keywords:  stale contenttypes   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Protosac):

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

Re: [Django] #24865: Add a feature to programmatically remove stale content types

[Django]

#24865: Add a feature to programmatically remove stale content types
--+
 Reporter:  Protosac  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.contenttypes  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  stale contenttypes| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Protosac):

 * cc: Protosac (added)


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

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

Re: [Django] #13910: Add generator version of Template.render(Context)

[Django]

#13910: Add generator version of Template.render(Context)
-+
 Reporter:  rooney   |Owner:  Gagaro
 Type:  New feature  |   Status:  assigned
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Gagaro):

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


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

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

Re: [Django] #24743: Django 1.8.1 migrations are actually slower than 1.8?

[Django]

#24743: Django 1.8.1 migrations are actually slower than 1.8?
--+
 Reporter:  pzrq  |Owner:  MarkusH
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Migrations|  Version:  1.8
 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 acdha):

 * cc: chris@… (added)


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

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

Re: [Django] #25019: DjangoJSONEncoder does not encode UUIDs

[Django]

#25019: DjangoJSONEncoder does not encode UUIDs
-+-
 Reporter:  lukas-hetzenecker|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core |  Version:  master
  (Serialization)|
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  UUIDField| Triage Stage:  Accepted
  DjangoJSONEncoder  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"6355a6d4f59eb220e05130d179beba7bb29c88af" 6355a6d]:
 {{{
 #!CommitTicketReference repository=""
 revision="6355a6d4f59eb220e05130d179beba7bb29c88af"
 Fixed #25019 -- Added UUID support in DjangoJSONEncoder
 }}}

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

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

Re: [Django] #24840: Add Warp and Transform functionality for GDALRasters

[Django]

#24840: Add Warp and Transform functionality for GDALRasters
-+
 Reporter:  yellowcap|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  GIS  |  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  raster gdal gis  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by claudep):

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


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

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

Re: [Django] #24840: Add Warp and Transform functionality for GDALRasters

[Django]

#24840: Add Warp and Transform functionality for GDALRasters
-+
 Reporter:  yellowcap|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  GIS  |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  raster gdal gis  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+

Comment (by Claude Paroz ):

 In [changeset:"c078021555dcda6b12363b5b0646eac5332a0d86" c078021]:
 {{{
 #!CommitTicketReference repository=""
 revision="c078021555dcda6b12363b5b0646eac5332a0d86"
 Refs #24840 -- Added GDALRaster Warp and transform methods

 Thanks to Tim Graham for the review.
 }}}

--
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.93a38ad2e56a2f946ebf9dfcd97286c2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #25022: collectstatic create self-referential symlink

[Django]

#25022: collectstatic create self-referential symlink
---+
   Reporter:  aaugustin|  Owner:  nobody
   Type:  Bug  | Status:  new
  Component:  contrib.staticfiles  |Version:  1.7
   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|
---+
 This has happened twice on our CI server, but I'm not sure how.

 Relevant settings:

 {{{
 STATICFILES_DIRS = ('/var/lib/jenkins/jobs/project-pr-
 endtoend/workspace/frontend/dist',)
 STATICFILES_STORAGE =
 'django.contrib.staticfiles.storage.ManifestStaticFilesStorage'
 STATIC_ROOT = '/var/lib/jenkins/jobs/project-pr-
 endtoend/workspace/project/static'
 STATIC_URL = '/static/'
 }}}

 Collectstatic command:

 {{{
 django-admin collectstatic --noinput --clear --link
 }}}

 (Possibly run several times in a row, with the same or different static
 files.)

 We ended up with `'/var/lib/jenkins/jobs/project-pr-
 endtoend/workspace/project/static/img/icon-sd3b7ad043d.png'` which was a
 symlink to itself.

 This prevented gunicorn from starting because we use whitenoise to serve
 static files, whitenoise scans the entire static directory on startup, and
 it couldn't `stat` a self-referential symlink.

 This is quite surprising because:

 - If I clear the directory and re-run collectstatic, I cannot reproduce
 the issue
 - I expect --clear to wipe the directory first
 - I don't expect --link to create a self-referential symlink

 (This may end up as needsinfo if I don't dig into the details and we can't
 figure out the bug from the code. But even then it may help someone who
 stumbles upon the same problem.)

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

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

[Django] #25021: HStore values query with contains does not actually work

[Django]

#25021: HStore values query with contains does not actually work
-+-
 Reporter:  amagidow |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Database layer   |Version:  1.8
  (models, ORM)  |   Keywords:  HStore, Postgresql,
 Severity:  Normal   |  queries
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 When using an HStore {{{__values}}} query with {{{__contains}}} chained on
 to it, the query does not work as expected in Django 1.8.2. Expected
 action is that any values which contain the text will be returned from the
 query.

 From my own app (I've removed some of the queryset results to make this
 easier to read)

 {{{
 >>> query1
 [, , , '...(remaining elements
 truncated)...']
 >>> query1.filter(multigloss__values__contains=["This"])
 []
 >>> query1.filter(multigloss__values__contains=["This (f)"])
 [,  , '...(remaining elements truncated)...']
 >>> query1.filter(multigloss__values__contains=["His"])
 [, ,
 , 
 '...(remaining elements truncated)...']
 >>> query1.filter(multigloss__values__contains=["Hi"])
 []
 }}}

 The expected result would be that the queries would return any data whose
 'multigloss' values contain the string, not only those strings which are
 exactly identical.


 The example in the documentation should also fail if you did not include
 the entire word "collie" (I have not tested, this is a hypothesized
 result):

 {{{
 >>> Dog.objects.create(name='Rufus', data={'breed': 'labrador'})
 >>> Dog.objects.create(name='Meg', data={'breed': 'collie', 'owner':
 'Bob'})

 >>> Dog.objects.filter(data__values__contains=['collie'])
 []

 >>>#Hypothesized example!
 >>> Dog.objects.filter(data__values__contains=['coll'])
 []
 >>>#Should have returned [Dog: Meg]
 }}}

 If this is not how {{{__values__contains}}} is supposed to work, this
 should be clarified in the documentation since it is extremely unclear how
 to do a search for values within the HStore that match a certain criterion
 (such as containing a string).

--
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/051.886ffd86ffe32f982e51ac971482de1b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25017: settings.DISALLOWED_USER_AGENTS should throw PermissionDenied exception

[Django]

#25017: settings.DISALLOWED_USER_AGENTS should throw PermissionDenied exception
-+-
 Reporter:  fschiettecatte   |Owner:
 Type:   |  SujaySKumar
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
  DISALLOWED_USER_AGENTS,|  Unreviewed
  PermissionDenied   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by MoritzS):

 SujaySKumar's pull request: https://github.com/django/django/pull/4915

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

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

Re: [Django] #25017: settings.DISALLOWED_USER_AGENTS should throw PermissionDenied exception

[Django]

#25017: settings.DISALLOWED_USER_AGENTS should throw PermissionDenied exception
-+-
 Reporter:  fschiettecatte   |Owner:
 Type:   |  SujaySKumar
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
  DISALLOWED_USER_AGENTS,|  Unreviewed
  PermissionDenied   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by SujaySKumar):

 * has_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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.395ca55e14dc7ca2577875fc8dd5380e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25017: settings.DISALLOWED_USER_AGENTS should throw PermissionDenied exception

[Django]

#25017: settings.DISALLOWED_USER_AGENTS should throw PermissionDenied exception
-+-
 Reporter:  fschiettecatte   |Owner:
 Type:   |  SujaySKumar
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
  DISALLOWED_USER_AGENTS,|  Unreviewed
  PermissionDenied   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by SujaySKumar):

 * status:  new => assigned
 * owner:  nobody => SujaySKumar


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

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

Re: [Django] #24941: Add get_exclude() hook to BaseModelAdmin

[Django]

#24941: Add get_exclude() hook to BaseModelAdmin
---+---
 Reporter:  peterfarrell   |Owner:  SujaySKumar
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+---
Changes (by SujaySKumar):

 * has_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 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/070.841a5541daab6d8f5458a518f66d1a01%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24941: Add get_exclude() hook to BaseModelAdmin

[Django]

#24941: Add get_exclude() hook to BaseModelAdmin
---+---
 Reporter:  peterfarrell   |Owner:  SujaySKumar
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  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 SujaySKumar):

 * owner:  nobody => SujaySKumar
 * status:  new => assigned


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

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

Re: [Django] #25019: DjangoJSONEncoder does not encode UUIDs

[Django]

#25019: DjangoJSONEncoder does not encode UUIDs
-+-
 Reporter:  lukas-hetzenecker|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core |  Version:  master
  (Serialization)|
 Severity:  Normal   |   Resolution:
 Keywords:  UUIDField| Triage Stage:  Accepted
  DjangoJSONEncoder  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by claudep):

 * stage:  Unreviewed => Accepted


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

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