2015-12-23 20:05:15 +03:00
|
|
|
import os
|
2016-09-23 00:25:09 +03:00
|
|
|
|
2015-12-23 20:05:15 +03:00
|
|
|
from setuptools import find_packages, setup
|
2016-09-23 00:25:09 +03:00
|
|
|
|
2015-12-23 20:05:15 +03:00
|
|
|
from daphne import __version__
|
|
|
|
|
|
|
|
# We use the README as the long_description
|
|
|
|
readme_path = os.path.join(os.path.dirname(__file__), "README.rst")
|
2016-09-23 00:25:09 +03:00
|
|
|
with open(readme_path) as fp:
|
|
|
|
long_description = fp.read()
|
2015-12-23 20:05:15 +03:00
|
|
|
|
|
|
|
setup(
|
|
|
|
name='daphne',
|
|
|
|
version=__version__,
|
2016-09-23 00:25:09 +03:00
|
|
|
url='https://github.com/django/daphne',
|
2015-12-23 20:05:15 +03:00
|
|
|
author='Django Software Foundation',
|
|
|
|
author_email='foundation@djangoproject.com',
|
2016-02-21 16:17:17 +03:00
|
|
|
description='Django ASGI (HTTP/WebSocket) server',
|
2016-09-23 00:25:09 +03:00
|
|
|
long_description=long_description,
|
2015-12-23 20:05:15 +03:00
|
|
|
license='BSD',
|
|
|
|
zip_safe=False,
|
2016-08-11 18:52:27 +03:00
|
|
|
package_dir={'twisted': 'daphne/twisted'},
|
|
|
|
packages=find_packages() + ['twisted.plugins'],
|
2015-12-23 20:05:15 +03:00
|
|
|
include_package_data=True,
|
2016-02-06 04:23:49 +03:00
|
|
|
install_requires=[
|
2017-04-01 17:18:43 +03:00
|
|
|
'asgiref~=1.1',
|
2017-03-18 22:32:04 +03:00
|
|
|
'twisted>=17.1',
|
2017-04-01 17:18:43 +03:00
|
|
|
'autobahn>=0.18',
|
2016-02-06 04:23:49 +03:00
|
|
|
],
|
Full test suite for HTTP requests (#91)
* Add Hypothesis for property-based tests
Hypothesis:
"It works by letting you write tests that assert that
something should be true for every case, not just the ones you happen to
think of."
I think it's well suited for the task of ensuring Daphne conforms to the
ASGI specification.
* Fix accidental cast to byte string under Python 2
While grepping for calls to str(), I found this bit which looks like a
cast to unicode was intended under Python 2.
* ASGITestCase - checking channel messages for spec conformance
This commit introduces a new test case class, with it's main method
assert_valid_http_request_message. The idea is
that this method is a translation of the ASGI spec to code, and can be
used to check channel messages for conformance with that part of the
spec.
I plan to add further methods for other parts of the spec.
* Add Hypothesis strategies for generating HTTP requests
Hypothesis, our framework for test data generation, contains only
general so-called strategies for generating data. This commit adds a few
which will be useful for generating the data for our tests.
Alos see http://hypothesis.readthedocs.io/en/latest/data.html.
* Add and convert tests for HTTP requests
This commit introduces a few Hypothesis tests to test the HTTP request
part of the specification. To keep things organized, I split the
existing tests module into two: one concerned with requests, and one
concerned with responses. I anticipate that we'll also add modules for
chunks and server push later.
daphne already had tests for the HTTP protocol. Some of them I converted
to Hypothesis tests to increase what was tested. Some were also
concerned with HTTP responses, so they were moved to the new response
module. And three tests were concerned with proxy behaviour, which I
wasn't sure about, and I just kept them as-is, but also moved them
to the request tests.
* Fix byte string issue in Python 2
Twisted seems to return a byte string for the client and server IP
address. It is easily rectified by casting to the required unicode
string. Also added a test to ensure this is also handled correctly in
the X-Forwarded-For header parsing.
* Check order of header values
I'm in the process of updating the ASGI spec to require that the order
of header values is kept. To match that work, I'm adding matching
assertions to the tests.
The code unfortunately is not as elegant as I'd like, but then it's only
a result of the underlying HTTP spec.
* Suppress warning about slow test
The kitchen sink test expectedly can be slow. So far it wasn't slow
enough for hypothesis to trigger a warning, but today Travis must've had
a bad day. I think for this test is is acceptable to exceed hypothesis'
warning threshold.
2017-03-15 00:12:07 +03:00
|
|
|
extras_require={
|
|
|
|
'tests': ['hypothesis', 'tox']
|
|
|
|
},
|
2015-12-23 20:05:15 +03:00
|
|
|
entry_points={'console_scripts': [
|
|
|
|
'daphne = daphne.cli:CommandLineInterface.entrypoint',
|
|
|
|
]},
|
2016-09-23 00:25:09 +03:00
|
|
|
classifiers=[
|
|
|
|
'Development Status :: 4 - Beta',
|
|
|
|
'Environment :: Web Environment',
|
|
|
|
'Intended Audience :: Developers',
|
|
|
|
'License :: OSI Approved :: BSD License',
|
|
|
|
'Operating System :: OS Independent',
|
|
|
|
'Programming Language :: Python',
|
|
|
|
'Programming Language :: Python :: 2',
|
|
|
|
'Programming Language :: Python :: 2.7',
|
|
|
|
'Programming Language :: Python :: 3',
|
2017-01-31 04:24:17 +03:00
|
|
|
'Programming Language :: Python :: 3.4',
|
2016-09-23 00:25:09 +03:00
|
|
|
'Programming Language :: Python :: 3.5',
|
2017-04-03 16:49:08 +03:00
|
|
|
'Programming Language :: Python :: 3.6',
|
2016-09-23 00:25:09 +03:00
|
|
|
'Topic :: Internet :: WWW/HTTP',
|
|
|
|
],
|
2015-12-23 20:05:15 +03:00
|
|
|
)
|