Custom global macro packages

[mstmob]

It would be nice to include custom packages via --packages which are located in a global directory (i.e. ~/yalafi/macros).
This could be done by accepting packages

• without prefix for builtin packages (already implemented)
• with . prefix for relative project packages (already implemented)
• with / prefix for absolute paths to global packages (missing feature)

[torik42]

If you add a package via --packages .something, YaLafi will just try to import something. Hence, a module something needs to be present at the python path. Either in the directory, from where you call YaLafi, or in any other. Hence, you can just add any folder, e.g. ~/yalafi/macros, to the python path. If you have a separate environment for YaLafi, it will not even change anything else.

If I find time for a configuration overhaul, I might add an option --packages-path which dynamically adds the argument to the python path. I would prefer to not add any folder by default.

[mstmob]

If you add a package via --packages .something, YaLafi will just try to import something. Hence, a module something needs to be present at the python path. Either in the directory, from where you call YaLafi, or in any other. Hence, you can just add any folder, e.g. ~/yalafi/macros, to the python path. If you have a separate environment for YaLafi, it will not even change anything else.

Thank you, good to know how this is handled internally! This is at least a temporary solution for my problem.

If I find time for a configuration overhaul, I might add an option --packages-path which dynamically adds the argument to the python path. I would prefer to not add any folder by default.

I agree with you: There shouldn't be a default folder for custom packages. But a --packages-path would be appreciated ;)