weird behavior difference: arrow.utcnow().timestamp and arrow.utcnow().timestamp()

[Distortedlogic]

I have two screenshots of running arrow.utcnow().timestamp and arrow.utcnow().timestamp() both on google colab and a local jupyter lab instance. On google collab, arrow.utcnow().timestamp() returns as expected, and as per the arrow docs. On the jupyter lab instance, arrow.utcnow().timestamp() raises TypeError: 'int' object is not callable and arrow.utcnow().timestamp returns the expected value as an int.

Google Colab with expected behavior, Python 3.7.12

Jupyter Lab with unexpected behavior, Python 3.9.7

Jupyter version info

System Info

• 🖥 OS name and version: windows 10 pro 10.0.19043
• 🏹 Arrow version: 1.2.1

[Distortedlogic]

Upon further investigation, it appears this is an OS difference. I ran the same lines of arrow in the python interpreter on my windows machine to one result and in a linux docker container to a different result replicating the scenario above with linux producing the expected behavior.

On windows

On linux in docker