It is not difficult (for me) - I developed the scripts to analyze files created by two different linux boxes (why two boxes is a longer story) (these are linux machines connected to gene sequencers) - the users are likely going to be fairly naive when it comes to running/using programs - and while the files can be transferred to the windows machine and then analyzed/examined, was trying to see if the windows machines can be used as simply a front end (no file transfers/etc) - but yes, it is indeed a solution that can be implemented - get the files over, run the script on windows machines (even as it makes me nervous to run scripts on windows systems - with or without anaconda - I am so used to being in the Linux environment that dealing with windows makes me nervous :(
On Sunday, June 4, 2017 at 5:05:49 PM UTC-5, Thomas Jollans wrote: > On 04/06/17 22:56, I wrote: > > I was looking for the "simplest" possible solution to take a script that > > runs on a Linux box and figure out a way to have it run from a windows > > client > > Care to comment on why getting the script to run on Windows directly is > so difficult? I'm sure you can build something that does the job with > Django/Flask/whatever, but it doesn't sound like it's necessarily the > simplest solution. > > > >> On Mon, Jun 5, 2017 at 2:41 AM, Michael Torrie wrote: > >>> I'm confused why you would need to ssh anywhere. Command-line programs > >>> in Python should work perfectly fine in Windows and work about the same > >>> as on Linux, if you wrote them in a portable way. I don't understand > >>> the need to complicate things with ssh, django, x2go, or any of the > >>> other suggestions here. I also don't understand why you'd need the > >>> Anaconda distro. Why won't standard Python from python.org work? -- https://mail.python.org/mailman/listinfo/python-list
