python-zulip-api/requirements.txt

crayons
twine
coverage>=4.4.1
pycodestyle==2.3.1
mock
pytest
-e ./zulip
-e ./zulip_bots
-e ./zulip_botserver
packaging: Automate the package release process. This commit adds a script to automate the PyPA release of the zulip, zulip_bots and zulip_botserver packages. The tools/release-packages script would take care of uploading the packages to PyPA, and push commits to both repos updating the package versions. If you have commit access to the repos, you can --push upstream to master. If not, then you can --push origin to a new branch on your fork and create a PR for those changes. Ideally, a release shouldn't take longer than however long it takes one to type the above command. If you have SSH set up on GitHub, you won't need to type in your GitHub username and password. You can also store your PyPA credentials in a file in your home directory; it isn't very secure, but it saves time nevertheless. 2017-09-18 20:04:03 -04:00			`crayons`
			`twine`
requirements: Add coverage. 2017-08-23 10:38:29 -04:00			`coverage>=4.4.1`
python-zulip-api: Add tools/provision for setting up dev env. 2017-08-07 19:07:58 -04:00			`pycodestyle==2.3.1`
requirements: Remove runtime dependency on mock. The zulip and zulip_botserver packages specify mock as a runtime dependency, which is only needed for testing during development. So, it made more sense to move it to requirements.txt so that it can be installed by ./tools/provision during development. 2018-01-09 15:22:30 -05:00			`mock`
test-bots: Add option to use pytest for running tests. * Add pytest to requirements.txt * Add pass-through option to run pytest in verbose mode * Use various default pytest options * Exclude merels bot for now 2018-06-03 18:01:39 -04:00			`pytest`
python-zulip-api: Add tools/provision for setting up dev env. 2017-08-07 19:07:58 -04:00			`-e ./zulip`
			`-e ./zulip_bots`
			`-e ./zulip_botserver`