[issue3210] subprocess.Popen does not release process handles if process cannot be started

[Geoffrey Bache]

Geoffrey Bache <[EMAIL PROTECTED]> added the comment:

A note on workarounds, the garbage collector seems to release the
handles when the function exits, so removing the file in a caller works
for me. However Tim's proposed fix with os.close didn't do so.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue993766] bdist_dumb and --relative on Windows fails

[zouguangxian]

zouguangxian <[EMAIL PROTECTED]> added the comment:

I encounter the same problem of Mark Hammond. I check the code in
repository, the ensure_relative function in python25 is:

def ensure_relative (path):
"""Take the full path 'path', and make it a relative path so
it can be the second argument to os.path.join().
"""
drive, path = os.path.splitdrive(path)
if sys.platform == 'mac':
return os.sep + path
else:
if path[0:1] == os.sep:
path = drive + path[1:]
return path

I also checked python24, and didn't find the code which described by 
Patrice LACOUTURE in msg60533 (view).

--
nosy: +weck

___
Python tracker <[EMAIL PROTECTED]>

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

[issue1276] LookupError: unknown encoding: X-MAC-JAPANESE

[Hye-Shik Chang]

Changes by Hye-Shik Chang <[EMAIL PROTECTED]>:


Added file: http://bugs.python.org/file10749/maccjkcodecs-1-py3k.diff

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3214] Suggest change to glossary explanation: "Duck Typing"

[Paddy McCarthy]

New submission from Paddy McCarthy <[EMAIL PROTECTED]>:

The official glossary entry here:
http://docs.python.org/tut/node18.html#l2h-46
says:
"
duck-typing
Pythonic programming style that determines an object's type by
inspection of its method or attribute signature rather than by
explicit relationship to some type object ("If it looks like a duck
and quacks like a duck, it must be a duck.") By emphasizing interfaces
rather than specific types, well-designed code improves its
flexibility by allowing polymorphic substitution. Duck-typing avoids
tests using type() or isinstance(). Instead, it typically employs
hasattr() tests or EAFP programming.
"

I think it is should be changed to delete the use of hasattr and just
rely on EAFP as in the second example here:
http://en.wikipedia.org/wiki/Python_syntax_and_semantics#Exceptions

The text would then read:
"
duck-typing
Pythonic programming style that determines an object's type by
inspection of its method or attribute signature rather than by
explicit relationship to some type object ("If it looks like a duck
and quacks like a duck, it must be a duck.") By emphasizing interfaces
rather than specific types, well-designed code improves its
flexibility by allowing polymorphic substitution. Duck-typing avoids
tests using type(), hasattr() or isinstance(). Instead, it typically
employs an EAFP style of programming.
"

The reason is that a hasattr test only tests for an attribute name. If
it is present and say the method signature is wrong, then its the
excecution of the code using the attribute that will find that out so
it is redundant. Best to use EAFP for Duck typing as we trust you know
what it is you are doing.

- Paddy.

--
assignee: georg.brandl
components: Documentation
messages: 68815
nosy: georg.brandl, paddy3118
severity: normal
status: open
title: Suggest change to glossary explanation:  "Duck Typing"
type: feature request
versions: Python 2.5, Python 2.6, Python 3.0

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3213] "pydoc -p" should listen to [::] if IPv6 is supported

[Martin v. Löwis]

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

That will break on systems where AF_INET6 doesn't default to
dual-stacked sockets and mapped v4 addresses (e.g. Windows); to make it
work correctly, you'll also have to disable the IPV6_V6ONLY option,
which then breaks on systems which don't implement that option (e.g.
Windows XP).

--
nosy: +loewis

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3211] warnings.warn_explicit raises SystemError

[Brett Cannon]

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

r64552 has the 3.0 fix. Thanks for the report gentleman!

--
status: pending -> closed

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3211] warnings.warn_explicit raises SystemError

[Brett Cannon]

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

Fixed in r64549 for 2.6. Currently testing the merge for 3.0.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3213] "pydoc -p" should listen to [::] if IPv6 is supported

[Hans Ulrich Niedermann]

New submission from Hans Ulrich Niedermann <[EMAIL PROTECTED]>:

According to "pydoc --help",

pydoc -p 
Start an HTTP server on the given port on the local machine.

The IP address pydoc binds to is not specified, thus I would expect it
to either bind to the local address or to the wildcard address.

Current behaviour of "pydoc -p 1234" is to bind to the IPv4-only 
address 0.0.0.0:1234.

