Re: [Python-Dev] avoiding accidental shadowing of top-level libraries by the main module

2010-07-12 Thread Steven D'Aprano
On Tue, 13 Jul 2010 08:05:24 am Nick Coghlan wrote: > On Tue, Jul 13, 2010 at 7:47 AM, Fred Drake wrote: > > On Mon, Jul 12, 2010 at 5:42 PM, Michael Foord > > > > wrote: > >> I'm sure Brett will love this idea, but if it was impossible to > >> reimport the script being executed as __main__ with

[Python-Dev] How to block a module import

2010-07-12 Thread Alexander Belopolsky
I thought that in order to block a module from being imported, one would need to assign None to the corresponding entry in sys.modules. However, it looks like the code in test.support uses 0 instead of None: def _save_and_block_module(name, orig_modules): """Helper function to save and block a

Re: [Python-Dev] [Idle-dev] Removing IDLE from the standard library

2010-07-12 Thread Greg Ewing
Fred Drake wrote: Not when both modules are at the top level; both acceptably provide the same name. The let's-play-with-it script just wasn't *intended* to be a module. I wonder whether this kind of problem would be less prevalent if the tutorials etc. encouraged naming top-level scripts wit

[Python-Dev] python-checkins

2010-07-12 Thread Stephen J. Turnbull
Antoine Pitrou writes: > You don't have to receive e-mail from it. Just take a look at the > archives from time to time after you have done some commits. > In a threaded view, it's easy to spot the few messages which aren't > commit notifications, since they are the only one not at the > top-

Re: [Python-Dev] [Idle-dev] Removing IDLE from the standard library; Scherer Agreement

2010-07-12 Thread Kurt B. Kaiser
On Mon, Jul 12 2010, Bruce Sherwood wrote: > I don't recall that VIDLE has anything to do with running multiple IDLE > copies. Well, I stole the ephemeral port idea from him! > What's in VIDLE is a lot of bug fixes and some improvements. For > example, you can configure it to not require having

Re: [Python-Dev] [Idle-dev] Removing IDLE from the standard library

2010-07-12 Thread Steve Holden
Neil Hodgson wrote: > Kurt B. Kaiser: > >>> The tear off menus are ugly as well as being non-standard on all three >>> major platforms. >> Well, would you discard them? They can (occasionally) be useful. > >Yes, I would replace the menus with ones missing the tear line. > Most of the GUI tool

Re: [Python-Dev] Removing IDLE from the standard library

2010-07-12 Thread Kurt B. Kaiser
On Mon, Jul 12 2010, Terry Reedy wrote: > On 7/12/2010 5:43 PM, "Martin v. Löwis" wrote: >> Am 12.07.2010 23:21, schrieb Terry Reedy: >>> On 7/12/2010 5:46 AM, Kurt B. Kaiser wrote: >>> On Windows, IDLE opens when you right click / edit a .py. Very useful. >>> >>> On my xp machine with 3.1.2,

Re: [Python-Dev] Issue 2986: difflib.SequenceMatcher is partly broken

2010-07-12 Thread Terry Reedy
On 7/11/2010 11:02 PM, Tim Peters wrote: The heuristic lowered the reported match ratio from .96 to .88, which would be bad when one wanted the unaltered value. BTW, it's not clear whether ratio() computes a _useful_ value in the presence of junk, however that may be defined. I agree, which

Re: [Python-Dev] Python equivalents in stdlib Was: Include datetime.py in stdlib or not?

2010-07-12 Thread Alexander Belopolsky
On Thu, Jul 8, 2010 at 9:44 PM, Alexander Belopolsky wrote: .. > and it still requires that '_pickle' is disabled to pass pickle tests. > I have found the problem in test_datetime. Restoring sys.modules has to be done in-place. With this fix, test_datetime looks as follows: = import unitte

Re: [Python-Dev] Removing IDLE from the standard library

2010-07-12 Thread Kurt B. Kaiser
On Mon, Jul 12 2010, Terry Reedy wrote: > On 7/12/2010 2:05 AM, "Martin v. Löwis" wrote: >>> What I specifically want right now is Commit Authorization Privilege, >>> especially for IDLE, >> >> Not sure who could grant that, but as far as I can: you have it. > > If I were approved to commit patche

Re: [Python-Dev] Removing IDLE from the standard library

2010-07-12 Thread Terry Reedy
On 7/12/2010 6:50 PM, "Martin v. Löwis" wrote: Am 13.07.2010 00:00, schrieb Terry Reedy: On 7/12/2010 5:43 PM, "Martin v. Löwis" wrote: There should be an "Edit with IDLE" (sic) context menu item. I agree, and thought about requesting such You misunderstand. To the contrary. You misunde

Re: [Python-Dev] [Idle-dev] Removing IDLE from the standard library

2010-07-12 Thread Kurt B. Kaiser
On Mon, Jul 12 2010, Steve Holden wrote: > I agree, the tear-off menus are an anachronism. OK, thanks for the input. I use them rarely, myself. > I'd also like a pony in the form of easily-changeable sets of > keystroke mappings. I have never found Alt-P and its cousins either > memorable or c

Re: [Python-Dev] Removing IDLE from the standard library

2010-07-12 Thread Terry Reedy
On 7/12/2010 10:49 PM, Kurt B. Kaiser wrote: I've not had experience with patches from Terry. I don't think there are any in IDLE, at least not acknowledged in NEWS. You posts in the last day have told me a lot more about you. Let me introduce myself to you in turn. I have been involved wi

Re: [Python-Dev] Removing IDLE from the standard library

2010-07-12 Thread Monte Milanuk
On 7/11/10 7:31 AM, Tal Einat wrote: However, I still think IDLE is not currently in a state that it should be suggested for use by beginners. Being one of those beginners... here's my $0.02 worth. IDLE being instantly available on pretty much anything I care to try my hand at python on... my

Re: [Python-Dev] [Idle-dev] Removing IDLE from the standard library

2010-07-12 Thread Fred Drake
I wrote: > Indeed!  And I'd be quite content with such a solution, since I > consider scripts and modules to be distinct. On Mon, Jul 12, 2010 at 5:59 PM, Antoine Pitrou wrote: > Except that modules can often be executed as scripts... Rest assured, I'm well aware of the history, and don't seriou

Re: [Python-Dev] [Idle-dev] Removing IDLE from the standard library

2010-07-12 Thread Martin v. Löwis
Am 13.07.2010 00:48, schrieb Eric Smith: > On 7/12/2010 6:04 PM, Michael Foord wrote: >> Given how high traffic python-checkins is I don't consider that a >> reasonable place to send follow-up and nor do I consider it the >> responsibility of committers to monitor it. As you said earlier this >> *i

<    1   2