requirements.txt

-e git+https://github.com/datastax/python-driver.git@cassandra-test#egg=cassandra-driver
# For ccm changes, please, create a PR to the master branch of the ccm repository.
# New commits to master are not automatically used by the python dtests. And changes 
# made to ccm and intended/needed to be used by the dtests can be put in use by re-tagging cassandra-test to master's HEAD.
# The re-tagging approach is
# git tag -a -f cassandra-test
# git push origin :refs/tags/cassandra-test
# git push -f origin refs/tags/cassandra-test
#
# In case you want to test a patch with your own CCM branch, further to changing below CCM repo and branch name, you need to add -e flag at the beginning
# Example: -e git+https://github.com/userb/ccm.git@cassandra-17182#egg=ccm
git+https://github.com/riptano/ccm.git@cassandra-test#egg=ccm
click==8.0.4
decorator==5.1.1
docopt==0.6.2
enum34==1.1.10
exceptiongroup==0.0.0a0
flaky==3.8.1
geomet==0.2.1.post1
iniconfig==1.1.1
lxml==5.1.0
mock==5.1.0
netifaces==0.11.0
packaging==21.3
parse==1.20.1
pluggy==1.0.0
psutil==5.9.8
py==1.11.0
pycodestyle==2.10.0
pyparsing==3.1.2
pytest==7.0.1
pytest-repeat==0.9.1
pytest-timeout==2.1.0
PyYAML==6.0.1
six==1.16.0
soupsieve==2.3.2.post1
thrift==0.16.0
tomli==1.2.3