[Django] #26717: Allow customizing stream attribute of Serializer for custom serializers

[Django]

#26717: Allow customizing stream attribute of Serializer for custom serializers
--+
 Reporter:  berkerpeksag  |  Owner:  nobody
 Type:  New feature   | Status:  new
Component:  Core (Serialization)  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Currently, `Serializer.serialize()` sets `self.stream` to `io.StringIO` if
 `stream` is not passed to `django.core.serializers.serializer()`:
 
https://github.com/django/django/blob/31a9a965a36c5ce923692e5dac430ea6a1cbf2a0/django/core/serializers/base.py#L69

 However, when implementing or using a custom serializer we either tell the
 users to pass `stream=io.BytesIO()` everytime they use it or need to make
 some unnecessary subclassing.

 It would be nice to define a `Serializer.stream` attribute similar to
 `Serializer.progress_class`.

 I noticed this while creating a msgpack serializer to understand what
 needs to be done in #15091.

 I already have a patch to implement my proposal.

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

Re: [Django] #26348: Add a __time lookup for DateTimeField

[Django]

#26348: Add a __time lookup for DateTimeField
-+-
 Reporter:  charettes|Owner:  charettes
 Type:  New feature  |   Status:  assigned
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
-+-
Changes (by charettes):

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


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

Re: [Django] #26257: Add support for expressions like (Lower('myfield'), ) in model Meta.ordering

[Django]

#26257: Add support for expressions like (Lower('myfield'),) in model 
Meta.ordering
-+-
 Reporter:  aluminiumgeek|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  meta, ordering,  | Triage Stage:  Accepted
  lower  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by charettes):

 This is related to #24747 because the requested feature could be expressed
 as `ordering = ['name__lower']` if support for transforms in `order_by()`
 lands.

 It's worth keeping this ticket open because the `ordering` checks will
 need to be adjusted to allow reference to transforms.

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

Re: [Django] #26715: Model objects with deferred fields don't send pre_save or post_save signals to receivers with explicit sender

[Django]

#26715: Model objects with deferred fields don't send pre_save or post_save 
signals
to receivers with explicit sender
-+-
 Reporter:  ezheidtmann  |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 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 charettes):

 * status:  new => closed
 * version:  1.10 => 1.9
 * resolution:   => invalid


Comment:

 Hi ezheidtmann,

 You've reported this bug against Django 1.10 but this should have been
 solved by 7f51876f99851fdc3fef63aecdfbcffa199c26b9 (#26207) which stopped
 creating custom proxy classes for deferred fields and which is part of
 1.10. The deletion signal part was tested to be fixed in #18100.

 Please reopen this ticket if you're still experiencing this issue with
 Django 1.10a1.

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

Re: [Django] #26714: Add examples for KMLSitemap and KMZSitemap (was: Documentation for Geographic Sitemaps is poor)

[Django]

#26714: Add examples for KMLSitemap and KMZSitemap
--+
 Reporter:  lordgordon|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  GIS   |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  sitemaps, KMLSitemap  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

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

Re: [Django] #26716: django.contrib.sites.CurrentSiteMiddleware needs to inherit MiddlewareMixin

[Django]

#26716: django.contrib.sites.CurrentSiteMiddleware needs to inherit 
MiddlewareMixin
-+
 Reporter:  bretth   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.sites|  Version:  1.10
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+
Changes (by timgraham):

 * needs_tests:  0 => 1
 * 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/064.efc9b8524b9eae25974e3d1034badadc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26716: django.contrib.sites.CurrentSiteMiddleware needs to inherit MiddlewareMixin

[Django]

#26716: django.contrib.sites.CurrentSiteMiddleware needs to inherit 
MiddlewareMixin
-+--
 Reporter:  bretth   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.sites|  Version:  1.10
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+--
Changes (by bretth):

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


Old description:

> As it says on the tin, CurrentSiteMiddleware isn't compatible with the
> new middleware.

New description:

 As it says on the tin, CurrentSiteMiddleware isn't compatible with the new
 middleware.

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

--

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

[Django] #26716: django.contrib.sites.CurrentSiteMiddleware needs to inherit MiddlewareMixin

[Django]

#26716: django.contrib.sites.CurrentSiteMiddleware needs to inherit 
MiddlewareMixin
-+
 Reporter:  bretth   |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  contrib.sites|Version:  1.10
 Severity:  Release blocker  |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  1|  UI/UX:  0
-+
 As it says on the tin, CurrentSiteMiddleware isn't compatible with the new
 middleware.

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

Re: [Django] #26715: Model objects with deferred fields don't send pre_save or post_save signals to receivers with explicit sender

[Django]

#26715: Model objects with deferred fields don't send pre_save or post_save 
signals
to receivers with explicit sender
-+-
 Reporter:  ezheidtmann  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 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 ezheidtmann):

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


