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

Input inference in Python boxes is too aggressive #406

Open
darabos opened this issue Jun 12, 2023 · 0 comments
Open

Input inference in Python boxes is too aggressive #406

darabos opened this issue Jun 12, 2023 · 0 comments
Labels
good first issue Good for newcomers

Comments

@darabos
Copy link
Contributor

darabos commented Jun 12, 2023

Specifically, if you have an output, it can be picked up as a non-existent input. E.g.

  • Inputs: <infer from code>
  • Outputs: vs.x: float
  • Code: vs['x'] = vs['name'].str.len()

This will tell you that vs.x is not a valid input.

I'm not sure what's the best solution. Maybe just drop missing inputs in "infer" mode. They may be an output, something in a comment, etc. We will get an error anyway when we try to use them.

(If someone hits this, the workaround is to use "infer" for both inputs and output, or for neither of them.)

@darabos darabos added the good first issue Good for newcomers label Jun 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant