Re: [Django] #29546: deprecate timezone.FixedOffset in favor of datetime.timezone

[Django]

#29546: deprecate timezone.FixedOffset in favor of datetime.timezone
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 Type:   |  Fedoseev
  Cleanup/optimization   |   Status:  closed
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"cb2be9d5d57c34a70f0c549b780183f8c73aec4b" cb2be9d5]:
 {{{
 #!CommitTicketReference repository=""
 revision="cb2be9d5d57c34a70f0c549b780183f8c73aec4b"
 Refs #29546 -- Removed django.utils.timezone.FixedOffset per deprecation
 timeline.
 }}}

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

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

Re: [Django] #29546: deprecate timezone.FixedOffset in favor of datetime.timezone

[Django]

#29546: deprecate timezone.FixedOffset in favor of datetime.timezone
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 Type:   |  Fedoseev
  Cleanup/optimization   |   Status:  closed
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"338f741c5eb6b91118f6a6b7c34b5e9b47a5661d" 338f741]:
 {{{
 #!CommitTicketReference repository=""
 revision="338f741c5eb6b91118f6a6b7c34b5e9b47a5661d"
 Fixed #29546 -- Deprecated django.utils.timezone.FixedOffset.
 }}}

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

Re: [Django] #29546: deprecate timezone.FixedOffset in favor of datetime.timezone

[Django]

#29546: deprecate timezone.FixedOffset in favor of datetime.timezone
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 Type:   |  Fedoseev
  Cleanup/optimization   |   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
-+-

Comment (by Tim Graham):

 Perhaps the deprecation should be delayed and included in #27753,
 otherwise projects that want to continue to support Python2  won't be able
 to avoid the deprecation warning. Django's usage of `FixedOffset` could be
 removed now.

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

Re: [Django] #29546: deprecate timezone.FixedOffset in favor of datetime.timezone

[Django]

#29546: deprecate timezone.FixedOffset in favor of datetime.timezone
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 Type:   |  Fedoseev
  Cleanup/optimization   |   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 Sergey Fedoseev):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/10145 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/068.4a795c24461962fb3eb04412bfd79698%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29546: deprecate timezone.FixedOffset in favor of datetime.timezone

[Django]

#29546: deprecate timezone.FixedOffset in favor of datetime.timezone
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 Type:   |  Fedoseev
  Cleanup/optimization   |   Status:  assigned
Component:  Utilities|  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 Tim Graham):

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

Re: [Django] #29546: deprecate timezone.FixedOffset in favor of datetime.timezone

[Django]

#29546: deprecate timezone.FixedOffset in favor of datetime.timezone
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 Type:   |  Fedoseev
  Cleanup/optimization   |   Status:  assigned
Component:  Utilities|  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 Sergey Fedoseev):

 * status:  new => assigned
 * owner:  nobody => Sergey Fedoseev


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

[Django] #29546: deprecate timezone.FixedOffset in favor of datetime.timezone

[Django]

#29546: deprecate timezone.FixedOffset in favor of datetime.timezone
+
   Reporter:  Sergey Fedoseev   |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Utilities |Version:  master
   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 |
+
 We have `FixedOffset` class each instance of which represents a timezone
 defined by a fixed offset from UTC, in Python 3.2 was added
 `datetime.timezone` class needed for the same purpose, so now we can get
 rid of our implementation.
 The possible pitfall is that `FixedOffset.dst()` returns `timedelta(0)`,
 but `datetime.timezone.dst()` returns `None`.

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

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