[issue9305] Don't use east/west of UTC in date/time documentation

Change by Stanley : -- nosy: +slateny nosy_count: 14.0 -> 15.0 pull_requests: +29817 pull_request: https://github.com/python/cpython/pull/31697 ___ Python tracker ___ __

[issue9305] Don't use east/west of UTC in date/time documentation

Change by Murali Ravipudi : -- nosy: +Murali Ravipudi ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue9305] Don't use east/west of UTC in date/time documentation

Chris Wilcox added the comment: Are you still working on this Ajay Mahato? -- nosy: +crwilcox ___ Python tracker ___ ___ Python-bugs

[issue9305] Don't use east/west of UTC in date/time documentation

Ajay Mahato added the comment: I am taking up this issue. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue9305] Don't use east/west of UTC in date/time documentation

Ajay Mahato added the comment: I would like to work on this issue. Please assign this to me. -- nosy: +Ajay Mahato ___ Python tracker ___ __

[issue9305] Don't use east/west of UTC in date/time documentation

Change by Paul Ganssle : -- nosy: +p-ganssle ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue9305] Don't use east/west of UTC in date/time documentation

Cheryl Sabella added the comment: Would one of the original authors of the patches like to create a GitHub pull request for this issue? -- nosy: +csabella ___ Python tracker __

[issue9305] Don't use east/west of UTC in date/time documentation

Martin Panter added the comment: Assuming you meant Issue 8810, yes these patches would collide with each other. I am yet to look at the patches, but I gess they should be merged. -- dependencies: +TZ offset description is unclear in docs -Don't use east/west of UTC in date/time docume

[issue9305] Don't use east/west of UTC in date/time documentation

Alexander Belopolsky added the comment: This seems to be touching the same areas as #9305. -- assignee: belopolsky -> ___ Python tracker ___ _

[issue9305] Don't use east/west of UTC in date/time documentation

Changes by Alexander Belopolsky : -- dependencies: +Don't use east/west of UTC in date/time documentation ___ Python tracker ___ ___ Py

[issue9305] Don't use east/west of UTC in date/time documentation

Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue9305] Don't use east/west of UTC in date/time documentation

Mark Lawrence added the comment: Well, we have a patch and it's been discussed here and on #7229, so can we take this forward? -- nosy: +BreamoreBoy ___ Python tracker ___ __

[issue9305] Don't use east/west of UTC in date/time documentation

Alexander Belopolsky added the comment: I've noticed that the time module docstring handles this issue rather nicely: >>> help('time') ... timezone -- difference in seconds between UTC and local standard time altzone -- difference in seconds between UTC and local DST time We can use s

[issue9305] Don't use east/west of UTC in date/time documentation

Rodrigo Bernardo Pimentel added the comment: 1. Done (it's on the patch I'm uploading). Sorry. 3. Ok, we've rewritten that sentence. As Henrique mentioned, we're working on a larger patch to make datetime documentation clearer, and we can include a definition of "standard time" there. 2. I

[issue9305] Don't use east/west of UTC in date/time documentation

Henrique Bastos added the comment: To clarify: 1) "we" means henriquebastos, rbp, Rodolpho.Eckhardt. 2) Mentioning fdrake I was trying to say that we followed his suggestion to only submit the specific changes on this patch, leaving further documentation changes to another issue. Sorry abou

[issue9305] Don't use east/west of UTC in date/time documentation

Alexander Belopolsky added the comment: On the second reading, I have a few issues with the patch. 1. Please run makepatcheck. There are whitespace issues in datetime.rst. 2. In docstrings, you remove the information about the sign. I would not mind leaving docstrings the way they are. Othe

[issue9305] Don't use east/west of UTC in date/time documentation

Changes by Alexander Belopolsky : -- assignee: d...@python -> belopolsky stage: needs patch -> commit review ___ Python tracker ___ ___

[issue9305] Don't use east/west of UTC in date/time documentation

Alexander Belopolsky added the comment: LGTM -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue9305] Don't use east/west of UTC in date/time documentation

