This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ron_adam
Recipients avdd, bquinlan, georg.brandl, r.david.murray, ron_adam
Date 2011-01-18.18:19:16
SpamBayes Score 0.0015197629
Marked as misclassified No
Message-id <1295374760.32.0.87609637974.issue10918@psf.upfronthosting.co.za>
In-reply-to
Content
Yes, you are correct.  Pulling the first value off of args would work.

This is new for 3.2, can it still be changed?


One more thing to consider...

One of the things I look at for functions like these is, how easy is it to separate the data from the program interface?

I prefer:
    submit_data = [fn, args, kwds]
    e.submit(*submit_data)

or..
    submit_args = [(a, k), (a, k), ... ]
    for args, kwds in submit_args:
        e.submit(fn, args, kwds)

But its a trade off against easier direct calling.  My feelings, is submit will be used more in an indirect way, like these examples, rather than being used directly by writing out each submit separately.
History
Date User Action Args
2011-01-18 18:19:20ron_adamsetrecipients: + ron_adam, georg.brandl, bquinlan, r.david.murray, avdd
2011-01-18 18:19:20ron_adamsetmessageid: <1295374760.32.0.87609637974.issue10918@psf.upfronthosting.co.za>
2011-01-18 18:19:16ron_adamlinkissue10918 messages
2011-01-18 18:19:16ron_adamcreate