I'd second this motion. It would make adopting the Python bindings much easier to approach for new users, and serve as a good learning tool when you're able to see the submit() piece input which is generated by a submit file parser.
-Michael Pelletier.
-----Original Message-----
From: HTCondor-users [mailto:htcondor-users-bounces@xxxxxxxxxxx] On Behalf Of Dimitri Maziuk
Sent: Friday, April 27, 2018 10:29 AM
To: htcondor-users@xxxxxxxxxxx
Subject: [External] Re: [HTCondor-users] thoughts on HTCondor python bindings submit improvements
On 2018-04-27 08:56, Brian Bockelman wrote:
I think there's a strong argument to have python able to cleanly submit from an unaltered submit file.
I don't see a strong argument to expose the complexity of the "queue" statement given the user controls the loop anyway.
I think you might be missing the point: make the submit file parser a separate piece. Use the output of that piece as input for submit() piece. Expose both pieces in your API.
Then you can add a submit_string( str ) and submit_file( name ) etc.
2-liner convenience wrappers on top.
It's the design that's known to work.
Dimitri
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/
_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/