Bugs item #1413379, was opened at 2006-01-23 18:05
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1413379&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Tkinter
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Eric McRae (sferic)
Assigned to: Martin v. Löwis (loewis)
Summary: Popened file object close hangs in latest Cygwin update
Initial Comment:
Today's update of my Cygwin installation caused a long
running Python/Tkinter application to fail to start.
Further investigation shows it hanging on a closed of a
popened file object. The problem seems associated with
importing Tkinter:
===========FILE START=====
#! /usr/bin/python
from Tkinter import *
from os import popen
print "Here"
#grab a calander in case we need it
calpipe = popen("/usr/bin/cal -3")
caltext = calpipe.read(1000)
print "Middle"
calpipe.close()
print "There"
print caltext
==========FILE END=====
prints "Here" and "Middle" and then hangs. Windows
task manager shows sh.exe and a copy of Python2.4.exe
sharing most of the CPU time. If I kill those two
processes, the program finishes its output normally.
If I comment out the from Tkinter line, everthing works
fine.
Cygcheck info attached
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1413379&group_id=5470
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
