[issue766910] fix one or two bugs in trace.py

Zooko O'Whielacronx added the comment: > Here is an updated version of the patch which simply removes some > dead code and updates a URL: > > regards, > > Zooko > > diff -rN -u old-up/setuptools-0.6c7/ez_setup.py new-up/ > setuptools-0.6c7/ez_setup.py > --- old-up/setuptools-0.6c7/ez_setup.py

[issue766910] fix one or two bugs in trace.py

Zooko O'Whielacronx added the comment: Hi! Sorry it took me so long to look at this. I just checked the source in current trunk, and the relevant code is the same so this patch is still useful. (See the initial post for details.) Here is an updated version of the patch which simply remove

[issue1218] Restrict Google search to docs when in the docs subtree?

Martin v. Löwis added the comment: > Is there some reason at this point that we need to maintain two separate > trackers? I don't know - I explained what is, not what should be. Whether or not pydotorg people want to use the tracker, I can't tell. Regards, Martin _

[issue1215] Python hang when catching a segfault

Miki Tebeka added the comment: Because it hangs Python :) I know, "while 1: pass" also hangs Python, however it'll nice if this behaviour was documented or (IMO better) that Python will raise an InvalidArgument exception on SIGSEGV (like it does for SIGKILL). __

[issue1210] imaplib does not run under Python 3

Raghuram Devarakonda added the comment: I have gone through the python-3000 discussions about similar problems in other stdlib modules (email, imghdr, sndhdr etc) and found PEP 3137 (Immutable Bytes and Mutable Buffer). Since that work is in progress, I don't think it is worthwhile to fix this pr

[issue1215] Python hang when catching a segfault

Guido van Rossum added the comment: Why is this a Python bug? -- nosy: +gvanrossum __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailin

[issue1218] Restrict Google search to docs when in the docs subtree?

Skip Montanaro added the comment: Martin> Website issues are not tracked in this tracker. See Martin> http://wiki.python.org/moin/PythonWebsiteCreatingNewTickets Is there some reason at this point that we need to maintain two separate trackers? A ton of work went into making our Roundup ins

[issue1219] 3.0 library/stdtypes.rst patch

Georg Brandl added the comment: Extended and committed in r58282. -- resolution: -> accepted status: open -> closed __ Tracker <[EMAIL PROTECTED]> __ _

[issue1211] cleanup patch for 3.0 tutorial/interpreter.rst

Georg Brandl added the comment: Thanks, committed in r58281. (I reordered the encoding section a bit.) -- nosy: +georg.brandl resolution: -> accepted status: open -> closed __ Tracker <[EMAIL PROTECTED]> ___

[issue1212] 3.0 tutorial/introduction.rst mentions 'long'

Georg Brandl added the comment: Thanks, committed in r58281. -- nosy: +georg.brandl resolution: -> accepted status: open -> closed __ Tracker <[EMAIL PROTECTED]> __ __

[issue1213] 3.0 tutorial/classes.rst patch

Georg Brandl added the comment: Thanks, committed in r58281. -- nosy: +georg.brandl resolution: -> accepted status: open -> closed __ Tracker <[EMAIL PROTECTED]> __ __

[issue1219] 3.0 library/stdtypes.rst patch

Changes by Georg Brandl: -- assignee: -> georg.brandl keywords: +patch nosy: +georg.brandl __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-li

[issue1219] 3.0 library/stdtypes.rst patch

New submission from Peter Harris: Cleanup (removal of 2.x references, long etc. ). I'm not 100% sure I've got the rich-comparison stuff correct. -- components: Documentation files: stdtypes.diff messages: 56186 nosy: scav severity: normal status: open title: 3.0 library/stdtypes.rst pat