| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
See https://www.python.org/dev/peps/pep-0479/
|
| |
|
|\
| |
| |
| | |
Bump version to 2.0.3
|
| | |
|
|/
|
|
| |
and add news to `docs/news.txt`.
|
|\
| |
| |
| | |
paste.wsgilib.add_close: Add __next__ method
|
| |
| |
| |
| | |
so we avoid logic duplication
|
| | |
|
| | |
|
| | |
|
| |\ |
|
| | |
| | |
| | |
| | | |
to support using `add_close` objects as iterators on Python 3.
|
|\ \ \
| |/ /
|/| |
| | | |
tox.ini: Measure test coverage
|
|/ / |
|
|\ \
| | |
| | |
| | | |
Enable testing with pypy
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
This involved:
- Adding "pypy" to the `tox.ini` envlist.
- Adding `# doctest: +IGNORE_EXCEPTION_DETAIL` to 2 doctests, because the
traceback message text is slightly different on PyPy.
|
|\ \
| | |
| | |
| | | |
tox.ini: Add py35 to envlist
|
|/ / |
|
|\ \
| | |
| | |
| | | |
Change six requirement to >=1.4.0
|
| |/ |
|
|\ \
| |/
|/|
| | |
Py3k fixes
|
| | |
|
| |
| |
| |
| | |
Mixing binary and text types causes errors later on.
|
| |
| |
| |
| | |
Exception details are formatted differently between Python 2 and 3.
|
| |
| |
| |
| |
| | |
Use sorted() instead, which works on lists as well as dict_items
objects.
|
| |
| |
| |
| |
| | |
The dict.has_keys() method doesn't exist anymore in python 3, check if
the locals() object has a .keys() method instead.
|
| |
| |
| |
| |
| |
| |
| | |
cgi.FieldStorage keeps some keys as str, some as the repr() of the
byte-encoded key, duh.
Fixes (well...): tests.test_cgiapp.test_form
|
| |
| |
| |
| | |
Fixes tests.test_cgiapp
|
| |
| |
| |
| |
| |
| |
| |
| | |
In Python 3, cgi.FieldStorage needs to know about encodings like
shiftjis in order to decode it properly (in Python 2 it's simply not
decoded at all).
Fixes tests.test_wsgiwrappers.test_wsgirequest_charset
|
| |
| |
| |
| | |
Fixes tests.test_wsgiwrappers.test_wsgirequest_charset
|
|/
|
|
| |
Fixes tests.test_wsgiwrappers.test_wsgirequest_charset
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, when the listening socket was already in use, this error message was displayed:
...
File "/private/tmp/n/lib/python2.7/site-packages/Paste-1.7.5.1-py2.7.egg/paste/httpserver.py", line 1106, in server_close
self.thread_pool.shutdown(60)
AttributeError: 'WSGIThreadPoolServer' object has no attribute 'thread_pool'
We prevent this by checking if `self` has a `thread_pool` attribute before trying to reference it.
Fixes issue #5 (https://bitbucket.org/ianb/paste/issue/5/invalid-error-message-when-the-socket-is)
|
|\
| |
| |
| | |
replace ``has_key`` method to ``in`` operator #9
|
| | |
|
|\ \
| | |
| | |
| | | |
Add HTTP exception for new code 429 "Too Many Requests"
|
| | |
| | |
| | |
| | | |
http://www.ietf.org/id/draft-nottingham-http-new-status-03.txt
|
|\ \ \
| | | |
| | | |
| | | | |
Escape CGI environment variables in HTTP 404 responses
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
Replace cgi.parse_qsl w/ six.moves.urllib.parse.parse_sql
|
| |\ \ \ \
| | | |_|/
| | |/| |
| | | | |
| | | | |
| | | | | |
msabramo/paste/test_wsgirequest_charset_use_UTF-8_instead_of_iso-8859-1 (pull request #24)
test_wsgirequest_charset: Use UTF-8 instead of iso-8859-1
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
because it seems that the defacto standard for encoding URIs is to use UTF-8.
I've been reading about url encoding and it seems like perhaps using an
encoding other than UTF-8 is very non-standard and not well-supported (this
test is trying to use `iso-8859-1`).
From http://en.wikipedia.org/wiki/Percent-encoding
> For a non-ASCII character, it is typically converted to its byte sequence in
> UTF-8, and then each byte value is represented as above.
> The generic URI syntax mandates that new URI schemes that provide for the
> representation of character data in a URI must, in effect, represent
> characters from the unreserved set without translation, and should convert
> all other characters to bytes according to UTF-8, and then percent-encode
> those values. This requirement was introduced in January 2005 with the
> publication of RFC 3986
From http://tools.ietf.org/html/rfc3986:
> Non-ASCII characters must first be encoded according to UTF-8 [STD63], and
> then each octet of the corresponding UTF-8 sequence must be percent-encoded
> to be represented as URI characters. URI producing applications must not use
> percent-encoding in host unless it is used to represent a UTF-8 character
> sequence.
From http://tools.ietf.org/html/rfc3987:
> Conversions from URIs to IRIs MUST NOT use any character encoding other than
> UTF-8 in steps 3 and 4, even if it might be possible to guess from the
> context that another character encoding than UTF-8 was used in the URI. For
> example, the URI "http://www.example.org/r%E9sum%E9.html" might with some
> guessing be interpreted to contain two e-acute characters encoded as
> iso-8859-1. It must not be converted to an IRI containing these e-acute
> characters. Otherwise, in the future the IRI will be mapped to
> "http://www.example.org/r%C3%A9sum%C3%A9.html", which is a different URI from
> "http://www.example.org/r%E9sum%E9.html".
See issue #7, which I think this at least partially fixes.
|
|/ / /
| | |
| | |
| | |
| | | |
because `cgi.parse_qsl` is deprecated, according to
https://docs.python.org/2/library/cgi.html#cgi.parse_qsl
|
| | |
| | |
| | |
| | | |
by wrapping `map` with `list`.
|
|\ \ \
| | | |
| | | |
| | | | |
Fix improper commas in request headers in wsgi_environ
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
as suggested by @haypo at https://bitbucket.org/ianb/paste/pull-request/22/fix-improper-commas-in-request-headers-in/diff#comment-6583636
|
| | | | |
|