Henrique Bastos added the comment: Here goes a patch to replace east/west references on datetime documentation. As spoken with fdrake we think the datetime documentation could be improved extracting the timezone subclassing details to specific section. We'll be filling a new issue for that pa

[issue9305] Don't use east/west of UTC in date/time documentation

Henrique Bastos added the comment: Here goes a patch to replace east/west references on datetime documentation. As spoken with fdrake we think the datetime documentation could be improved extracting the timezone subclassing details to specific section. We'll be filling a new issue for that pa

[issue9305] Don't use east/west of UTC in date/time documentation

Changes by Rodrigo Bernardo Pimentel : -- nosy: +rbp ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue9305] Don't use east/west of UTC in date/time documentation

Alexander Belopolsky added the comment: On Tue, Jul 20, 2010 at 12:08 PM, anatoly techtonik wrote: .. > Ok. Sold. Good. All we need now is just a patch. :-) -- ___ Python tracker

[issue9305] Don't use east/west of UTC in date/time documentation

Alexander Belopolsky added the comment: On Tue, Jul 20, 2010 at 12:14 PM, Alexander Belopolsky wrote: .. > Interesting.  I actually like the original wording better.  For me, > "my watch is 6 hours behind UTC" makes it clear that when the Big Ben > clock shows tea time (18:00), my watch display

[issue9305] Don't use east/west of UTC in date/time documentation

Alexander Belopolsky added the comment: On Tue, Jul 20, 2010 at 11:39 AM, Tim Peters wrote: >..  As I recall it, the current wording was just to avoid saying "ahead of >UTC" or "behind UTC" (which was the original wording). Interesting. I actually like the original wording better. For me, "

[issue9305] Don't use east/west of UTC in date/time documentation

Fred L. Drake, Jr. added the comment: On Tue, Jul 20, 2010 at 12:08 PM, anatoly techtonik wrote: > I've took the convention from here. I thought docs are generated from > docstrings. They're not, but I don't think that really matters. Older documentation used the imperative form consistently,

[issue9305] Don't use east/west of UTC in date/time documentation

anatoly techtonik added the comment: > Documenting utcoffset() as "Return timedelta equal to local UTC > offset." is almost circular.  It does not explain whether it has to be > added or subtracted from UTC to arrive at local time. Ok. Sold. >> I believe the correct convention is "Return timed

[issue9305] Don't use east/west of UTC in date/time documentation

Fred L. Drake, Jr. added the comment: On Tue, Jul 20, 2010 at 10:46 AM, anatoly techtonik wrote: > I believe the correct convention is "Return timedelta...". This is handled inconsistently in the documentation; I'm hoping the current maintainers reinforce the "Returns ..." structure. The docu

[issue9305] Don't use east/west of UTC in date/time documentation

Tim Peters added the comment: FYI, I like the change. As I recall it, the current wording was just to avoid saying "ahead of UTC" or "behind UTC" (which was the original wording). Technically pure or not, I never saw anyone get truly confused by "East of UTC" or "West of UTC", but I fully t

[issue9305] Don't use east/west of UTC in date/time documentation

Alexander Belopolsky added the comment: On Tue, Jul 20, 2010 at 10:46 AM, anatoly techtonik wrote: > .. Another > concern - if UTC is 0 reference point then there is no reason to add > something to it - you just can say - "Return timedelta equal to local > UTC offset." No, UTC is not a 0 refer

[issue9305] Don't use east/west of UTC in date/time documentation

anatoly techtonik added the comment: On Mon, Jul 19, 2010 at 7:21 PM, Alexander Belopolsky wrote: > > I suggest the following wording for time.timezone description: > > time.timezone: The number of seconds one must add to the local time to arrive > at UTC. Makes sense. I can't see any other r

[issue9305] Don't use east/west of UTC in date/time documentation

Changes by Alexander Belopolsky : -- dependencies: +Manual entry for time.daylight can be misleading ___ Python tracker ___ ___ Python-

[issue9305] Don't use east/west of UTC in date/time documentation

New submission from Alexander Belopolsky : I am opening this to supersede issue7229. See discussion following msg107148. In many places offsets representing the difference between local time and UTC are described as minutes or seconds east or west of UTC. This is not correct because UTC is