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

2022-03-05 Thread Stanley
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

2020-02-14 Thread Murali Ravipudi
Change by Murali Ravipudi : -- nosy: +Murali Ravipudi ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

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

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

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

2019-01-04 Thread Ajay Mahato
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

2019-01-04 Thread Ajay Mahato
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

2018-07-05 Thread Paul Ganssle
Change by Paul Ganssle : -- nosy: +p-ganssle ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

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

2017-10-24 Thread Cheryl Sabella
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

2014-06-29 Thread Alexander Belopolsky
Changes by Alexander Belopolsky alexander.belopol...@gmail.com: -- dependencies: +Don't use east/west of UTC in date/time documentation ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9305 ___

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

2014-06-29 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: This seems to be touching the same areas as #9305. -- assignee: belopolsky - ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9305 ___

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

2014-02-03 Thread Mark Lawrence
Changes by Mark Lawrence breamore...@yahoo.co.uk: -- nosy: -BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9305 ___ ___

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

2013-03-30 Thread Mark Lawrence
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 rep...@bugs.python.org http://bugs.python.org/issue9305

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

2011-01-11 Thread Alexander Belopolsky
Alexander Belopolsky belopol...@users.sourceforge.net 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

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

2010-11-20 Thread Rodrigo Bernardo Pimentel
Changes by Rodrigo Bernardo Pimentel r...@isnomore.net: -- nosy: +rbp ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9305 ___ ___ Python-bugs-list

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

2010-11-20 Thread Henrique Bastos
Henrique Bastos henri...@bastos.net 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

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

2010-11-20 Thread Henrique Bastos
Henrique Bastos henri...@bastos.net 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

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

2010-11-20 Thread Alexander Belopolsky
Alexander Belopolsky belopol...@users.sourceforge.net added the comment: LGTM -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9305 ___ ___

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

2010-11-20 Thread Alexander Belopolsky
Changes by Alexander Belopolsky belopol...@users.sourceforge.net: -- assignee: d...@python - belopolsky stage: needs patch - commit review ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9305

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

2010-11-20 Thread Alexander Belopolsky
Alexander Belopolsky belopol...@users.sourceforge.net 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

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

2010-11-20 Thread Henrique Bastos
Henrique Bastos henri...@bastos.net 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

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

2010-11-20 Thread Rodrigo Bernardo Pimentel
Rodrigo Bernardo Pimentel r...@isnomore.net 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

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

2010-07-20 Thread anatoly techtonik
anatoly techtonik techto...@gmail.com added the comment: On Mon, Jul 19, 2010 at 7:21 PM, Alexander Belopolsky rep...@bugs.python.org 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.

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

2010-07-20 Thread Alexander Belopolsky
Alexander Belopolsky belopol...@users.sourceforge.net added the comment: On Tue, Jul 20, 2010 at 10:46 AM, anatoly techtonik rep...@bugs.python.org 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

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

2010-07-20 Thread Tim Peters
Tim Peters tim.pet...@gmail.com 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,

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

2010-07-20 Thread Fred L. Drake, Jr.
Fred L. Drake, Jr. fdr...@acm.org added the comment: On Tue, Jul 20, 2010 at 10:46 AM, anatoly techtonik techto...@gmail.com wrote: I believe the correct convention is Return timedelta This is handled inconsistently in the documentation; I'm hoping the current maintainers reinforce the

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

2010-07-20 Thread anatoly techtonik
anatoly techtonik techto...@gmail.com 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

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

2010-07-20 Thread Fred L. Drake, Jr.
Fred L. Drake, Jr. fdr...@acm.org added the comment: On Tue, Jul 20, 2010 at 12:08 PM, anatoly techtonik rep...@bugs.python.org 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

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

2010-07-20 Thread Alexander Belopolsky
Alexander Belopolsky belopol...@users.sourceforge.net added the comment: On Tue, Jul 20, 2010 at 11:39 AM, Tim Peters rep...@bugs.python.org 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

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

2010-07-20 Thread Alexander Belopolsky
Alexander Belopolsky belopol...@users.sourceforge.net added the comment: On Tue, Jul 20, 2010 at 12:14 PM, Alexander Belopolsky rep...@bugs.python.org 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

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

2010-07-20 Thread Alexander Belopolsky
Alexander Belopolsky belopol...@users.sourceforge.net added the comment: On Tue, Jul 20, 2010 at 12:08 PM, anatoly techtonik rep...@bugs.python.org 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

2010-07-19 Thread Alexander Belopolsky
New submission from Alexander Belopolsky belopol...@users.sourceforge.net: 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.

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

2010-07-19 Thread Alexander Belopolsky
Changes by Alexander Belopolsky belopol...@users.sourceforge.net: -- dependencies: +Manual entry for time.daylight can be misleading ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9305 ___