Old description:

> Because the objects returned by `Model.objects.only(*fields)` are of a
> special object type, and that type is used as the `sender` for the
> `post_save` signal send, these deferred objects never invoke signal
> handlers that registered with an explicit signal sender.
>
> Something like this should reproduce:
>
> ```
> # models.py
> class MyModel(models.Model):
>  bigfield = models.TextField(null=True, blank=True)
>
> # signals.py
> @receiver.register(post_save, sender=models.MyModel)
> def mymodel_post_save_handler(sender, **kwargs):
>  print "handler called"
>
> # repro code
> m = MyModel.objects.create()
> # (handler is called)
> deferred_m = MyModel.objects.only('id').get(id=m.id)
> deferred_m.bigfield = 'yo'
> deferred_m.save()
> # (handler should be called, but is not)
> ```
>
> Happy to produce a proper test app/project if needed.
>
> Evan

New description:

 Because the objects returned by `Model.objects.only(*fields)` are of a
 special object type, and that type is used as the `sender` for the
 `post_save` signal send, these deferred objects never invoke signal
 handlers that registered with an explicit signal sender.

 Something like this should reproduce:

 {{{
 # models.py
 class MyModel(models.Model):
  bigfield = models.TextField(null=True, blank=True)

 # signals.py
 @receiver.register(post_save, sender=models.MyModel)
 def mymodel_post_save_handler(sender, **kwargs):
  print "handler called"

 # repro code
 m = MyModel.objects.create()
 # (handler is called)
 deferred_m = MyModel.objects.only('id').get(id=m.id)
 deferred_m.bigfield = 'yo'
 deferred_m.save()
 # (handler should be called, but is not)
 }}}

 Happy to produce a proper test app/project if needed.

 Evan

--

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

[Django] #26715: Model objects with deferred fields don't send pre_save or post_save signals to receivers with explicit sender

[Django]

#26715: Model objects with deferred fields don't send pre_save or post_save 
signals
to receivers with explicit sender
--+
 Reporter:  ezheidtmann   |  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.10
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Because the objects returned by `Model.objects.only(*fields)` are of a
 special object type, and that type is used as the `sender` for the
 `post_save` signal send, these deferred objects never invoke signal
 handlers that registered with an explicit signal sender.

 Something like this should reproduce:

 ```
 # models.py
 class MyModel(models.Model):
  bigfield = models.TextField(null=True, blank=True)

 # signals.py
 @receiver.register(post_save, sender=models.MyModel)
 def mymodel_post_save_handler(sender, **kwargs):
  print "handler called"

 # repro code
 m = MyModel.objects.create()
 # (handler is called)
 deferred_m = MyModel.objects.only('id').get(id=m.id)
 deferred_m.bigfield = 'yo'
 deferred_m.save()
 # (handler should be called, but is not)
 ```

 Happy to produce a proper test app/project if needed.

 Evan

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

Re: [Django] #26714: Documentation for Geographic Sitemaps is poor (was: Documentation for Geographic Sitemaps is empty)

[Django]

#26714: Documentation for Geographic Sitemaps is poor
-+-
 Reporter:  lordgordon   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  sitemaps,| Triage Stage:
  KMLSitemap |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by lordgordon):

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


Old description:

> Hi there,
>
> I found a part of the documentation for GeoDjango completely empty:
> https://docs.djangoproject.com/en/1.9/ref/contrib/gis/sitemaps/.
>
> The related file in the repository is empty too, so is not an issue in
> the generated doc:
> https://github.com/django/django/blob/stable/1.10.x/docs/ref/contrib/gis/sitemaps.txt
>
> The status of this file is the same in the master tree, as well in 1.9
> and 1.10 branches. A quick look in trac doesn't show any ticket about
> this issue.
>
> Best Regards,
>
> Nicholas

New description:

 Hi there,

 I found a part of the documentation for GeoDjango mostly empty:
 https://docs.djangoproject.com/en/1.9/ref/contrib/gis/sitemaps/.

 The abovementioned page lacks of example and details on how
 {{{KMLSitemap}}} and {{{KMZSitemap}}} works.

 The related file in the repository is empty too, so is not an issue in the
 generated doc:
 
https://github.com/django/django/blob/stable/1.10.x/docs/ref/contrib/gis/sitemaps.txt

 The status of this file is the same in the master tree, as well in 1.9 and
 1.10 branches. A quick look in trac doesn't show any ticket about this
 issue.

 Best Regards,

 Nicholas

--

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

Re: [Django] #10107: Allow mark_safe() to be used as a decorator

[Django]

#10107: Allow mark_safe() to be used as a decorator
-+
 Reporter:  matehat  |Owner:  svvitale
 Type:  New feature  |   Status:  assigned
Component:  Utilities|  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 svvitale):

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

[Django] #26714: Documentation for Geographic Sitemaps is empty

[Django]

#26714: Documentation for Geographic Sitemaps is empty
--+--
 Reporter:  lordgordon|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  GIS   |Version:  master
 Severity:  Normal|   Keywords:  sitemaps, KMLSitemap
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+--
 Hi there,

 I found a part of the documentation for GeoDjango completely empty:
 https://docs.djangoproject.com/en/1.9/ref/contrib/gis/sitemaps/.

 The related file in the repository is empty too, so is not an issue in the
 generated doc:
 
https://github.com/django/django/blob/stable/1.10.x/docs/ref/contrib/gis/sitemaps.txt

 The status of this file is the same in the master tree, as well in 1.9 and
 1.10 branches. A quick look in trac doesn't show any ticket about this
 issue.

 Best Regards,

 Nicholas

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

Re: [Django] #26706: Reverse many to one and forward many to many managers's prefetch object cache should be cleared on clear().

[Django]

#26706: Reverse many to one and forward many to many managers's prefetch object
cache should be cleared on clear().
-+-
 Reporter:  cosmosgenius |Owner:  yoongkang
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  manytomany m2m   | Triage Stage:  Ready for
  clear  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by yoongkang):

 I just read #25344, thanks, didn't know there were other methods that were
 affected.

 I think the behaviour should be added in both cases. Is it not reasonable,
 in general, to expect the cache to be cleared when you mutate the items?
 If the historical cached list is needed for any reason, it could always be
 stored in a variable.

 I do agree that in either case it should be documented. Either that your
 prefetched values could be out of date, or that any changes via the add(),
 clear() and remove() methods will clear the cache.

 I have updated my patch to cater for add(), remove() in addition to
 clear(). Happy to amend and add documentation either way we go, but I'll
 wait for consensus before adding documentation.

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

Re: [Django] #26710: CreateModel.references_model should take app_label into account

[Django]

#26710: CreateModel.references_model should take app_label into account
-+-
 Reporter:  sir-sigurd   |Owner:  sir-
 Type:   |  sigurd
  Cleanup/optimization   |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"7fc4c1db627807874966e4f96b34cff7c9af886f" 7fc4c1d]:
 {{{
 #!CommitTicketReference repository=""
 revision="7fc4c1db627807874966e4f96b34cff7c9af886f"
 Fixed #26710 -- Made CreateModel.references_model() take app_label into
 account.
 }}}

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

Re: [Django] #26713: Recommend running tests with deprecation warnings, prior to upgrade.

[Django]

#26713: Recommend running tests with deprecation warnings, prior to upgrade.
--+
 Reporter:  tomchristie   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 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 Tim Graham ):

 In [changeset:"d9b78be324cb2ccc331a7c27ec2d677a2d219fae" d9b78be]:
 {{{
 #!CommitTicketReference repository=""
 revision="d9b78be324cb2ccc331a7c27ec2d677a2d219fae"
 [1.10.x] Fixed #26713 -- Documented resolving deprecation warnings before
 upgrade.

 Backport of 316395d82874beea6af08a873e91b1880d0b982a 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/069.cfaba1565afcd680672ed0164f057b3c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26713: Recommend running tests with deprecation warnings, prior to upgrade.

[Django]

#26713: Recommend running tests with deprecation warnings, prior to upgrade.
--+
 Reporter:  tomchristie   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 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 Tim Graham ):

 In [changeset:"73d64a020cedebb6d78f8b3e2355a10b7a663635" 73d64a02]:
 {{{
 #!CommitTicketReference repository=""
 revision="73d64a020cedebb6d78f8b3e2355a10b7a663635"
 [1.9.x] Fixed #26713 -- Documented resolving deprecation warnings before
 upgrade.

 Backport of 316395d82874beea6af08a873e91b1880d0b982a 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/069.0e0c59e98375ad17834ba5ef6e13043d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26713: Recommend running tests with deprecation warnings, prior to upgrade.

[Django]

#26713: Recommend running tests with deprecation warnings, prior to upgrade.
--+
 Reporter:  tomchristie   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"316395d82874beea6af08a873e91b1880d0b982a" 316395d8]:
 {{{
 #!CommitTicketReference repository=""
 revision="316395d82874beea6af08a873e91b1880d0b982a"
 Fixed #26713 -- Documented resolving deprecation warnings before upgrade.
 }}}

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

Re: [Django] #26712: Avoid unnecessary SET TIMEZONE queries on PostgreSQL when no changes are required

[Django]

#26712: Avoid unnecessary SET TIMEZONE queries on PostgreSQL when no changes are
required
-+-
 Reporter:  charettes|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
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
-+-

Comment (by Simon Charette ):

 In [changeset:"271581df606b307d89c141e8b1a50ace763bea81" 271581df]:
 {{{
 #!CommitTicketReference repository=""
 revision="271581df606b307d89c141e8b1a50ace763bea81"
 Refs #26712 -- Removed workarounds for PostgreSQL queries on TIME_ZONE
 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 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.167dc0469d0f0167900410b165a10b22%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26712: Avoid unnecessary SET TIMEZONE queries on PostgreSQL when no changes are required

[Django]

#26712: Avoid unnecessary SET TIMEZONE queries on PostgreSQL when no changes are
required
-+-
 Reporter:  charettes|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
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 Simon Charette ):

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


Comment:

 In [changeset:"b484f167bed61f4cff215208eddf98a0655239d4" b484f167]:
 {{{
 #!CommitTicketReference repository=""
 revision="b484f167bed61f4cff215208eddf98a0655239d4"
 Fixed #26712 -- Avoided unnecessary SET TIMEZONE queries on PostgreSQL.

 A change of the USE_TZ or TIME_ZONE settings doesn't necessarily require a
 change to the active connections' timezones.
 }}}

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

Re: [Django] #21588: "Modifying upload handlers on the fly" documentation doesn't replicate internal magic

[Django]

#21588: "Modifying upload handlers on the fly" documentation doesn't replicate
internal magic
-+-
 Reporter:  Keryn Knight |Owner:
   |  berkerpeksag
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  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 timgraham):

 * needs_better_patch:  0 => 1


Comment:

 Idea for improvement on the 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/095.011f576cafa1405becfc312c6ba588f2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26712: Avoid unnecessary SET TIMEZONE queries on PostgreSQL when no changes are required

[Django]

#26712: Avoid unnecessary SET TIMEZONE queries on PostgreSQL when no changes are
required
-+-
 Reporter:  charettes|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
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:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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

Re: [Django] #26712: Avoid unnecessary SET TIMEZONE queries on PostgreSQL when no changes are required

[Django]

#26712: Avoid unnecessary SET TIMEZONE queries on PostgreSQL when no changes are
required
-+-
 Reporter:  charettes|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 charettes):

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


Comment:

 (I had accidently checked ''needs tests'' instead of ''has patch'' when I
 linked to the 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/067.5d2ea73cf73285db47886de418bd3817%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26690: Add the option in the prefetch_related to have the prefetched results returned as a list or as a queryset

[Django]

#26690: Add the option in the prefetch_related to have the prefetched results
returned as a list or as a queryset
-+-
 Reporter:  Ursidours|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  Prefetch | Triage Stage:
  prefetch_related queryset  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by charettes):

 Personally I'm -0 on adding such a feature for the following reasons:

 > In many cases, there is no need to chain further queries to the default
 prefetch_related. By explicitly asking for a list it would then become
 possible to benefit from the speed improvement.

 The default `prefetch_related()` results are stored in a `QuerySet()` in
 order to make sure the returned instances' prefetched relations still
 behave the same as if they were not prefetched. Storing lists in there
 would make such instances/querysets unusable by many components of Django
 such as forms and model level validation where it would fail in non-
 obvious ways.

 Using `Prefetch('relation', to_attr='relation_as_list')` already serves
 this purpose and don't think introducing another way to do it such as
 `Prefetch('relation', as_list=True)` is worth it. If we'd really want to
 speed up default prefetches I think we should investigate assigning
 objects that quack like `QuerySet` (e.g. `PrefetchedQuerySet`) but only
 lazily build their underlying query when required as this is the part that
 slow down performance here.

 > Conversely, some developers may be happy to take the performance hit in
 order to further refine a Prefetch with to_attr.

 I've never personally required to refine a prefetched result, that sounds
 like an anti-pattern to me.

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

Re: [Django] #26710: CreateModel.references_model should take app_label into account

[Django]

#26710: CreateModel.references_model should take app_label into account
-+-
 Reporter:  sir-sigurd   |Owner:  sir-
 Type:   |  sigurd
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

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

Re: [Django] #16501: Add option to accept unicode characters in SlugField

[Django]

#16501: Add option to accept unicode characters in SlugField
---+
 Reporter:  norn   |Owner:  pbnan
 Type:  New feature|   Status:  closed
Component:  Core (Other)   |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords:  unicode, slug  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Tim Graham ):

 In [changeset:"307de7d9e80e1148685b981eede0bd2fdbe91d46" 307de7d9]:
 {{{
 #!CommitTicketReference repository=""
 revision="307de7d9e80e1148685b981eede0bd2fdbe91d46"
 [1.9.x] Refs #16501, #26474 -- Added xregexp.js source file.

 Backport of 054e74420b7a31bac67d4993b462eea7b9b7a5ba 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/062.10a0b453e9503ea36dded0306045ee23%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26474: Add source of minified javascript files

[Django]

#26474: Add source of minified javascript files
-+-
 Reporter:  rhertzog |Owner:  knightrix
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Packaging|  Version:  1.9
 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 Tim Graham ):

 In [changeset:"307de7d9e80e1148685b981eede0bd2fdbe91d46" 307de7d9]:
 {{{
 #!CommitTicketReference repository=""
 revision="307de7d9e80e1148685b981eede0bd2fdbe91d46"
 [1.9.x] Refs #16501, #26474 -- Added xregexp.js source file.

 Backport of 054e74420b7a31bac67d4993b462eea7b9b7a5ba 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/066.d44a9046e34e88a04f7431b1716a9c8f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26474: Add source of minified javascript files

[Django]

#26474: Add source of minified javascript files
-+-
 Reporter:  rhertzog |Owner:  knightrix
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Packaging|  Version:  1.9
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


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

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

Re: [Django] #26474: Add source of minified javascript files

[Django]

#26474: Add source of minified javascript files
-+-
 Reporter:  rhertzog |Owner:  knightrix
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Packaging|  Version:  1.9
 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 Tim Graham ):

 In [changeset:"36b9e4ab4d188d1adb8167e39a4bda82a957cbc5" 36b9e4a]:
 {{{
 #!CommitTicketReference repository=""
 revision="36b9e4ab4d188d1adb8167e39a4bda82a957cbc5"
 [1.9.x] Refs #26474, DEP 0003 -- Added blanket.js source file.

 Backport of 8f8dc830dfeb321b0de3325a8d2c859fdc20c3af 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/066.e54203f76649026ab6881f26db4d572a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26690: Add the option in the prefetch_related to have the prefetched results returned as a list or as a queryset

[Django]

#26690: Add the option in the prefetch_related to have the prefetched results
returned as a list or as a queryset
-+-
 Reporter:  Ursidours|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  Prefetch | Triage Stage:
  prefetch_related queryset  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * cc: charettes (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Simon, care to add your thoughts?

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

Re: [Django] #16501: Add option to accept unicode characters in SlugField

[Django]

#16501: Add option to accept unicode characters in SlugField
---+
 Reporter:  norn   |Owner:  pbnan
 Type:  New feature|   Status:  closed
Component:  Core (Other)   |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords:  unicode, slug  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Tim Graham ):

 In [changeset:"ef93af919b557563e678ec0f9fb507bd2c6768d9" ef93af91]:
 {{{
 #!CommitTicketReference repository=""
 revision="ef93af919b557563e678ec0f9fb507bd2c6768d9"
 [1.10.x] Refs #16501, #26474 -- Added xregexp.js source file.

 Backport of 054e74420b7a31bac67d4993b462eea7b9b7a5ba 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/062.345487d4452c7d3ed1e79b42916e135c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26474: Add source of minified javascript files

[Django]

#26474: Add source of minified javascript files
-+-
 Reporter:  rhertzog |Owner:  knightrix
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Packaging|  Version:  1.9
 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 Tim Graham ):

 In [changeset:"a9b0b0762fafff3ad9e6df56e781f84ec811c68f" a9b0b07]:
 {{{
 #!CommitTicketReference repository=""
 revision="a9b0b0762fafff3ad9e6df56e781f84ec811c68f"
 [1.10.x] Refs #26474, DEP 0003 -- Added blanket.js source file.

 Backport of 8f8dc830dfeb321b0de3325a8d2c859fdc20c3af 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/066.0da787eca228caa07d63ebb37cbc493c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26474: Add source of minified javascript files

[Django]

#26474: Add source of minified javascript files
-+-
 Reporter:  rhertzog |Owner:  knightrix
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Packaging|  Version:  1.9
 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 Tim Graham ):

 In [changeset:"ef93af919b557563e678ec0f9fb507bd2c6768d9" ef93af91]:
 {{{
 #!CommitTicketReference repository=""
 revision="ef93af919b557563e678ec0f9fb507bd2c6768d9"
 [1.10.x] Refs #16501, #26474 -- Added xregexp.js source file.

 Backport of 054e74420b7a31bac67d4993b462eea7b9b7a5ba 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/066.46649517a04fd7b1f1030f4ed4750d28%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26474: Add source of minified javascript files

[Django]

#26474: Add source of minified javascript files
-+-
 Reporter:  rhertzog |Owner:  knightrix
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Packaging|  Version:  1.9
 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 Tim Graham ):

 In [changeset:"8f8dc830dfeb321b0de3325a8d2c859fdc20c3af" 8f8dc830]:
 {{{
 #!CommitTicketReference repository=""
 revision="8f8dc830dfeb321b0de3325a8d2c859fdc20c3af"
 Refs #26474, DEP 0003 -- Added blanket.js source file.
 }}}

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

Re: [Django] #16501: Add option to accept unicode characters in SlugField

[Django]

#16501: Add option to accept unicode characters in SlugField
---+
 Reporter:  norn   |Owner:  pbnan
 Type:  New feature|   Status:  closed
Component:  Core (Other)   |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords:  unicode, slug  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Tim Graham ):

 In [changeset:"054e74420b7a31bac67d4993b462eea7b9b7a5ba" 054e7442]:
 {{{
 #!CommitTicketReference repository=""
 revision="054e74420b7a31bac67d4993b462eea7b9b7a5ba"
 Refs #16501, #26474 -- Added xregexp.js source file.
 }}}

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

Re: [Django] #26474: Add source of minified javascript files

[Django]

#26474: Add source of minified javascript files
-+-
 Reporter:  rhertzog |Owner:  knightrix
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Packaging|  Version:  1.9
 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 Tim Graham ):

 In [changeset:"054e74420b7a31bac67d4993b462eea7b9b7a5ba" 054e7442]:
 {{{
 #!CommitTicketReference repository=""
 revision="054e74420b7a31bac67d4993b462eea7b9b7a5ba"
 Refs #16501, #26474 -- Added xregexp.js source file.
 }}}

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

Re: [Django] #26707: Add a QueryDict.fromkeys() method

[Django]

#26707: Add a QueryDict.fromkeys() method
-+-
 Reporter:  wimglenn |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  http querydict   | 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:"5ebebd1159b4bacfce1999e41831081679b6f35a" 5ebebd11]:
 {{{
 #!CommitTicketReference repository=""
 revision="5ebebd1159b4bacfce1999e41831081679b6f35a"
 Fixed #26707 -- Added QueryDict.fromkeys()
 }}}

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

Re: [Django] #26683: Oracle DBs: Add option to use VARCHAR2 data type

[Django]

#26683: Oracle DBs: Add option to use VARCHAR2 data type
+-
 Reporter:  elarandjelovic  |Owner:  nobody
 Type:  New feature |   Status:  new
Component:  Migrations  |  Version:  1.9
 Severity:  Normal  |   Resolution:
 Keywords:  Oracle  | Triage Stage:  Someday/Maybe
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+-
Changes (by timgraham):

 * stage:  Unreviewed => Someday/Maybe


Comment:

 If there are advantages to dropping Oracle 11.2 support, we might consider
 making Django 1.11 LTS (supported until at least April 2020) the last
 version to support it.

 I'll bump this ticket to "Someday/Maybe" to get it off the unreviewed
 queue. If we have a specific plan for how to move it forward, we can move
 it to "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/072.975079a54547581f24846065f2e749ba%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26693: RenameModel causes state.apps rendering leading to massive time increase in makemigrations

[Django]

#26693: RenameModel causes state.apps rendering leading to massive time 
increase in
makemigrations
--+
 Reporter:  simonpercivall|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  1.9
 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 timgraham):

 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 In the event this can't be fixed, perhaps we can reclassify as a
 documentation issue.

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

Re: [Django] #26712: Avoid unnecessary SET TIMEZONE queries on PostgreSQL when no changes are required

[Django]

#26712: Avoid unnecessary SET TIMEZONE queries on PostgreSQL when no changes are
required
-+-
 Reporter:  charettes|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_docs:  0 => 1
 * has_patch:  0 => 1
 * 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/067.4152d4ba67ac53ebee82b27068fe40e1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26713: Recommend running tests with deprecation warnings, prior to upgrade.

[Django]

#26713: Recommend running tests with deprecation warnings, prior to upgrade.
--+
 Reporter:  tomchristie   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  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 timgraham):

 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 I merged the second PR and left a few comments for improvement on the
 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/069.f5b2a919dc0b535700712d68cc8e69bf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26706: Reverse many to one and forward many to many managers's prefetch object cache should be cleared on clear().

[Django]

#26706: Reverse many to one and forward many to many managers's prefetch object
cache should be cleared on clear().
-+-
 Reporter:  cosmosgenius |Owner:  yoongkang
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  manytomany m2m   | Triage Stage:  Ready for
  clear  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 I agree the current behavior might be unexpected, however, I'm not sure if
 it's a good idea to add this behavior on some manager methods but not
 others (see #25344)? At least the behavior should be documented, probably.

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

Re: [Django] #26713: Recommend running tests with deprecation warnings, prior to upgrade.

[Django]

#26713: Recommend running tests with deprecation warnings, prior to upgrade.
-+-
 Reporter:  tomchristie  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 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 tomchristie):

 Also related - link prominently to the upgrade docs from the release
 notes.

 PR: https://github.com/django/django/pull/6733

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

Re: [Django] #26713: Recommend running tests with deprecation warnings, prior to upgrade.

[Django]

#26713: Recommend running tests with deprecation warnings, prior to upgrade.
-+-
 Reporter:  tomchristie  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 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 tomchristie):

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


Comment:

 PR: https://github.com/django/django/pull/6732

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

[Django] #26713: Recommend running tests with deprecation warnings, prior to upgrade.

[Django]

#26713: Recommend running tests with deprecation warnings, prior to upgrade.
--+
 Reporter:  tomchristie   |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Currently the upgrade docs recommend upgrading Django, and then working
 through the tests with deprecation warnings turned on.

 Really we ought to recommend working through the tests with deprecation
 warnings turned on *first* prior to upgrading.

 Further discussion on this at https://groups.google.com/forum/#!topic
 /django-developers/tz40MK4AOjo

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

Re: [Django] #26251: SimpleArrayField missing clean method which leads to unexpected validation error.

[Django]

#26251: SimpleArrayField missing clean method which leads to unexpected 
validation
error.
-+-
 Reporter:  sgallen  |Owner:  sgallen
 Type:  Bug  |   Status:  assigned
Component:  contrib.postgres |  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:  postgres,| Triage Stage:  Accepted
  arrayfield, simplearrayfield   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by mvantellingen):

 * cc: michaelvantellingen@… (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/065.c103113b32cbb9ccc693a69c4c972093%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.