Fixing the Python subprocess interface

Re:Fixing the Python subprocess interface by ulope on Monday January 30, 2012 @04:59PM (#3530826)

As long as the package you need doesn't include a C extension (which most don't) you can just ship it with your code (license permitting ofc.) - just add the path to the libary to sys.path. It's not a very clean solution but can be a real life saver when you have to work on "broken" systems.

[ Parent | on HN ]

Re:Fixing the Python subprocess interface by scott_s on Monday January 30, 2012 @05:46PM (#3530955)

Sorry, I wasn't clear. This is a system I log into every day, and I don't want to maintain my own install of Python and related packages on it. It's too much overhead. I'd rather just use the default Python, even though it's old.

[ Parent | on HN ]

Re:Fixing the Python subprocess interface by rat87 on Tuesday January 31, 2012 @02:29AM (#3532265)

For simple libs I just dump the py file/folder in the same folder as the script and import.

[ Parent | on HN ]