[issue2693] IDLE doesn't work with Tk 8.5

[Martin v. Löwis]

Martin v. Löwis <[EMAIL PROTECTED]> added the comment:

> I wish I could be as cavalier about Tk 8.5.  The last version of Tk 8.4
> just came out and it really shows its age, especially on Mac OS X, and
> those are ~25% of our application's downloads.

Still, why is that a problem to use it for IDLE?

> Since Python 2.6a2 is
> "not suitable for production use", that leaves us with patching 2.5. 

If you need to patch Python 2.5, just go ahead and do it. You don't need
your patch accepted for that. Python 2.5.3 will likely be released
*after* Python 2.6, at which point the "not suitable for production use"
argument will be invalid.

> Backporting, the _tkinter and Tkinter changes, was not hard, but then we
> get "SystemError: Objects/tupleobject.c:89: bad argument to internal
> function" errors with both the 2.5 and the 2.6a2 idlelibs.  Looking at
> the SVN log, it is not clear which patch to tupleobject.c fixed that
> problem (does anyone know?).

I don't think there was any such change to tupleobject.c. If you got
the internal error after changing something, you probably changed it
incorrectly.

> So fixing WidgetRedirector.py to not screw up the string representation
> of tuples is the easiest solution to get idle to work with Tk 8.5. and
> Python 2.5 (you still would want the Tkinter.py changes for other
> reasons).  A slightly more robust solution would be to use Tcl quoting:
> 
> r = '{%s}' % '} {'.join(map(str, r))
> 
> But that has not been important in practice.

This is what I'm concerned about. I cannot accept a patch whose
correctness was just established through testing. In fact, I don't
understand what the proposed change actually does: what are the
values of the variables at the point, what is the expected result,
what is the actual result, and how does the patch change that?

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2700] document PyNumber_ToBase

[Georg Brandl]

Georg Brandl <[EMAIL PROTECTED]> added the comment:

You should mention that if base is none of 2, 8, 10, or 16, the output
looks like "12#555" where 12 is the base.

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2702] pickling of large recursive structures crashes cPickle

[Daniel Darabos]

New submission from Daniel Darabos <[EMAIL PROTECTED]>:

The documentation[1] says:

  Trying to pickle a highly recursive data structure may exceed the
  maximum recursion depth, a RuntimeError will be raised in this
  case. You can carefully raise this limit with sys.setrecursionlimit().

The lightweight pickle module handles this problem correctly (in that it
raises a RuntimeError), but cPickle sometimes raises KeyError instead,
or just silently terminates the interpreter (=crashes). (I have not been
able to pinpoint what it depends on. In the attached example I get
silent termination, but if instead of lists I use sets to describe the
connections, I get the RuntimeError.)

This was mentioned in issue 2480, but that has now been changed to a
feature request to eliminate recursion altogether. That may have a lower
priority, but this crash can be hard to diagnose in a complex
application, and I am not sure if sys.setrecursionlimit() affects
cPickle behavior (I guess not).

[1]: http://docs.python.org/lib/node317.html

--
components: Library (Lib)
files: bugdemo.py
messages: 65876
nosy: alexandre.vassalotti, bkline, cyhawk, jcea, schmir
severity: normal
status: open
title: pickling of large recursive structures crashes cPickle
type: crash
versions: Python 2.5
Added file: http://bugs.python.org/file10119/bugdemo.py

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2480] eliminate recursion in pickling

[Daniel Darabos]

Daniel Darabos <[EMAIL PROTECTED]> added the comment:

I have also described the crash, but it makes sense to handle it
separately. So I have created issue 2702, and changed the title of this
issue.

--
title: pickling of large recursive structures fails -> eliminate recursion in 
pickling

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2702] pickling of large recursive structures crashes cPickle

[Martin v. Löwis]

Martin v. Löwis <[EMAIL PROTECTED]> added the comment:

What operating system and compiler are you using?

--
nosy: +loewis

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2702] pickling of large recursive structures crashes cPickle

[Daniel Darabos]

Daniel Darabos <[EMAIL PROTECTED]> added the comment:

Python 2.5 (r25:51908, Sep 19 2006, 09:52:17) [MSC v.1310 32 bit
(Intel)] on win32

(Windows XP Professional 32 bits)

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2677] Argument rules for callables do not apply when function implementation uses PyArg_ParseTuple

