Opened 16 years ago

Last modified 11 years ago

#50 enhancement new

conch command-line client doesn't work in win32

Reported by: radix Owned by:
Priority: normal Milestone:
Component: conch Keywords:
Cc: Cory Dodt, radix, z3p, teratorn Branch:


Change History (12)

comment:1 Changed 16 years ago by radix

Traceback (most recent call last):
File "C:\PYTHON22\scripts\", line 31, in ?
from twisted.scripts.conch import run
line 25, in ?
from twisted.internet import reactor, stdio, defer,
line 33, in ?
import abstract, fdesc
line 27, in ?
import fcntl
ImportError: No module named fcntl

(I am opening this as a reminder, since I happen to be
thinking about it at this moment.)

comment:2 Changed 16 years ago by z3p

Win32 doesn't have this module, nor the capabitlity for 
real terminal control.  This is why PuTTY emulates a 
terminal.  If you really want the conch client on Win32, 
tkconch is what you want.  Perhaps this should be an FAQ 
(it's not the first time I've seen this)?

comment:3 Changed 16 years ago by Cory Dodt

Perhaps what's needed is a rewrite of conch with the
terminal IO decoupled from the user interface, so you could
plug in a win32 terminal emulator that does, basically,
whatever cygwin does.  tkconch is not suitable on windows
either; the UI makes a lot of unixy assumptions that
basically make the whole thing unusable; and pubkey
authentication doesn't work even if you grit your teeth and
configure it in a Unix-y way.  If these issues were
resolved, commandline conch could be configured to launch
tkconch when a terminal was required and fcntl was not

Finally, there are a lot of things ssh does that don't even
require a terminal.  It seems a shame to cut win32 users out
of all of those simply because real terminals are not available.

comment:4 Changed 16 years ago by z3p

I'm not sure what you mean by 'plug in a win32 terminal 
emulator' besides 'run conch under a win32 terminal 
emulator' which works as is.

I do agree that things like port forwarding should be able 
to be used from the command line, and I'll try to work on 
making that happen.

comment:5 Changed 16 years ago by Cory Dodt

Basically, I don't see how conch could work under a win32
terminal emulator.  The problem is that it imports code
that's not available on Windows, and it doesn't matter what
environment it's run under.

comment:6 Changed 16 years ago by itamarst

For cvs and other automated uses you don't need console access, just the
command-running capabilities and portforwarding, so that could be supported.
What z3p said. Of course, for that we're going to need some sort of t.i.stdio
for win32. Probably using threads, woot. Or with win32reactor, that might work
too without threads, though I ended up having to use threads for the process

comment:7 Changed 16 years ago by Moshe Zadka

perhaps have another version of conch, which is only command-line, and will
work on both win32 and unix?

comment:8 Changed 16 years ago by Moshe Zadka

Downgrading to feature.

comment:9 Changed 13 years ago by Cory Dodt

Owner: changed from Cory Dodt to z3p

It still doesn't, but this shouldn't be assigned to me. Perhaps z3p.

comment:10 Changed 12 years ago by teratorn

Cc: teratorn added

comment:11 Changed 11 years ago by Glyph

Summary: conch doesn't work in win32conch command-line client doesn't work in win32

Updating the summary to reflect the nature of the issue.

Conch does work on win32; besides the buildbots, c.f.

comment:12 Changed 8 years ago by <automation>

Owner: z3p deleted
Note: See TracTickets for help on using tickets.