[issue10974] IDLE 3.2 not loading on double-click in Finder, OSX 10.6

[Ned Deily]

Changes by Ned Deily :


--
Removed message: http://bugs.python.org/msg126820

___
Python tracker 

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

[issue10974] IDLE 3.2 not loading on double-click in Finder, OSX 10.6

[Ned Deily]

Ned Deily  added the comment:

>From the traceback, IDLE is crashing on a decode error when trying to process 
>the list of recently used files which is used to populate its recent files 
>menu.  That list of files is saved in ~/.idlerc/recent-file.lst so an easy 
>workaround is to delete the file before launching IDLE.app.  Most likely, the 
>list of files contains at least one path name with a non-ASCII character.  
>IDLE appears to be dependent here on locale LANG settings.  When launched by 
>double-clicking, like all Mac GUI apps IDLE.app does not inherited environment 
>variables set in shell profiles, as in a terminal session.  The problem can be 
>easily reproduced with bin/idle which is started from a shell environment:

$ echo $LANG
en_US.UTF-8
$ echo "/Users/nad/Documents/test_ä.py" > ~/.idlerc/recent-files.lst
$ /usr/local/bin/idle3.2
# with UTF-8 locale, idle starts normally with the umlauted file name in the 
recent files menu
$ unset LANG
$ /usr/local/bin/idle3.2
Traceback (most recent call last):
  File "/usr/local/bin/idle3.2", line 5, in 
main()
  File 
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/idlelib/PyShell.py",
 line 1388, in main
shell = flist.open_shell()
  File 
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/idlelib/PyShell.py",
 line 277, in open_shell
self.pyshell = PyShell(self)
  File 
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/idlelib/PyShell.py",
 line 813, in __init__
OutputWindow.__init__(self, flist, None, None)
  File 
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/idlelib/OutputWindow.py",
 line 16, in __init__
EditorWindow.__init__(self, *args)
  File 
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/idlelib/EditorWindow.py",
 line 267, in __init__
self.update_recent_files_list()
  File 
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/idlelib/EditorWindow.py",
 line 777, in update_recent_files_list
rf_list = rf_list_file.readlines()
  File 
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/encodings/ascii.py",
 line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 26: 
ordinal not in range(128)

A similar exception occurs (without a crash) when saving a file to a non-ASCII 
file name and LANG is not properly set:

Exception in Tkinter callback
Traceback (most recent call last):
  File 
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/tkinter/__init__.py",
 line 1399, in __call__
return self.func(*args)
  File 
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/idlelib/MultiCall.py",
 line 166, in handler
r = l[i](event)
  File 
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/idlelib/IOBinding.py",
 line 328, in save
self.save_as(event)
  File 
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/idlelib/IOBinding.py",
 line 350, in save_as
self.updaterecentfileslist(filename)
  File 
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/idlelib/IOBinding.py",
 line 515, in updaterecentfileslist
self.editwin.update_recent_files_list(filename)
  File 
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/idlelib/EditorWindow.py",
 line 795, in update_recent_files_list
rf_file.writelines(rf_list)
UnicodeEncodeError: 'ascii' codec can't encode character '\xe4' in position 16: 
ordinal not in range(128)

--

___
Python tracker 

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

[issue10974] IDLE 3.2 not loading on double-click in Finder, OSX 10.6

[Ned Deily]

Ned Deily  added the comment:

>From the traceback, IDLE is crashing on a decode error when trying to process 
>the list of recently used files which is used to populate its recent files 
>menu.  That list of files is saved in ~/.idlerc/recent-file.lst so an easy 
>workaround is to delete the file before launching IDLE.app.  IDLE appears to 
>be dependent on locale LANG settings.  When launched by double-clicking, like 
>all Mac GUI apps IDLE.app does not inherited environment variables set in 
>shell profiles, as in a terminal session.  The problem can be easily 
>reproduced with bin/idle which is started from a shell environment:

$ echo $LANG
en_US.UTF-8
$ echo "/Users/nad/Documents/test_ä.py" > ~/.idlerc/recent-files.lst
nad@fimt:~$ /usr/local/bin/idle3.2
# idle starts normally with the umlauted file name in the recent files menu
$ unset LANG
$ /usr/local/bin/idle3.2
Traceback (most recent call last):
  File "/usr/local/bin/idle3.2", line 5, in 
main()
  File 
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/idlelib/PyShell.py",
 line 1388, in main
shell = flist.open_shell()
  File 
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/idlelib/PyShell.py",
 line 277, in open_shell
self.pyshell = PyShell(self)
  File 
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/idlelib/PyShell.py",
 line 813, in __init__
OutputWindow.__init__(self, flist, None, None)
  File 
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/idlelib/OutputWindow.py",
 line 16, in __init__
EditorWindow.__init__(self, *args)
  File 
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/idlelib/EditorWindow.py",
 line 267, in __init__
self.update_recent_files_list()
  File 
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/idlelib/EditorWindow.py",
 line 777, in update_recent_files_list
rf_list = rf_list_file.readlines()
  File 
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/encodings/ascii.py",
 line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 26: 
ordinal not in range(128)

A similar exception occurs (without a crash) when saving a file to a non-ASCII 
file name and LANG is not properly set:

Exception in Tkinter callback
Traceback (most recent call last):
  File 
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/tkinter/__init__.py",
 line 1399, in __call__
return self.func(*args)
  File 
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/idlelib/MultiCall.py",
 line 166, in handler
r = l[i](event)
  File 
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/idlelib/IOBinding.py",
 line 328, in save
self.save_as(event)
  File 
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/idlelib/IOBinding.py",
 line 350, in save_as
self.updaterecentfileslist(filename)
  File 
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/idlelib/IOBinding.py",
 line 515, in updaterecentfileslist
self.editwin.update_recent_files_list(filename)
  File 
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/idlelib/EditorWindow.py",
 line 795, in update_recent_files_list
rf_file.writelines(rf_list)
UnicodeEncodeError: 'ascii' codec can't encode character '\xe4' in position 16: 
ordinal not in range(128)

--
assignee:  -> ned.deily
nosy: +ned.deily
priority: normal -> high
stage:  -> needs patch
versions: +Python 3.1

___
Python tracker 

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

[issue10911] cgi: add more tests

[Pierre Quentel]

Pierre Quentel  added the comment:

Hi,

I have written more tests, but also propose changes to cgi.py : 
- rewrite the parse_qs() and parse_multipart() functions so that they use 
FieldStorage methods instead of duplicating them
- add a function set_stdout_encoding(encoding), using the IOMix class proposed 
by Glen Linderman in issue #4953

Should I post the new version of test_cgi.py here and open another issue for 
the other proposed changes to cgi.py, or use this issue to discuss both ?

--
nosy: +quentel

___
Python tracker 

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

[issue10967] move regrtest over to using more unittest infrastructure

[Raymond Hettinger]

Raymond Hettinger  added the comment:

Wouldn't the time be better spent factoring the test suite or improving 
coverage?  I'm not sure how simply rearranging the tests makes us better-off.

--
nosy: +rhettinger

___
Python tracker 

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

[issue10979] setUpClass exception causes explosion with "-b"

[R. David Murray]

Changes by R. David Murray :


--
nosy: +michael.foord
type: crash -> behavior

___
Python tracker 

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

[issue4216] subprocess.Popen hangs at communicate() when child exits

[Ross Lagerwall]

Ross Lagerwall  added the comment:

Yes I think subprocess is working correctly.

Since this feature request is 2 years old now without any interest, I think it 
should be closed. If the functionality is needed, it can always be programmed 
by the user when needed.

--
nosy: +rosslagerwall

___
Python tracker 

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

[issue10979] setUpClass exception causes explosion with "-b"

[Brandon Craig Rhodes]

New submission from Brandon Craig Rhodes :

