summaryrefslogtreecommitdiffstats
path: root/Tools
Commit message (Collapse)AuthorAgeFilesLines
* Add Python Documentation entry to Help menu.Guido van Rossum1999-08-261-0/+3
|
* Find the help.txt file relative to __file__ or ".", not in sys.path.Guido van Rossum1999-08-261-8/+14
| | | | | | | | (Suggested by Moshe Zadka, but implemented differently.) Add <<python-docs>> event which, on Unix, brings up Netscape pointing to http://www.python.doc/current/ (a local copy would be nice but its location can't be predicted). Windows solution TBD.
* Scrit by Marc-Andre Lemburg to generate htmlentitydefs.py.Guido van Rossum1999-08-191-0/+65
|
* Bump to version 1.1Barry Warsaw1999-08-181-1/+1
|
* __update(): Jeremy Hylton reports occurances of sunaudiodev.errorBarry Warsaw1999-08-181-5/+14
| | | | | | | | | (interrupted system call) when getting the device information. I've never seen it, but this patch should take care of the problem. If we get that exception and we're polling, just return since we'll wake up again soon and get the right information. If we're not polling, try 4 times and then give up.
* Initial implementationBarry Warsaw1999-08-131-0/+268
|
* Initial revisionBarry Warsaw1999-08-111-0/+1
|
* Moshe noticed an inconsistency in his comment, so I'm rephrasing it toGuido van Rossum1999-08-111-2/+1
| | | | be clearer.
* Patch inspired by Moshe Zadka to search for the Icons directory in theGuido van Rossum1999-08-111-5/+11
| | | | | same directory as __file__, rather than searching for it along sys.path. This works better when idle is a package.
* Mark Hammond writes:Guido van Rossum1999-07-302-2/+6
| | | | | | | | | | | | | | | | """ If the filename being complained about contains a space, enclose the file-name in quotes. The reason is simply that when I try and parse tabnanny's output, filenames with spaces make it very difficult to determine where the filename stops and the linenumber begins! """ Tim approves. I slightly changed the patch (use 'in' instead of string.find()) and arbitrarily bumped the __version__ variable up to 6.
* New wishes.Guido van Rossum1999-07-151-1/+5
|
* Make the color for stderr red (i.e. the standard warning/danger/stopGuido van Rossum1999-07-101-1/+1
| | | | color) rather than green. Suggested by Sam Schulenburg.
* make_view_popups(): Catch import error which can occur if a viewer isBarry Warsaw1999-07-061-1/+7
| | | | | | dynamically imported when Pynche is running via askcolor out of a package. If the ImportError occurs, try again, prepending the package name and digging out the module.
* Close debugger when closing. This may break a cycle.Guido van Rossum1999-06-251-0/+1
|
* Break cycle on close.Guido van Rossum1999-06-251-0/+2
|
* Destroy the tree when closing.Guido van Rossum1999-06-251-1/+2
|
* Add destroy() method to recursively destroy a tree.Guido van Rossum1999-06-251-0/+6
|
* Extend _close() to break cycles.Guido van Rossum1999-06-251-13/+18
| | | | Break some other cycles too (and destroy the root when done).
* Add _close() method that does the actual cleanup (close() asks theGuido van Rossum1999-06-251-10/+26
| | | | | | | | user what they want first if there's unsaved stuff, and may cancel). It closes more than before. Add unload_extensions() method to unload all extensions; called from _close(). It calls an extension's close() method if it has one.
* Add close() method that breaks cycles.Guido van Rossum1999-06-251-0/+8
|
* Add unregister() method.Guido van Rossum1999-06-251-4/+12
| | | | | Unregister everything at closing. Don't call close() in __del__, rely on explicit call to close().
* Add close() method that breaks a cycle.Guido van Rossum1999-06-253-4/+23
|
* Simplified version of a patch by Chih-Hao Huang, who wrote:Guido van Rossum1999-06-231-2/+3
| | | | | | | | | | | | | | | | | | | """ When there are additional Setup files, specified by -e option of freeze, checkextenstions.py assumes that *.o, *.a, -Lpath, and -Rpath are all relative to where the Setup file is. select() inserts the path to the Setup file to make them absolute. However, the assumption is not true. There are cases that absolute paths are specified for them. The inserted prefix, by select(), results in error. The following fix check for absolute paths. The assumption is: an absolute path begins with either '/' or '$'. In the latter case, it is from the environmental variable. (Variables defined locally in the Setup file have already been handled by expandvars()) """ My version of the patch has been verified by Charles Waldman (a colleague of Chih-Hao).
* Patch submitted by Toby Dickenson and approved by Mark Hammond.Guido van Rossum1999-06-211-2/+2
| | | | | | | | | | | | | | | | Toby writes: winmakemakefile.py tries to allow for spaces in the python install path, by adding quotes around the appropriate filenames. It doesn't quite get this correct; sometimes the quotes end up in the middle of the path. Microsoft's NMAKE version 6.0 is happy with this (!!!!) unless there is also a space in the name. I guess most users of freeze on windows do not use the same path as the binary distribution. I've tested the following changes on systems with and without a space in the path.
* Tim Peters smart.patch:Guido van Rossum1999-06-113-59/+77
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | EditorWindow.py: + Added get_tabwidth & set_tabwidth "virtual text" methods, that get/set the widget's view of what a tab means. + Moved TK_TABWIDTH_DEFAULT here from AutoIndent. + Renamed Mark's get_selection_index to get_selection_indices (sorry, Mark, but the name was plain wrong <wink>). FormatParagraph.py: renamed use of get_selection_index. AutoIndent.py: + Moved TK_TABWIDTH_DEFAULT to EditorWindow. + Rewrote set_indentation_params to use new VTW get/set_tabwidth methods. + Changed smart_backspace_event to delete whitespace back to closest preceding virtual tab stop or real character (note that this may require inserting characters if backspacing over a tab!). + Nuked almost references to the selection tag, in favor of using get_selection_indices. The sole exception is in set_region, for which no "set_selection" abstraction has yet been agreed upon. + Had too much fun using the spiffy new features of the format-paragraph cmd.
* Code by Mark Hammond to format paragraphs embedded in comments.Guido van Rossum1999-06-101-10/+55
| | | | | Read the comments (which I reformatted using the new feature :-) for some limitations.
* Added abstraction get_selection_index() (Mark Hammond). AlsoGuido van Rossum1999-06-101-14/+23
| | | | | reformatted some comment blocks to show off a cool feature I'm about to check in next.
* Adapt to the new pyclbr's support of listing top-level functions. IfGuido van Rossum1999-06-101-33/+34
| | | | | | | | this functionality is not present (e.g. when used with a vintage Python 1.5.2 installation) top-level functions are not listed. (Hmm... Any distribution of IDLE 0.5 should probably include a copy of the new pyclbr.py!)
* Fix off-by-one error in Tim's recent change to comment_region(): theGuido van Rossum1999-06-101-1/+1
| | | | | | list of lines returned by get_region() contains an empty line at the end representing the start of the next line, and this shouldn't be commented out!
* Mark Hammond writes: Here is another change that allows it to work forGuido van Rossum1999-06-101-14/+37
| | | | | class creation - tries to locate an __init__ function. Also updated the test code to reflect your new "***" change.
* Mark Hammond writes: Tim's suggestion of copying the font for theGuido van Rossum1999-06-101-1/+2
| | | | | CallTipWindow from the text control makes sense, and actually makes the control look better IMO.
* Append "..." if the appropriate flag (for varargs) in co_flags is set.Guido van Rossum1999-06-091-1/+3
| | | | Ditto "***" for kwargs.
* Hmm... Tim didn't turn "replace all" into a single undo block.Guido van Rossum1999-06-081-0/+2
| | | | I think I like it better if it os, so here.
* Tim Peters: made replacement atomic for undo/redo.Guido van Rossum1999-06-081-0/+2
|
* Tim Peters:Guido van Rossum1999-06-081-3/+2
| | | | | | | | | | | | | | | + Set usetabs=1. Editing pyclbr.py was driving me nuts <0.6 wink>. usetabs=1 is the Emacs pymode default too, and thanks to indentwidth != tabwidth magical usetabs disabling, new files are still created with tabs turned off. The only implication is that if you open a file whose first indent is a single tab, IDLE will now magically use tabs for that file (and set indentwidth to 8). Note that the whole scheme doesn't work right for PythonWin, though, since Windows users typically set tabwidth to 4; Mark probably has to hide the IDLE algorithm from them (which he already knows). + Changed comment_region_event to stick "##" in front of every line. The "holes" previously left on blank lines were visually confusing (made it needlessly hard to figure out what to uncomment later).
* Remove unnecessary reference to pyclbr from test() code.Guido van Rossum1999-06-072-5/+0
|
* Tim Peters:Guido van Rossum1999-06-071-19/+75
| | | | | | | | | | | | | | Smarter logic for finding a parse synch point. Does a half to a fifth the work in normal cases; don't notice the speedup, but makes more breathing room for other extensions. Speeds terrible cases by at least a factor of 10. "Terrible" == e.g. you put """ at the start of Tkinter.py, undo it, zoom to the bottom, and start typing in code. Used to take about 8 seconds for ENTER to respond, now some large fraction of a second. The new code gets indented correctly, despite that it all remains "string colored" until the colorizer catches up (after which, ENTER appears instantaneous again).
* Might as well enable CallTips by default.Guido van Rossum1999-06-041-0/+1
| | | | If there are too many complaints I'll remove it again or fix it.
* New offerings by Tim Peters; he writes:Guido van Rossum1999-06-033-26/+66
| | | | | | | | | | IDLE is now the first Python editor in the Universe not confused by my doctest.py <wink>. As threatened, this defines IDLE's is_char_in_string function as a method of EditorWindow. You just need to define one similarly in whatever it is you pass as editwin to AutoIndent; looking at the EditorWindow.py part of the patch should make this clear.
* Enclose pattern in quotes in status message.Guido van Rossum1999-06-031-1/+1
|
* Mark Hammond fixed some comments and improved the way the tip text isGuido van Rossum1999-06-031-11/+12
| | | | constructed.
* My fix to Mark's code: restore the universal check on <KeyRelease>.Guido van Rossum1999-06-021-14/+2
| | | | Always cancel on <Key-Escape> or <ButtonPress>.
* A version that Mark Hammond posted to the newsgroup. Has some newerGuido van Rossum1999-06-021-27/+38
| | | | | | stuff for getting the tip. Had to fix the Key-( and Key-) events for Unix. Will have to re-apply my patch for catching KeyRelease and ButtonRelease events.
* Call tips by Mark Hammond (plus tiny fix by me.)Guido van Rossum1999-06-022-0/+232
|
* Changes by Mark Hammond: (1) support optional output_sep argument toGuido van Rossum1999-06-021-6/+22
| | | | | the constructor so he can eliminate the sys.ps2 that PythonWin leaves in the source; (2) remove duplicate history items.
* Changes by Mark Hammond to allow using IDLE extensions in PythonWin asGuido van Rossum1999-06-021-9/+10
| | | | well: make three dialog routines instance variables.
* Change by Mark Hammond to allow using IDLE extensions in PythonWin asGuido van Rossum1999-06-021-0/+5
| | | | well: make three dialog routines instance variables.
* Hah! A fix of my own to Tim's code!Guido van Rossum1999-06-011-0/+2
| | | | | | | Unix bindings for <<toggle-tabs>> and <<change-indentwidth>> were missing, and somehow that meant the events were never generated, even though they were in the menu. The new Unix bindings are now the same as the Windows bindings (M-t and M-u).
* Tim Peters again:Guido van Rossum1999-06-013-107/+146
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The new version (attached) is fast enough all the time in every real module I have <whew!>. You can make it slow by, e.g., creating an open list with 5,000 90-character identifiers (+ trailing comma) each on its own line, then adding an item to the end -- but that still consumes less than a second on my P5-166. Response time in real code appears instantaneous. Fixed some bugs. New feature: when hitting ENTER and the cursor is beyond the line's leading indentation, whitespace is removed on both sides of the cursor; before whitespace was removed only on the left; e.g., assuming the cursor is between the comma and the space: def something(arg1, arg2): ^ cursor to the left of here, and hit ENTER arg2): # new line used to end up here arg2): # but now lines up the way you expect New hack: AutoIndent has grown a context_use_ps1 Boolean config option, defaulting to 0 (false) and set to 1 (only) by PyShell. Reason: handling the fancy stuff requires looking backward for a parsing synch point; ps1 lines are the only sensible thing to look for in a shell window, but are a bad thing to look for in a file window (ps1 lines show up in my module docstrings often). PythonWin's shell should set this true too. Persistent problem: strings containing def/class can still screw things up completely. No improvement. Simplest workaround is on the user's head, and consists of inserting e.g. def _(): pass (or any other def/class) after the end of the multiline string that's screwing them up. This is especially irksome because IDLE's syntax coloring is *not* confused, so when this happens the colors don't match the indentation behavior they see.
* Tim Peters again:Guido van Rossum1999-06-011-166/+69
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | [Tim, after adding some bracket smarts to AutoIndent.py] > ... > What it can't possibly do without reparsing large gobs of text is > suggest a reasonable indent level after you've *closed* a bracket > left open on some previous line. > ... The attached can, and actually fast enough to use -- most of the time. The code is tricky beyond belief to achieve that, but it works so far; e.g., return len(string.expandtabs(str[self.stmt_start : ^ indents to caret i], ^ indents to caret self.tabwidth)) + 1 ^ indents to caret It's about as smart as pymode now, wrt both bracket and backslash continuation rules. It does require reparsing large gobs of text, and if it happens to find something that looks like a "def" or "class" or sys.ps1 buried in a multiline string, but didn't suck up enough preceding text to see the start of the string, it's completely hosed. I can't repair that -- it's just too slow to reparse from the start of the file all the time. AutoIndent has grown a new num_context_lines tuple attribute that controls how far to look back, and-- like other params --this could/should be made user-overridable at startup and per-file on the fly.
generated by cgit v0.12 at 2025-02-16 03:40:46 (GMT)