Consider refactoring to use the behaving.* namespace

[lampmantech]

Are you still working on this?

If so, you might want to consider restructuring the package to use the behaving namespace https://github.com/ggozad/behaving which I think is the way to go for
behave step libraries to work together. It's important to get the structures right so that the step libraries can work together. It's something that RobotFramework did well, and behave has been lacking so far.

For a trivial example see our https://github.com/lampmantech/behaving.cmd
If you want a hand restructuring longaccess-client, let us know. If this project is dead,we may pull your pexpect into behaving.cmd as a behaving.pexpect

See also the discussion at at your original collaboration issue and:
behave/behave4cmd#2

[kouk]

@lampmantech hey, thanks for reaching out. This project isn't being worked on anymore. The step library is at this repo btw: https://github.com/longaccess/longaccess-behave. I might have use for it in another project, so if you think it's a good idea to move to the behaving namespace then I might look into it in the future.

[lampmantech]

Thanks, I missed longaccess-behave.

Moving to the behaving namespace is almost trivial so it's easy to do,
and lets the behave step libraries interoperate.

I see that longaccess shut down, so I imagine the project won't get worked on any more.
I'll feel free then to pull any of the code into behaving.cmd, with attribution of course.
It's the pexpect code that I may need. If you leave this issue open, I'll come back here if I do, to keep you posted.

Speaking of the pexpect code, do you know the sh package on pypi?
I'm wondering if that might make the subprocess code easier to maintain...

[kouk]

@lampmantech alright. I'll leave this open. No, haven't checked that package out.