On a IPv4/IPv6 dual-stack machine, I would expect pydoc to listen to
either both 127.0.0.1:1234 and [::1]:, or just [::]: ([::]
also catches accesses to IPv4 addresses such as 127.0.0.1).

Then access to the pydoc webserver is
available both via IPv4 (e.g. http://127.0.0.1:1234/) and IPv6 (e.g.
http://[::1]:1234/), and in both cases via http://localhost:1234/
regardless whether localhost is resolved via IPv6 or IPv4.

Trivial patch attached (tested on Linux x86 machine with local IPv6
networking).

--
components: Library (Lib)
files: python-pydoc-p-ipv6.patch
keywords: patch
messages: 68811
nosy: ndim
severity: normal
status: open
title: "pydoc -p" should listen to [::] if IPv6 is supported
type: behavior
versions: Python 2.5, Python 2.6
Added file: http://bugs.python.org/file10748/python-pydoc-p-ipv6.patch

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3125] test_multiprocessing causes test_ctypes to fail

[Jesse Noller]

Jesse Noller <[EMAIL PROTECTED]> added the comment:

Sorry - I've been sick and overly busy this week, the mp issues are on  
my asap pile

On Jun 26, 2008, at 7:17 PM, Amaury Forgeot d'Arc <[EMAIL PROTECTED] 
 > wrote:

>
> Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:
>
> Jesse: ping?
>
> ___
> Python tracker <[EMAIL PROTECTED]>
> 
> ___

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3211] warnings.warn_explicit raises SystemError

[Brett Cannon]

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

I have a fix in the works; just waiting for the test suite to finish.

--
status: open -> pending

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3125] test_multiprocessing causes test_ctypes to fail

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

Jesse: ping?

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3212] ssl module - should test for a wrong cert

[Bill Janssen]

Bill Janssen <[EMAIL PROTECTED]> added the comment:

OK, good idea.  I'll put it in.

Bill

On Thu, Jun 26, 2008 at 11:34 AM, Jonas Wagner <[EMAIL PROTECTED]>
wrote:

>
> New submission from Jonas Wagner <[EMAIL PROTECTED]>:
>
> Currently test_ssl.py only tests for empty or broken certificates. One
> can break certificate validation in _ssl.c and they still pass.
>
> The following patch should fix this.
>
> - Jonas
>
> --
> components: Tests
> files: add_wrong_cert_test.diff
> keywords: patch
> messages: 68797
> nosy: janssen, jonas.wagner
> severity: normal
> status: open
> title: ssl module - should test for a wrong cert
> type: feature request
> versions: Python 2.6
> Added file: http://bugs.python.org/file10745/add_wrong_cert_test.diff
>
> ___
> Python tracker <[EMAIL PROTECTED]>
> 
> ___
>

Added file: http://bugs.python.org/file10747/unnamed

___
Python tracker <[EMAIL PROTECTED]>

___OK, good idea.  I'll put it in.BillOn Thu, Jun 26, 2008 at 11:34 AM, Jonas Wagner [EMAIL PROTECTED]> wrote:

New submission from Jonas Wagner <[EMAIL PROTECTED]>:

Currently test_ssl.py only tests for empty or broken certificates. One
can break certificate validation in _ssl.c and they still pass.

The following patch should fix this.

- Jonas

--
components: Tests
files: add_wrong_cert_test.diff
keywords: patch
messages: 68797
nosy: janssen, jonas.wagner
severity: normal
status: open
title: ssl module - should test for a wrong cert
type: feature request
versions: Python 2.6
Added file: http://bugs.python.org/file10745/add_wrong_cert_test.diff"; 
target="_blank">http://bugs.python.org/file10745/add_wrong_cert_test.diff

___
Python tracker [EMAIL 
PROTECTED]>
http://bugs.python.org/issue3212>
___

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

[issue1774370] Add Tkinter.Checkbutton get() and set(value)

[Guilherme Polo]

Guilherme Polo <[EMAIL PROTECTED]> added the comment:

> Graham Horler <[EMAIL PROTECTED]> added the comment:
>
>> I'm aware of that and that is why everywhere I see Checkbutton
>> being used I see a explicit variable being created.
>
> Absolutely the reason for this patch, to get rid of unnecessary code.
> What's not to like?

