1- Hackers Guide
2- =============
3-
4- 1 . Setting up the environment
5- -----------------------------
1+ # Setting up the environment
62
73If you already have system installed versions of python-bugzilla
84dependencies, running the command line from git is as simple as doing:
5+
96 cd python-bugzilla.git
107 ./bugzilla-cli [arguments]
118
12- If you'd like to use pip and virtualenv to install a local development
9+ If you want to use pip and virtualenv to install a local development
1310environment, use the following command.
11+
1412 source contrib/activate-dev-env [python2|python3]
1513
16- Note: Providing no arguments will attempt to use python2.
14+ Then you can manually activate an environment with:
1715
18- # Manually activating an environment
1916 source dev-env-${NAME}/bin/activate
2017
2118
22- 2 . Running tests
23- ----------------
19+ # Running tests
20+
2421Once you have already activated an environment, you can use the following.
2522
26- # Basic unit test suite
23+ ## Basic unit test suite
24+
2725 python setup.py test
2826
29- # Read-Only Functional tests
27+ ## Read-Only Functional tests
3028There are more comprehensive tests that are disabled by default. Readonly
3129functional tests that run against several public bugzilla instances. No
3230login account is required:
3331
3432 python setup.py test --ro-functional
3533
36- # Read/Write Functional Tests.
34+ ## Read/Write Functional Tests.
3735
3836Before running rw-functional tests, make sure you have logged into bugzilla
3937using. These currently run against the test bugzilla instance at
@@ -42,25 +40,26 @@ partner-bugzilla.redhat.com, and requires a valid login there:
4240 bugzilla-cli --bugzilla=partner-bugzilla.redhat.com --user=$USER login
4341 python setup.py test --rw-functional
4442
45- # Testing across python versions
43+ ## Testing across python versions
4644To test all supported python versions, run tox using any of the following.
4745
4846 tox
4947 tox -- --ro-functional
5048 tox -- --rw-functional
5149
5250
53- 3 . pylint and pep8
54- ------------------
51+ # pylint and pep8
52+
5553To test for pylint or pep8 violations, you can run:
54+
5655 python setup.py pylint
5756
5857Note: This expects that you already have pylint and pep8 (installed when setting
5958up virtualenv) installed.
6059
6160
62- 4 . Patch Submission
63- -------------------
61+ # Patch Submission
62+
6463If you are submitting a patch, ensure the following:
6564 [ REQ] verify that no new pylint or pep8 violations
6665 [ REQ] run basic unit test suite across all python versions as described
@@ -69,11 +68,5 @@ If you are submitting a patch, ensure the following:
6968Running any of the functional tests is not a requirement for patch submission,
7069but please give them a go if you are interested.
7170
72- Submitting a patch is straight forward; you need to submit it to
73- python-bugzilla@lists.fedorahosted.org using the git-send-email command.
74-
75- For example, assuming you have configured smtp and is working on a feature branch, the following will submit all commits you have on top of master.
76-
77- $ git send-email --from <your email id > --to python-bugzilla@lists.fedorahosted.org master
78-
79- For more information about git-send-email refer to http://git-scm.com/docs/git-send-email
71+ Patches can be submitted via github pull-request, or via the mailing list
72+ at python-bugzilla@lists.fedorahosted.org using 'git send-email'.
0 commit comments