U ˀX @s*ddlZddlmZGdddejZdS)N)urljoincs:eZdZdZdZd fdd ZfddZddZZS) BaseUrlSessionaA Session with a URL that all requests will use as a base. Let's start by looking at an example: .. code-block:: python >>> from requests_toolbelt import sessions >>> s = sessions.BaseUrlSession( ... base_url='https://example.com/resource/') >>> r = s.get('sub-resource/' params={'foo': 'bar'}) >>> print(r.request.url) https://example.com/resource/sub-resource/?foo=bar Our call to the ``get`` method will make a request to the URL passed in when we created the Session and the partial resource name we provide. We implement this by overriding the ``request`` method so most uses of a Session are covered. (This, however, precludes the use of PreparedRequest objects). .. note:: The base URL that you provide and the path you provide are **very** important. Let's look at another *similar* example .. code-block:: python >>> from requests_toolbelt import sessions >>> s = sessions.BaseUrlSession( ... base_url='https://example.com/resource/') >>> r = s.get('/sub-resource/' params={'foo': 'bar'}) >>> print(r.request.url) https://example.com/sub-resource/?foo=bar The key difference here is that we called ``get`` with ``/sub-resource/``, i.e., there was a leading ``/``. This changes how we create the URL because we rely on :mod:`urllib.parse.urljoin`. To override how we generate the URL, sub-class this method and override the ``create_url`` method. Based on implementation from https://github.com/kennethreitz/requests/issues/2554#issuecomment-109341010 Ncs|r ||_tt|dS)N)base_urlsuperr__init__)selfr __class__s