Shelling out or inlining once per file will cost you - that's common sense. If you can compile a list of files to transfer first, via Perl, which then you send *once* to the python script, shelling out or inlining cost will be much less / insignificant.

Alternatively: modify the python script to sit in a loop and wait until it receives via socket the fullpath to a file to be transfered. Once there is something in the queue, python will transfer it. Then via Perl you decide what files to send and just communicate their names to the python "server". You will have the cost of only opening a local socket connection for each file. I assume perl+python scripts sit locally and communicate to the provider's remote server. So, you communicate to python the filename on local disk.

bw, bliako

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.