Transitioning from Linux to Windows

[chitturk at uah.edu]

Precisely - (as Chris wrote) - the problem is NOT python itself (and yes, it can indeed run on windows machines - though I have run into some minor issues) - it is about the "user"/"users" who are pretty clueless if there is no "GUI" - several have suggested django (am going through the tutorial), cherrypy looks "simple" - perhaps even x2go ... 

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 (yes, putty/ssh can work - and files can be scp'ed back and so on) (someone also referenced "fabric" (which uses paramiko) ... 

And yes, I was indeed trying to avoid spending time on the "UI" beyond simple text messages - asking for user input/etc and printing messages (errors) and if the computation was successful etc etc - django does seem powerful, and perhaps I may (just may) try that or cherrypy or whatever works best (!)

On Sunday, June 4, 2017 at 12:48:40 PM UTC-5, Chris Angelico wrote:
> 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?
> 
> If I'm understanding the OP correctly, the intention is to leave the
> script where it is on the Linux box, but trigger it (and maybe provide
> some parameters) from a Windows box. That by definition means some
> sort of network connection, hence SSH or HTTP or some other protocol.
> 
> ChrisA