Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Dave Korn" To: Subject: RE: Bug Report: python os.popen seems to have recently been broken Date: Mon, 8 Aug 2005 16:59:44 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: Message-ID: ----Original Message---- >From: Nick Burch >Sent: 08 August 2005 15:13 > On Mon, 8 Aug 2005, Dave Korn wrote: >> I reckon you probably got bitten by the recent sh/ash/bash transition >> problems. You could post your cygcheck output as described at >> http://cygwin.com/problems.html if you want us to take a looksee, or you >> could just try re-runiong setup.exe and making sure you're up-to-date >> with the latest shell packages. > > The first thing I tried was running setup.exe. It didn't find any packages > in need of being updated :( > > The fact that you have the same version of python and it does work for you > makes me think it must be related to my setup. I've included a copy of the > output of cygcheck in case there's anything obvious in there Absolutely: >Not Found: sh That'll be it. All system (...) calls are critically dependent on sh existing and being runnable! Re-run setup and select 'Reinstall' for bash, or manually run the postinstall script, or just "cp /bin/bash.exe /bin/sh.exe", then have another go.... cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/