Normally, unittest cleanly reports an exception in a setUpClass method. But if 
I place the attached test in a directory by itself and then run "python -m 
unittest discover -b" from inside of the same directory, then instead of being 
shown the setUpClass exception I am instead shown a long traceback because 
unittest seems to think that it has put a stringIO in place of sys.stdout but a 
file is there instead.

--
components: Library (Lib)
files: test_example.py
messages: 126816
nosy: brandon-rhodes
priority: normal
severity: normal
status: open
title: setUpClass exception causes explosion with "-b"
type: crash
versions: Python 2.7
Added file: http://bugs.python.org/file20484/test_example.py

___
Python tracker 

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

[issue10909] thread hang, possibly related to print

[Terry J. Reedy]

Terry J. Reedy  added the comment:

I ran the 2.7 file (on 2.7) and after several minutes, threadA stopped 
printing, but no error message.

Antoine, could improvement from 2.7 to 3.2 have anything to new with the new 
implementation of the Global Interpreter Lock?

Scott, if you can do your project with 3.2, I strongly recommend it. Even with 
2.7, one can run files outside of IDLE even though you edit with IDLE. You just 
give up the F5 convenience. Or, I believe there are other editors without a 
shell which do so directly. Or, you could write a dp() (debug print) function 
that writes to a scrolled window in your toplevel app window (where running 
numbers appear now.

--
nosy: +pitrou

___
Python tracker 

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

[issue10967] move regrtest over to using more unittest infrastructure

[Ezio Melotti]

Changes by Ezio Melotti :


--
keywords: +gsoc
nosy: +ezio.melotti

___
Python tracker 

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

[issue10970] "string".encode('base64') is not the same as base64.b64encode("string")

[Mahmoud Abdelkader]

Mahmoud Abdelkader  added the comment:

Thanks for the clarification Terry. This is indeed not a bug. For reference, 
the pieces of code I pasted line-wrapped after the 76th character, which was my 
main source of confusion.

After reading RFC3548, I am now informed that the behavior of string.encode is 
the correct and expected result, as the documentation per 7.8.3 state that it's 
MIME 64.

--

___
Python tracker 

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

[issue10957] Python developer FAQ grammar error

[Brett Cannon]

Brett Cannon  added the comment:

That entire portion of the FAQ has been removed as it was redundant compared to 
other parts of the devguide.

Closing as out of date.

--
resolution:  -> out of date
status: open -> closed

___
Python tracker 

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

[issue10954] No warning for csv.writer API change

[R. David Murray]

R. David Murray  added the comment:

Newline='' is indeed needed. It preserves the newlines so that the csv module 
can correctly parse them according to the weird csv quoting roles.  And for 
output, the fact that it isn't documented there is a an issue that was only 
noticed recently.

--
nosy: +r.david.murray

___
Python tracker 

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

[issue10970] "string".encode('base64') is not the same as base64.b64encode("string")

[Terry J. Reedy]

Terry J. Reedy  added the comment:

Questions should generally be asked on python-list or its mirrors.

The docs do not say that the result should be exactly, byte-for-byte, the same. 
base64 module refers to RFC 3548. Both our doc and the RFC describe variations. 
The base64 codec does 'Mime base64' (7.8.3. Standard Encodings). The RFC says 
things like "MIME does not define "base 64" per se, but rather a "base 64 
Content-Transfer-Encoding" for use within MIME." It also mentions 'line-break 
issues'.

You neglected to identify and post what the difference is ;-).

>>> import base64
>>> s='I am a string'
>>> s.encode('base64')
'SSBhbSBhIHN0cmluZw==\n'
>>> base64.b64encode(s)
'SSBhbSBhIHN0cmluZw=='
>>> s.encode('base64')== base64.b64encode(s)+'\n'
True

The addition of '\n' for the Mime version looks to be intentional, and will not 
be changed for 2.7.

(2.5 and 2.6 only get security patches now.)

--
nosy: +terry.reedy
resolution:  -> invalid
status: open -> closed
versions:  -Python 2.5, Python 2.6

___
Python tracker 

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

[issue10954] No warning for csv.writer API change

[Terry J. Reedy]

Terry J. Reedy  added the comment:

Changing csv api is a feature request that could only happen in 3.3.

--
nosy: +skip.montanaro
type: behavior -> feature request
versions: +Python 3.3 -Python 2.7, Python 3.1, Python 3.2

___
Python tracker 

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

[issue10954] No warning for csv.writer API change

[Terry J. Reedy]

Terry J. Reedy  added the comment:

Failing when passed a bytesIO object seems reasonable.
I question the bit about newlines though. The doc does not specify that 
newlines='' is needed on output. While is says it is needed for input, why? Why 
is a mix of '\n', '\r\n', and '\r' better than always '\n'?
It is not clear to me that the information is available to csv anyway.

--
nosy: +terry.reedy
versions:  -Python 2.6

___
Python tracker 

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

[issue10968] threading.Timer should be a class so that it can be derived

[R. David Murray]

R. David Murray  added the comment:

See also issue 5831.  That should probably be closed as a dup of this since 
this has an explanation.

--
nosy: +r.david.murray

___
Python tracker 

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

[issue5863] bz2.BZ2File should accept other file-like objects.

[Nadeem Vawda]

Nadeem Vawda  added the comment:

I have been working on a patch for this issue. I've implemented everything 
except for readline(), readlines() and the iterator protocol.

In the existing implementation, the reading methods seem to interact weirdly - 
iternext() uses a readahead buffer, while none of the other methods do. Does 
anyone know if there's a reason for this? I was planning on having all the 
reading methods use a common buffer, which should allow free mixing of read 
methods and iteration.

Looking at issue8397, I'm guessing it would be fine, but I wanted to 
double-check in case there's a quirk of the iteration protocol that I've 
overlooked, or something like that.

--

___
Python tracker 

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

[issue10957] Python developer FAQ grammar error

[Terry J. Reedy]

Terry J. Reedy  added the comment:

In general, the website is separate from Python code and documentation and 
website issues should be sent to webmas...@python.org, not here, as code/doc 
committers cannot change web pages.

However, this particular page (dev/faq) has being pulled into the (hg) 
repository as part of expanded docs for developers. It is possible that 'to 
faster compilation time' has already been corrected. Brett? (and will the web 
page go away or be replaced?)

--
nosy: +brett.cannon, terry.reedy

___
Python tracker 

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

[issue10973] 'ñ' not working with IDLE 3.2rc1 - OSX 10.6.6

[Nestor Aguilera]

Nestor Aguilera  added the comment:

On 21 Jan 2011, at 21:12, Martin v. Löwis wrote:

> 
> Martin v. Löwis  added the comment:
> 
>> I see your point. The problem is that IDLE is somewhat included with
>> Python (so in a sense it is not "3rd party"), and seems like a good
>> tool for learning Python: my concern is similar to that in message
>> 126276 .
> 
> Unfortunately, there is little we can do about this (IIUC). One option
> would be to include a fixed Tk version, but there is none to include
> (IIUC). The only real solution to "fix" both the reported problem and
> the problem of msg126276 would be to stop including IDLE with the MacOS
> distributions, and asking users who want to use IDLE to switch to
> Linux or Windows.

(:-)

I hope you will not consider to also stop including tkinter!

Nestor

--

___
Python tracker 

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

[issue10957] Python developer FAQ grammar error

[Jerry Seutter]

Changes by Jerry Seutter :


--
title: Python FAQ grammar error -> Python developer FAQ grammar error

___
Python tracker 

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

[issue10978] Add optional argument to Semaphore.release for releasing multiple threads

[Raymond Hettinger]

New submission from Raymond Hettinger :

Call sem.release(5) would have the same effect as:

with lock:
for i in range(5):
 sem.release()

The use case is when a single semaphore is holding up multiple threads and 
needs to release them all.  According to "The Little Book of Semaphores 
", this is a common design pattern.

Basic patch attached.  If the proposal meets with acceptance, will add tests 
and a doc update.

--
components: Library (Lib)
files: sem.diff
keywords: patch
messages: 126804
nosy: rhettinger
priority: normal
severity: normal
status: open
title: Add optional argument to Semaphore.release for releasing multiple threads
type: behavior
versions: Python 3.3
Added file: http://bugs.python.org/file20483/sem.diff

___
Python tracker 

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

[issue10973] 'ñ' not working with IDLE 3.2rc1 - OSX 10.6.6

[Martin v . Löwis]

Martin v. Löwis  added the comment:

> I see your point. The problem is that IDLE is somewhat included with
> Python (so in a sense it is not "3rd party"), and seems like a good
> tool for learning Python: my concern is similar to that in message
> 126276 .

Unfortunately, there is little we can do about this (IIUC). One option
would be to include a fixed Tk version, but there is none to include
(IIUC). The only real solution to "fix" both the reported problem and
the problem of msg126276 would be to stop including IDLE with the MacOS
distributions, and asking users who want to use IDLE to switch to
Linux or Windows.

--

___
Python tracker 

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

[issue10957] Python FAQ grammar error

[Jerry Seutter]

Jerry Seutter  added the comment:

I agree with what Rafe said.

--

___
Python tracker 

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

[issue10973] 'ñ' not working with IDLE 3.2rc1 - OSX 10.6.6

[Nestor Aguilera]

Nestor Aguilera  added the comment:

On 21 Jan 2011, at 20:39, Martin v. Löwis wrote:

> Martin v. Löwis  added the comment:
> 
> As this clearly seems to be a Tk bug, I suggest to close this report as 
> "won't fix - 3rd party".

I see your point. The problem is that IDLE is somewhat included with Python (so 
in a sense it is not "3rd party"), and seems like a good tool for learning 
Python: my concern is similar to that in message 126276 
.

All the best,

Nestor

--

___
Python tracker 

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

[issue10977] Concrete object C API needs abstract path for subclasses of builtin types

[Raymond Hettinger]

New submission from Raymond Hettinger :

Currently, the concrete object C API bypasses any methods defined on subclasses 
of builtin types.  

It has long been accepted that subclasses of builtin types need to override 
many methods rather than just a few because the type itself was implemented 
with direct internal calls.  This work-around requires extra work but still 
makes it possible to create a consistent subclass (a case-insensitive 
dictionary for example).

However, there is another problem with this workaround.  Any subclassed builtin 
may still be bypassed by other functions and methods using the concrete C API.

For example, the OrderedDict class overrides enough dict methods to make itself 
internally consistent and fully usable by all pure python code.  However, any 
builtin or extension using PyDict_SetItem() or PyDict_DelItem() will update the 
OrderedDict's internal unordered dict
and bypass all the logic keeping dict ordering invariants intact.  Note, this 
problem would still impact OrderedDict even if it were rewritten in C.  The 
concrete calls would directly access the original dict structure and ignore any 
of the logic implemented in the subclass (whether coded in pure python or in C).

Since OrderedDict is written in pure python, the consequence of having its 
invariants violated would result in disorganization, but not in a crash.  
However if OrderedDict were rewritten in C, augmenting the inherited data 
structure with its own extra state, then this problem could result in 
seg-faulting.

Note this is only one example.  Pretty much any subclass of a builtin type that 
adds additional state is vulnerable to a concrete C API that updates only part 
of the state while leaving the extra state information in an inconsistent state.

Another example would be a list subclass that kept extra state tracking the 
number of None objects contained within.  There is no way to implement that 
subclass, either in C or pure python, even if every method were overridden, 
that wouldn't be rendered inconsistent by an external tool using 
PyList_SetItem().

My recommendation is to find all of the mutating methods for the concrete C API 
and add an alternate path for subclasses.  The alternate path should use the 
abstract API.

Pseudo-code for PyList_SetItem():

   if type(obj) is list:
  # proceed as currently implemented
   else:
  # use PyObject_SetItem() adapting the 
  # function parameters and return values if necessary
  # to match the API for PyList_SetItem().
   else:
  raise BadInternalCall('object should be a list')

--
components: Interpreter Core
messages: 126800
nosy: rhettinger
priority: normal
severity: normal
status: open
title: Concrete object C API needs abstract path for subclasses of builtin  
types
type: behavior
versions: Python 3.3

___
Python tracker 

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

[issue10909] thread hang, possibly related to print

[Terry J. Reedy]

Terry J. Reedy  added the comment:

FWIW, I downloaded, edited for 3.2, and ran. 45 minutes later, with counter in 
box near 16000, and output sequence looking about the same as initially, I 
killed with Task Manager (also on winxp). You might try same on your system.

--
Added file: http://bugs.python.org/file20482/e10909.py

___
Python tracker 

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

[issue10943] abitype: Need better support to port C extension modules to the stable C API

[Martin v . Löwis]

Martin v. Löwis  added the comment:

Notice that a boilerplate module is already available: xxlimited.c.

--

___
Python tracker 

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

[issue10973] 'ñ' not working with IDLE 3.2rc1 - OSX 10.6.6

[Martin v . Löwis]

Martin v. Löwis  added the comment:

As this clearly seems to be a Tk bug, I suggest to close this report as "won't 
fix - 3rd party".

--
nosy: +loewis

___
Python tracker 

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

[issue10949] logging.RotatingFileHandler not robust enough

[Vinay Sajip]

Vinay Sajip  added the comment:

Fix checked into py3k, release27-maint, release31-maint (r88139). The 2.6 
branch is closed for changes other than security fixes.

--
assignee:  -> vinay.sajip
resolution:  -> fixed
status: open -> closed

___
Python tracker 

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

[issue10957] Python FAQ grammar error

[Rafe Kettler]

Rafe Kettler  added the comment:

>for a faster compile
Compile isn't a noun; the most grammatically correct sentences would be "for 
faster compilation."

--
nosy: +rafe.kettler

___
Python tracker 

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

[issue10925] Document pure Python version of integer-to-float correctly-rounded conversion

[Terry J. Reedy]

Terry J. Reedy  added the comment:

I see there is already something similar for true division.

I find
+q_max, shift_max = 1 << sig_bits, sys.float_info.max_exp - sig_bits
easier to read as two lines
+q_max = 1 << sig_bits
+shift_max = sys.float_info.max_exp - sig_bits

Not having precedence memorized, I prefer added parens here:
+ ...  (n >> shift) | bool(n & (1 << shift) - 1)

I presume that for normal production testing, you would comment out
+   float = long_to_float

--
nosy: +terry.reedy

___
Python tracker 

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

[issue10961] Pydoc touchups in new browser for 3.2

[Ron Adam]

Ron Adam  added the comment:

George, My apologies to you for the late corrections.  And thanks for doing 
this.

Eric, I replied to your comments on Rietveld.  Thanks for taking a look.

I'll wait until you have a chance to reply and test it, then upload a new patch 
with any needed changes.

Ron

--

___
Python tracker 

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

[issue10909] thread hang, possibly related to print

[Scott M]

Scott M  added the comment:

It hasn't failed yet when run "straight".

Here's the issue, though. I'm going to be introducing Python as the scripting 
language of choice, to a bunch of people who are less than fluent in 
programming. Because debugging is not an obvious concept to them, they are 
going to hunt for problems by sticking in print statements everywhere, and the 
environment is inherently multithreaded, so it's hard for me to imagine they 
won't experience this bug. I hit it in my very first multithreaded experiment. 
And I can't possibly ask them not to use IDLE - without syntax coloring and a 
friendly editor to show them which line is wrong, they will never get off the 
ground.

It would be tolerable if there was at least a traceback, but if threads vanish 
silently, they will not realize it's a environment problem; they will either 
assume that they did something inexplicably wrong and that "scripting is too 
hard", or it will get around that I provided a "broken" solution.

So even if it's "just the IDE", it's still life and death for this project. 
"Won't fix" probably means I have to abandon Python.