[Georg Brandl]

Georg Brandl <[EMAIL PROTECTED]> added the comment:

Ah sorry, I should really read the OP next time.

Added a note in r62521.

--
resolution:  -> fixed
status: open -> closed

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2703] SimpleXMLRPCDispatcher.__init__ is not python2.4-backward-compatible

[Matthias Klose]

New submission from Matthias Klose <[EMAIL PROTECTED]>:

[forwarded from http://bugs.debian.org/470645]

"SimpleXMLRPCDispatcher.__init__ used to take a single argument
(self) in python2.4 and now it takes three. The two new arguments
need to get default values or else this breaks backwards
compatibility badly."

while SimpleXMLRPCDispatcher is not described as part of the interface,
it is mentioned in the docs. The fix seems to be easy. Ok for trunk and
the branch?

--
components: Library (Lib)
files: dispatcher.diff
keywords: patch, patch
messages: 65883
nosy: doko
severity: normal
status: open
title: SimpleXMLRPCDispatcher.__init__ is not python2.4-backward-compatible
type: behavior
versions: Python 2.5, Python 2.6
Added file: http://bugs.python.org/file10120/dispatcher.diff

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2699] Exception name improperly indented

[Georg Brandl]

Georg Brandl <[EMAIL PROTECTED]> added the comment:

You could add a function to the _testcapi module to invoke PyErr_Display.

--
nosy: +georg.brandl

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2337] Backport oct() and hex() to use __index__

[Georg Brandl]

Georg Brandl <[EMAIL PROTECTED]> added the comment:

I don't assume there are too many people using oct() and hex() with
custom types anyway :)

Since PyNumber_ToBase and the new oct() format octal numbers with "0o"
instead of "0", I still think it's better if you need to import the new
oct() from future_builtins. For hex(), I have no preference.

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2701] csv.reader accepts string instead of file object (duck typing gone bad)

[Skip Montanaro]

Skip Montanaro <[EMAIL PROTECTED]> added the comment:

It's not a mistake.  In fact, the csv unit tests make use of being able
to iterate over strings.  I don't think this feature is going away.

--
nosy: +skip.montanaro

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2693] IDLE doesn't work with Tk 8.5

[Kurt B. Kaiser]

Changes by Kurt B. Kaiser <[EMAIL PROTECTED]>:


--
nosy: +kbk

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2053] IDLE - standardize dialogs

[Kurt B. Kaiser]

Kurt B. Kaiser <[EMAIL PROTECTED]> added the comment:

Please provide a single patch file.

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1180] Option to ignore or substitute ~/.pydistutils.cfg

[Paul Winkler]

Changes by Paul Winkler <[EMAIL PROTECTED]>:


Removed file: http://bugs.python.org/file10105/python_distutils_1180_2.patch

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1180] Option to ignore or substitute ~/.pydistutils.cfg

[Paul Winkler]

Paul Winkler <[EMAIL PROTECTED]> added the comment:

Phillip, thanks, I missed that script_args is always passed by
core.setup(). I'm replacing the patches with two new versions that check
self.script_args instead of sys.argv (and assumes false if for some
reason script_args isn't passed).

We can't check for it in Distribution.parse_command_line() because that
doesn't get called until after loading the config files.

Added file: http://bugs.python.org/file10121/python_distutils_1180.patch

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1180] Option to ignore or substitute ~/.pydistutils.cfg

[Paul Winkler]

Changes by Paul Winkler <[EMAIL PROTECTED]>:


Removed file: http://bugs.python.org/file9763/python_distutils_1180.patch

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1180] Option to ignore or substitute ~/.pydistutils.cfg

[Paul Winkler]

Paul Winkler <[EMAIL PROTECTED]> added the comment:

and here's the revised version of the dependency-injection approach.

Added file: http://bugs.python.org/file10122/python_distutils_1180_2.patch

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2700] document PyNumber_ToBase

[Benjamin Peterson]

Changes by Benjamin Peterson <[EMAIL PROTECTED]>:


--
versions: +Python 3.0
Added file: http://bugs.python.org/file10123/tobase_doc2.patch

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2704] IDLE: Patch to make PyShell behave more like a Terminal interface

[Roger Serwy]

New submission from Roger Serwy <[EMAIL PROTECTED]>:

See attached diff file. Patching PyShell.py Version 1.2.1

PyShell ignores letter/number key presses when the cursor is not on the
command line. Instead it should redirect any letter/number key presses
to the command line. (Changed ModifiedUndoDelegator)

Also, up/down arrow presses should scroll through history when the
cursor is on the command line. But when the cursor is not on the command
line, the arrow keys should move around the PyShell window. (Added new
bindings with conditional logic)

--
components: IDLE
files: patch_PyShell.py
messages: 65888
nosy: serwy
severity: normal
status: open
title: IDLE: Patch to make PyShell behave more like a Terminal interface
type: behavior
versions: Python 2.5
Added file: http://bugs.python.org/file10124/patch_PyShell.py

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2700] document PyNumber_ToBase

[Georg Brandl]

Georg Brandl <[EMAIL PROTECTED]> added the comment:

Okay, go ahead and commit.

--
assignee: georg.brandl -> benjamin.peterson
resolution:  -> accepted

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2700] document PyNumber_ToBase

[Benjamin Peterson]

Benjamin Peterson <[EMAIL PROTECTED]> added the comment:

Commited in r62535.

--
status: open -> closed

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1180] Option to ignore or substitute ~/.pydistutils.cfg

[Phillip J. Eby]

Phillip J. Eby <[EMAIL PROTECTED]> added the comment:

I much prefer the simpler of the two patches - better to monkeypatch in
the tests than adding complications to the already over-complicated
distutils.dist.  I don't find monkeypatching in tests to be horrible at
all, but if it really bothers you, just create a temporary directory for
HOME to point to, and test a Distribution subclass with an overridden
check_environ. 

By the way, the patch could be simpler if you just made the "if 'HOME'
in os.environ" read "if not self.no_user_cfg and 'HOME' in os.environ",
rather than reworking the entire code region.  On the other hand, if
you'd rather have ultra-clean unit tests, you could split the
functionality of find_config_files() into two methods: one that creates
the candidate list and the other that filters it by existence.

Personally, my vote is to keep the monkeypatching in the tests and make
the barest minimal changes to the Distribution class though.

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2337] Backport oct() and hex() to use __index__

[Benjamin Peterson]

Benjamin Peterson <[EMAIL PROTECTED]> added the comment:

Here's a patch for that. It warns for hex() when __hex__ is used,
otherwise it uses __index__. (This doesn't work for old style classes
because ob_tp->tp_as_number->tp_hex is filled.) Use of oct() just gets a
warning. The __hex__ and __oct__ methods of builtin number objects
should probably be removed.

--
keywords: +patch
Added file: http://bugs.python.org/file10125/oct_and_hex_py3k.patch

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2352] Use of __oct__/__hex__ should raise a Py3K warning

[Benjamin Peterson]

Benjamin Peterson <[EMAIL PROTECTED]> added the comment:

This is being taken care of as #2337.

--
nosy: +benjamin.peterson
resolution:  -> duplicate
status: open -> closed
superseder:  -> Backport oct() and hex() to use __index__

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2705] incompatible change to warnings.showwarning

[Jean-Paul Calderone]

New submission from Jean-Paul Calderone <[EMAIL PROTECTED]>:

In Python 2.5 and earlier, the `showwarning´ function in the `warnings´
module has this signature:

  def showwarning(message, category, filename, lineno, file=None):

In trunk (and presumably what will become Python 2.6), this has become:

  def showwarning(message, category, filename, lineno, file=None,
line=None):

`showwarning´ is documented as a hook which libraries or applications
may override in order to control how warnings are reported.  The
addition of a new parameter to the function and the change to related
code to call it with an argument for that new parameter means that
libraries and applications which replaced it will not work without
modification on Python 2.6.  Instead, a `TypeError´ will be raised when
a warning is emitted.

I suggest restoring the previous signature for `showwarning´ and adding
a new (perhaps preferred) API for showing a warning with the extra
information available.  It may also make sense to emit a deprecation
warning when an overridden old-style `showwarning´ is found.

--
components: Library (Lib)
messages: 65894
nosy: exarkun
severity: normal
status: open
title: incompatible change to warnings.showwarning
type: behavior
versions: Python 2.6

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2705] incompatible change to warnings.showwarning

[Antoine Pitrou]

Antoine Pitrou <[EMAIL PROTECTED]> added the comment:

Well, all you have to do is to change the hook's signature to the new
one and, since the last parameter is optional, it should not cause any
backwards compatibility problems. That is, the new hook should work fine
on Python < 2.6 as well. Am I missing something?

--
nosy: +pitrou

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2705] incompatible change to warnings.showwarning

[Benjamin Peterson]

Benjamin Peterson <[EMAIL PROTECTED]> added the comment:

We should have an entry under "Porting to 2.6" in whatsnew.

--
nosy: +benjamin.peterson

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2699] Exception name improperly indented

[Brett Cannon]

Brett Cannon <[EMAIL PROTECTED]> added the comment:

On Sun, Apr 27, 2008 at 2:34 AM, Georg Brandl <[EMAIL PROTECTED]> wrote:
>
>  Georg Brandl <[EMAIL PROTECTED]> added the comment:
>
>  You could add a function to the _testcapi module to invoke PyErr_Display.
>

That's true and probably the only sane idea.

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2705] incompatible change to warnings.showwarning

[Glyph Lefkowitz]

Glyph Lefkowitz <[EMAIL PROTECTED]> added the comment:

pitrou: You're missing a few steps.  If you are maintaining project X,
which depends on library Y, that adds a showwarning hook for some
reason, you need to:

 * check out a development version of library Y, which you do not
normally maintain
 * change the hook's signature to the new one
 * submit a patch to library Y
 * make a local fork of library Y so that you can verify the rest of
your code under 2.6
 * send out an email to your mailing list explaining that they cannot
run with python 2.6 without this patch (linking to the patch in library Y)
 * write a FAQ entry because 200 people show up asking why it does not
work on python 2.6
 * if library Y's development is slow, do a new release of project X
which includes monkeypatching to allow running project X on 2.6

These steps may be unavoidable if library Y has been unmaintained for a
long enough time, but it would be nice to be able to avoid this with a
single new Python release.

--
nosy: +glyph

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2705] incompatible change to warnings.showwarning

[Antoine Pitrou]

Antoine Pitrou <[EMAIL PROTECTED]> added the comment:

Is it a theoretical case or are you thinking about a specific library Y? 

Also, seeing some things break when a new Python version is released is
not new as you certainly know : see
http://twistedmatrix.com/trac/ticket/1867

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2705] incompatible change to warnings.showwarning

[Brett Cannon]

Brett Cannon <[EMAIL PROTECTED]> added the comment:

I have emailed python-dev to try to decide how to handle this.

--
assignee:  -> brett.cannon
nosy: +brett.cannon
priority:  -> critical

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2705] incompatible change to warnings.showwarning

[Brett Cannon]

Changes by Brett Cannon <[EMAIL PROTECTED]>:


--
priority: critical -> release blocker

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2705] incompatible change to warnings.showwarning

[Jean-Paul Calderone]

Jean-Paul Calderone <[EMAIL PROTECTED]> added the comment:

