~+h, dZddlmZddlZddlZddlmZddlmZddl m Z m Z m Z dZ Gdd eZGd d ej e d d dZej$ZGddeZGddeZGddej e ddZej$ZGddeZGddeZGddeZGdd eZy)!zSThis module defines the Version classes, and the related Manifest implementations. )with_statementN)six)FileHunk)md5_constructorRegistryMetaclassis_url) get_versionerVersionIndeterminableErrorVersionTimestampVersion get_manifest HashVersionManifest FileManifestc eZdZy)r N)__name__ __module__ __qualname__D/var/www/html/venv/lib/python3.12/site-packages/webassets/version.pyr r srr ceZdZdZddZdZy)r aUA Version class that can be assigned to the ``Environment.versioner`` attribute. Given a bundle, this must determine its "version". This version can then be used in the output filename of the bundle, or appended to the url as a query string, in order to expire cached assets. A version could be a timestamp, a content hash, or a git revision etc. As a user, all you need to care about, in most cases, is whether you want to set the ``Environment.versioner`` attribute to ``hash`` or ``timestamp``. A single instance can be used with different environments. Nct)aReturn a string that represents the current version of the given bundle. This method is called on two separate occasions: 1) After a bundle has been built and is about to be saved. If the output filename contains a placeholder, this method is asked for the version. This mode is indicated by the ``hunk`` argument being available. 2) When a version is required for an already built file, either because: *) An URL needs to be constructed. *) It needs to be determined if a bundle needs an update. *This will only occur* if *no manifest* is used. If there is a manifest, it would be used to determine the version instead. Support for option (2) is optional. If not supported, then in those cases a manifest needs to be configured. ``VersionIndeterminableError`` should be raised with a message why. NotImplementedError)selfbundlectxhunks rdetermine_versionzVersion.determine_version*s 0"##rcy)z_Hook called after a bundle has been built. Some version classes may need this. Nrrrrfilenameversions r set_versionzVersion.set_versionDsrN)rrr__doc__r r%rrrr r s $4 rr ctSr&)r rrrr)s'rr za version implementation)clazz attributedesccBeZdZdZdZddZdZedZedZ y) r zwUses the most recent 'last modified' timestamp of all source files as the version. Uses second-precision. timestampNc|s8ddlm}||js |j|j |S |j ||S#t $r|JtdwxYw)Nrhas_placeholderzddlm}||jst|j |}n t d|j }|j|jjd|jd|jS)Nrr0zoutput target has a placeholderzutf-8) r2r1r3rr5r rNupdatedataencode hexdigestrI)rrrrr1rNs rr zHashVersion.determine_versions 8"6==1 5 5c :;1577 diik((12!,4;;//rr&) rrrr'rDrErKrrOr rrrrrs1 B o 0rrceZdZdZdZdZy)ravPersists information about the versions bundles are at. The Manifest plays a role only if you insert the bundle version in your output filenames, or append the version as a querystring to the url (via the url_expire option). It serves two purposes: - Without a manifest, it may be impossible to determine the version at runtime. In a deployed app, the media files may be stored on a different server entirely, and be inaccessible from the application code. The manifest, if shipped with your application, is what still allows to construct the proper URLs. - Even if it were possible to determine the version at runtime without a manifest, it may be a costly process, and using a manifest may give you better performance. If you use a hash-based version for example, this hash would need to be recalculated every time a new process is started. (*) (*) It needs to happen only once per process, because Bundles are smart enough to cache their own version in memory. A special case is the ``Environment.auto_build`` option. A manifest implementation should re-read its data from its out-of-process data source on every request, if ``auto_build`` is enabled. Otherwise, if your application is served by multiple processes, then after an automatic rebuild in one process all other processes would continue to serve an old version of the file (or attach an old version to the query string). A manifest instance is currently not guaranteed to function correctly with multiple Environment instances. ctr&rrrrr$s rrememberzManifest.remember !##rctr&rrrrs rqueryzManifest.queryrYrN)rrrr'rXr\rrrrrs@$$rrctSr&)rrrrr)r)s(rza manifest implementation)r*r,cDeZdZdZdZed dZdZdZdZ dZ d Z y) raStores version data in a single file. Uses Python's pickle module to store a dict data structure. You should only use this when the manifest is read-only in production, since it is not multi-process safe. If you use ``auto_build`` in production, use ``CacheManifest`` instead. By default, the file is named ".webassets-manifest" and stored in ``Environment.directory``. fileNcj|sd}|tjj|j|S)Nz.webassets-manifest)r:pathjoin directory)r@rr#s rrKzFileManifest.makes(,H277<< x899rc2||_|jyr&)r#_load_manifest)rr#s rrOzFileManifest.__init__s   rcV||j|j<|jyr&)manifestr3_save_manifestrWs rrXzFileManifest.remembers '. fmm$ rc|jr|j|jj|jdSr&) auto_buildrerggetr3r[s rr\zFileManifest.querys0 >>    !}}  55rctjj|jr:t |jd5}t j ||_dddyi|_y#1swYyxYw)Nrb)r:raexistsr#openpickleloadrgrfs rrezFileManifest._load_manifestsX 77>>$-- (dmmT* /a & A  / /DM / /s A,,A5ct|jd5}tj|j|ddddy#1swYyxYw)Nwb)protocol)ror#rpdumprgrrs rrhzFileManifest._save_manifests; $-- & 6! KK q1 5 6 6 6s #AA r&) rrrr'rDrErKrOrXr\rerhrrrrrs9  B:: 6 6rrc2eZdZdZdZfdZdZdZxZS) JsonManifestz:Same as ``FileManifest``, but uses JSON instead of pickle.jsoncj ddl}||_tt||i|y#t$rddl}Y*wxYw)Nr)r{ ImportError simplejsonsuperrzrO)rakwr{ __class__s rrOzJsonManifest.__init__s< &   lD*A44 & % &s " 22ctjj|jr@t |jd5}|j j ||_dddyi|_y#1swYyxYw)Nr)r:rarnr#ror{rqrgrrs rrezJsonManifest._load_manifests] 77>>$-- (dmmS) 2Q $ q 1  2 2DM 2 2s !A22A;ct|jd5}|jj|j|dddddy#1swYyxYw)NwT)indent sort_keys)ror#r{rxrgrrs rrhzJsonManifest._save_manifestsG $-- % G IINN4==!AN F G G Gs *A  A) rrrr'rDrOrerh __classcell__)rs@rrzrzsD B5Grrzc&eZdZdZdZdZdZdZy) CacheManifestawStores version data in the webassets cache. Since this has bad portability (you hardly want to copy your cache between machines), this only makes sense when you are building on the same machine where you're application code runs. When you are using ``auto_build`` in production, this is exactly what you want to use, since it is multi-process safe. cachec2|js tdy)NzAYou are using the cache manifest, but have not enabled the cache.)rEnvironmentError)rrs r_checkzCacheManifest._check)s yy"%& &rcv|j||jjd|jf|yNrg)rrsetr3rWs rrXzCacheManifest.remember/s) C z6==17;rcr|j||jjd|jfSr)rrrkr3r[s rr\zCacheManifest.query3s* Cyy}}j&--899rN)rrrr'rDrrXr\rrrrrs B& <:rrceZdZdZdZy)SymlinkManifestzcCreates a symlink to the actual file. E.g. compressed-current.js -> compressed-1ebcdc5.js ctr&r)rs rrOzSymlinkManifest.__init__BrYrN)rrrr'rOrrrrr8s $rr)r' __future__rr:rp webassetsrwebassets.mergerwebassets.utilsrrr__all__ Exceptionr with_metaclassr resolver r rrr rrzrrrrrrs& $FF G   /  c  !2 %8 #"%&/ d 5w5p"0'"0J&$!s!!"3 !<#>?&$R *68*6ZG<G2:H:8 $h $r