You are not getting my point here. What I'm trying to say is: if you
are going to add such code to make it easier to get/set the variable
option value then you better add it to every other widget that
supports a variable option, or a textvariable (*variable in general).
This would make things uniform, you would never need to create a
Variable instance yourself. What I would really hate to see is a
widget that acts like a Variable was created for me, so I can
access/set its value, and others that have the same option but doesn't
allow me that.
And, finally, being explicit is not a bad thing.

>
>> I was referring to the other widgets that accepts *variable options.
>> ... add this functionality everywhere it would cause some
>> benefit, not only for Checkbutton.
>
> I'm all for that, just could not find another widget that created an
> inaccessible default variable.  Suggestions welcome.
>

Radiobutton for example ?

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3122] sys.getsizeof() gives an AttributeError for _sre objects.

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

Robert,
looking at your patch for the _sre module, I noticed that
MatchObject.__sizeof__ includes the sizeof of one of its member (regs: a
tuple of (begin, end) pairs).
Why this one and not the others? I thought the rule (if there is a rule)
was to include the used memory for members that are *not* python objects.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3122] sys.getsizeof() gives an AttributeError for _sre objects.

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

I wondered why getsizeof fails for _sre.SRE_Pattern objects when it
succeeds for _socket.socket or struct.Struct.

It turns out that _sre.SRE_Pattern defines the tp_getattr slot, and this
prevents attribute lookup from searching the base class (object).
This is a pity, because the base implementation (which use tp_basicsize)
does the right thing for many objects.

So I borrowed some code from the __format__ method, and here is a patch.
Now classes are not handled specially any more; the distinction is
between old-style instances, and all other objects.

All tests pass, but I may have missed something important...

--
nosy: +amaury.forgeotdarc
Added file: http://bugs.python.org/file10746/sizeof.patch

___
Python tracker <[EMAIL PROTECTED]>

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

[issue1774370] Add Tkinter.Checkbutton get() and set(value)

[Graham Horler]

Graham Horler <[EMAIL PROTECTED]> added the comment:

> I'm aware of that and that is why everywhere I see Checkbutton
> being used I see a explicit variable being created.

Absolutely the reason for this patch, to get rid of unnecessary code.
What's not to like?

> I was referring to the other widgets that accepts *variable options.
> ... add this functionality everywhere it would cause some
> benefit, not only for Checkbutton.

I'm all for that, just could not find another widget that created an
inaccessible default variable.  Suggestions welcome.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3122] sys.getsizeof() gives an AttributeError for _sre objects.

[Robert Schuppenies]

Robert Schuppenies <[EMAIL PROTECTED]> added the comment:

The attribute error is caused by pattern_getattr, which tries to find
__sizeof__, fails and then sets the error message. I don't know if
casting the error is the right thing to do. Actually, sys.getsizeof()
should work on any type.

Another suggestion was a that sys.getsizeof allows one optional
argument for a default size. If the default argument is provided,
sys.getsizeof will not throw an exception (if the __sizeof__ method is
missing or for any other error), but instead return the given default
size.
Still, an agreement on the right error message is needed.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3122] sys.getsizeof() gives an AttributeError for _sre objects.

[Benjamin Peterson]

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

I think it would be better to give a TypeError rather than an
AttributeError for objects that don't support __sizeof__ as per other
special methods.

--
nosy: +benjamin.peterson

___
Python tracker <[EMAIL PROTECTED]>

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

[issue2512] decide what to do with gettext API

[Benjamin Peterson]

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

This is something that should definitely happen before beta 2.

--
priority: critical -> release blocker

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3211] warnings.warn_explicit raises SystemError

[Benjamin Peterson]

Changes by Benjamin Peterson <[EMAIL PROTECTED]>:


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

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3211] warnings.warn_explicit raises SystemError

[Georg Brandl]

Changes by Georg Brandl <[EMAIL PROTECTED]>:


--
priority:  -> critical

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3204] operator module docs are not updated to 3.0

[Georg Brandl]

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

Thanks, committed as r64536.

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

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3209] Grammar error in UserDict module docs

[Georg Brandl]

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

Already fixed in SVN. Thanks!

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

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3212] ssl module - should test for a wrong cert

[Jonas Wagner]

New submission from Jonas Wagner <[EMAIL PROTECTED]>:

Currently test_ssl.py only tests for empty or broken certificates. One
can break certificate validation in _ssl.c and they still pass.

The following patch should fix this.

- Jonas