By the way, I just noticed that Lib/idlelib/PyShell.py includes an
override of `showwarning´ which is defined with the old signature.

I ran idle from trunk and verified that is indeed breaks warning reporting.

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2706] datetime: define division timedelta/timedelta

[webograph]

New submission from webograph <[EMAIL PROTECTED]>:

i suggest that division be defined for timedelta1/timedelta2, in that
sense that it gives how many times timedelta2 fits in timedelta1 (ie the
usual meaning of division), using integer arithmetics for floor division
(//) and returning float for truediv (/ after `from __future__ import
division`)

use case


aside from the obvious how-many-times-does-a-fit-into-b, this solves the
issue of having individual methods for conversion to a number of
seconds, hours, days or nanocenturies (as described in #1673409).
example:

from datetime import timedelta
duration = timedelta(hours=1.5, seconds=20)
print "Until the time is up, you can listen to 'We will rock you' %d
times."%(duration//timedelta(minutes=5, seconds=3))
import time
time.sleep(duration/timedelta(seconds=1))


history
---

this issue follows a discussion on python-list, re-initiated by [1].

there have previously been similar feature requests on datetime, most of
which have been rejected due to ambiguities (e.g. [2]), conflicts with
time_t or issues with time zones.

the only issue i've seen that can be relevant here is the
integer-vs-float discussion, which is here handled by floordiv (//) and
truediv.

patch
-

i've written a patch against svn trunk revision 62520.

it uses function pointers to reduce code duplication; in case this
inappropriate here, i also have a pointerless version.

i familiar with c but not experienced, especially with the python ways
of writing c. most of the code is just adapted from other functions in
the same files, so it is probably, but should nevertheless checked with
special care.

i've also added test, but am not sure what has to be tested and what not.


compatibility
-

only cases in which division would fail without the patch are changed.
this will be a problem if (and only if) someone divides unknown objects
and waits for TypeError to be raised.
such behavior is probably rare.


[1] ,
http://mail.python.org/pipermail/python-list/2008-April/488406.html
[2] http://mail.python.org/pipermail/python-dev/2002-March/020604.html

--
components: Library (Lib)
files: datetime_datetime_division.patch
keywords: patch
messages: 65902
nosy: webograph
severity: normal
status: open
title: datetime: define division timedelta/timedelta
type: feature request
Added file: http://bugs.python.org/file10126/datetime_datetime_division.patch

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1196903] smarter behaviour for home key in IDLE

[Kurt B. Kaiser]

Kurt B. Kaiser <[EMAIL PROTECTED]> added the comment:

The toggling is useful when ending a def. If other IDEs
have this binding, I can't see a problem.  I've been running the
patch for awhile now, and notice that Ctrl-A also has this
new action now. It seems useful, let's give it a try.

r62546

--
resolution:  -> accepted
status: open -> closed

_
Tracker <[EMAIL PROTECTED]>

_
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2062] IDLE - autocompletion logic optimization

[Kurt B. Kaiser]

Kurt B. Kaiser <[EMAIL PROTECTED]> added the comment:

r62548

--
resolution:  -> accepted
status: open -> closed

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2061] IDLE - autocompletion to support alternate path separators

[Kurt B. Kaiser]

Kurt B. Kaiser <[EMAIL PROTECTED]> added the comment:

r62549

--
resolution:  -> accepted
status: open -> closed

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2663] shutil.copytree glob-style filtering [patch]

[Tarek Ziadé]

Tarek Ziadé <[EMAIL PROTECTED]> added the comment:

Agreed, rmtree should have it as well. I'll add that in the patch as well,

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2663] shutil.copytree glob-style filtering [patch]

[Tarek Ziadé]

Tarek Ziadé <[EMAIL PROTECTED]> added the comment:

while working on the patch to add the same feature in rmtree, I realized
this is a non sense since the root folder itself is removed at the end
of the function when all its content is removed.

So, unless we change this behavior, which I doubt it is a good idea, it
won't be possible.

Maybe another API could be added in shutil, in order to do any kind of
treatment in a tree, like removing files, or whatever, and without
copying it like copytree does.

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2663] shutil.copytree glob-style filtering [patch]

[Tarek Ziadé]

Tarek Ziadé <[EMAIL PROTECTED]> added the comment:

I have thaught of various ways to write this new API for the deletion
use case, but I think nothing makes it easier and shorter than a simple
os.walk call.

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2663] shutil.copytree glob-style filtering [patch]

[Tarek Ziadé]

Tarek Ziadé <[EMAIL PROTECTED]> added the comment:

This patch includes the documentation for shutils.rst as well. (I
removed the older patches)

Added file: http://bugs.python.org/file10127/shutil.copytree.patch

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2663] shutil.copytree glob-style filtering [patch]

[Tarek Ziadé]

Changes by Tarek Ziadé <[EMAIL PROTECTED]>:


Removed file: http://bugs.python.org/file10066/shutil.copytree.filtering.patch

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2663] shutil.copytree glob-style filtering [patch]

[Tarek Ziadé]

Changes by Tarek Ziadé <[EMAIL PROTECTED]>:


Removed file: http://bugs.python.org/file10073/shutil.copytree.filtering.patch

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2699] Exception name improperly indented

[Brett Cannon]

Brett Cannon <[EMAIL PROTECTED]> added the comment:

Fix in revision 62555.

--
resolution:  -> fixed
status: open -> closed

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2707] Tiny fix for os.walk docstring

[Yinon Ehrlich]

New submission from Yinon Ehrlich <[EMAIL PROTECTED]>:

os.walk.__doc__ has the following example-line (os.py, line 271):
  for root, dirs, files in walk('python/Lib/email'):

it should be os.walk

--
components: Library (Lib)
messages: 65911
nosy: Yinon
severity: normal
status: open
title: Tiny fix for os.walk docstring
versions: Python 2.6

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com