It would be lovely if timestamps with milliseconds were accepted & parsed.
eg
df 1397478409577

also, this is awesome

I've seen in the Alfred forum post that you were working on a tz parameter.
Did you publish it after all? If so, how one use it?

Thanks 🙂

df 1518372345
show 2018-02-11 18:05:45

Actually 2018/2/12 2:5:45

Apple removed the system python 2. I use this workflow all the time and needed to bring it back. Here's what I did.

First get python 2 back

# Download/run the legacy macOS installer (pick which one for your sys)
https://www.python.org/downloads/release/python-2716/

# Add pip for python2.7
curl https://bootstrap.pypa.io/pip/2.7/get-pip.py -o get-pip2.py
python2 get-pip2.py

# Add the missing macos plist lib alfred uses
curl https://raw.githubusercontent.com/python/cpython/2.7/Lib/plistlib.py -o /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plistlib.py

# Add missing pip for this workflow
python2 -m pip install delorean

# Optionally add the helpers like easy_install back onto your path
# In your ~/.zprofile or whatever bash/shell profile equivalent
PATH="/Library/Frameworks/Python.framework/Versions/2.7/bin:${PATH}"
export PATH

Now open alfred preferences > Workflows > double click on the script filter square in the workflow GUI
Update the script filter to one of the two below.

If which python shows 2.7

/usr/local/bin/python process.py "{query}"

If which python shows 3...

/usr/local/bin/python2 process.py "{query}"

For more legacy python2 help I wrote an SO post: https://stackoverflow.com/a/71513250/786389

The conversion from unix time is not working for me.

I am using Alfred 3 but this should not matter as putting now works as expected.