On 09/23/2013 08:44 PM, Arun Neelicattu wrote:
----- Original Message -----
> From: "Ralph Bean" <rbean(a)redhat.com>
> To: "python-bugzilla user/developer list"
<python-bugzilla(a)lists.fedorahosted.org>
> Sent: Tuesday, September 24, 2013 9:48:53 AM
> Subject: Re: [python-bugzilla] Python 3 support
>
> The standard way to do this in the python community is with the "tox"
> test runner:
http://testrun.org/tox/latest/ It is widely used.
>
Did not think of that, thanks. I will look into that.
> I do not use it for my projects just because I haven't gotten around
> to absorbing it into my workflow yet. I do depend on
travis-ci.org to
> run my tests against py2.6, py2.7, and py3.3 after I push -- this is
> quite easy to set up.
>
+1 for travis or some automated CI infra.
Are there any thoughts on moving the project to github? Might open up to a
wider audience and make workflow a bit more easier. But that is for another
thread I suppose.
I'm down with moving to github, though truthfully the idea of more
contributions or people starting to use python-bugzilla to interact with
something other than rhbz scares me :) At this point my time and inclination
is pretty limited beyond keeping the lights on.
- Cole