The maintainers of pyOpenSSL have deprecated the tsafe module because it is neither used nor complete. It was removed from in paste in 78dd2ec01384 but because of a lack of test coverage it caused a regression as described in #19. Reviewing the code and pyOpenSSL, it appears that the right fix is to simply not subclass the SSL.Connection, and let get and set timeout be called on the socket object that Connection keeps, without a lock. A concern here is that if someone is doing something multi- threaded with paste/httpserver the removal of the use of tsafe may present some issues. On the other hand, if someone is doing something multi-threaded, one hopes they are using a more robust web and modern web server. Fixes #19
It would fail if the length of bytes and unicode differs. It now passes non-bytes to `Form` directly.
* py3 fixes for form handling in paste.fixture It uses "not six.PY2" in contrast to other places in the code to be forward-compatible. I've not looked too closely, but it might make sense to decode body/text in the beginning already, instead of having it as bytes internally?! Also, like mentioned in [1] already, it should probably use the correct source encoding?! 1: https://github.com/cdent/paste/blob/36e5b8bd16a6063ec654faf04541f3a20d19f7fe/paste/fixture.py#L820 * Add test, using/fixing SlowConsumer form app
* pytest: fix collection warnings via __test__=False Fixes > "cannot collect test class %r because it has a __init__ constructor Ref: https://github.com/pytest-dev/pytest/issues/2007 * pytest: configure testpaths This is faster with test collection. * pytest: fix warning with doctests Fixes > /usr/lib/python3.7/site-packages/_pytest/python.py:764: > RemovedInPytest4Warning: usage of Generator.Function is deprecated, > please use pytest.Function instead * Minor fixes around s/py.test/pytest/
Future is calling installation endless recursion. We are only using it for an html.escape method, so we make our own and get rid of future. Related-Bug: #6
In Python3, the iterator protocol uses a method named __next__(), not next(). (For compatibility with Python 2.6, we still need to support both though.) Ensure all iterator objects support the Python3 protocol. Signed-off-by: Zane Bitter <zbitter@redhat.com>
This will cause a runtime error in Python 3.7, due to PEP479. Signed-off-by: Zane Bitter <zbitter@redhat.com>
pytest exposes many warnings, some but not all of which are cleaned up here. The main switch is to use html.escape instead of cgi.escape. This inspired the addition of 'future' to requirements. The remaining warnings are related to pytest deprecations or over-eager test discovery. It is perhaps ironic that the switch to pytest is to avoid nose being mostly dead, and now we are using features in pytest that pytest wants to make dead. These are left for later cleanups, which means that running the tests is noisy.