Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[HTCondor-users] custom universes?
- Date: Thu, 8 Jan 2015 00:51:13 +0000
- From: Klint Gore <kgore4@xxxxxxxxxx>
- Subject: [HTCondor-users] custom universes?
Just a thought - would there be a way to setup a python universe like the java universe? Is there some threshold where an interpreter becomes a candidate for its own universe?
Sooner or later, I'm going to have to deal with python across a mix of ubuntu and centos which have different default python versions. If I could create a universes like python26, python27 and python3 that might make life easier. I'm envisaging something like /etc/condor/universe.d/python27.conf that contains where the interpreter is, the environment setup for it particular to the node, and how to construct the line to execute the program.
Klint.
-----Original Message-----
From: HTCondor-users [mailto:htcondor-users-bounces@xxxxxxxxxxx] On Behalf Of Roger Herikstad
Sent: Wednesday, 7 January 2015 12:49 PM
To: HTCondor-Users Mail List
Subject: Re: [HTCondor-users] Submit python on to windows host
This is good enough for now. The reason I wanted to use the script as the executable initially is that I was hoping that the OS on the Windows machine would figure out how to run python script using its default python interpreter. In other words, I wanted a way to emulate the effect of adding the following 'shebang' on a unix machine #!/usr/bin/env python I realise that that's probably not a good idea anyway, since then I'd have no control over which packages are available on that particular machine. By specifying the path to a particular interpreter, I avoid that uncertainty.
Anyway, thanks again for the help.
~ Roger
On 6 Jan 2015, at 23:19, Ben Cotton wrote:
> Roger,
>
> Offhand, I'm inclined to think the issue is that user condor-slot1 has
> a different environment than the user (you?) who runs testscript.py
> interactively. Specifically, I'm guessing that the Python interpreter
> is not in its path. If you set your executable to be
> C:\Python27\python.exe (or whatever is appropriate for your system)
> and use testscript.py as an argument, does that work?