Print

Print

@simonmichal Sorry for the delay in my response

Ideally, it would be nice to be determined automatically, but as you point out, this would be ambiguous. pyenv users have a ton of different ways to specify a python version, so I think trying to guess the right version would cause issues. That being said, I think there are two possibilities for automatic detection:

  1. use python-config --prefix
  2. use pyenv prefix

For both cases, it will automatically pick out the right python version since pyenv will route the call to the proper version. If you only want to look at these for the pyenv case, you could look for the PYENV_ROOT variable, or look for pyenv in the path. I'm happy to provide more info about pyenv if needed

If for some reason those two options aren't possible, then I suppose I would prefer manually specifying XRD_PY_PREFIX_PATH since trying to guess without grabbing the current prefix seems error prone (as you noted above)

Thanks!

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1474#issuecomment-907359273", "url": "https://github.com/xrootd/xrootd/issues/1474#issuecomment-907359273", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1