--

___
Python tracker 

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

[issue10922] Unexpected exception when calling function_proxy.__class__.__call__(function_proxy)

[Terry J. Reedy]

Changes by Terry J. Reedy :


--
versions:  -Python 2.5, Python 2.6

___
Python tracker 

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

[issue10614] ZipFile and CP932 encoding

[STINNER Victor]

STINNER Victor  added the comment:

In #10972, I propose to add an option for the filename encoding to UTF-8. But I 
would like to force UTF-8 to create a ZIP file, it doesn't concern the 
decompression of a ZIP file.

Proposal of a specification to fix both issues at the same time.


"default_encoding" name is confusing because it doesn't specify if it is the 
encoding of (text?) file content or the encoding the filename. Why not simply 
"filename_encoding"?

The option can be added in multiple places:
 - argument to ZipFile constructor: this is needed to decompress
 - argument to ZipFile.write() and ZipInfo, because they are 3 different 
manners to add files

ZipFile.filename_encoding (and ZipInfo.filename_encoding) will be None by 
default: in this case, use the current algorithm (try cp437 or use UTF-8). 
Otherwise, use the encoding. If the encoding is UTF-8: set unicode flag.

Examples:
---
zipfile.ZipFile("non-ascii-cp932.zip", filename_encoding="cp932")

f = zipfile.ZipFile("test.zip", "w")
f.write(filename, filename_encoding="UTF-8")
info = ZipInfo(filename, filename_encoding="UTF-8")
f.writestr(info, b'data')
---

Don't add filename_encoding argument to ZipFile.writestr(), because it may 
conflict if a ZipInfo is passed and ZipInfo.filename_encoding and 
filename_encoding are different.

--

___
Python tracker 

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

[issue10909] thread hang, possibly related to print

[Terry J. Reedy]

Terry J. Reedy  added the comment:

What happens if you run your program without IDLE? 
(either with right-click and run or run from Command Prompt window?) 

I would not be surprised if your problems go away. IDLE runs a saved file in a 
separate pythonw process. Printing (or writing) to stdout requires sending 
output back to the IDLE process. I can imagine that doing that from 2 
subthreads could lead to conflicts.

If the problems do go away, then we should probably close this as won't fix. 
IDLE is a development environment, not a production running environment

--
nosy: +terry.reedy

___
Python tracker 

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

[issue10960] os.stat() does not mention that it follow symlinks by default

[R. David Murray]

R. David Murray  added the comment:

I almost closed this as invalid, since the name is, after all 'os.stat' and the 
docs clearly say that it calls the 'stat' system call.  However, I see that our 
docs do not contain the more explicit language used by the 'stat' system call 
docs: "stats the file pointed to by path".  Although even that isn't crystal 
clear unless you also read the definition of 'lstat' right below it.  If you 
read our docs for lstat it does become clear even as things stand, but lstat 
isn't right below stat in our docs.

So on reflection I think the docs could use improvement in this area.

--
nosy: +r.david.murray
stage:  -> needs patch

___
Python tracker 

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

[issue10949] logging.RotatingFileHandler not robust enough

[R. David Murray]

Changes by R. David Murray :


--
nosy: +vinay.sajip

___
Python tracker 

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

[issue10943] abitype: Need better support to port C extension modules to the stable C API

[R. David Murray]

Changes by R. David Murray :


--
nosy: +loewis

___
Python tracker 

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

[issue10976] json.loads() throws TypeError on bytes object

[Antoine Pitrou]

Antoine Pitrou  added the comment:

I've committed a doc fix in r88137.

--

___
Python tracker 

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

[issue10966] eliminate use of ImportError implicitly representing TestSkipped

[R. David Murray]

R. David Murray  added the comment:

Ah, I see what you are getting at now.  I was confused by the "raise SkipTest 
directly" part, since the test suite currently does raise SkipTest instead of 
ImportError.  So the key change here is to make the test show as a *failure* on 
those platforms where it is currently reported as an unexpected skip.  We can 
then eliminate the whole "these skips are expected" bit from regrtest.  That 
would be a very nice cleanup.

I'm going to mark this as easy, since it is basically a mechanical 
transformation from the expected skip list in regrtest to calls to a fairly 
simple new test.support function, and then ripping the obsolete code out of 
regrtest.  Tedious, but doable in a day.

--
keywords: +easy

___
Python tracker 

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

[issue10042] total_ordering stack overflow

[Éric Araujo]

Changes by Éric Araujo :


--
status: closed -> open
versions: +Python 2.7

___
Python tracker 

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

[issue10976] json.loads() throws TypeError on bytes object

[Éric Araujo]

Éric Araujo  added the comment:

Georg: Is it still time to deprecate the encoding parameter in 3.2?

--
nosy: +eric.araujo, georg.brandl

___
Python tracker 

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

[issue10976] json.loads() throws TypeError on bytes object

[Antoine Pitrou]

Antoine Pitrou  added the comment:

Indeed, the documentation (and function docstring) needs fixing instead. It's a 
pity we didn't remove the useless `encoding` parameter.

--
assignee:  -> docs@python
components: +Documentation -Library (Lib)
nosy: +docs@python

___
Python tracker 

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

[issue3831] Multiprocessing: Expose underlying pipe in queues

[Forest Wilkinson]

Changes by Forest Wilkinson :


--
nosy: +forest

___
Python tracker 

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

[issue10967] move regrtest over to using more unittest infrastructure

[Brett Cannon]

Brett Cannon  added the comment:

Yes, I somewhat view this as an index issue. I don't expect a wholesale move 
but a more step-by-step move.

--

___
Python tracker 

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

[issue10966] eliminate use of ImportError implicitly representing TestSkipped

[Brett Cannon]

Brett Cannon  added the comment:

Yes. So for _winreg (if we even have tests) it would be skipped on all OSs 
other than Windows, on on Windows it would be a test failure if it didn't work 
as it is expected to exist.

--

___
Python tracker 

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

[issue10976] json.loads() throws TypeError on bytes object

[R. David Murray]

R. David Murray  added the comment:

Hmm.  According to issue 4136, all bytes support was supposed to have been 
removed.

--
nosy: +pitrou, r.david.murray

___
Python tracker 

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

[issue10967] move regrtest over to using more unittest infrastructure

[R. David Murray]

Changes by R. David Murray :


--
Removed message: http://bugs.python.org/msg126780

___
Python tracker 

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

[issue10967] move regrtest over to using more unittest infrastructure

[R. David Murray]

R. David Murray  added the comment:

I think we have already been moving in this direction for quite some time.  
Past policy is to only change things when we are working on that area of code 
anyway.  If someone wants to make some specific proposals to simplify regrtest 
by doing a wholesale move of test code away from a regrtest supported 
infrastructure to a unittest supported infrastructure, I think that's worth 
considering, but I think it should be done bit by bit with specific proposals 
to replace specific regrtest features.

Extending regrtest to support unittest test discovery directly is also a 
worthwhile specific proposal.

Do you intend this issue to be an "index issue" that links to issues with 
specific proposals?

(Note: see also the closely related issue 8273).

--

___
Python tracker 

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

[issue10967] move regrtest over to using more unittest infrastructure

[R. David Murray]

R. David Murray  added the comment:

I think we have already been moving in this director for quite some time.  Past 
policy is to only change things when we are working on that area of code 
anyway.  If someone wants to make some specific proposals to simplify regrtest 
by doing a wholesale move of test code away from a regrtest supported 
infrastructure to a unittest supported infrastructure, I think that's worth 
considering, but I think it should be done bit by bit with specific proposals 
to replace specific regrtest features.

Extending regrtest to support unittest test discovery directly is also a 
worthwhile specific proposal.

Do you intend this issue to be an "index issue" that links to issues with 
specific proposals?

(Note: see also the closely related issue 8273).

--
nosy: +r.david.murray

___
Python tracker 

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

