Arun Babu Neelicattu author That was part of original commit by Jajcus in https://bitbucket.org/Jajcus/jira-python/commits/e3e7e2871f24e885788986b995c8b3d7638e3de4 I can resend the pull without that change if required. 2013-10-03T10:46:40+00:00
Jajcus My change was to move tools to the jira package, so it doesn't pollute the name space. 2013-10-03T11:07:38+00:00
Arun Babu Neelicattu author Updated pull request without refactoring. Sorin Sbarnea Let me know if any other changes are required. 2013-10-08T03:07:38+00:00
Rotem Yaari +1 for this. We are using Jira-python and it's one of the things holding us back from migrating to Python 3.3. I'd really appreciate 0.14 to be released with support for Python 3. 2013-10-17T07:36:11+00:00
Any reason for moving tool outside jira package?
That was part of original commit by Jajcus in https://bitbucket.org/Jajcus/jira-python/commits/e3e7e2871f24e885788986b995c8b3d7638e3de4
I can resend the pull without that change if required.
My change was to move tools to the jira package, so it doesn't pollute the name space.
Updated pull request without refactoring.
Sorin Sbarnea Let me know if any other changes are required.
+1 for this. We are using Jira-python and it's one of the things holding us back from migrating to Python 3.3. I'd really appreciate 0.14 to be released with support for Python 3.
Any updates on this one?