Re: [MTT users] Python client

[Jeff Squyres (jsquyres)]

+1 on both Ralph and Josh's comments.

> On Dec 13, 2015, at 11:56 AM, Josh Hursey  wrote:
> 
> I think this is fine. If we do start to organize ourselves for a formal 
> release then we might want to move to pull requests to keep the branch stable 
> for a bit, but for now this is ok with me.
> 
> The Python client looks like it will be a nice addition. Hopefully, I will 
> have the REST submission interface finished in the next couple months and 
> that will make it easier to submit to the DB. I probably won't get cycles to 
> finish that work until after Jan 12. I plan to have it done before the end of 
> Jan - let me know if you need it before then.
> 
> 
> On Thu, Dec 10, 2015 at 1:10 PM, Ralph Castain  wrote:
> Hey folks
> 
> I'm working on the Python client and it is coming along pretty well. The code 
> is completely separate from the Perl-based client and doesn't interact with 
> it, so I would like to push it into the repo on an on-going basis so others 
> can look at it and comment as I go rather than hold it until it is "complete".
> 
> Any objections? Obviously, it won't be fully functional at times - mostly 
> available for architectural review and directional suggestions.
> 
> Ralph
> 
> 
> ___
> mtt-users mailing list
> mtt-us...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
> Link to this post: 
> http://www.open-mpi.org/community/lists/mtt-users/2015/12/0834.php
> 
> 
> 
> -- 
> Joshua Hursey
> Assistant Professor of Computer Science
> University of Wisconsin-La Crosse
> http://cs.uwlax.edu/~jjhursey
> ___
> mtt-users mailing list
> mtt-us...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
> Link to this post: 
> http://www.open-mpi.org/community/lists/mtt-users/2015/12/0837.php


-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/

Re: [MTT users] Python client

[Josh Hursey]

I think this is fine. If we do start to organize ourselves for a formal
release then we might want to move to pull requests to keep the branch
stable for a bit, but for now this is ok with me.

The Python client looks like it will be a nice addition. Hopefully, I will
have the REST submission interface finished in the next couple months and
that will make it easier to submit to the DB. I probably won't get cycles
to finish that work until after Jan 12. I plan to have it done before the
end of Jan - let me know if you need it before then.


On Thu, Dec 10, 2015 at 1:10 PM, Ralph Castain  wrote:

> Hey folks
>
> I'm working on the Python client and it is coming along pretty well. The
> code is completely separate from the Perl-based client and doesn't interact
> with it, so I would like to push it into the repo on an on-going basis so
> others can look at it and comment as I go rather than hold it until it is
> "complete".
>
> Any objections? Obviously, it won't be fully functional at times - mostly
> available for architectural review and directional suggestions.
>
> Ralph
>
>
> ___
> mtt-users mailing list
> mtt-us...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
> Link to this post:
> http://www.open-mpi.org/community/lists/mtt-users/2015/12/0834.php
>



-- 
Joshua Hursey
Assistant Professor of Computer Science
University of Wisconsin-La Crosse
http://cs.uwlax.edu/~jjhursey