Python Function components do not accept dynamic inputs (Langflow Desktop v1.3.2.1)

[sophiamoa]

Bug Description

I'm using Langflow Desktop version 1.3.2.1 and encountered a critical bug: the Python Function component (and other Python execution variants) do not accept dynamic inputs.

Reproduction

Steps to reproduce the behavior:

1. Add a Parse JSON component and a Python Function component.
2. Connect the output of Parse JSON to the input of Python Function.
3. Add a simple function like:
   def my_func(data):
   return data
4. Run the flow. The input is not passed to the function.

Expected behavior

Expected behavior: The input should be passed to the function argument.

Actual behavior: The function runs with no input data, making dynamic processing impossible.

Who can help?

No response

Operating System

macOS 15.3.1 (24D70)

Langflow Version

1.3.2.1

Python Version

3.12

Screenshot

No response

Flow File

No response

[dosubot]

Hello @sophiamoa! I'm here to help you with any bugs, questions, or contributions you might have while we wait for a human maintainer. Let's get started!

The issue you're experiencing with the Python Function component not accepting dynamic inputs in Langflow Desktop version 1.3.2.1 might be related to how the component processes input data connections. The Python Function component is designed to handle inputs by processing each connection or parameter through a method that checks if the input value is a component or a callable method. If the input is not correctly recognized as a component or callable, it might not be passed to the function as expected ^[1].

To troubleshoot this issue, you can verify the following:

1. Ensure that the output from the Parse JSON component is correctly formatted and compatible with the expected input format of the Python Function component. The expected input format is a CodeInput with the name "function_code" ^[2][3].

2. Check if there are any specific error messages or logs that might indicate why the input is not being passed correctly.

3. Consider testing with a simpler setup or different components to isolate the issue further.

If the problem persists, it might be a bug specific to this version, and you may need to look for updates or patches that address this issue.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}