Node.py - Python for Node-RED?

Thanks for your input. But, given that you don't appear to favor Py vs JS for an ESP8266, I'll stick with microPython I've installed umqtt into the Lib and it seems to function adequately for it's application. :slightly_smiling_face:

I would also like to see something like a Node.py for Node-RED, but I've experienced a lot of push-back on that suggestion. :wink:

It would be nice as TotallyInformation suggested, if there were another flow-base visual tool that was structured flexible enough to allow various Back-Ends to be added, as there will always be new programmings tools in the future.

Can you elaborate what you think node-red would actually gain by writing it in python other than some syntactic differences and curly braces ?

Moderator's comment: I'm wary of this topic going in circles and repeating the same talking points and becoming unproductive. There's little benefit having an endless discussion trading blows over what language is 'better'.

Please consider carefully whether you have something substantially new to add to the discussion regarding a Python runtime for Node-RED.

The rationales for the suggestion have been stated through-out the thread. Ultimately it comes down to a personal preference for Python.

There are some domains (machine learning in particular) that have better support in Python than JavaScript - and having a native python runtime might be able to benefit from that.

If you mean you haven't convinced the core development team to put aside JavaScript and rewrite everything in Python, then well, yes - that isn't something we're going to do based on this one suggestion.

That doesn't preclude anyone else from taking on the substantial task of producing a python runtime - keeping in mind you'd need to not just implement the runtime but a large number of nodes for it to be useful.

2 Likes

From my perspective, and taking into account what I said about not simply translating from JS to Py, such a tool would open up flow-based, low-code programming to a very large community that is familiar with Python but not really with JavaScript.

It would also potentially get access to all of the science, engineering and data analytics libraries.

I would personally really love to see the power of Python's data management libraries wrapped into a visual programming tool making it relatively easy to analyse massive, complex CSV files for example.

I've tried all of the JavaScript libraries that claim to offer parity with the Python ones and they absolutely don't. Indeed, many of them don't work at all reliably.

Node-RED is great for IoT, home automation and the like, but it lacks the libraries for data analytics. Not the fault of Node-RED at all. Just that the libraries don't really exist for Node.js.

I m sorry, but I, for one, still do not understand exactly what you mean by a node.py for node-red. Node.js is a javascript runtime engine. Node red is written (mostly) in javascript and runs under node.js. So what exactly would node.py consist of?

@Colin see this post which I think summarises it: Node.py - Python for Node-RED? - #39 by mdkrieg

Once upon a time we did have one really keen person wanting to port Node-RED to Java as they considered it more enterprise acceptable, and I think they did start on it. That was about 7 years ago but I haven’t seen it yet.

1 Like

In my one of my past posts I explicitly stated that I WASN'T suggesting abandoning JS, but PERHAPS Python could be added as and additional Back-End (e.g. Node.py). The "push-back" was no one seemed to like that idea either. When mdkrieg appeared to be suggesting the same thing I was just replying as to what my experiences were. I hope this clarifies the issue :slightly_smiling_face:

Oh I see, so not a replacement for node.js, and not something that allows nodes written in python to be installed into the existing node-red.

EXACTLY, sorry if I didn't make my intent clear.

So at least I feel fully confident I selected this path already so long time ago - when I realized my advanced (already developed) Python AI scripts should be kept "as is" and only communicate the results back to NR when they happens. Has been working so well during the years, no need to think differently now

1 Like

Indeed - if it works - don't fix it.

1 Like

You wont, of course, expect an Enterprise Architect such as myself to agree to that statement I hope! :grinning:

1 Like

Of course not ! It'll always be better after you have spent 24 months and $M on the project ... maybe.

1 Like

How do you expect people to give you $M's with an attitude like that?

hence why I work in Open Source :slight_smile:

3 Likes

How else will I get my kids through Uni :wink:

1 Like