[issue10966] eliminate use of ImportError implicitly representing TestSkipped

[R. David Murray]

R. David Murray  added the comment:

On second reading I see one way it is different: you suggest to move the list 
of expected skips out of regrtest.  So, are you suggesting, essentially, that 
support.import_module be replaced by an optional_import that takes arguments to 
indicate on which platforms the skip is expected?

--

___
Python tracker 

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

[issue10966] eliminate use of ImportError implicitly representing TestSkipped

[R. David Murray]

R. David Murray  added the comment:

How is this different from issue 2409?

--
nosy: +r.david.murray

___
Python tracker 

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

[issue10822] test_getgroups failure under Solaris

[Jesús Cea Avión]

Jesús Cea Avión  added the comment:

Sorry, Firefox insists in cache-ing the tracker, with bad results.

I beg your pardon.

--
nosy: +rosslagerwall
resolution:  -> fixed
stage: needs patch -> committed/rejected
status: open -> closed

___
Python tracker 

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

[issue10935] wsgiref.handlers.BaseHandler and subclasses of str

[R. David Murray]

R. David Murray  added the comment:

> 4. The explicit-vs-implicit is about the contract defined in the spec (making 
> explicit what, precisely, is required of both parties), not the type test.

Perhaps a clarification in the () spec that 'type str' means "type(s) is 
str" would be in order, then, since this discussion makes it clear that "type 
str" in English can also mean "isinstance(s, str)".

--

___
Python tracker 

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

[issue10822] test_getgroups failure under Solaris

[Jesús Cea Avión]

Jesús Cea Avión  added the comment:

Antoine, can you confirm that the problem is solved, and mark this issue as 
closed/fixed?.

Thanks.

--
nosy:  -rosslagerwall
resolution: fixed -> 
stage: committed/rejected -> needs patch
status: closed -> open

___
Python tracker 

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

[issue10936] Simple CSS fix for left margin at docs.python.org

[Christopher Dunn]

Christopher Dunn  added the comment:

I was just trying to help fix the CSS, and I think I've done that.

If we're reconsidering the behavior of the nav sidebar, then I'd like to point 
out that if you're far down the page, the sidebar is blank to your right. From 
a usability point of view, it's already broken. It was a neat idea, but a ToC 
for the page would serve the purpose better.

My monitor is quite large, and rotated 90 degrees, so it's narrow and tall. A 
web-page can be infinitely long, but its practical width is limited to the 
user's screen, which is different for every user. That's why HTML was designed 
the way it is, with auto-word-wrap.

When you have a bunch of stuff that you want to fit within a window, a sidebar 
makes more sense. For Python docs, I'd vote to drop it altogether, as 
attractive-looking as it is.

But if you really want it, give it its own vertical scrollbar, so that a 
relevant portion is always visible. Then people can talk about dynamic controls.

That's just my opinion. I created this bug because, when I zoon, the sidebar 
consumes most of my screen with no visible text. It's such a huge problem that 
I was afraid someone had already submitted this.

--

___
Python tracker 

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

[issue10948] Trouble with dir_util created dir cache

[Éric Araujo]

Éric Araujo  added the comment:

> So It is better to define what a "public function" is.
That is no easy task.  See #10894 for a general discussion.  For the particular 
case of distutils, there is no distinction between internal helpers that we 
should be free to change and public functions provided to third-party code.  
That’s one of the reasons we had to fork under a new name to have a chance to 
clean things up (i.e. make nearly everything private).

> If new people get involved in distutils development they will need to
> read all the code, line by line and every comment, because the old
> developers decided not to document the inner workings of its functions.
A lot of people have bee learning distutils internals in recent years: Tarek, 
the current maintainer; hackers from Montreal; Google Summer of Code students 
like me.  So it is possible to get involved with distutils, starting with one 
area (network code, or versions and dependencies, or commands, or 
compilers...).  That said, I agree the doc is very lacking, and improving it is 
one of my big goals for distutils2 in Python 3.3.  (I will give priority to 
important user-facing functions and classes over helpers like mkpath, however.)

> Well, I know nothing about this. However, if you tell me that
> distutils2 will replace distutils, I may agree with you and distutils
> just needs to be deprecated. Otherwise, I keep my opinion.
distutils is frozen and only gets bug fixes; distutils2 is a fork where we can 
break compatibility to fix the design and behavior.  More information on 
http://tarekziade.wordpress.com/2010/03/03/the-fate-of-distutils-pycon-summit-packaging-sprint-detailed-report/

I am now closing this issue.  If I have misunderstood your last message and 
you’re not satisfied with that, please reopen.  Thanks again for your report, 
and don’t hesitate to report any bug you may find in the future.

--
resolution:  -> works for me
stage:  -> committed/rejected
status: open -> closed

___
Python tracker 

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

[issue10976] json.loads() throws TypeError on bytes object

[hhas]

New submission from hhas :

json.loads() accepts strings but errors on bytes objects. Documentation and API 
indicate that both should work. Review of json/__init__.py code shows that the 
loads() function's 'encoding' arg is ignored and no decoding takes place before 
the object is passed to JSONDecoder.decode()

Tested on Python 3.1.2 and Python 3.2rc1; fails on both. 

Example:

#

#!/usr/local/bin/python3.2

import json

print(json.loads('123'))
# 123

print(json.loads(b'123'))
# 
/Library/Frameworks/Python.framework/Versions/3.1/lib/python3.1/json/decoder.py:325:
  
#   TypeError: can't use a string pattern on a bytes-like object

print(json.loads(b'123', encoding='utf-8'))
# 
/Library/Frameworks/Python.framework/Versions/3.1/lib/python3.1/json/decoder.py:325:
  
#   TypeError: can't use a string pattern on a bytes-like object

#

Patch attached.

--
components: Library (Lib)
files: json.diff
keywords: patch
messages: 126772
nosy: hhas
priority: normal
severity: normal
status: open
title: json.loads() throws TypeError on bytes object
type: behavior
versions: Python 3.1, Python 3.2
Added file: http://bugs.python.org/file20481/json.diff

___
Python tracker 

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

[issue10968] threading.Timer should be a class so that it can be derived

[Guido van Rossum]

Guido van Rossum  added the comment:

IIRC:

The design started out this way because it predates new-style classes. When 
this was put in one couldn't subclass extension types, and there were 
plans/hopes to replace some of the lock types with platform-specific built-in 
versions on some platforms.

Since it is now possible to write subclassable extension types the Thing/_Thing 
design is no longer needed.

I'm not sure about the _Verbose hacks, if it is deemed not useful I'm fine with 
letting it go.

--

___
Python tracker 

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

[issue10936] Simple CSS fix for left margin at docs.python.org

[Christopher Dunn]

Christopher Dunn  added the comment:

@eric.araujo:

Not a 'pop-up', that you would have to click to close. But something dynamic, 
based on mouse location.

--

___
Python tracker 

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

[issue9723] pipes.quote() needs to be documented

[Éric Araujo]

Changes by Éric Araujo :


--
stage: unit test needed -> needs patch

___
Python tracker 

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

[issue10936] Simple CSS fix for left margin at docs.python.org

[Éric Araujo]

Éric Araujo  added the comment:

Also, laptops and handheld devices have a limited screen size.

-1 on a pop-up, for obvious usability reasons.

--
nosy: +eric.araujo

___
Python tracker 

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

[issue9723] pipes.quote() needs to be documented

[Éric Araujo]

Éric Araujo  added the comment:

Why do you want to move quote from pipes to shlex?  The function is available, 
the issue here is lack of documentation.

--
stage:  -> unit test needed
type: feature request -> 

___
Python tracker 

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

[issue10961] Pydoc touchups in new browser for 3.2

[Éric Araujo]

Éric Araujo  added the comment:

Some comments on http://codereview.appspot.com/4090042

--

___
Python tracker 

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

[issue10975] #10961: Pydoc touchups in new 3.2 Web server (issue4090042)

[Éric Araujo]

Éric Araujo  added the comment:

One day, email from rietveld will go to the right roundup report.

--
resolution:  -> invalid
stage:  -> committed/rejected
status: open -> closed

___
Python tracker 

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

[issue10975] #10961: Pydoc touchups in new 3.2 Web server (issue4090042)

[Éric Araujo]

New submission from Éric Araujo :

Some comments.  Haven’t tested the patch yet.

http://codereview.appspot.com/4090042/diff/1/Lib/pydoc.py
File Lib/pydoc.py (right):

http://codereview.appspot.com/4090042/diff/1/Lib/pydoc.py#newcode2507
Lib/pydoc.py:2507: 
Does this work fine with common Web browsers, including not-most-recent
versions, and various resolutions?  (“fine” being defined as “not worse
than before the patch”)

http://codereview.appspot.com/4090042/diff/1/Lib/pydoc.py#newcode2591
Lib/pydoc.py:2591: return '%s' % (name,
name)
I see no reason for polluting the key value with “.html”

http://codereview.appspot.com/4090042/diff/1/Lib/pydoc.py#newcode2713
Lib/pydoc.py:2713: raise TypeError('unknown content type %r' % ([url,
content_type]))
You can remove the extraneous parens around the list.

http://codereview.appspot.com/4090042/diff/1/Lib/test/test_pydoc.py
File Lib/test/test_pydoc.py (right):

http://codereview.appspot.com/4090042/diff/1/Lib/test/test_pydoc.py#newcode431
Lib/test/test_pydoc.py:431: ("", "PyDoc: Index of Modules"),
I’m not sure “PyDoc” is better than “Python”.  What about “Python Doc”?
Very clear and still short.

http://codereview.appspot.com/4090042/

--
messages: 126765
nosy: eric.araujo
priority: normal
severity: normal
status: open
title: #10961: Pydoc touchups in new 3.2 Web server (issue4090042)

___
Python tracker 

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

[issue10974] IDLE 3.2 not loading on double-click in Finder, OSX 10.6

[Nestor Aguilera]

New submission from Nestor Aguilera :

Here is the report from "Console" (date/time removed):

[0x0-0x1a11a1].org.python.IDLE[5541]Traceback (most recent call last):
[0x0-0x1a11a1].org.python.IDLE[5541]  File "/Applications/Python 
3.2/IDLE.app/Contents/Resources/idlemain.py", line 73, in 
[0x0-0x1a11a1].org.python.IDLE[5541]main()
[0x0-0x1a11a1].org.python.IDLE[5541]  File 
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/idlelib/PyShell.py",
 line 1388, in main
[0x0-0x1a11a1].org.python.IDLE[5541]shell = flist.open_shell()
[0x0-0x1a11a1].org.python.IDLE[5541]  File 
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/idlelib/PyShell.py",
 line 277, in open_shell
[0x0-0x1a11a1].org.python.IDLE[5541]self.pyshell = PyShell(self)
[0x0-0x1a11a1].org.python.IDLE[5541]  File 
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/idlelib/PyShell.py",
 line 813, in __init__
[0x0-0x1a11a1].org.python.IDLE[5541]OutputWindow.__init__(self, flist, 
None, None)
[0x0-0x1a11a1].org.python.IDLE[5541]  File 
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/idlelib/OutputWindow.py",
 line 16, in __init__
[0x0-0x1a11a1].org.python.IDLE[5541]EditorWindow.__init__(self, *args)
[0x0-0x1a11a1].org.python.IDLE[5541]  File 
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/idlelib/EditorWindow.py",
 line 267, in __init__
[0x0-0x1a11a1].org.python.IDLE[5541]self.update_recent_files_list()
[0x0-0x1a11a1].org.python.IDLE[5541]  File 
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/idlelib/EditorWindow.py",
 line 777, in update_recent_files_list
[0x0-0x1a11a1].org.python.IDLE[5541]rf_list = rf_list_file.readlines()
[0x0-0x1a11a1].org.python.IDLE[5541]  File 
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/encodings/ascii.py",
 line 26, in decode
[0x0-0x1a11a1].org.python.IDLE[5541]return codecs.ascii_decode(input, 
self.errors)[0]
[0x0-0x1a11a1].org.python.IDLE[5541]UnicodeDecodeError: 'ascii' codec can't 
decode byte 0xcc in position 55: ordinal not in range(128)
com.apple.launchd.peruser.501[168]  ([0x0-0x1a11a1].org.python.IDLE[5541]) 
Exited with exit code: 1

Thanks,

Néstor Aguilera

--
components: IDLE
messages: 126764
nosy: naguilera
priority: normal
severity: normal
status: open
title: IDLE 3.2 not loading on double-click in Finder, OSX 10.6
type: crash
versions: Python 3.2

___
Python tracker 

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

[issue10968] threading.Timer should be a class so that it can be derived

[Éric Araujo]

Éric Araujo  added the comment:

Adding Guido, who checked the module in, to nosy.

Guido: Could you tell us whether the fake classes in threading.py should stay 
as is or can be fixed?  The whole _Verbose business and Thing/_Thing 
indirection seem a bit outdated and unneeded.

--
nosy: +eric.araujo, gvanrossum

___
Python tracker 

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

[issue10973] 'ñ' not working with IDLE 3.2rc1 - OSX 10.6.6

[Nestor Aguilera]

Nestor Aguilera  added the comment:

Thanks Victor and Ned, I'll send a report on the second issue as well (I 
thought it was known).

Néstor Aguilera

--

___
Python tracker 

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

[issue10935] wsgiref.handlers.BaseHandler and subclasses of str

[Phillip J. Eby]

Phillip J. Eby  added the comment:

1. WSGI is a *Python* spec, not a *CPython* spec, so CPython implementation 
details have little bearing on how the spec should work.

Most non-CPython implementations have a native string type optimized for their 
runtime or VM (i.e. Jython and IronPython), and thus have *different* 
implementation-dependent details of what constitutes a "native" string, other 
than that it has type 'str' as seen by Python code.  (See my previous point 
about people bringing these sorts of implicit assumptions to the table!)

(Also, as you may or may not be aware, WSGI supports Python 2.1, mainly for 
Jython's sake at the time, and in Python 2.1 there was *no such thing* as a 
subclass of 'str' to begin with.)

2. The specific practical goal of WSGI is interoperability, *not* programmer 
convenience.  (Says so right in the PEP.)

3. You are free to patch wsgiref's Headers class to *accept* non-str values (as 
long as they are converted to conforming strings in the process) and to make 
any proposals you like for future versions of WSGI or another interop protocol 
via the Web-SIG, so this entire discussion has been moot for some time now.

4. The explicit-vs-implicit is about the contract defined in the spec (making 
explicit what, precisely, is required of both parties), not the type test.

5. Since this discussion is moot (see point 3), we'll have to agree to disagree 
here.  Whether you (or I!) like what the spec says is not what matters: wsgiref 
is the *reference library* for the specification, and therefore must conform to 
the actual spec, not what any of us would like the spec to be.

Heck, I tried to add some *much* more minor amendments to PEP 333 than this 
about three or four months ago, and Guido said he'd reject the whole PEP if I 
tried!  That's why we have PEP  instead of a slightly-amended PEP 333.  
This particular bikeshed was painted six years ago, so let's get on with the 
actual bicycling already.

--

___
Python tracker 

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

[issue3080] Full unicode import system

[Nick Coghlan]

Nick Coghlan  added the comment:

On Sat, Jan 22, 2011 at 3:08 AM, STINNER Victor  wrote:
> I should maybe add some unit tests for non-ASCII module paths and non-ASCII 
> module names :-)

Indeed. There are a few tests in test_runpy that could be adapted to
that task fairly easily (it creates the test packages at run time in a
temporary directory, so copying that to make a non-ASCII path and
module name test should be too difficult).

--

