a Sic@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|jjddS)Nz.{cls}.determine_version() must be implemented.)cls)NotImplementedErrorformat __class____name__)selfrequestargskwargsmsgrU/var/www/html/django/DPS/env/lib/python3.9/site-packages/rest_framework/versioning.pydetermine_versionsz BaseVersioning.determine_versionNcKst|||||fi|SNrrviewnamerrrr extrarrrreverseszBaseVersioning.reversecCs&|js dS|dur||jkp$||jvS)NT)allowed_versionsdefault_version)rversionrrris_allowed_versions z!BaseVersioning.is_allowed_version)NNNN) r __module__ __qualname__rDEFAULT_VERSIONrALLOWED_VERSIONSr 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|}||s:t |j |Sr) r accepted_media_typeparamsgetr&rrr r NotAcceptableinvalid_version_message)rrrr media_typerrrrr*s    z(AcceptHeaderVersioning.determine_versionN)rr!r"__doc___r,rrrrrr'"sr'cs2eZdZdZedZddZdfdd 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}||s4t|j|Sr)r*r&rr rNotFoundr,rrrrrrrrrIs   z#URLPathVersioning.determine_versionNc sB|jdur&|durin|}|j||j<tj|||||fi|Sr)rr&superrrrrrrRs   zURLPathVersioning.reverse)NNNN rr!r"r.r/r,rr __classcell__rrr4rr06s r0cs: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.cOsXt|dd}|dus|js |jS|jd}|D]}||r0|Sq0t|jdS)Nresolver_match:)getattr namespacersplitr rr1r,)rrrrr8Zpossible_versionsrrrrrvs    z%NamespaceVersioning.determine_versionNc s2|jdur|||}tj|||||fi|Sr)rget_versioned_viewnamer3rrr4rrrs   zNamespaceVersioning.reversecCs|jd|S)Nr9)r)rrrrrrr=sz*NamespaceVersioning.get_versioned_viewname)NNNN) rr!r"r.r/r,rrr=r6rrr4rr7\s  r7c@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}||sJt|j |S)Nr9) get_host partitionhostname_regexmatchrgroupr rr1r,) rrrrhostname separatorportrCrrrrrs    z$HostNameVersioning.determine_versionN) rr!r"r.recompilerBr/r,rrrrrr>s r>cs2eZdZdZedZddZdfdd ZZS) 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}||s(t|j|Sr) query_paramsr*r&rr rr1r,r2rrrrs  z*QueryParameterVersioning.determine_versionNc s:tj|||||fi|}|jdur6t||j|jS|Sr)r3rrrr&)rrrrrr rurlr4rrrs  z QueryParameterVersioning.reverse)NNNNr5rrr4rrJsrJ)rHdjango.utils.translationrr/rest_frameworkrrest_framework.compatrrest_framework.reverserrest_framework.settingsrZ*rest_framework.templatetags.rest_frameworkrrest_framework.utils.mediatypesr r r'r0r7r>rJrrrrs       &1