--
components: Tests
files: add_wrong_cert_test.diff
keywords: patch
messages: 68797
nosy: janssen, jonas.wagner
severity: normal
status: open
title: ssl module - should test for a wrong cert
type: feature request
versions: Python 2.6
Added file: http://bugs.python.org/file10745/add_wrong_cert_test.diff

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3210] subprocess.Popen does not release process handles if process cannot be started

[Tim Golden]

Tim Golden <[EMAIL PROTECTED]> added the comment:

The attached file sp-3.py simulates what I think is happening within the
subprocess module. Note that the OS handle is duplicated to allow
inheritance and then left unclosed on failure. If it is explicitly
closed, the file can be removed.

There is no hope of closing the file handle since it was local to the
__init__ method which failed but was not closed before exit and is now
inaccessible.

On the surface, the obvious fix would be a try/except block around the
CreateProcess call (or its caller) which would then release whatever
handles were needed. I'll try to get the time to put a patch together,
but it would be useful to have confirmation of my theory.

--
nosy: +tim.golden
Added file: http://bugs.python.org/file10744/sp-3.py

___
Python tracker <[EMAIL PROTECTED]>

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

[issue2235] __eq__ / __hash__ check doesn't take inheritance into account

[Guido van Rossum]

Guido van Rossum <[EMAIL PROTECTED]> added the comment:

I'm going to have to ask someone else to look at this code.  I am too
busy with too many things to be able to take on a detailed code review.

--
assignee: gvanrossum -> 

___
Python tracker <[EMAIL PROTECTED]>

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

[issue2235] __eq__ / __hash__ check doesn't take inheritance into account

[Ralf Schmitt]

Changes by Ralf Schmitt <[EMAIL PROTECTED]>:


--
nosy: +schmir

___
Python tracker <[EMAIL PROTECTED]>

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

[issue1774370] Add Tkinter.Checkbutton get() and set(value)

[Guilherme Polo]

Guilherme Polo <[EMAIL PROTECTED]> added the comment:

On Thu, Jun 26, 2008 at 1:02 PM, Graham Horler <[EMAIL PROTECTED]> wrote:
>
> Graham Horler <[EMAIL PROTECTED]> added the comment:
>...
> When you create a Checkbutton widget without giving a variable=SomeVar,
> a default variable is created which Tkinter does not give you easy
> access to.

I'm aware of that and that is why everywhere I see Checkbutton being
used I see a explicit variable being created.

> ...
> What do you mean by "add it to all the other widgets that play with it"?
>

I was referring to the other widgets that accepts *variable options.
Ideally I would to prefer to never need to instantiate Variable or any
of its subclasses, adding methods at the correct places. So what I
meant was to add this functionality everywhere it would cause some
benefit, not only for Checkbutton.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3211] warnings.warn_explicit raises SystemError

[Andrii V. Mishkovskyi]

Andrii V. Mishkovskyi <[EMAIL PROTECTED]> added the comment:

Even more, Python 3.0 crashes from following code:
Python 3.0b1+ (py3k:64528M, Jun 26 2008, 11:40:20)
[GCC 4.2.3 (Ubuntu 4.2.3-2ubuntu7)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from warnings import warn_explicit
>>> warn_explicit(None, UserWarning, None, 0, None, None)
Traceback (most recent call last):
  File "", line 1, in 
SystemError: Objects/dictobject.c:709: bad argument to internal function
>>> warn_explicit(None, UserWarning, None, 0, None, {})
Segmentation fault

--
nosy: +mishok13
type:  -> crash
versions: +Python 3.0

___
Python tracker <[EMAIL PROTECTED]>

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

[issue2235] __eq__ / __hash__ check doesn't take inheritance into account

[Glyph Lefkowitz]

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

As barry said, this should have been a release blocker for the first
beta... ;-)

--
nosy: +glyph
priority: critical -> release blocker

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3211] warnings.warn_explicit raises SystemError

[Jean-Paul Calderone]

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

