Print

Print

So, the current situation is that there is a global Env and then there are signatures with defaults that override the global environment (like the pythons CopyProcess::add_job )
It would help greatly for consistency (and allow flexibility) if any Env related variables are NOT used in function signatures, but have each XrdCl::CopyJob inherit a (modifiable) copy of global Env (with the corresponding setters/getters and their python representations). For python this would require the existence of a CopyJob object that can be instantiated, modified and then passed to CopyProcess::add_job as an argument (like CopyProcess::add_job(copy_job_instance))

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <xrootd/xrootd/issues/1839@github.com>

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1839", "url": "https://github.com/xrootd/xrootd/issues/1839", "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