[Python-bugs-list] [ python-Bugs-697985 ] Move gmtime function from calendar to time module

[SourceForge.net]

Bugs item #697985, was opened at 2003-03-05 05:40
Message generated for change (Comment added) made by bcannon
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=697985&group_id=5470

Category: Python Library
Group: Feature Request
Status: Open
Resolution: None
Priority: 5
Submitted By: Erland Lewin (erl)
Assigned to: Nobody/Anonymous (nobody)
Summary: Move gmtime function from calendar to time module

Initial Comment:
The gmtime function in the calendar module would be
much more logical to have in the time module, since it
manipulates tm tuples and unix timestamps, which the
other functions in time do, but no other functions in
calendar.

Related to bug #697983


----------------------------------------------------------------------

>Comment By: Brett Cannon (bcannon)
Date: 2003-05-28 18:50

Message:
Logged In: YES 
user_id=357491

OK, assuming the OP meant calendar.timegm , doesn't time.mktime provide 
the same functionality?  Or is the desire to have it because  it specifies the 
epoch as 1970-01-01?

----------------------------------------------------------------------

Comment By: Tim Peters (tim_one)
Date: 2003-05-22 21:47

Message:
Logged In: YES 
user_id=31435

I expect the OP meant the calendar.timegm() function.

----------------------------------------------------------------------

Comment By: Neal Norwitz (nnorwitz)
Date: 2003-05-22 14:46

Message:
Logged In: YES 
user_id=33168

The gmtime function is in time, not calendar.  Did you mean
the opposite that you believe gmtime should be in calendar?
  gmtime comes from the C version which is the purpose of
time, to expose C functions.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=697985&group_id=5470