Python 2.6b1+ (trunk:64531M, Jun 26 2008, 10:40:14)
[GCC 4.0.3 (Ubuntu 4.0.3-1ubuntu5)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import warnings
>>> warnings.warn_explicit(None, UserWarning, None, 0, None, {})
None:0: UserWarning: None
>>> warnings.warn_explicit(None, UserWarning, None, 0, None, None)
Traceback (most recent call last):
  File "", line 1, in 
SystemError: Objects/dictobject.c:677: bad argument to internal function
>>>

--
components: Library (Lib)
messages: 68791
nosy: exarkun
severity: normal
status: open
title: warnings.warn_explicit raises SystemError
versions: Python 2.6

___
Python tracker <[EMAIL PROTECTED]>

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

[issue1774370] Add Tkinter.Checkbutton get() and set(value)

[Graham Horler]

Graham Horler <[EMAIL PROTECTED]> added the comment:

I referred to the man page, as it says this:
 Command-Line Name:-variable ... Defaults to the name of the button 
within its parent.

When you create a Checkbutton widget without giving a variable=SomeVar, 
a default variable is created which Tkinter does not give you easy 
access to.

My patch adds easy access to this default variable.

This is analogous to being able to use an Entry widget without having 
to assign SomeVar to textvariable first.

Yes it could be a property, but Tkinter.py does not use property 
anywhere else, and I am stuck with having to support python 2.1.

What do you mean by "add it to all the other widgets that play with it"?

Thanks

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3122] sys.getsizeof() gives an AttributeError for _sre objects.

[Robert Schuppenies]

Robert Schuppenies <[EMAIL PROTECTED]> added the comment:

What would be a good way to identify *all* possible types? 
When I started, I included all objects in /Objects, but obviously this
is not sufficient.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3122] sys.getsizeof() gives an AttributeError for _sre objects.

[Facundo Batista]

Facundo Batista <[EMAIL PROTECTED]> added the comment:

Robert, do you have a test suite for the sizeof functionality?  If not,
you should start one ASAP, ;)

This test should be included in that suit...

--
nosy: +facundobatista

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3210] subprocess.Popen does not release process handles if process cannot be started

[Geoffrey Bache]

New submission from Geoffrey Bache <[EMAIL PROTECTED]>:

Run the following code on Windows:

import subprocess, os

file = open("filename", "w")
try:
proc = subprocess.Popen("nosuchprogram", stdout=file)
except OSError:
file.close()
os.remove("filename")

This produces the following exception:

Traceback (most recent call last):
  File "C:\processown.py", line 10, in 
os.remove("filename")
WindowsError: [Error 32] The process cannot access the file because it
is being used by another process: 'filename'

When the CreateProcess call fails the subprocess module should release
the handles it provides. Unfortunately it seems to raise WindowsError
before doing this.

See also
http://groups.google.com/group/comp.lang.python/browse_thread/thread/6157691ea3324779/6274e9f8bc8a71ee?hl=en#6274e9f8bc8a71ee

As Tim Golden points out, this can be worked around by doing
os.close(file.fileno()) at the end instead of file.close()

--
components: Extension Modules
messages: 68787
nosy: gjb1002
severity: normal
status: open
title: subprocess.Popen does not release process handles if process cannot be 
started
type: behavior
versions: Python 2.5

___
Python tracker <[EMAIL PROTECTED]>

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

[issue2650] re.escape should not escape underscore

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

The escaped regexp is not utf-8 (why should it be?), but it still
matches the same bytes in the searched text, which has to be utf-8
encoded anyway:

>>> text = u"été".encode('utf-8')
>>> regexp = u"é".encode('utf-8')
>>> re.findall(regexp, text)
['\xc3\xa9', '\xc3\xa9']
>>> escaped_regexp = re.escape(regexp)
>>> re.findall(escaped_regexp, text)
['\xc3\xa9', '\xc3\xa9']

--
nosy: +amaury.forgeotdarc

___
Python tracker <[EMAIL PROTECTED]>

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

[issue2650] re.escape should not escape underscore

[Morten Lied Johansen]

Morten Lied Johansen <[EMAIL PROTECTED]> added the comment:

One issue that the current implementation has, which I can't see have 
been commented on here, is that it kills utf8 characters (and probably 
every other character encoding that is multi-byte).

A é character in an utf8 encoded string will be represented by two 
bytes. When passed through re.escape, those two bytes are checked 
individually, and both are considered non-alphanumeric, and is 
consequently escaped, breaking the utf8 string into complete gibberish 
instead.

--
nosy: +mortenlj

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3209] Grammar error in UserDict module docs

[Michael Schreifels]

New submission from Michael Schreifels <[EMAIL PROTECTED]>:

The second paragraph of the UserDict module documentation begins with this:

"This also module defines a class..."

which should be:

"This module also defines a class..."

(See http://docs.python.org/lib/module-UserDict.html )

--
assignee: georg.brandl
components: Documentation
messages: 68784
nosy: georg.brandl, technel
severity: normal
status: open
title: Grammar error in UserDict module docs

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3208] function annotation for builtin and C function

[Haoyu Bai]

