o cZh@sddlZddlmZddlmZddlmZddlm Z ddl m Z ddl m Z ddlmZGd d d ZGd d d eZGd ddeZGdddeZGdddeZGdddeZdS)N) gettext_lazy) exceptions)unicode_http_header_reverse) api_settings)replace_query_param) _MediaTypec@s8eZdZejZejZejZ ddZ dddZ ddZ dS) BaseVersioningcOsd}t|j|jjd)Nz.{cls}.determine_version() must be implemented.)cls)NotImplementedErrorformat __class____name__)selfrequestargskwargsmsgrP/var/www/html/lang_env/lib/python3.10/site-packages/rest_framework/versioning.pydetermine_versionsz BaseVersioning.determine_versionNcKst|||||fi|SNrrviewnamerrrr extrarrrreverseszBaseVersioning.reversecCs&|jsdS|dur||jkp||jvS)NT)allowed_versionsdefault_version)rversionrrris_allowed_versions z!BaseVersioning.is_allowed_versionNNNN) r __module__ __qualname__rDEFAULT_VERSIONrZALLOWED_VERSIONSrZ VERSION_PARAM version_paramrrr rrrrr s  r c@s eZdZdZedZddZdS)AcceptHeaderVersioningzb GET /something/ HTTP/1.1 Host: example.com Accept: application/json; version=1.0 z#Invalid version in "Accept" header.cOs>t|j}|j|j|j}t|}||st |j |Sr) r Zaccepted_media_typeparamsgetr%rrr rZ NotAcceptableinvalid_version_message)rrrr media_typerrrrr*s   z(AcceptHeaderVersioning.determine_versionN)rr"r#__doc___r)rrrrrr&"s r&c2eZdZdZedZddZdfdd ZZS) URLPathVersioninga8 To the client this is the same style as `NamespaceVersioning`. The difference is in the backend - this implementation uses Django's URL keyword arguments to determine the version. An example URL conf for two views that accept two different versions. urlpatterns = [ re_path(r'^(?P[v1|v2]+)/users/$', users_list, name='users-list'), re_path(r'^(?P[v1|v2]+)/users/(?P[0-9]+)/$', users_detail, name='users-detail') ] GET /1.0/something/ HTTP/1.1 Host: example.com Accept: application/json zInvalid version in URL path.cOs8||j|j}|dur|j}||st|j|Sr)r(r%rr rNotFoundr)rrrrrrrrrIs   z#URLPathVersioning.determine_versionNc sB|jdur|dur in|}|j||j<tj|||||fi|Sr)rr%superrrrrrrRs   zURLPathVersioning.reverser! rr"r#r+r,r)rr __classcell__rrr2rr.6s  r.cs:eZdZdZedZddZd fdd Zdd ZZ S) NamespaceVersioninga To the client this is the same style as `URLPathVersioning`. The difference is in the backend - this implementation uses Django's URL namespaces to determine the version. An example URL conf that is namespaced into two separate versions # users/urls.py urlpatterns = [ path('/users/', users_list, name='users-list'), path('/users//', users_detail, name='users-detail') ] # urls.py urlpatterns = [ path('v1/', include('users.urls', namespace='v1')), path('v2/', include('users.urls', namespace='v2')) ] GET /1.0/something/ HTTP/1.1 Host: example.com Accept: application/json zBInvalid version in URL path. Does not match any version namespace.cOsTt|dd}|dus |js|jS|jd}|D] }||r#|Sqt|j)Nresolver_match:)getattr namespacersplitr rr/r))rrrrr6Zpossible_versionsrrrrrvs    z%NamespaceVersioning.determine_versionNc s2|jdur |||}tj|||||fi|Sr)rget_versioned_viewnamer1rrr2rrrs   zNamespaceVersioning.reversecCs|jd|S)Nr7)r)rrrrrrr;sz*NamespaceVersioning.get_versioned_viewnamer!) rr"r#r+r,r)rrr;r4rrr2rr5\s  r5c@s*eZdZdZedZedZddZ dS)HostNameVersioningzX GET /something/ HTTP/1.1 Host: v1.example.com Accept: application/json z,^([a-zA-Z0-9]+)\.[a-zA-Z0-9]+\.[a-zA-Z0-9]+$zInvalid version in hostname.c OsN|d\}}}|j|}|s|jS|d}||s%t|j |S)Nr7) get_host partitionhostname_regexmatchrgroupr rr/r)) rrrrhostname separatorportrArrrrrs    z$HostNameVersioning.determine_versionN) rr"r#r+recompiler@r,r)rrrrrr<s   r<cr-) QueryParameterVersioningza GET /something/?version=0.1 HTTP/1.1 Host: example.com Accept: application/json z#Invalid version in query parameter.cOs,|j|j|j}||st|j|Sr)Z query_paramsr(r%rr rr/r)r0rrrrs  z*QueryParameterVersioning.determine_versionNc s:tj|||||fi|}|jdurt||j|jS|Sr)r1rrrr%)rrrrrr rurlr2rrrs  z QueryParameterVersioning.reverser!r3rrr2rrHs rH)rFZdjango.utils.translationrr,Zrest_frameworkrZrest_framework.compatrZrest_framework.reverserZrest_framework.settingsrZ*rest_framework.templatetags.rest_frameworkrZrest_framework.utils.mediatypesr r r&r.r5r<rHrrrrs       &1