`time` module does not translate well!

Describe the bug when using methods from the time module, the only method that is translated properly is time.sleep(), while the others result the same python code in Go.

Python code example

import time

def main():
    print(time.time())
    print(time.time_ns())
    print(time.ctime(time.time()))

if __name__ == '__main__':
    main()

Current behavior the above three methods are not being translated into Go code but rather written as is in python, and this code is generated. which is not a valid Go code!

package main

import "fmt"

func main() {
	fmt.Println(time.time())
	fmt.Println(time.time_ns())
	fmt.Println(time.ctime(time.time()))
}

Expected behavior

1. time.time() should be translated into time.Now().Unix() in Go
2. time.time_ns() should be translated into time.Now().UnixNano() in Go
3. time.ctime(time.time()) should be translated into time.Now() in Go

Correct Go code example

package main

import (
	"fmt"
	"time"
)

func main() {
	fmt.Println(time.Now().Unix())
	fmt.Println(time.Now().UnixNano())
	fmt.Println(time.Now())
}

[mbaraa]

@mbaraa But they return different types, I believe.

https://pkg.go.dev/time#Time.Unix - int64 (second precision) https://docs.python.org/3/library/time.html#time.time - float (precision better than 1 second on most systems)

I agree it’s a bit weird but I’m not sure of a better way to get nanosecond precision on a float like Python does. Example where this kinda matters:

t1 = time.time()
half_second_operation()
t2 = time.time()
print(t2 - t1)

If you want that to print approximately 0.5 in Go, you’d need to preserve that information right?

I could add an explicit case for int(time.time()) to simplify it to time.Now().Unix()

aha, I thought time.time() returns an int in python. my bad 😅

[nottheswimmer]

@mbaraa But they return different types, I believe.

https://pkg.go.dev/time#Time.Unix - int64 (second precision) https://docs.python.org/3/library/time.html#time.time - float (precision better than 1 second on most systems)

I agree it’s a bit weird but I’m not sure of a better way to get nanosecond precision on a float like Python does. Example where this kinda matters:

t1 = time.time()
half_second_operation()
t2 = time.time()
print(t2 - t1)

If you want that to print approximately 0.5 in Go, you’d need to preserve that information right?

I could add an explicit case for int(time.time()) to simplify it to time.Now().Unix()