New submission from Haoyu Bai <[EMAIL PROTECTED]>:

It is better if the function annotation(PEP 3107) can be supported by
built-in function and C function writtin in extension module, just like
the __doc__ attribute.

--
messages: 68783
nosy: bhy
severity: normal
status: open
title: function annotation for builtin and C function
type: feature request
versions: Python 3.0

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3206] Multiprocessing Array and sharedctypes.Array error in docs/implementation

[Benjamin Peterson]

Changes by Benjamin Peterson <[EMAIL PROTECTED]>:


--
assignee: georg.brandl -> jnoller

___
Python tracker <[EMAIL PROTECTED]>

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

[issue1636874] File Read/Write Flushing Patch

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

It seems that python3.0 behaves better in this area, specially on
Windows. See the examples given in issue3207.

And since the 'file' type does not use FILE* anymore, the given
workaround is not necessary.

--
nosy: +amaury.forgeotdarc
resolution:  -> out of date
status: open -> closed

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3207] file.write() after file.readline() in mode "r+"

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

Yes, the exact behaviour depends on multiple aspects.

You should follow the C library conventions: 
http://www.cplusplus.com/reference/clibrary/cstdio/fopen.html
"""
For the modes where both read and writing (or appending) are allowed
(those which include a "+" sign), the stream should be flushed (fflush)
or repositioned (fseek, fsetpos, rewind) between either a reading
operation followed by a writing operation or a writing operation
followed by a reading operation.
"""

In your case, I suggest a call to fp.seek(0, os.SEEK_CUR) before you
start writing data. And a fp.flush() after, in case you want to read again.

Python 3.0 has a completely new I/O implementation, which may have its
own problems, but hopefully the same on all platforms. And it happens to
do the right thing in your example.

--
resolution:  -> wont fix
status: open -> closed

___
Python tracker <[EMAIL PROTECTED]>

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

[issue1276] LookupError: unknown encoding: X-MAC-JAPANESE

[Hye-Shik Chang]

Hye-Shik Chang <[EMAIL PROTECTED]> added the comment:

Added a patch that implements codecs for CJK Macintosh encodings.
I tried to implement that just alike the other existing CJK codecs,
but it required many inefficient mapping tables due to their odd
mappings (like this: u'ABCDE' <-> 'ab' AND u'ABCD' <-> 'ac'!).

So, I decided to implement a general extension codec wrapper that
can be easily modified by dictionaries given by Python code.
Because all Mac CJK encodings have codecs that implement their base
encodings, I just put their difference in Python codec code.
The extension mechanism may be reused in customized codecs for
in-house applications or legacy encoding supports.

The first patch was generated for 2.6 trunk.  I'm working on porting
it to 3.0.

Added file: http://bugs.python.org/file10743/maccjkcodecs-1.diff

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3207] file.write() after file.readline() in mode "r+"

[Peter]

Peter <[EMAIL PROTECTED]> added the comment:

Amaury Forgeot d'Arc, your example really raise IOError 0
Thing is that you had 1 string in the file
Here is it:
>>> open("delete.me", "w").write("first\nsecond\nthird")
>>> fp = open("delete.me", "r+t")
>>> fp.readline()
'first\n'
>>> fp.write("Newbie")
>>> fp.close()
>>> open("delete.me", "r").read()
'first\nsecond\nthird'

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3207] file.write() after file.readline() in mode "r+"

[Peter]

Changes by Peter <[EMAIL PROTECTED]>:


___
Python tracker <[EMAIL PROTECTED]>

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

[issue3207] file.write() after file.readline() in mode "r+"

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

I tried this on windows 2000:

>>> # create a file with some text
>>> open("delete.me","w").write("some text\n")
>>>
>>> fp = open("delete.me", "r+t")
>>> fp.readline()
'some text\n'
>>> fp.write("New line \n")
Traceback (most recent call last):
  File "", line 1, in 
IOError: [Errno 0] Error

On all 2.x versions of python I tried (2.4, 2.5.1, 2.5.2, 2.6b1, some
compiled with VS7.1, some with VS8.0)

With python3.0, there is no error, and the "New line" is appended at the
end of the file.

issue1636874 may be related to this one.

--
nosy: +amaury.forgeotdarc

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3207] file.write() after file.readline() in mode "r+"

[Peter]

Peter <[EMAIL PROTECTED]> added the comment:

Sorry. I use Windows XP SP2 with all updates on 26.06.2008
Python 2.5.2

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3207] file.write() after file.readline() in mode "r+"

[Georg Brandl]

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

Can't reproduce on Linux on 2.6 or 3.0.

--
assignee: georg.brandl -> 

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3008] Let bin/oct/hex show floats

[Raymond Hettinger]

Raymond Hettinger <[EMAIL PROTECTED]> added the comment:

Add support for non-float floats.

Added file: http://bugs.python.org/file10742/float8.diff

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3207] file.write() after file.readline() in mode "r+"

[Peter]

New submission from Peter <[EMAIL PROTECTED]>:

Following code:
   fp = open("delete.me", "r+t")
   fp.readline()
   fp.write("New line \n")
   fp.close()

Won't do anything. I mean nor writing to file, nor raising exception. 
Nothing.
I can't find any note about this crap. So, it is the best place for it.

P.S. It's my first bug-report and I think I was wrong in filling bug-
form. Sorry.

--
assignee: georg.brandl
components: Documentation
messages: 68773
nosy: georg.brandl, peterdemin
severity: normal
status: open
title: file.write() after file.readline() in mode "r+"
type: performance
versions: Python 2.5

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3206] Multiprocessing Array and sharedctypes.Array error in docs/implementation

[Andrii V. Mishkovskyi]

Andrii V. Mishkovskyi <[EMAIL PROTECTED]> added the comment:

And here is the patch itself. :)

--
keywords: +patch
Added file: http://bugs.python.org/file10741/multiprocessing.diff

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3206] Multiprocessing Array and sharedctypes.Array error in docs/implementation

[Andrii V. Mishkovskyi]

Changes by Andrii V. Mishkovskyi <[EMAIL PROTECTED]>:


--
assignee:  -> georg.brandl
components: +Documentation
nosy: +georg.brandl

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3206] Multiprocessing Array and sharedctypes.Array error in docs/implementation

[Andrii V. Mishkovskyi]

New submission from Andrii V. Mishkovskyi <[EMAIL PROTECTED]>:

multiprocessing.sharedctypes.Array and
multiprocessing.sharedctypes.Value if used according to documentation
fail with AssertionError.

Python 3.0b1+ (py3k:64518, Jun 25 2008, 12:52:38)
[GCC 4.2.3 (Ubuntu 4.2.3-2ubuntu7)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from multiprocessing import sharedctypes
>>> sharedctypes.Array('i', 1, lock=True)
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/local/lib/python3.0/multiprocessing/sharedctypes.py", line
88, in Array
assert hasattr(lock, 'acquire')
AssertionError
>>> sharedctypes.Array('i', 1, lock=False)
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/local/lib/python3.0/multiprocessing/sharedctypes.py", line
88, in Array
assert hasattr(lock, 'acquire')
AssertionError
>>> sharedctypes.Array('i', 1, lock=None)
>
>>> Value('i', lock=True)
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/local/lib/python3.0/multiprocessing/__init__.py", line 246,
in Value
return Value(typecode_or_type, *args, **kwds)
  File "/usr/local/lib/python3.0/multiprocessing/sharedctypes.py", line
75, in Value
assert hasattr(lock, 'acquire')
AssertionError

The same goes for multiprocessing.Array and multiprocessing.Value.

Comparing code to documentation it's obvious that lock argument can be
one of Lock, RLock or None objects (or any object with "acquire"
attribute), but not True or False. Also, looking at the code it seems
strange to me that 'lock' is a keyword-only argument. Why not use simple
default argument "lock=None" for Array() function?
Proposed patch tries to address these issues.

--
components: Library (Lib)
messages: 68771
nosy: jnoller, mishok13, roudkerk
severity: normal
status: open
title: Multiprocessing Array and sharedctypes.Array error in docs/implementation
versions: Python 3.0

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3205] bz2 iterator fails silently on MemoryError

[Michiel de Hoon]

New submission from Michiel de Hoon <[EMAIL PROTECTED]>:

PyMem_Malloc is called in the Util_ReadAhead function in bz2module.c.
The code checks if PyMem_Malloc returns NULL, but in that case no
MemoryError is raised. So, if in the following code:

>>> input = bz2.BZ2File("myfile.txt.bz2")
>>> for line in input:
... # do something with the line

Python runs out of memory during the for-loop, then the for-loop exits
without an Exception being raised. To the user, it appears that the end
of the myfile.txt.bz2 file was reached and that no error occurred.

In the attached patch, I call PyErr_NoMemory() if PyMem_Malloc fails.
This then raises the MemoryError exception as appropriate.

--
components: Extension Modules
files: bz2module.c.patch
keywords: patch
messages: 68770
nosy: mdehoon
severity: normal
status: open
title: bz2 iterator fails silently on MemoryError
type: behavior
Added file: http://bugs.python.org/file10740/bz2module.c.patch

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3147] tests for sys.getsizeof fail on win64

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

> long's structure is 'lP PP l H'
No, it's a VAR-sized object, and ob_size is a Py_ssize_t, which is best
represented as a 'P' as you already did for other types. I suggest 'lP
PP P H'.

> the function size which is 'lp PP 9l'
According to Include/funcobject.h, there are nine PyObject*, the
description should end with "9P".

I think there are some other inconsistencies. For example, the tests for
'list' should be
self.check_sizeof([], size(h + 'PPP'))
self.check_sizeof([1, 2, 3], size(h + 'PPP') + 3*self.P)
for the same reasons as for the 'long' type (ob_size is a Py_ssize_t),
even if the total is the same thanks to alignment.

I agree it's very difficult to get it right...

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3192] exec(open(filename)) doesn't work

[Georg Brandl]

Changes by Georg Brandl <[EMAIL PROTECTED]>:


--
resolution:  -> duplicate
status: open -> closed

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3147] tests for sys.getsizeof fail on win64

[Martin v. Löwis]

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

I can't quite follow your layout of a longint; in debug mode, I think it is
- 2P (next/prev)
- ssize_t (refcnt)
- P (type)
- ssize_t (size)
- digits

Notice that a ssize_t is 64 bits on Win64, so there shouldn't be any
longs in the structure on Win64.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue1974] email.MIMEText.MIMEText.as_string incorrectly folding long subject header

[Chris Withers]

Chris Withers <[EMAIL PROTECTED]> added the comment:

Ori,

I do agree with both you and Barry but is there any chance someone could
make the one-character change to make the /t a space so we can stop
seeing weirdness in common mail clients?

Perhaps a separate issue could be raised to refactor this all correctly?

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3204] operator module docs are not updated to 3.0

[Andrii V. Mishkovskyi]

New submission from Andrii V. Mishkovskyi <[EMAIL PROTECTED]>:

__*slice__() methods of sequence-like objects are removed in Python 3.0,
but "operator.rst" has sections on *slice()/__*slice__() functions.
Attached patch removes this functions from documentation.

--
assignee: georg.brandl
components: Documentation
files: operator.rst.diff
keywords: patch
messages: 68766
nosy: georg.brandl, mishok13
severity: normal
status: open
title: operator module docs are not updated to 3.0
versions: Python 3.0
Added file: http://bugs.python.org/file10739/operator.rst.diff

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3147] tests for sys.getsizeof fail on win64

[Robert Schuppenies]

Robert Schuppenies <[EMAIL PROTECTED]> added the comment:

The tests still do not pass on the AMD64 W2k8. Surprisingly,
struct.calcsize behaves as expected, but sizeof() on the C level does
not. The former seems to assumes long to be 4 byte in size, the latter
8!

The tests pass until it comes to a situation where the size of long
affects the alignment of the structure end. In this case long and
function.
long's structure is 'lP PP l H' which gives an expected size of

8+8+16+4+2(+2) = 40

At least this how I think it should be and struct.calcsize does,
too. But what seems to be computed is

8+8+16+8+2(+6) = 48.

It appears as if sizeof(long) = 8. The same explanation holds true for
the failure on the function size which is 'lp PP 9l' and
struct.calcsize : 8+8+16+36(+4) = 72
sizeof  : 8+8+16+72 = 104

Now I don't know how I should address this problem. It seems to be
Windows AMD64 specific, but I found a post [1] which indicates that
it's Windows AMD64 on Windows 2K specific. Tests do also fail on the
Win64 XP buildbot, but it gets killed before the verbose output is
generated. I don't have access to such a platform, so I cannot verify
it.

It may also be a problem with struct.calcsize on Win64.

Any suggestions?

[1]
http://www.velocityreviews.com/forums/t491385-different-behavior-of-amd64-compiler-14004031041-on-windows-xp-and-2k.html

--
nosy: +loewis

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3179] cPickle is seriously broken

[Jesús Cea Avión]

Changes by Jesús Cea Avión <[EMAIL PROTECTED]>:


--
nosy: +jcea

___
Python tracker <[EMAIL PROTECTED]>

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