From david@rebirthing.co.nz Tue Apr 1 03:47:11 2003 From: david@rebirthing.co.nz (David McNab) Date: 01 Apr 2003 15:47:11 +1200 Subject: [Idle-dev] Patch for debugger hotkeys Message-ID: <1049168831.2207.17.camel@rebirth> --=-0R8c7w4hfm/u4t/ZN6HM Content-Type: text/plain Content-Transfer-Encoding: 7bit Attached is a modified Debugger.py file (from IDLEfork v0.9a2) which implements hotkeys with the debugger panel. Changes: - Debugger window regains focus after step/next/over/out/go commands - Key bindings for debugger window - windows-style: - F9 - Go - F10 - Next - F11 - Step - Shift-F11 - Out - source display enabled by default In case the file attachment doesn't get through, I've put up the file on: http://www.freenet.org.nz/misc/Debugger.py.gz I leave it to people who are much more up-to-speed with IDLE to incorporate these bindings into the key bindings menu. Ahhh, now my poor sore mouse-fingers can take a break!! :)) Cheers David --=-0R8c7w4hfm/u4t/ZN6HM Content-Disposition: attachment; filename=Debugger.py.gz Content-Type: application/x-gzip; name=Debugger.py.gz Content-Transfer-Encoding: base64 H4sICHUBiT4AA0RlYnVnZ2VyLnB5AMVbe4/bNhL/fz8FqyC3cuoIdq443O3FKdrNNg3Qa3rZbRNg byHoQdvCyqJKyXb87W+GD4mkKNtJezgjWdvi8EdyOG/SxaZmvCWsuSjkpzRP9cf2UNPmYsnZhtw9 FlVLOVEtz+TTD0WVs/1PRdPqBvxM8ztWl3RHS0l1m3FWljQ36cxnF3q8m7xoGZegFxdZmTQNeZun IUwp+j5PJ1cXFwReOV2SOC6qoo3jsKHlckpW2wJaiXrhswgekQU2dI8VTGT1nfSY24byuCwqqkCX PNlQPSi+MhYvi5JW8BigRXO0jDOW08hounjyxOgwQiwIO2DoUXNg8KtXzaGB+TVtTjmP4ykJni23 VdYWrLoiwdQPcxYKTM6L0M36HBRkDqm2m5TyETDetEhUsbPwcGAB9FlL8TGkZFlSNtGKtqHCmv7M Kgq72+8GafnhyvwuRiIfP34k8xfkNc3Ii9nsBbl+c0fu3pHX767IDyCKZJ8cSMsIQJOEcLqknFYZ xUftmvrhsi0HorY8EL6tqqJaET3piLxdYr/uAVknDUmqIQ6+krblRbptKYHVgbaQ4DVNt6sV5bct re/WnG1Xa+BCzUHbqlYA54rCjygUElS0rnFWrUQAJSthCNxEcodzA9VkeyTIGW2qy5bsGX/0AxYV /GvaBFmyoe2a5U1Efkx4LvBy0jCQf+yewFAVNLowyAhDQeRG3qtNfHCpiyVuBPIlxI7TMY7MJoOd xpcQKhJ8xE16ffP9r2/e3Lwnt3c3v/zy9uc35O7H9+9+ffNj4OspbEpD2xiZF058JJy2W27tJP2U 0bodzKQGw2Yov8EeYD0Xu1hzlpZ0Q5KU7Xq1ALxym6M9CS95nUX14XJKLmEXaZLDdqnvLxuQmmr1 6nLSdURY6IDKjjumcHqLqVhr2ANQ523VhqrTxCb1MWSEG/rrhjZNssKpi45xLDb8hXocSls7sOCR 8DqJ0JRQ0WrD7BhuyWukM6z3FFa7ZMbs//RpqBFMz2RD2r5EI6NyOG6h36zex4xaaWlkTb2xrW6a NBqDNVGdtOtIPwo12MTDleBpc/W0CchTEmr6qRqsJxeS0jsg8hX0+zawRcSGJE+bcCJQO+6ZCD20 lBrd+0JHAVrJlTPegcHJHgF717Atz3CUnTQc+GlVslR+RBcwGjPUh2ZNyxI2ME8XwllcmSuEp6Ro BISjJ9CwEHGJjB8sYVGgQKA+2c2yL/y1H4tN1PO1WjbJI41BAkNnnE4gwUgvyKxfJDgctb5nCV81 xpqE9zMX4gGaWwRqM/TMI8SWqIasVuCZTgMbM8xK1mi1EG7Lw3wXwYPfsjpKgcGO6XHMjsYSArMr 6B5laIBltEZyepN/Dlrc/XlCrkuaVGRb673G0dAWwRKL7BGcn/bFIOxVCwGvXDvZFzk4schACq8T 6AiBAIQDfFOC9IONbnlCskMGJlv7adE91qjhRA9oILVstSrNoYXH1xMUegTaVW39chu5IxjIP7O9 mr8ZZnRL24uwPYKXjYz7lFNwSewQGmayE2yhRP2e9ApkzstRlxIziU7F5HebhDOGFOpNE+LXweyg Xfy1U5cQaSfDpew3cVu0JQ1l4EGu5fIDP2kB3BE2V1IbVIoA/HzLMlaGwYd/xa9vfrq5u4k/vP35 9bsPEMQIJMFyD3oK/A6DlzdNltT01Qj1E7tfqg1N9+EHfA8Bb+KjBMeRPYYQ260ZXwR7d5EQmbas QkOb4obdP4yOi0KCZPD/e9EpTJX3bEHOF8EbJpKAzSap8oVcCPToh0vLKKlrCitO3Tlg+HEM+i+3 GBm68NhrnKk/zOcdR09RzjrKCsYbp7xdF8v2uYkMpuoI8D/6PbVYMXidwySc2jEmvdtR7rLIXs4R cFjHUext60JbK/9y5H9viwH07/DsBHYvnBgWpxgQp6XtFVJk+rJYbTl4Kkg36CLIiyaBkDwPJg6l 0JGmyIGmpMs2GNW+TCtdZmtf6os6M0MBT4CDE6jAzIluMjLyuLg4FpFUHEdd8PQ9Y+jAfku4bQC6 PpISg/xwPlQ7CXK9ptmjNAShnPPUApI7dYvUAx1cs30scKZkl/AC2bswBvYOGa14kYNx3i9mCFdu N9ViNhnhhQgOTzBDB5Bj3FBja7Iz1yvI/QsWTcMVi8f+YX1rno+sWYbBx9fchcqnJUDVVbwi0MGc x5OfBLmXJxJpwBP52D9sz5P5STlQCcFxpvRZw3FJ6OnOW/YbSe9dt8IaLFw9Hxnat/T5qNVB87XF 6f6UQLiMK5qSUY8uiU+4fco542cCCloXb4opbrkIPnmp05UO/mTnDIt6QQoQK1EjGTewS22Uuqhm Sta0WK3bhSu8klROjH6qcVvmelopa9fuzJadsI9FTIriMyB7STpjvnrvz4F32KJsi6vEOjVSVh65 PPHlRp2VDj19jbrraGdJ4+vdCfSx7orIzYANY4p5RZdYmKUamWT6CjZuzmml4eLdqxh9VCCUWyGP OGUcx14UHqigspdbjGFEKQBobBI3S8fXZo5JCnQGg4XpRBxbJLL0Rb7T1eIb1JsRlEBWdyAfCxHQ tvkwaTE5LHyg+RwWP0anaA6A5R5Z7AEJxZEE6GQYw+r6qA9MFEnNB8IuBAeKtemga6Fl40xRziKw uZq62XuHaBoen+1ytxyW1NuiRbryqt1OAxv1A0v8d460yyio0N2w2rIStVUR/3XCiVLjuOldVLIk 15QKZ9wboNZob9OEXrfRGwYVfYxp56HKlAbKY7OjIbaZMZ4MtivGN0k5btIwUWofeVI01LULmLdH m6SoSsbqP3FKnvj/iGUI/I5wQGUJkymKrv03K4SdrRvsgFNM0b16CDdAEg/ttTsVNF0tnvY1Z6t0 ju1ibCeLgQF01/ur+QP5uv/6fH71IIrGL18FEDrkXYmafiqatukL1B6hE7WeaMVa1g/szNCTVI/I CjYtWbZtYvSNniJ+N8b/p4qvCrDuAo1aKqtaNbeEr7xODU0JHtMgaVFt/fqCWbO5fnGmcx6uc/wz jon1hDMxO9LIlxp70YFVosdRXMnPz0QW3x3FslBVh+NInkJyz+0+xHLGMdMYEwGV5qzgzRpVuCWR iv8mHoVGKDw11Et+HoQGPds8p4FnOzB5LD/of8KNDd38cR+rp7wTrHLKIz52jbBsEDOoyapTAo99 Ev3vL2Ucf/kgDlWcnZZB63Crv9Tr2vCCz0rRQsV0ZRg/J+C1AwU1iAzlh9xRMfox+VZZgLPqsttF E/pz8gylIuVuZD/dKcNKG0iiqKUCugChixTHBA8GPHswn/SUfunpN0VdgbBF6IzN6VitMyaH16uO 19Z2fVZapri9GmPAQBC87O7qHl115ATDzx/Px/HVKY4rlD/A8r5FRQoM9HMxO1/ST23OF4VyZV5k WEFfqXeLO0NGa3L7Lo5FsnJI1GSHCiLs7kq+SVzIKUXv4U6Wvul51KxUTgLJQ9FJMXpqH2KKEkAd 8TrLytaKSF05WpmIq7MR+70HF5dymjzWDEjiNeVdqOgGpSPBg+jtCWH7EK+kCf8Dgxj9Tw+DBJK2 cYYYh07K0urXXy/pwAWP+yUMLBOY3SQnvxxukdnmLVBidMLKDiPNNq05y/CEXB9B96m+2q6YAkQs D6Qb5yRZJRBFtaO8objj0SM9mNUlTA8RYC+utnkxbSEyIn3VLypYNAj28eUtneCAKhPAu1kKwli5 v0AizZJHAMfzIXydWSzS6YK+gWOGjebl3SOXcjcJ5AYcREjGlPYdXRMjGum4L/J2vfj7zM2F1fG/ 59h/eOm3j+nkCbUtk314Ou1C2Cqnn7xZhEYR73aT0ARHhgrcTZ5UKxrCfsiYduK4Uys809D3xcNp odmw3LlarJ1YoGuEwYNn448hBd/aVbNj6a2Y/RkprqDbVplDN6BRV8CRE1mSre1GGe6K28eLngTj kxMFAANZXooch5XtEb5B6tu1DLKgbjGwuyFwDIKYQGU1Q94WLd3ImqicG3ma98VRyXc96SkZG3To qG3oCC/XHcHXM556zcjR16mpYZWbLBZSacbn+IoE5GvxbZjPqPN5bLRctYAcL0Qr61dScNyC1HA3 Nau3dSzulpn3zEyHw8D88wLEG285qovLgTl8r/G+6phtvsbG62eExzQxXrsaeL7jE8Eu2oHhZ6sh SvI8VoeKYYmHcXiRBi+mq9Nq3K/gyK5bB5JYUjPzysnJsW4h8JUWS5qIs4fq6x2xe5WXVbHaVMlI ubWfs3Ez8lLJI3lJhOHtdtKXTuPtXidtjpQVRowHe24520KQ/2VzG5xauWLr7sCgQiAWpZMIELyU fYrEwzDAA68dHdSmj4zmbsIfGu1/yne3aDLkvMqAwmNzmPj02E6v3BK3OZ+O8o/WfGGuutxdNNg6 Vu7GQLBL+ETQysBSem5vK1SkH5pgfCp0W0jUoEB+aGCVINVttOdggmFrWzDEtbi1C4ZEVM1loK0u eP6nCibdtWwnuz8dCoqrk1OCYbcbYolgT9wU1k9kMg6PvpmZ3BvmkB3hi9kz3HWkmKif4ryYoX9i aUP5juaalC3JTQVxlbqKa2uNnCzAyQ92o1gBnsbiez8tGWNwWjvk+ATvocJb9B7+DOrE2LBJPsno Ayj/NvMTsHYt5uS2WyW87iqBnLnvDOn8+wnCynfXPMyLd2oXU8ZzymWQ/mIKaywLulwEK87Y0BQJ NDn4yOWPXZrgAtWbdLDwWY+MMr8IsNXoiF/NO3Icd7e7X3Jwh8iSapdgRth9uBYfQs/tnfGXuqKx Karwr7MZCven8JuZvroxmZyL04glcroqWLUIAWCmUp4eqrc6Yp6D64DW/kHYobbVZtB9oLxv8NAt PTpgfcmBvw8Ock4mvWBx4+oIpOFdRWrr3CaWYK4rWhZ5P3oGKWtLVTrdLR2/LDRcf6moGtwq6ms2 QtWV2ZFFpOdzJ8cTdNIMGQUevErH6yzOQGi9P0HQNSsxoPiiTxJE/6PexOSOya1zqnmYOmbidFp1 irJ1UeacVpG4RtG4JdnMuF5vcWmkqoZLGNrQXtP7DZBn1NjfufRanriFOcxYUHtR33wFl649asCI ur/ngBjTdAqaRToFEx2Hbk9eY5Hj3ctfErokjabp7Sz+UZdVwH0Y3wadn5BbTBTVrzR+37IWlpfh jzhykh7EzzXRngvzzyrxi4kwKfF3egcfGNJd5mrWDf6UMwFFBA+LHd//ci1vNS0TV+7wBVvaC/JI qahbqvhwP796Ph8yZFQEhuGGIO+FAP73YoCVlCJ7PDiKa44ifK8xivQhM9ulzHxDFhU48hYtRjOy MyPTmp+YlpQz+Pv13KtF+NY1yNDimm3LnOwp/gSHJOTltb7c8UrsfyoSI/V7zu4ntd8OjES0rXM0 hkVe0jZpHkE1YIDvIMD6ahAcdX32eHEs5vR30WLoTBcLDUllU+g6Fa0B8pvPYd4HpqsSXsHrrkwr o+bxioCLdOyVwpQUAg1ohmUxO1I5Zlw8iPLjCdCZVf/Wv0rzHpIaNva/WTd5QjJBAAA= --=-0R8c7w4hfm/u4t/ZN6HM-- From noreply@sourceforge.net Tue Apr 1 05:51:13 2003 From: noreply@sourceforge.net (SourceForge.net) Date: Mon, 31 Mar 2003 21:51:13 -0800 Subject: [Idle-dev] [ idlefork-Bugs-677263 ] On W32 Can't Terminate Subprocess Not Doing IO Message-ID: Bugs item #677263, was opened at 2003-01-29 20:02 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109579&aid=677263&group_id=9579 Category: None Group: None Status: Open Resolution: Accepted Priority: 7 Submitted By: Bruce Sherwood (bsherwood) Assigned to: Kurt B. Kaiser (kbk) Summary: On W32 Can't Terminate Subprocess Not Doing IO Initial Comment: With 0.9a2 it is still the case that something is very wrong with the run environment for VPython programs, at least on Windows. I run the simplest program from visual import * sphere() Next I kill the graphics display window (by clicking in the close box), then type in the shell "2+2". I get the following: Traceback (most recent call last): File "C:\Python23\Lib\site-packages\idleforklib\rpc.py", line 187, in asynccall self.putmessage((seq, request)) File "C:\Python23\Lib\site-packages\idleforklib\rpc.py", line 289, in putmessage n = self.sock.send(s) File "", line 1, in send error: (10054, 'Connection reset by peer') I then try to kill the shell window and get a dialog box asking this: "The program is still running; do you want to kill it?" I say I want to kill it, the dialog box goes away, but nothing happens to the shell window. The only way I can kill Python is with the Windows task manager. Even independent of what may be special about a VPython program, shouldn't IDLE honor the request to kill? I emphasize that with the original idlefork when one killed a VPython graphics window you were in a good state. Another possible hint at the source of the new problem is that with the original idlefork after F5 to run I could press F5 and the existing graphics window would be killed and I'd get a new spawned process. Now I seem to get two spawned processes in this situation. http://vpython.org is a place to get the VPython stuff. I have no idea whether the problem is in some sense with VPython or with the new idlefork. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2003-03-31 21:51 Message: Logged In: NO More on run/kill issues: When I'm running my Tkinter app and editing the source code, idlefork will sometimes hang when looking up a CallTip. The IDLE windows won't redraw until I kill my app, and then the editor is in a confused state. I can't evaluate expressions in the shell or restart the program. I also can't restart the shell. I'm using Win32. I think I'll get around to investigating this more and typing up a bug report, but I was hoping this little bit would help some. Randall Farmer, rfarmer@simons-rock.spam.edu ---------------------------------------------------------------------- Comment By: Kurt B. Kaiser (kbk) Date: 2003-01-30 08:24 Message: Logged In: YES user_id=149084 I changed the title, this isn't just a VPython issue. I can confirm what you are seeing, and I have some ideas on how to fix it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109579&aid=677263&group_id=9579 From fyvdv@chass.utoronto.ca Mon Apr 7 17:12:57 2003 From: fyvdv@chass.utoronto.ca (fyvdv@chass.utoronto.ca) Date: Mon, 07 Apr 2003 13:12:57 -0300 Subject: [Idle-dev] Digital sports events, movies, etc. Message-ID: <40b23db2f826$baae663e$527c6c14@mxlsxapdiqkwr.ibbi> ------=_NextPart_A8E_7426_DB6E3328.9BBE55BD Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ------=_NextPart_A8E_7426_DB6E3328.9BBE55BD Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
The next big thing for digital cable users?  Check it out ... Clik here
 
 
If you don't want to receive any more emails, go here.
 
------=_NextPart_A8E_7426_DB6E3328.9BBE55BD-- From s997659@ee.cuhk.edu.hk Wed Apr 9 12:05:17 2003 From: s997659@ee.cuhk.edu.hk (Geiger Ho) Date: Wed, 9 Apr 2003 19:05:17 +0800 (HKT) Subject: [Idle-dev] Question on run module Message-ID: Hi all, I use idlefork 0.9a2. My problem is that when I run my module with other module imported altogether in my specific path, say "c:\mywork", I get "ImportError: No module named XXX". Is there any solution for this? My propose solution is that I in my module, append my path to sys.path. However, os.path.abspath() gives me that idlefork path rather than the path my module situated. Any solution too? Thanks in advance. Regards, Geiger From heikos@foni.net Sat Apr 12 23:08:49 2003 From: heikos@foni.net (Heiko =?iso-8859-1?q?Schr=F6der?=) Date: Sun, 13 Apr 2003 00:08:49 +0200 Subject: [Idle-dev] IDLE 0.8 - severe bug? Message-ID: <200304130008.49993.heikos@foni.net> Dear list, I tried hard to find any information about the following bug, which I suppose to be a familiar one. I am using: System: Linux SuSE 8.2 IDLE-Version: 0.8 Python-Version: 2.2.2 Tkinter-Version: 8.4 Problem: Every trial to open a window -- even a help window -- in IDLE producesa similar Errorcode like this (tried to open Python-Documentation in IDLE): Exception in Tkinter callback: File /var/tmp/python-2.2.2.-build//usr/lib/python2.2/lib-tk/Tkinter.py, line 1299 in __call__ args=apply(self.subst,args) File /var/tmp/python-2.2.2-build//usr/lib/python2.2/lib-tk/Tkinter.py, line 1035, in _substitute e.num=getint(b) Value Error: invalid literal for int(): ?? Do you know where I will get hints to fix this bug? I am afraid that the Tkinter version does not match the IDLE-Version in the package which SuSE 8.2 uses. Thanks for your help Heiko -- Heiko Schroeder Ahrensburg, Germany http://home.foni.net/~heikos From noreply@sourceforge.net Sun Apr 13 00:01:22 2003 From: noreply@sourceforge.net (SourceForge.net) Date: Sat, 12 Apr 2003 16:01:22 -0700 Subject: [Idle-dev] [ idlefork-Patches-661363 ] Run multiple IDLEforks on the same machine simultanously Message-ID: Patches item #661363, was opened at 2003-01-03 00:57 Message generated for change (Comment added) made by noamr You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=309579&aid=661363&group_id=9579 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Noam Raphael (noamr) Assigned to: Nobody/Anonymous (nobody) Summary: Run multiple IDLEforks on the same machine simultanously Initial Comment: Instead of defining a specific port (8833), a list of legitimate ports is defined. When IDLE starts, it goes over the list and tries each of the ports. When it finds a port which is ok, it starts the subprocess. The list of ports which I defined is very arbitrary, and should be reviewed. A more minor change, which is calling the spawn_subprocess method only after the RPCClient class was succesfully initialized, solves the bug that when opening a second IDLE, an error message is displayed but a malfunctioning shell window is displayed, and when it's closed, the subprocess keeps on running until the first IDLE is shut down. ---------------------------------------------------------------------- >Comment By: Noam Raphael (noamr) Date: 2003-04-13 02:01 Message: Logged In: YES user_id=679426 This better patch tries the ports at a random order, which is much faster when some IDLEfork instances are already running. ---------------------------------------------------------------------- Comment By: Kurt B. Kaiser (kbk) Date: 2003-01-03 05:55 Message: Logged In: YES user_id=149084 Converted Noam Raphael's file to a context patch ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=309579&aid=661363&group_id=9579 From noreply@sourceforge.net Sun Apr 13 11:47:55 2003 From: noreply@sourceforge.net (SourceForge.net) Date: Sun, 13 Apr 2003 03:47:55 -0700 Subject: [Idle-dev] [ idlefork-Bugs-720581 ] Restarting Shell (sometimes) causes sub-process to hang Message-ID: Bugs item #720581, was opened at 2003-04-13 20:47 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109579&aid=720581&group_id=9579 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nigel Rowe (fisheggs) Assigned to: Nobody/Anonymous (nobody) Summary: Restarting Shell (sometimes) causes sub-process to hang Initial Comment: When restarting the Shell windows (Using Ctrl+F6), the sub-process intermittantly hangs in rpc.py with an unhandled exception (usually "connection reset by peer" or "Broken pipe") from socket.send() in putmessage(). When PyShell restarts, it interupts and shutsdown the sub-process, then closes the socket before waiting for the subprocess to exit. Proposed solution, reverse the order of self.rpcclt.close() and os.wait() in restart_subprocess(). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109579&aid=720581&group_id=9579 From noreply@sourceforge.net Sun Apr 13 12:17:50 2003 From: noreply@sourceforge.net (SourceForge.net) Date: Sun, 13 Apr 2003 04:17:50 -0700 Subject: [Idle-dev] [ idlefork-Bugs-720581 ] Restarting Shell (sometimes) causes sub-process to hang Message-ID: Bugs item #720581, was opened at 2003-04-13 20:47 Message generated for change (Comment added) made by fisheggs You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109579&aid=720581&group_id=9579 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nigel Rowe (fisheggs) Assigned to: Nobody/Anonymous (nobody) Summary: Restarting Shell (sometimes) causes sub-process to hang Initial Comment: When restarting the Shell windows (Using Ctrl+F6), the sub-process intermittantly hangs in rpc.py with an unhandled exception (usually "connection reset by peer" or "Broken pipe") from socket.send() in putmessage(). When PyShell restarts, it interupts and shutsdown the sub-process, then closes the socket before waiting for the subprocess to exit. Proposed solution, reverse the order of self.rpcclt.close() and os.wait() in restart_subprocess(). ---------------------------------------------------------------------- >Comment By: Nigel Rowe (fisheggs) Date: 2003-04-13 21:17 Message: Logged In: YES user_id=756090 Possibly relevant. This was on a fast, dual cpu machine ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109579&aid=720581&group_id=9579 From josh_robb@fastmail.fm Tue Apr 15 15:22:52 2003 From: josh_robb@fastmail.fm (Josh Robb) Date: Tue, 15 Apr 2003 15:22:52 +0100 Subject: [Idle-dev] Some Pychecker Goodness... Message-ID: <00d601c3035a$8070ec50$0600000a@privateu6b70b4> Well. Finally I had some time this weekend to finally finish up this code. Here are the results: http://treehouse.homedns.org/~josh/pychecker.gif http://treehouse.homedns.org/~josh/pycheck-results.gif http://treehouse.homedns.org/~josh/pycheck-options.gif I need to clean up the options dialogue, fix up some corner cases in the editor error markup. Should be done this week all going well. Coming back to programming python is such a nice feeling. Any Feedback? The options dialogue will need some usability work. j. From neal@metaslash.com Wed Apr 16 02:52:31 2003 From: neal@metaslash.com (Neal Norwitz) Date: Tue, 15 Apr 2003 21:52:31 -0400 Subject: [Idle-dev] Some Pychecker Goodness... In-Reply-To: <00d601c3035a$8070ec50$0600000a@privateu6b70b4> References: <00d601c3035a$8070ec50$0600000a@privateu6b70b4> Message-ID: <20030416015231.GJ1579@epoch.metaslash.com> On Tue, Apr 15, 2003 at 03:22:52PM +0100, Josh Robb wrote: > Well. Finally I had some time this weekend to finally finish up this > code. > > Here are the results: > > http://treehouse.homedns.org/~josh/pychecker.gif > > http://treehouse.homedns.org/~josh/pycheck-results.gif > > http://treehouse.homedns.org/~josh/pycheck-options.gif > > I need to clean up the options dialogue, fix up some corner cases in the > editor error markup. Should be done this week all going well. Coming > back to programming python is such a nice feeling. If you hurry, you may be able to get your changes into python 2.3. :-) 2.3 beta should be coming out any week now--I'm not really sure when though. Hopefully, we will get idlefork moved into 2.3 also. Not sure of the status of idlefork either. > Any Feedback? The options dialogue will need some usability work. Looks good so far. Feel free to re-organize options if you think they make more sense another way. I can always change it in pychecker too. Neal From guido@python.org Wed Apr 16 16:53:48 2003 From: guido@python.org (Guido van Rossum) Date: Wed, 16 Apr 2003 11:53:48 -0400 Subject: [Idle-dev] Python 2.3b1 release Message-ID: <200304161553.h3GFrmD10196@odiug.zope.com> I'd like to release Python 2.3b1 around April 25. I'd like this to include IDLEfork instead of IDLE. Is that feasible? Can somebody help with the CVS work? (I don't need the CVS history to be transferred, just the files.) --Guido van Rossum (home page: http://www.python.org/~guido/) From basherwo@unity.ncsu.edu Wed Apr 16 18:25:14 2003 From: basherwo@unity.ncsu.edu (Bruce Sherwood) Date: Wed, 16 Apr 2003 13:25:14 -0400 Subject: [Idle-dev] Python 2.3b1 release References: <200304161553.h3GFrmD10196@odiug.zope.com> Message-ID: <000b01c3043d$24caea20$6401a8c0@hyperon> Like many other potential users, I'm eager to see this happen, but I'm concerned that there hasn't been a release since IDLEfork-0.9a2 on Jan. 27. Since that time there has been lots of activity but no new release, which means to me that there hasn't been the kind of testing that is needed before replacing the old IDLE. There were many things wrong with 0.9a2; if everything has been fixed, we need a new release so that people can beat on it. I have not attempted to use CVS versions; with very limited time I can only contribute to use-testing major releases. Bruce Sherwood ----- Original Message ----- From: "Guido van Rossum" To: Sent: Wednesday, April 16, 2003 11:53 AM Subject: [Idle-dev] Python 2.3b1 release > I'd like to release Python 2.3b1 around April 25. I'd like this to > include IDLEfork instead of IDLE. Is that feasible? Can somebody > help with the CVS work? (I don't need the CVS history to be > transferred, just the files.) > > --Guido van Rossum (home page: http://www.python.org/~guido/) > > _______________________________________________ > IDLE-dev mailing list > IDLE-dev@python.org > http://mail.python.org/mailman/listinfo/idle-dev > > From kbk@shore.net Thu Apr 24 06:15:51 2003 From: kbk@shore.net (Kurt B. Kaiser) Date: Thu, 24 Apr 2003 01:15:51 -0400 Subject: [Idle-dev] Python 2.3b1 release In-Reply-To: <200304161553.h3GFrmD10196@odiug.zope.com> (Guido van Rossum's message of "Wed, 16 Apr 2003 11:53:48 -0400") References: <200304161553.h3GFrmD10196@odiug.zope.com> Message-ID: Guido van Rossum writes: > I'd like to release Python 2.3b1 around April 25. I'd like this to > include IDLEfork instead of IDLE. Is that feasible? Can somebody > help with the CVS work? (I don't need the CVS history to be > transferred, just the files.) Status: I've got the threaded subprocess running and it's passed my initial tests. I had a major computer issue and then a bout of flu or something and just got back on line today. I'll be finishing up my testing later today and then I'll do a check-in. __ KBK From basherwo@unity.ncsu.edu Thu Apr 24 16:03:08 2003 From: basherwo@unity.ncsu.edu (Bruce Sherwood) Date: Thu, 24 Apr 2003 11:03:08 -0400 Subject: [Idle-dev] Python 2.3b1 release References: <200304161553.h3GFrmD10196@odiug.zope.com> Message-ID: <001901c30a72$9e06ef70$e5770198@muon> Will there be a release of IDLEfork? There hasn't been one since Jan. 26 (0.9a2). I repeat my concern that without a release, which encourages people to beat on it, there will have been almost no extensive testing, which makes me nervous. Bruce Sherwood ----- Original Message ----- From: "Kurt B. Kaiser" To: "Guido van Rossum" Cc: Sent: Thursday, April 24, 2003 1:15 AM Subject: Re: [Idle-dev] Python 2.3b1 release > Guido van Rossum writes: > > > I'd like to release Python 2.3b1 around April 25. I'd like this to > > include IDLEfork instead of IDLE. Is that feasible? Can somebody > > help with the CVS work? (I don't need the CVS history to be > > transferred, just the files.) > > Status: I've got the threaded subprocess running and it's passed my > initial tests. > > I had a major computer issue and then a bout of flu or something and > just got back on line today. I'll be finishing up my testing later > today and then I'll do a check-in. > > __ > KBK > > _______________________________________________ > IDLE-dev mailing list > IDLE-dev@python.org > http://mail.python.org/mailman/listinfo/idle-dev > > From guido@python.org Thu Apr 24 16:09:57 2003 From: guido@python.org (Guido van Rossum) Date: Thu, 24 Apr 2003 11:09:57 -0400 Subject: [Idle-dev] Python 2.3b1 release In-Reply-To: Your message of "Thu, 24 Apr 2003 11:03:08 EDT." <001901c30a72$9e06ef70$e5770198@muon> References: <200304161553.h3GFrmD10196@odiug.zope.com> <001901c30a72$9e06ef70$e5770198@muon> Message-ID: <200304241509.h3OF9vm11713@odiug.zope.com> > Will there be a release of IDLEfork? There hasn't been one since > Jan. 26 (0.9a2). I repeat my concern that without a release, which > encourages people to beat on it, there will have been almost no > extensive testing, which makes me nervous. Kurt's been away, but he's back now. With a release as part of Python 2.3b1, there will be plenty of extensive testing. Kurt now has checkin permissions on the Python project to move the IDLEfork codebase there and fix bugs as they occur. --Guido van Rossum (home page: http://www.python.org/~guido/) From basherwo@unity.ncsu.edu Thu Apr 24 18:46:18 2003 From: basherwo@unity.ncsu.edu (Bruce Sherwood) Date: Thu, 24 Apr 2003 13:46:18 -0400 Subject: [Idle-dev] Python 2.3b1 release References: <200304161553.h3GFrmD10196@odiug.zope.com> <001901c30a72$9e06ef70$e5770198@muon> <200304241509.h3OF9vm11713@odiug.zope.com> Message-ID: <001401c30a89$690d4320$e5770198@muon> Ah. I see. With Python itself as the beta test, that makes complete sense. I had been concerned that perhaps one would have wanted major testing of idlefork BEFORE it showed up in Python, but if you're willing for the idlefork beta test to be part of the Python beta test, great. My impression of past Python betas was that they were in very good shape already, and it wasn't clear to me that idlefork was in the same state of near readiness. I look forward to testing both Python and idlefork! Bruce Sherwood ----- Original Message ----- From: "Guido van Rossum" To: "Bruce Sherwood" Cc: "Kurt B. Kaiser" ; Sent: Thursday, April 24, 2003 11:09 AM Subject: Re: [Idle-dev] Python 2.3b1 release > > Will there be a release of IDLEfork? There hasn't been one since > > Jan. 26 (0.9a2). I repeat my concern that without a release, which > > encourages people to beat on it, there will have been almost no > > extensive testing, which makes me nervous. > > Kurt's been away, but he's back now. > > With a release as part of Python 2.3b1, there will be plenty of > extensive testing. Kurt now has checkin permissions on the Python > project to move the IDLEfork codebase there and fix bugs as they > occur. > > --Guido van Rossum (home page: http://www.python.org/~guido/) > > From kbk@users.sourceforge.net Fri Apr 25 17:37:35 2003 From: kbk@users.sourceforge.net (Kurt B. Kaiser) Date: Fri, 25 Apr 2003 09:37:35 -0700 Subject: [Idle-dev] CVS: idle NEWS.txt,1.12,1.13 CREDITS.txt,1.4,1.5 INSTALL.txt,1.5,1.6 setup.cfg,1.1,1.2 Message-ID: Update of /cvsroot/idlefork/idle In directory sc8-pr-cvs1:/tmp/cvs-serv27763 Modified Files: NEWS.txt CREDITS.txt INSTALL.txt setup.cfg Log Message: Update for 2.3b1 Modified Files: NEWS.txt CREDITS.txt INSTALL.txt setup.cfg Index: NEWS.txt =================================================================== RCS file: /cvsroot/idlefork/idle/NEWS.txt,v retrieving revision 1.12 retrieving revision 1.13 diff -C2 -r1.12 -r1.13 *** NEWS.txt 12 Mar 2003 20:52:00 -0000 1.12 --- NEWS.txt 25 Apr 2003 16:37:30 -0000 1.13 *************** *** 3,10 **** +++++++++++++ ! What's New in IDLEfork 0.9 Alpha 3? =================================== ! *Release date: xx-xxx-2003* - Implemented the 'interrupt' extension module, which allows a subthread --- 3,10 ---- +++++++++++++ ! What's New in IDLEfork? =================================== ! *Release date: 25-Apr-2003* - Implemented the 'interrupt' extension module, which allows a subthread Index: CREDITS.txt =================================================================== RCS file: /cvsroot/idlefork/idle/CREDITS.txt,v retrieving revision 1.4 retrieving revision 1.5 diff -C2 -r1.4 -r1.5 *** CREDITS.txt 26 Jan 2003 20:37:01 -0000 1.4 --- CREDITS.txt 25 Apr 2003 16:37:31 -0000 1.5 *************** *** 25,30 **** There are others who should be included here, especially those who contributed ! to IDLE versions prior to 0.8, principally Mark Hammond, Tim Peters, and Moshe ! Zadka. For additional details refer to NEWS.txt and Changelog. Please contact the IDLEfork maintainer to have yourself included here if you --- 25,31 ---- There are others who should be included here, especially those who contributed ! to IDLE versions prior to 0.8, principally Mark Hammond, Jeremy Hylton, ! Tim Peters, and Moshe Zadka. For additional details refer to NEWS.txt and ! Changelog. Please contact the IDLEfork maintainer to have yourself included here if you Index: INSTALL.txt =================================================================== RCS file: /cvsroot/idlefork/idle/INSTALL.txt,v retrieving revision 1.5 retrieving revision 1.6 diff -C2 -r1.5 -r1.6 *** INSTALL.txt 27 Jan 2003 02:40:20 -0000 1.5 --- INSTALL.txt 25 Apr 2003 16:37:31 -0000 1.6 *************** *** 13,26 **** to avoid conflict with the original Python IDLE. ! IDLEfork-0.9xx-1.noarch.rpm ! This is an rpm which is designed to install as idleforklib in the ! /usr/lib/python2.2 tree created by the Python2 rpm. It requires ! python2 and python2-tkinter rpms. It installs as idlefork to avoid conflict with Python IDLE. ! The Python2 rpm is designed to work with Redhat systems prior to Rev 8. ! It is available at http://www.python.org/2.2.2/rpms.html and ! http://www.python.org/2.2.1/rpms.html . See the warning/explanation ! on the latter web page, which discusses the reason for python2. IDLEfork-0.9xx.tar.gz --- 13,23 ---- to avoid conflict with the original Python IDLE. ! IDLEfork-0.9xx-1.noarch.rpm ! This is an rpm which is designed to install as idleforklib in an ! existing /usr/lib/python2.2 tree. It installs as idlefork to avoid conflict with Python IDLE. ! Python rpms are available at http://www.python.org/2.2.2/rpms.html and ! http://www.python.org/2.2.1/rpms.html. IDLEfork-0.9xx.tar.gz *************** *** 30,38 **** Unpack in ..../Tools/, cd to the IDLEfork directory created, and ! to install in ....site-packages/idlelib. This will overwrite the Python IDLE installation. If you don't want to overwrite Python IDLE, it is also possible to ! simply call to run from the IDLEfork source directory without making an installation. In this case, IDLE will not be on your PATH unless you are in the source directory. Also, it is then --- 27,35 ---- Unpack in ..../Tools/, cd to the IDLEfork directory created, and ! "python setup.py install" to install in ....site-packages/idlelib. This will overwrite the Python IDLE installation. If you don't want to overwrite Python IDLE, it is also possible to ! simply call "python idle.py" to run from the IDLEfork source directory without making an installation. In this case, IDLE will not be on your PATH unless you are in the source directory. Also, it is then *************** *** 41,44 **** --- 38,46 ---- conflict. + On Redhat Linux systems prior to 8.0, /usr/bin/python may be pointing + at python1.5. If so, change the first line in the /usr/bin/idle + script to read: + !# /usr/bin/python2.2 + See README.txt for more details on this version of IDLEfork. Index: setup.cfg =================================================================== RCS file: /cvsroot/idlefork/idle/setup.cfg,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -r1.1 -r1.2 *** setup.cfg 22 Dec 2002 01:48:28 -0000 1.1 --- setup.cfg 25 Apr 2003 16:37:31 -0000 1.2 *************** *** 2,4 **** release = 1 packager = Kurt B. Kaiser ! requires = python2, python2-tkinter --- 2,4 ---- release = 1 packager = Kurt B. Kaiser ! From kbk@users.sourceforge.net Fri Apr 25 18:48:10 2003 From: kbk@users.sourceforge.net (Kurt B. Kaiser) Date: Fri, 25 Apr 2003 10:48:10 -0700 Subject: [Idle-dev] CVS: idle NEWS.txt,1.13,1.14 idlever.py,1.9,1.10 Message-ID: Update of /cvsroot/idlefork/idle In directory sc8-pr-cvs1:/tmp/cvs-serv30033 Modified Files: NEWS.txt idlever.py Log Message: Update for release into Python NEWS.txt idlever.py Index: NEWS.txt =================================================================== RCS file: /cvsroot/idlefork/idle/NEWS.txt,v retrieving revision 1.13 retrieving revision 1.14 diff -C2 -r1.13 -r1.14 *** NEWS.txt 25 Apr 2003 16:37:30 -0000 1.13 --- NEWS.txt 25 Apr 2003 17:48:08 -0000 1.14 *************** *** 3,7 **** +++++++++++++ ! What's New in IDLEfork? =================================== --- 3,7 ---- +++++++++++++ ! What's New in IDLEfork 0.9b1? =================================== Index: idlever.py =================================================================== RCS file: /cvsroot/idlefork/idle/idlever.py,v retrieving revision 1.9 retrieving revision 1.10 diff -C2 -r1.9 -r1.10 *** idlever.py 27 Jan 2003 02:40:20 -0000 1.9 --- idlever.py 25 Apr 2003 17:48:08 -0000 1.10 *************** *** 1 **** ! IDLE_VERSION = "0.9a2" --- 1 ---- ! IDLE_VERSION = "0.9b1" From gvanrossum@users.sourceforge.net Fri Apr 25 19:36:35 2003 From: gvanrossum@users.sourceforge.net (Guido van Rossum) Date: Fri, 25 Apr 2003 11:36:35 -0700 Subject: [Idle-dev] CVS: idle IOBinding.py,1.13,1.14 Message-ID: Update of /cvsroot/idlefork/idle In directory sc8-pr-cvs1:/tmp/cvs-serv16219 Modified Files: IOBinding.py Log Message: New feature: when saving a file, keep the eol convention of the original. New files are written using the eol convention of the platform, given by os.linesep. All files are read and written in binary mode. Index: IOBinding.py =================================================================== RCS file: /cvsroot/idlefork/idle/IOBinding.py,v retrieving revision 1.13 retrieving revision 1.14 diff -C2 -r1.13 -r1.14 *** IOBinding.py 4 Mar 2003 04:42:04 -0000 1.13 --- IOBinding.py 25 Apr 2003 18:36:31 -0000 1.14 *************** *** 179,182 **** --- 179,186 ---- return "break" + eol = r"(\r\n)|\n|\r" # \r\n (Windows), \n (UNIX), or \r (Mac) + eol_re = re.compile(eol) + eol_convention = os.linesep # Default + def loadfile(self, filename): try: *************** *** 192,197 **** chars = self.decode(chars) # We now convert all end-of-lines to '\n's ! eol = r"(\r\n)|\n|\r" # \r\n (Windows), \n (UNIX), or \r (Mac) ! chars = re.compile( eol ).sub( r"\n", chars ) self.text.delete("1.0", "end") --- 196,203 ---- chars = self.decode(chars) # We now convert all end-of-lines to '\n's ! firsteol = self.eol_re.search(chars) ! if firsteol: ! self.eol_convention = firsteol.group(0) ! chars = self.eol_re.sub(r"\n", chars) self.text.delete("1.0", "end") *************** *** 307,312 **** self.fixlastline() chars = self.encode(self.text.get("1.0", "end-1c")) try: ! f = open(filename, "w") f.write(chars) f.close() --- 313,320 ---- self.fixlastline() chars = self.encode(self.text.get("1.0", "end-1c")) + if self.eol_convention != "\n": + chars = chars.replace("\n", self.eol_convention) try: ! f = open(filename, "wb") f.write(chars) f.close()