___
Python tracker 

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

[issue10972] zipfile: add "unicode" option to the force the filename encoding to UTF-8

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc  added the comment:

This looks similar to issue10614

--

___
Python tracker 

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

[issue10973] 'ñ' not working with IDLE 3.2rc1 - OSX 10.6.6

[Ned Deily]

Ned Deily  added the comment:

(Regarding the second problem: if IDLE does not launch when you double-click on 
it, please check for and report any error messages from /var/log/system.log at 
the time. You can use /Applications/Utilities/Console.app to view system.log.)

--
assignee:  -> ned.deily

___
Python tracker 

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

[issue8754] ImportError: quote bad module name in message

[STINNER Victor]

STINNER Victor  added the comment:

My patch for #3080 uses repr() to format module name in all error messages.

--
nosy: +haypo

___
Python tracker 

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

[issue3080] Full unicode import system

[STINNER Victor]

STINNER Victor  added the comment:

I tried issue3080-5.patch. The whole test suite pass on Windows. It pass also 
on Linux with "-Wd -Werror -R 3:3:" (except #10971 which is unrelated to this 
issue).

I should maybe add some unit tests for non-ASCII module paths and non-ASCII 
module names :-)

--

___
Python tracker 

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

[issue3080] Full unicode import system

[STINNER Victor]

STINNER Victor  added the comment:

> but I'm going to have trouble diagnosing things that don't fail 
> on my development machine.

On Windows, try any character not encodable into your ANSI code page (eg. Ł 
with cp1252) in the module path and non-ASCII characters in the module name.

On Mac OS X, sorry, it already works.

On other OSes, set the locale to something else than UTF-8 (and than ASCII 
because ASCII is not very interesting) and try non-ASCII module names. The 
patch includes issue3080.py: set the locale to fr_FR.iso88591 to have 
ISO-8859-1 as locale encoding and try to load a module called 'issue3080\xE4'. 
U+00E4 is encoded to b'\xE4' in ISO-8859-1 and b'\xC3\xA4' to UTF-8.

--

___
Python tracker 

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

[issue10973] 'ñ' not working with IDLE 3.2rc1 - OSX 10.6.6

[STINNER Victor]

STINNER Victor  added the comment:

> I cannot start IDLE by double-clicking its icon in the Finder.

You may open a new issue for this proble.

--

___
Python tracker 

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

[issue10973] 'ñ' not working with IDLE 3.2rc1 - OSX 10.6.6

[STINNER Victor]

STINNER Victor  added the comment:

No problem on Linux (Debian Sid): I tried "ŁñØ=1" in IDLE interpreter (written 
using the compose key).

It looks like the bug is specific to Mac OS X and comes from Tk directly:
http://sourceforge.net/tracker/index.php?func=detail&aid=2907388&group_id=12997&atid=112997
"(...)  this crash happens for [all] composite characters. (...) the crash is 
caused by the "sticky" modifier key and not by the accented character itself."

--

___
Python tracker 

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

[issue3080] Full unicode import system

[Nick Coghlan]

Nick Coghlan  added the comment:

Oops, missed that post - that was indeed the problem. With that fixed, tests 
are all good on this system. I'll give the patch a look anyway, but I'm going 
to have trouble diagnosing things that don't fail on my development machine.

As far as the test_reprlib failure goes, I seem to recall addressing a similar 
problem elsewhere in the standard lib by replace a "%r" code with "'%s'" to get 
the single quotes without the backslash escaping. A similar change should 
probably do the trick here.

--

___
Python tracker 

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

[issue10935] wsgiref.handlers.BaseHandler and subclasses of str

[Antoine Pitrou]

Antoine Pitrou  added the comment:

> Implicit knowledge in your own head about what might or might not be a
> good idea to program is not the same thing as a specification.
> "type(x) is str" is a good specification in this context, while
> "string subclasses, but only if they're really str" does not.
> 
> And the reason why that is, is because the first specification allows
> server implementers to say, "your type is not str, so you are not
> conformant; go fix your code."   The second "specification" is just an
> invitation to (number of server implementations)*(number of string
> implementations) arguments about what conformance is.

You might argue about this all the way you want, but let me repeat it:
the interpreter already, implicitly, uses the "second specification" in
many of its internal routines (e.g. C implementations of stdlib
functions and types). Why do you think what is fine for the interpreter
and its stdlib is not fine for WSGI?

> Practicality beats purity, and explicit is better than implicit. 

And, ironically, you are arguing for a pure specification at the expense
of practicality. As for explicit/implicit, it isn't involved here: an
isinstance() test is as explicit as a type() equality test.

--

___
Python tracker 

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

[issue10947] imaplib: Internaldate2tuple and ParseFlags require (and latter returns) bytes arrays; should allow/return str

[Joe Peterson]

Joe Peterson  added the comment:

Yep, I agree, and in light of this, we should probably just close this issue 
and work toward reviewing/improving imaplib in the ways you are suggesting.

As I migrate my imap stuff more to Python3, I'll see if I run into any problems 
with using bytes throughout (beyond what is addressed in issue 10939).

--

___
Python tracker 

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

[issue8713] multiprocessing needs option to eschew fork() under Linux

[Antoine Pitrou]

Changes by Antoine Pitrou :


--
nosy: +asksol
stage:  -> needs patch
versions: +Python 3.3 -Python 3.2

___
Python tracker 

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

[issue10935] wsgiref.handlers.BaseHandler and subclasses of str

[Phillip J. Eby]

Phillip J. Eby  added the comment:

Implicit knowledge in your own head about what might or might not be a good 
idea to program is not the same thing as a specification.  "type(x) is str" is 
a good specification in this context, while "string subclasses, but only if 
they're really str" does not.

And the reason why that is, is because the first specification allows server 
implementers to say, "your type is not str, so you are not conformant; go fix 
your code."   The second "specification" is just an invitation to (number of 
server implementations)*(number of string implementations) arguments about what 
conformance is.

That makes the latter an objectively worse specification than the first, even 
if EVERYONE would prefer to be able to use their own string type.  Practicality 
beats purity, and explicit is better than implicit.  These principles are 
doubly true where interop protocol definitions are concerned.

To put it another way, the greater the social separation between parties, the 
more explicit and specific a contract between those two parties has to be in 
order to co-ordinate their actions, because they can't rely on having the same 
operating assumptions as the other party.  This situation is a terrific example 
of that principle in action.  ;-)

--

___
Python tracker 

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

[issue8713] multiprocessing needs option to eschew fork() under Linux

[dholth]

dholth  added the comment:

+1

--
nosy: +dholth

___
Python tracker 

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

[issue10947] imaplib: Internaldate2tuple and ParseFlags require (and latter returns) bytes arrays; should allow/return str

[R. David Murray]

R. David Murray  added the comment:

Well, we recently added support for parsing binary data streams to the email 
module (or added back, if you are looking at it from a python2 perspective), 
exactly because "in the wild" headers are not always RFC compliant ASCII, and 
because bodies often are RFC *compliant* 8bit.  So yes, the appropriate type 
for imaplib to be returning is bytes, and the application has to figure out how 
to decode it to string using the information contained internally in the email 
message.  The email package is the obvious way to do this, and if there are 
helper routines that an imaplib programmer would want in order to make that job 
easier, those would be very legitimate feature requests (but most of what one 
needs should already be there; specifically decode_header and friends, although 
there's an outstanding feature request for a convenience wrapper around that).

--
nosy: +eric.smith

___
Python tracker 

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

[issue10972] zipfile: add "unicode" option to the force the filename encoding to UTF-8

[Antoine Pitrou]

Changes by Antoine Pitrou :


--
nosy: +amaury.forgeotdarc

___
Python tracker 

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

[issue10972] zipfile: add "unicode" option to the force the filename encoding to UTF-8

[Antoine Pitrou]

Antoine Pitrou  added the comment:

> > The question is, rather, why you need an external flag for that.
> 
> Because I don't want to change the default encoding. I am not sure
> that all applications support UTF-8 encodings.

If this is a ZIP standard flag, why should we care about applications
which don't support it? Should we add other flags to disable other
features out of fear that other applications might not support them
either?

> But if you control your environment, force UTF-8 encoding should
> improve your Unicode support.

How is a random user supposed to know if their tools support UTF-8
encoding? It's not like everyone is an expert in ZIP files. This is the
kind of situation where asking the user to make a choice is more
confusing than helpful. When adding the flag, not only you complicate
the API, but you have to support this flag for the rest of your life
(well, almost :-)).

