This isn't possible at the moment. Variable files, like resource files, are always taken into use by using a path to the variable/resource file. Python (and Java) variable files could also be imported as modules same way as libraries, and I agree that would be a good idea. It would make it possible to include variables in normal Python packages, possibly even bundling them to same packages with libraries.

If the given path to resource/variable file doesn't match any file, Robot will automatically check is such a file found from directories in PYTHONPATH. This is not the same as importing discussed above, because the value still needs to be a path or file name like my_variables.py, not only the module name like my_variables. We are also kind of misusing PYTHONPATH, and should probably introduce our own environment variable like ROBOTPATH and search imported files from there instead.

Although I agree this would be a good idea, I cannot give promises when, if ever, this will be implemented. I'd like to have this in, but I doubt I have time in the near future. If someone else is interested to look at implementing this, I'd be happy to help. Shouldn't be overly complicated.

I am ready to work on this issue.

Cool! The first step would probably be changing Importer('variable file').import_class_or_module_by_path to use import_class_or_module instead. After that needs to see what acceptance tests possibly break (see atest/README.rst for details running then) and new tests need to be added.

How does the implementation look like @OzairKhanBro? Anything I could already review?