I’m trying to build my own RF package, so I’m diving into the SSHLibrary source code to learn from it.
I’ve noticed that SSHLibrary uses a terminal-based approach for data transfer, as opposed to using Paramiko’s built-in methods. Can you elaborate on the technical considerations that led to this design decision?
Hi,
I am uncertain, if anyone can answer that. Pekka himself, maybe. Could be historical reasons, maybe they did not know any better or something wasn’t possible back then. Maybe some Python2 constraint.
SSHLibrary is very old, infact it has been around since the beginning of RFW. Different people have worked on it, had to move on, others took over.
If you want to suggest paramiko builtin methods, please elaborate, maybe open a PR let’s see how the tests behave.
Can you provide links to the code snippets you are referring to?
Kind regards,
Markus
2 Likes
Got it. I haven’t started coding the package yet; I’m still figuring things out.
Before, I made a Python model with Paramiko for my Robot Framework, but I used the connection way to talk to it.
I know Robot Framework has SSHLibrary, so I’ve been checking out how it works.
Here’s a simple function , Use paramiko connection of the Python model.
I’m attempting to create a simple RF package , but I’m uncertain about the best approach for testing it.
Upon a careful examination of the source code, I’ve discovered that my previous understanding was incorrect. It appears that Paramiko is consistently employed throughout the codebase. Please accept my apologies for the mistake.
2 Likes