We could instead use utf-8 by default for all non-ascii filenames (and
*perhaps* have a separate force_cp437 flag, but default it to False).

--

___
Python tracker 

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

[issue10972] zipfile: add "unicode" option to the force the filename encoding to UTF-8

[STINNER Victor]

STINNER Victor  added the comment:

> The question is, rather, why you need an external flag for that.

Because I don't want to change the default encoding. I am not sure that all 
applications support UTF-8 encodings.

But if you control your environment, force UTF-8 encoding should improve your 
Unicode support.

--

___
Python tracker 

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

[issue10955] Possible regression with stdlib in zipfile

[STINNER Victor]

STINNER Victor  added the comment:

> I cannot avoid haveing non-ascii filenames when a python package
> contains data files that have such names.

Are "data files" Python modules (.py files)? Or can it be anything?

--

___
Python tracker 

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

[issue10955] Possible regression with stdlib in zipfile

[Antoine Pitrou]

Antoine Pitrou  added the comment:

> Again, the whole zip central directory is loaded on first import. If
> the zip file contains non-ascii filenames, nothing can be imported.

Does it have to be decoded eagerly, though?

--

___
Python tracker 

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

[issue10955] Possible regression with stdlib in zipfile

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc  added the comment:

> We are only talking about bootstrap-time importing of encodings modules.
Again, the whole zip central directory is loaded on first import. If the zip 
file contains non-ascii filenames, nothing can be imported.

--

___
Python tracker 

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

[issue10973] 'ñ' not working with IDLE 3.2rc1 - OSX 10.6.6

[Antoine Pitrou]

Changes by Antoine Pitrou :


--
nosy: +ned.deily

___
Python tracker 

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

[issue10955] Possible regression with stdlib in zipfile

[Antoine Pitrou]

Antoine Pitrou  added the comment:

> The python32.zip file generated by py2app contains both files from the
> stdlib and application files.  I cannot avoid haveing non-ascii
> filenames when a python package contains data files that have such
> names.

I don't think this is a problem. We are only talking about
bootstrap-time importing of encodings modules. Once the encodings
machinery is initialized, importing non-ascii files should work fine.

--

___
Python tracker 

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

[issue10973] 'ñ' not working with IDLE 3.2rc1 - OSX 10.6.6

[STINNER Victor]

Changes by STINNER Victor :


--
nosy: +haypo

___
Python tracker 

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

[issue10955] Possible regression with stdlib in zipfile

[Ronald Oussoren]

Ronald Oussoren  added the comment:

The python32.zip file generated by py2app contains both files from the stdlib 
and application files.  I cannot avoid haveing non-ascii filenames when a 
python package contains data files that have such names.

The patch in Issue10972 would be nice to have, that way py2app can enforce that 
the zipfile uses UTF-8 names.

--

___
Python tracker 

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

[issue10973] 'ñ' not working with IDLE 3.2rc1 - OSX 10.6.6

[Nestor Aguilera]

New submission from Nestor Aguilera :

When trying to type 'ñ' in idle 3.2 (no problem in terminal), python "quits 
unexpectedly" when started from terminal:

$ idle3
2011-01-21 11:21:55.883 Python[5228:a07] setCanCycle: is deprecated.  Please 
use setCollectionBehavior instead
2011-01-21 11:21:55.890 Python[5228:a07] setCanCycle: is deprecated.  Please 
use setCollectionBehavior instead
2011-01-21 11:21:55.891 Python[5228:a07] setCanCycle: is deprecated.  Please 
use setCollectionBehavior instead
2011-01-21 11:22:08.777 Python[5228:a07] An uncaught exception was raised
2011-01-21 11:22:08.779 Python[5228:a07] *** -[NSCFString characterAtIndex:]: 
Range or index out of bounds
2011-01-21 11:22:08.781 Python[5228:a07] *** Terminating app due to uncaught 
exception 'NSRangeException', reason: '*** -[NSCFString characterAtIndex:]: 
Range or index out of bounds'
*** Call stack at first throw:
(
0   CoreFoundation  0x7fff829c47b4 
__exceptionPreprocess + 180
1   libobjc.A.dylib 0x7fff816300f3 
objc_exception_throw + 45
2   CoreFoundation  0x7fff829c45d7 
+[NSException raise:format:arguments:] + 103
3   CoreFoundation  0x7fff829c4564 
+[NSException raise:format:] + 148
4   Foundation  0x7fff839c15e1 -[NSCFString 
characterAtIndex:] + 97
5   Tk  0x0001012ba035 
-[TKApplication(TKKeyEvent) tkProcessKeyEvent:] + 664
6   Tk  0x0001012c0b38 
TkMacOSXEventsCheckProc + 349
7   Tcl 0x000101175667 
Tcl_DoOneEvent + 316
8   _tkinter.so 0x00010077d801 
Tkapp_MainLoop + 177
9   Python  0x0001000b2b62 
PyEval_EvalFrameEx + 30530
10  Python  0x0001000b34ca 
PyEval_EvalCodeEx + 1770
11  Python  0x0001000b19e3 
PyEval_EvalFrameEx + 26051
12  Python  0x0001000b1bfd 
PyEval_EvalFrameEx + 26589
13  Python  0x0001000b34ca 
PyEval_EvalCodeEx + 1770
14  Python  0x0001000b37df 
PyEval_EvalCode + 63
15  Python  0x0001000da19b 
PyRun_FileExFlags + 187
16  Python  0x0001000da469 
PyRun_SimpleFileExFlags + 521
17  Python  0x0001000ef253 Py_Main + 
3059
18  Python  0x00010e5f 0x0 + 
4294970975
19  Python  0x00010d04 0x0 + 
4294970628
)
terminate called after throwing an instance of 'NSException'
Abort trap
 
#--
The welcome in idle 3.2 is:

Python 3.2rc1 (r32rc1:88040, Jan 15 2011, 13:31:22) 
[GCC 4.2.1 (Apple Inc. build 5664)] on darwin
Type "copyright", "credits" or "license()" for more information.

#--
I cannot start IDLE by double-clicking its icon in the Finder.

Best,

Néstor Aguilera

--
components: IDLE
messages: 126739
nosy: naguilera
priority: normal
severity: normal
status: open
title: 'ñ' not working with IDLE 3.2rc1 - OSX 10.6.6
type: crash
versions: Python 3.2

___
Python tracker 

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

[issue10968] threading.Timer should be a class so that it can be derived

[Eric Smith]

Changes by Eric Smith :


--
nosy: +eric.smith
title: Timer should be a class so that it can be derived -> threading.Timer 
should be a class so that it can be derived

___
Python tracker 

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

[issue10936] Simple CSS fix for left margin at docs.python.org

[Fred L. Drake, Jr.]

Fred L. Drake, Jr.  added the comment:

On Fri, Jan 21, 2011 at 2:58 AM, Christopher Dunn
 wrote:
> For narrow-width screens, there really shouldn't be a sidebar. Maybe a 
> dynamic element would be better.

Right.  I'd be in favor of removing the sidebar and having a pop-out
ToC navigator of some sort.  Most of the time, most of us are looking
at the content, not at how to navigate the content.  Spending so much
screen real-estate on navigation is painful.  Large, hi-res screens
just aren't *that* cheap yet.

--

___
Python tracker 

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