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
Some packages want to define env-vars with paths, and they often use self.package_folder for it, so this is broken for editable packages, for example, in which package_folder=None. It also doesn't work for other abstractions over paths as unix_paths, which depend on the consumer, not the package creator.
Let's investigate some mechanism that allow to define abstract env-vars for PATHs that are resolved better in the consumer side.
The text was updated successfully, but these errors were encountered:
Comes from #12192 (comment)_
Some packages want to define env-vars with paths, and they often use
self.package_folder
for it, so this is broken foreditable
packages, for example, in whichpackage_folder=None
. It also doesn't work for other abstractions over paths asunix_paths
, which depend on the consumer, not the package creator.Let's investigate some mechanism that allow to define abstract env-vars for PATHs that are resolved better in the consumer side.
The text was updated successfully, but these errors were encountered: