X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: <20070920002241 DOT AHA56826 AT riddler DOT int DOT colorado DOT edu> Subject: RE: Python 2.5.1: Potential Bug in "print" Date: Thu, 20 Sep 2007 15:32:19 +0100 Message-ID: <014701c7fb93$0cbb8a50$2e08a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <20070920002241.AHA56826@riddler.int.colorado.edu> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On 20 September 2007 07:23, Mike MacFerrin wrote: > I'm a grad student in a Compiler Tools course, and (as part of the course) > we're compiling a subset of the Python language down to C, and from there > to x86 Assmebly. Our code has to pass a lengthy series of test-suites for > correctness (comparing the output of our compiled C Code with that of > native Python code), and I stumbled across what seems to be a quirky bug in > Cygwin Python 2.5.1 (the most recent install). > Any suggestions or workarounds? Can you roll back your install? 2.4.3 doesn't reproduce the problem. 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/