installation / module grp

1,470 views
Skip to first unread message

bob.ha...@gmail.com

unread,
Dec 11, 2016, 7:24:57 PM12/11/16
to OHC-OPAL
I am trying to get Opal running on Windows 10 (64-bit).

Installed using pip (Python 2.7.10, pip 9.0.1) and there don't seem to be any problems.

`opal` was not available from cmd (I can't figure out why, I seem to have the right directories in my Path variable). If I change the `opal` file in my Scripts folder to `opal.py` and run that, it searches for the `grp` module (dependency of `fss`) and fails to find it ('ImportError: no module named grp')

I looked up grp and it seems to be a base module available to Unix users. Why would it be needed? Anything major that I'm missing here?

Many thanks
Bob

David Miller

unread,
Dec 12, 2016, 11:58:33 AM12/12/16
to bob.ha...@gmail.com, OHC-OPAL
Hi Bob,

Thanks for looking at Opal :) 

The short version is: 

Opal doesn't currently support Windows, but we'd be delighted to merge PRs/patches that make it do so and/or work with a Windows maintainer going forwards.

If you wanted to immediately try out Opal your best bet is to do so on a Unix environment - otherwise you'll probably need to work through some issues - sorry :(

The longer version is:

Currently, we actively support unix platforms, but don't have bandwidth to support Windows.

That said, I suspect we'd be very receptive to patches that don't change functionality but just added Windows support, or Open Health Care would happily add Windows support if there was someone willing to sponsor/make it sustainable.

(At some stage Opal did work on Windows - I can remember running some alpha testing of an application from a doctor's work laptop a few years back.)

Looking through the error you're getting:

There's a dependency importing the `grp` module, which doesn't work on Windows.

That module is used for code generation and scaffolding steps here (amongst other places) https://github.com/openhealthcare/opal/blob/v0.8.0/opal/core/scaffold.py and the package `ffs` is used quite heavily for our scaffolding.

I imagine there's a number of other Windows issues in `ffs` - at a glance, I can see that same file imports `pwd` which is another Unix only module.

It's been an awfully long time since I wrote any Python for Windows in anger, so I don't have a good feel for the simplest option, but it seems to me that there would be two strategies:

* Work through issues in the dependencies at source (e.g. in `ffs` put those imports inside the function definitions that use them and raise a better error than ImportError on Windows, submit a PR, update the Opal dependency version, etc)
* Work through any dependencies that have issues on Windows and replace the functionality they provide

Hope that helps and happy to answer any other questions / help work through things if you decide to push through with getting things running on Windows.

Sorry again that you've had issues !

Best

David Miller
Open Health Care

--
You received this message because you are subscribed to the Google Groups "OHC-OPAL" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohc-opal+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Best regards

David Miller
Open Health Care

David Miller

unread,
Apr 8, 2018, 3:43:10 AM4/8/18
to OHC-OPAL
Quick bump to this thread: 

The recent 0.10.0 Opal release (More details: http://openhealthcare.org.uk/blog/2018/04/07/opal-10/) should now support Windows so if you've struggled to install it there please do test it out !
To unsubscribe from this group and stop receiving emails from it, send an email to ohc-opal+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages