how do I install and test my changes to jira-python?

Question

I'd like to contribute to jira-python. I cloned the repo and made my changes locally, now I need to install and test. However, every method I've used to install the package from a local directory has failed with the following: Complete output from command python setup.py egg_info: Traceback (most recent call last): File "", line 1, in File "/Users/davidmcbride/projects/python_jira/jira/setup.py", line 201, in **get_metadata(base_path, NAME, 'package_meta.py') File "/Users/davidmcbride/projects/python_jira/jira/setup.py", line 39, in get_metadata exec(code, scope) File "/Users/davidmcbride/projects/python_jira/jira/jira/package_meta.py", line 103, in __version__ = get_version() File "/Users/davidmcbride/projects/python_jira/jira/jira/package_meta.py", line 38, in get_version version = base_version.base_version AttributeError: 'tuple' object has no attribute 'base_version' I've tried 'pip install -e', 'easy_install', and 'python setup.py'. I also made sure that 'setuptools' was updated. Obviously, people are contributing to jira-python, so I guess I just need to understand the workflow better. Using OS X 10.11.6

Sorin Sbarnea · Answer

Clone and run `make test`, this will run the tests, no need to try to create the venv yourself as that's done by make. There are several other make commands available that are of great help, just check the Makefile, is easy to read.

Guy Matz · Answer

D'oh!  Forgot one thing!  After step 6 above, make sure you're able to track changes in the upstream code:

git remote add upstream git@github.com:pycontribs/jira.git

Then you can pull changes from upstream,

git pull upstream develop

Guy Matz · Answer

OK, getting a bit better at this, I think . . .

* Fork python-JIRA
* virtualenv jira
* source jira/bin/activate
* pip install pytest-runner
* pip install -e pip install -e git+git@github.com:YOUR_USERNAME/jira#egg=Package
* cd jira/src/package
* pip install -r requirements-dev.txt
* edit tests.local to point to a dev JIRA instance (see above)
* ./test.local tests

* edit code
* goto 9

Would love to hear what @Sorin Sbarnea thinks about this