T]jR*ddlZddlZddlZddZdZy)Nc|ddlm}nt|dk(sJ|ddvsJ|ddk(rdnd}djd |d|D}d }|dd k(r|d xs t }d |z}nG|ddk(r|d dk(rt }|r+d|z}n%|ddk7rdddd}||dt |d z}t ||zS)z8Returns a PEP 386-compliant version number from VERSION.Nr)VERSION)alphabetarcfinal.c32K|]}t|ywN)str).0xs T/var/www/zogu/zoguvenv/lib/python3.12/site-packages/easy_thumbnails/version_utils.py zget_version..s4qCF4spostz.post%srz.dev%sr z.az.bz.rc)rrr )easy_thumbnailsrlenjoinget_git_changesetr)versionpartsmainsubsub_v git_changesetmappings r get_versionr"s67|q   qz====qAaE 884GFUO4 4D CqzV 1/1% w 71:?)+ ]*C w  $e<gaj!C O3 tcz?ctjjtjjtjjt}t j dt jt jd|d}|jd} tjjt|}|jdS#t$rYywxYw)a%Returns a numeric identifier of the latest git changeset. The result is the UTC timestamp of the changeset in YYYYMMDDHHMMSS format. This value isn't guaranteed to be unique, but collisions are very unlikely, so it's sufficient for generating the development version numbers. z+git log --pretty=format:%ct --quiet -1 HEADT)stdoutstderrshellcwduniversal_newlinesrNz %Y%m%d%H%M%S)ospathdirnameabspath__file__ subprocessPopenPIPE communicatedatetimeutcfromtimestampint ValueErrorstrftime)repo_dirgit_log timestamps rrr'swwrwwrwwx/HIJH5zT;G##%a(I%%66s9~F    n -- s)(C"" C.-C.r)r3r*r/r"rr#rr<s B.r#