You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But this approach is certainly not the intended way of using environment collector plugins.
And it is fragile, since it relies on the collector plugin and the context substitution being executed within the same process.
The obvious solution seems to be, to let the context substitution peek into the env-vars dictionary of the current environment.
But these information are not handed over to the context substitution at the moment (source).
Do you have an idea, how this could be solved? Or maybe the os.environ hack above is sufficient?
The text was updated successfully, but these errors were encountered:
I am using an environment collector plugin in order to populate an environment variable (here:
GDAL_VERSION_SPECIFICATION
):This environment variable is referenced in
pyproject.toml
:But currently only real environment variables are used for context substitution:
(source)
Thus, I am currently setting a real environment in my environment collector plugin as a workaround:
But this approach is certainly not the intended way of using environment collector plugins.
And it is fragile, since it relies on the collector plugin and the context substitution being executed within the same process.
The obvious solution seems to be, to let the context substitution peek into the
env-vars
dictionary of the current environment.But these information are not handed over to the context substitution at the moment (source).
Do you have an idea, how this could be solved? Or maybe the
os.environ
hack above is sufficient?The text was updated successfully, but these errors were encountered: