Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use python files as source for the UDF #25

Open
tkilias opened this issue Mar 15, 2022 · 0 comments
Open

Use python files as source for the UDF #25

tkilias opened this issue Mar 15, 2022 · 0 comments
Labels
feature Product feature

Comments

@tkilias
Copy link
Collaborator

tkilias commented Mar 15, 2022

Background

  • currently, we use wrapper functions with imports, classes and functions as source for the source code for the UDF
  • another useful source might be python files, because then you can write your UDF as a normal python file
    • the only limitation is, you can't import it, if you use the global exa object. In this case, you need to use the mock which injects it.

Hints:

  • Check if we can somehow reference the python file, maybe via importlib_resources and if we get a resource we load the source code from there
  • Alternatively, check the type of the input and if it is str, use this string as source code
  • Third, option might be pathlib Paths

Acceptance Criteria

  • Users can use a python file as input of the udf mock
@tkilias tkilias added the feature Product feature label Mar 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Product feature
Projects
None yet
Development

No branches or pull requests

1 participant