delta/python-packages/webob.git/tests/test_descriptors.py, branch bugfix/set_cookie_datetime

test_descriptors.py convert to assert from nose/unittest

2016-04-15T08:20:45+00:00

Add tests with invalid header values

2016-01-03T07:17:05+00:00

Fix optional and bad whitespace parsing in auth-param

2014-09-22T06:41:26+00:00

Fixes PEP8 warnings

2012-12-28T08:42:30+00:00

bytesrequest renamed to legacyrequest... it no longer eagerly converts to bytes, it just presents the older native string api expected by existing systems. textrequest renamed to baserequest, it is the new default request type.. it no longer eagerly converts to text, either unless an encattr is named on the environ_decoder

2012-01-28T12:07:20+00:00

First cut at distinct TextRequest/BytesRequest implementations as a

2012-01-25T23:24:20+00:00

fix for issue #21.

TextRequest is the default when Request or BaseRequest is imported under
Python 3 for backwards compatibility.  The only difference Python 3 users
should see after upgrading to this: script_name and path_info will be
decoded, and methods which erroneously dealt in raw environ values will
now deal correctly in text.

BytesRequest is the default when Request or BaseRequest is imported under
Python 2 for backwards compatibility.  It works just like the old BaseRequest
under Python 2.  Under Python 2, environ values are still dealt with as
bytes by all methods.  Under Python 3, it coerces all environ values to bytes.
It's doubtful anyone will use this under Python 3.

Either BytesRequest or TextRequest are usable directly under Python 2 or
Python 3, but the intent is to transition people over time to TextRequest on
both.  Certainly new frameworks could start off using TextRequest.

* ``Response.request`` and ``Response.environ`` attrs are undeprecated and no

2011-10-06T17:27:30+00:00

  longer raise exceptions when used.  These can also be passed to the
  Response constructor.  This is to support codebases that pass them to the
  constructor or assign them to a response instance.  However, some behavior
  differences from 1.1 exist.  In particular, synchronization is no longer
  done between environ and request attribute properties of Response; you may
  pass either to the constructor (or both) or assign one or the other or
  both, but they wont be managed specially and will remain the same over the
  lifetime of the response just as you passed them.  Default values for both
  ``request`` and ``environ`` on any given response are ``None`` now.

refactor Range to only handle a single range

2011-09-26T07:16:44+00:00

Merge branch 'sergey-1.2-py2-only' into 1.2-merge

2011-09-25T16:23:54+00:00

Conflicts:
	tests/test_descriptors.py
	tests/test_etag.py
	tests/test_misc.py
	tests/test_multidict.py
	tests/test_request.py
	tests/test_request_nose.py
	tox.ini
	webob/cookies.py
	webob/dec.py
	webob/descriptors.py
	webob/etag.py
	webob/exc.py
	webob/multidict.py
	webob/request.py
	webob/response.py

remove text_to_wsgi

2011-09-25T13:23:19+00:00

if the header is set to
* text on py3 we trust it to be in latin-1 charset
* bytes on py3 the resulting response is invalid
* text on py2 we encode to latin-1 like we always did
* bytes on py2 we use it verbatim