Re: [HTCondor-users] thoughts on HTCondor python bindings submit improvements

[John M Knoeller <johnkn@xxxxxxxxxxx>]

If I understand what you are saying, then yes.   

So this

with schedd.transaction as txn : 
    for d in list_of_dcts :
       sub.update(d)
       sub.queue(txn)

would produce N jobs in N clusters. 

with schedd.transaction as txn : 
       sub.queue(txn, list_of_dicts)

would produce N jobs in 1 cluster

-tj

-----Original Message-----
From: HTCondor-users [mailto:htcondor-users-bounces@xxxxxxxxxxx] On Behalf Of Dimitri Maziuk
Sent: Friday, April 27, 2018 3:42 PM
To: htcondor-users@xxxxxxxxxxx
Subject: Re: [HTCondor-users] thoughts on HTCondor python bindings submit improvements

On 04/27/2018 03:04 PM, Dimitri Maziuk wrote:
> On 04/27/2018 02:29 PM, John M Knoeller wrote:
> 
>> with schedd.transaction as txn : 
>>    for d in list_of_dcts :
>>       sub.update(d)
>>       sub.queue(txn)
> 
> Should that last bit be inside the for loop?

I.e. the point is,
- if you can't support that "pythonic iterator" directly on top of the
bindings,
- and you're not going to change the API so that you can collect the
args and then submit in a separate step,
=> then you can't have the "pythonic iterator".

You can only take the args as an iterable and run the for loop yourself.

-- 
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu